claim candidate goes to: this-edition E explorer
Your own newsroom is the public example of your product, and underneath it a CRM and a publishing workflow
The hardest part of selling behaviour policies and licences to operate is showing them in action, because customer work cannot be shared; the ecosystem around the newsroom, its agents, their behaviour policy, the status report every few answers, the leak scan before every commit, the releases with their logs, is the best public example RiskMandate has of a policy under real load every day. And a very effective newsroom is, underneath, a very effective CRM and publishing workflow: agents that follow up people and threads, draft, publish and keep a record, matured by readers in a way the product's own volumes could not yet force. Follow the users and the feedback loops, even when the user is you.
Decided by. Nobody yet: a candidate for Dinis to read, comment on and decide (keep, rewrite, merge, cut, article first, later, not doing it).
Note. RiskMandate's traction is described, not measured, in the article.
Where it comes from
- Not a straight line The newsroom is RiskMandate's workflow, and its example; Why the newsroom could solve it and RiskMandate could not (newsroom)
What it answers in the 2018 book
- Blogs answered outline, Your CV
- Publish, Publish Publish answered outline, Life Patterns
Where it goes
Chapter Publish, publish, publish: your own newsroom, part Getting the job, or making it (drafting); topic Publish, publish, publish: your own newsroom.
Other ideas proposed for the same chapter: Publish, publish, publish: your own newsroom, Write it once, link it many times; every part buys the next, The voice is not a setting: a corpus, a memo, a short list of rules, and a reader who corrects, Speak it, do not type it: a memo carries how you got there, a brief only what to write.
Node idea:your-newsroom-is-your-demo-and-your-crm in graph.json; see it in the graph. Source: admin/content/graph/ideas.json.