Strategy and influence
Communication & Influence
5 lessons · ~29 min total
Lead with the bottom line
~5 minStructure a message so a busy reader gets the point and knows what you need from them, in the first sentence.
- Open with the conclusion and the ask; the reasoning defends the headline, it doesn't build up to it.
- If the reader stops after your first sentence, they should still have the thing that mattered.
- An escalation without an explicit ask and deadline reads as an FYI and gets triaged like one.
Match the altitude to the audience
~6 minAdjust the abstraction level of the same message so an executive, a peer manager, and the person doing the work each get what they actually need.
- Pitch the message to the decision the listener actually owns: scope and risk for execs, coordination for peers, constraints for builders.
- Being clear at the wrong altitude still fails, and it's easy to blame the audience for it.
- 'Leadership wants it' is not a constraint; give the builder the real tradeoff so they can reuse the judgment.
Getting a peer team to move
~6 minGet another team or a skeptical peer to move your way when you have no power to make them.
- Frame the ask around the other party's goals; people commit to outcomes that advance something they already care about.
- Pre-wire decisions one-on-one before the meeting; the meeting ratifies alignment, it rarely creates it.
- Escalation before influence spends capital and breeds resentment; reserve authority for genuine deadlock.
Disagree, then commit
~6 minVoice strong dissent in a way that improves the decision, and back a choice you argued against without going silent or subverting it.
- Argue hard while the decision is open; once it's made, commit out loud so your team isn't reading your silence.
- Deadlocks over positions ('Kafka vs SQS') dissolve when you name the interest underneath ('I need replay and no data loss').
- Side-channel dissent after a decision is settled is sabotage, not honesty; reopen it in the open or let it go.
Writing that gets read
~6 minStructure documents so a busy reader gets the point in a minute: conclusion first, detail on demand.
- Readers arrive asking what you want from them: conclusion and ask in the first paragraph, journey below.
- Headings carry findings, not topics, so a scanner reconstructs the argument in thirty seconds.
- Number the open questions and give silence a deadline.
A sample from the Delivering Feedback track. The real checks unlock with an account.
In a 1:1, you tell a report their demo ran long and rambled. They say: "Everyone goes over sometimes." What is your best next move?
Start Communication & Influence.
Your first lesson takes five minutes, and you can do it right now without an account.