Per task: who Responsible, Accountable, Consulted, Informed — no duplication for first two.

R, A, C, I per task.

Place each risk on 2x2: probability × impact — treat high/high first.

When he opens sensitive topic, say "tell me more" vs reply.

For each recurring decision specify Responsible, Accountable, Consulted, Informed — leave no column empty.

Before any project starts, write a one-page charter answering six core questions.

List your top 10 risks with probability, impact, and owner; review the first Monday each month.

Turn a vague goal into a specific, measurable, time-bound formulation.

Start from delivery day and reverse-engineer what must be ready each week.

Compress any project into one page: why, what, who, when, success looks like...

For each task and person: R responsible, A accountable, C consulted, I informed.

A living table of every project risk: probability, impact, owner, action.

For each task estimate: optimistic, most-likely, pessimistic — then compute expected.

Rate each risk on a 5×5 grid — color dictates response urgency.

Per key stakeholder: what to send, when, via which channel, what to expect.

Project first meeting: explicit expectations — scope, date, quality, comms, alarms.

For every new addition request mid-project, apply one rule: it enters in exchange for something leaving, or waits for the next release.

When one person is needed for three tasks the same week, reschedule instead of stacking them beyond their capacity.

Within a week of any project delivery, gather to document what worked and what failed — before memory evaporates.

For every stakeholder, explicitly define: how often, which channel, what level of detail — no randomly-timed communication.