Read your client's news before your client does
A workflow for people who advise: what a story means for the client, whether it is a problem, and whether it is a reason to call.
The problem
Advisers are judged on noticing first. But a story about a client is only worth a phone call some of the time, and the ones that are worth it do not announce themselves in the headline.
The workflow
-
1
First the downside: is this something the client is about to be asked about, and by whom.
-
2
Then the other reading — a change in their situation is frequently a reason to talk, not only a risk.
-
3
And what you would actually do about it today, which is what decides whether you pick up the phone.
What you put in
News about a client, their sector, their regulator or their largest customer.
What you get back
The last step answers under these headings. They are read from What Should I Do Next? itself, so this list changes when the template does — it is not a transcript of a run.
- What options are presented?
- What are the pros and cons of each?
- Which factors should I prioritize?
- What next steps should I consider?
Setting it up
- Open the workflow builder and start a new workflow.
- Add the three templates above as steps, in that order.
- Keep a separate profile per client if you advise more than one — the profile switcher on the account page exists for exactly this, and the library remembers which profile produced which result.
- Save it, and run it from the Chrome extension as you read.
If it does not work
Every story reads as urgent.
The first step is looking for downside, which is its job. The third step is the one that decides whether it is worth acting on — read that one first, and the first step as its evidence.
It mixes up my clients.
One profile is one context. Running everything under a single profile blends them; a profile per client keeps each reading inside its own situation.