Draft the proposed operating model to confirm with the principal
Reasons from engagement scope to a concrete proposed operating model — cadence, format, async channel, escalation path, and reporting — phrased as a short proposal the principal can react to.
In / outEngagement scope → proposed operating model (meeting cadence, async channel, escalation path, reporting)
You might say…
“We'd never explicitly agreed how we'd work. Six weeks in I still wasn't sure if my weekly note was being read or just filed.”
What it does
Reasons from the engagement scope to a concrete proposed operating model — standing meeting frequency and format, async channel, escalation path for urgent issues, and reporting/copy-in list — phrased as a short proposal the principal can react to. Used to seed the alignment conversation rather than starting it blank.
Trigger: Use to seed the cadence-alignment conversation with a concrete proposal rather than starting it blank — so the conversation is a reaction, not a construction.
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