Lead with conclusion first, then supporting arguments, then details — never the reverse.

Start with conclusion, then 3 arguments, then details per argument — top-down.

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

Every work email starts with one sentence: "what I need from you" or "the bottom line".

One document answering every "how do we work here?" question for new hires.

Each significant decision: a text file with context, options, choice, consequences.

Each SOP: one-line title, 7-step checklist, then reference details.

Each policy: title, scope, 5 rules, exceptions, review date — one page only.

One page answering "where do I find X?" for 80% of team questions.

Each major decision: context, options, decision, consequences — one page, sequential.

List "things only X knows" — each is risk if they leave.

Track last 100 support tickets — top 20 repeats = your FAQ page.

New hire week 1: one page with everything they need — not "ask so-and-so".

Conclusion first, 3 arguments, evidence per argument. Leaders speak from top, not foundation.

In few-shot, deliberate variety (positive/negative/edge case) matters more than count.

First line of email: answer/request/decision. Context after. Cuts read time 70%.