Communicating async + running 1:1s

• QuestionWhat is "Async vs sync — when to use which"?Tap to revealAnswerAsync by default; sync for the human moments.
• QuestionIn "Async vs sync — when to use which", explain:Tap to revealAnswerAsync-default for status, plans, decisions with > 3 readers.
• QuestionIn "Async vs sync — when to use which", explain:Tap to revealAnswerSync-default for feedback, conflict, recognition, ambiguous topics.
• QuestionIn "Async vs sync — when to use which", explain:Tap to revealAnswerWrite async first; promote to sync when you can't finish the message.
• QuestionWhat is "Writing a status update that doesn't need a meeting"?Tap to revealAnswerA useful status update has three parts in order: what shipped (outcome, not activity), what's blocked (specific blocker + who you need help from), one thing you're doing differently next week (continuous improvement)
• QuestionIn "Writing a status update that doesn't need a meeting", explain:Tap to revealAnswerThree sentences: shipped (outcome), blocked (specific + who), one improvement.
• QuestionIn "Writing a status update that doesn't need a meeting", explain:Tap to revealAnswerOutcomes beat activities. 'Shipped login fix' beats 'worked on auth'.
• QuestionIn "Writing a status update that doesn't need a meeting", explain:Tap to revealAnswerSpecific help-asks unblock; vague ones invite another meeting.
• QuestionWhat is "Running a productive 1:1 — IC + manager view"?Tap to revealAnswerA 1:1 is not a status meeting (your written update covers that)
• QuestionIn "Running a productive 1:1 — IC + manager view", explain:Tap to revealAnswer1:1 ≠ status meeting. Agenda owned by the IC.
• QuestionIn "Running a productive 1:1 — IC + manager view", explain:Tap to revealAnswerManager doesn't cancel; signal cost is too high.
• QuestionIn "Running a productive 1:1 — IC + manager view", explain:Tap to revealAnswerEnd with named owners + dates, not 'we should look into that'.
• QuestionWhat is "Giving feedback that lands"?Tap to revealAnswerFeedback that lands is specific, timely, and tied to an observable behaviour, not an inferred trait
• QuestionIn "Giving feedback that lands", explain:Tap to revealAnswerSpecific + observable + timely. Trait labels are not feedback.
• QuestionIn "Giving feedback that lands", explain:Tap to revealAnswerSBI: Situation, Behaviour, Impact. No compliment sandwich.
• QuestionIn "Giving feedback that lands", explain:Tap to revealAnswerAsk for feedback up the chain every 1:1; safety is built by repetition.

1. 1List the core idea

   Analyse~10 min

   In your own words, list the central idea of "Async vs sync — when to use which". Aim for one paragraph, no jargon you haven't earned.

   Done when: A non-expert could read your paragraph and explain it back to you.

   Re-read the source concept

2. 2Solve it to a real situation

   Apply~15 min

   Find a real situation from your own work / life where "Giving feedback that lands" applies. Solve the idea — describe the situation, the move you'd make, and the alternative you considered first.

   Done when: You can name a specific situation (not a hypothetical), state your move, and explain the trade-off in one paragraph.

   Re-read the source concept

3. 3Teach it back

   Evaluate~5 min

   Pick someone (a colleague, a peer, a rubber duck) and explain the section to them in under 5 minutes. Use your own example, not the one from the lesson.

   Done when: Your listener can repeat the core idea + the trade-off back to you without prompting.

Why this matters. Reading + quizzing prove recall; applying it in a real situation is the only evidence of transfer. Treat at least one of these as non-negotiable before you move on.