Working-cadence designer
Proposes a concrete operating rhythm — session frequency and format, async channels, response-time norms, and context-feed mechanics — fitted to the chosen model and the client's working style.
In / outEngagement model + client working style + scope → cadence proposal: sessions, format, channels, async norms, context feed
You might say…
“The cadence isn't the diary invite — it's the architecture of how I'll actually stay informed enough to be useful between sessions.”
What it does
Proposes a concrete operating rhythm — session frequency and format, channels, async response-time norms, and context-feed mechanics (board packs, data access, intros) — fitted to the chosen model and the client's working style. Used to convert an agreed model and scope into a runnable interaction plan.
Trigger: Use to convert an agreed model and scope into a runnable interaction plan before the engagement kicks off.
Recognise the problem?
The primitives are the commodity part. The fastest next step is a conversation about composing them into something that works for you.
Start a conversation