Messages you can
put your name on

Curate your personal voice rules, adapt one decision for your team and senior sponsor without changing the promise, and rehearse under pressure.

Marcus cases

Voice skill curation (Lectures 4.1–4.2)

01 / 04

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

Agent-proposed rule	Quoted sample evidence	Marcus’s curation action	Saved rule in personal-voice
1. State decision and reason in the opening lines	Samples 1 & 2 openings + spoken note	KEEP	Open updates with the confirmed decision and practical reason before listing next steps.
2. Never exceed 12 words per sentence	“We paused external file exports on staging.” “Use the internal test bucket today, effective immediately until audit closure.” (all under 12 words)	CHANGE (Too rigid; risks cutting needed reasons)	Prefer clear, concise sentences without removing the reason behind a request or condition.
3. Close with “effective immediately until audit closure”	Sample 3 compliance note	REMOVE (One-off incident phrase from 2 months ago)	Excluded so isolated incident phrases and past dates never enter the reusable skill.

Team & sponsor drafts (Lecture 4.3)

02 / 04

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.

Draft to the 8-person team

Tuesday planning meeting: 30-minute focus on blockers

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

Draft to the senior sponsor

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

Spoken recommendation rehearsal (Lecture 4.4)

03 / 04

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.

Challenge question: “After 3 weeks, how will you know whether the meeting runs over less than it does now?”

First spoken attempt (Gap exposed): Explained how frustrating the long status round has become for the team, but never said how he will measure the change.

What he finds: The meeting has been running past its 30 minutes, but he has never counted by how much, so he has no starting number.

Revised spoken answer: “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.”

Where a broadcast message ends (Lecture 4.5)

04 / 04

When a senior analyst replies that posting status updates before 9 a.m. on Tuesdays conflicts with an early client support call in another time zone, another polished paragraph is not the answer—opening a two-way conversation in Section 5 comes next.