Module 1 · Structure

Two real-shaped examples

The same problem, escalated badly and then well.

Reading ~6 minLesson 2 of 5

DOI-native

Version A — produces a meeting

"Hi, quick one — the reporting thing is still not working and I'm a bit stuck on what to do. The client's side seems flaky and I've chased a few times. Can we talk about it when you have a moment?"

There is no impact, no deadline and no decision. The reader's cheapest response is a meeting invite.

Version B — produces a decision

"Feed failing since Tue 14:00. Monday's report is blocked; two teams lose their weekly view. I need one of: (a) approve ~4h manual export this week, or (b) accept a one-week gap and note it to the client. Already re-ran the sync, confirmed credentials, ticket with their IT open 36h with no reply. Default if I hear nothing by 16:00 today: I do the manual export."

The stated default

A default is what makes an escalation safe to ignore. It tells the reader what happens on silence, so a slow reply is not a blocked week.

Key takeaways

Ask for a choice, not a conversation
State a default so silence is not a blocker
Keep it short enough to read on a phone

Preview · Sample data — Demo course content authored by DOI for this prototype. Signed in, progress is saved to your DOI account; otherwise it stays on this device. Finishing lessons records learning; it does not prove competence — that comes from reviewed practical evidence and DOI assessment. DOI claims no accreditation for this course.