Marcus's Messages, a Prepared Example

Prepared fictional example. Marcus, his 8-person team, the senior analyst and the senior sponsor are invented for this course. The voice rules, drafts and rehearsal are authored teaching material, not output from an observed agent run. No message has been sent.

This is the text of the communication page shown in Section 4. The same page, with its four tabs, is in the starter zip as practice/leadership-communication.html.

Marcus supplies 3 permitted past updates and a spoken explanation, then curates the agent’s proposed rules before saving personal-voice.

The quoted evidence is what lets Marcus spot rule 3 at once: the phrase came from one unusual compliance note, not from how he writes.

Two audience drafts built from the same confirmed Tuesday planning-meeting decision. Marcus checks each against the decision record. He changes one line in the sponsor draft, from “will keep delivery on schedule” to “should help us catch blockers earlier, and I will check after 3 weeks whether the meeting still runs over.” The team draft needs no change.

Subject: Tuesday planning meeting: 30-minute focus on blockers starting next week

Starting next Tuesday, we are moving routine status updates into the project folder so our 30-minute planning meeting can focus on decisions and blockers.

Please post your brief status update in the project folder before 9 a.m. each Tuesday. In the meeting, we will focus on what is stuck and assign one follow-up owner to each unresolved blocker. If you are stuck on something, bring it on Tuesday, even if you do not have a fix yet.

We will test this routine for 3 weeks and check together whether it reduces meeting spillover.

Thanks,
Marcus

Subject: Department planning cadence: 3-week trial to protect blocker resolution

From next Tuesday, routine status updates move into the project folder, so our 30-minute meeting can focus on decisions and blockers.

Every unresolved blocker raised in the meeting will have a single named owner so accountability stays clear. We will run this format as a 3-week trial before deciding whether to make it permanent. It should help us catch blockers earlier, and I will check after 3 weeks whether the meeting still runs over.

Best,
Marcus

Marcus rehearses presenting the 3-week Tuesday trial aloud to the senior sponsor in the weekly delivery review. The agent drafts 3 plausible questions from his decision record: why now, what the team gains, and how he will know it worked.

The Tuesday meeting has been running past its 30 minutes. The new format is meant to bring it back inside 30 minutes. I do not yet have the starting number, so before this review I will check how long each of the last 4 Tuesday meetings actually ran. After 3 weeks, I will compare the new meetings against that number.

The questions are plausible challenges drawn from the supplied material, not a prediction of what the sponsor will say.

After the team announcement goes out, a senior analyst replies that posting status updates before 9 a.m. on Tuesdays will be difficult, because she leads an early support call with a client in another time zone.

Another polished paragraph repeating the 9 a.m. rule is not the answer. A broadcast message can explain the decision and invite a response, but it cannot solve an obstacle that has not yet been heard out. Opening a two-way conversation is the subject of Section 5.

Prepared course illustration for Section 4. All drafts remain unsent teaching examples.