Explore a topic
Communication and feedback
Make clear requests, give useful feedback and handle difficult conversations.
Start with a practical guide
Clarify an unclear work task
Turn a vague request into a result someone can check. Separate facts, assumptions and open questions, then choose a question or test that could change your next step.
Read the story LongreadPrepare to give feedback
Give difficult feedback about a missed handoff. Explain what happened, hear your colleague's side and agree on one change you can check.
Read the story LongreadBook summaries or a method for the task?
Choose a summary to learn from a book. Use a method only when a real task still needs a clearer next step or check.
Read the storyStart with a collection
Compare all collections on this topic
Write asynchronous messages that can be acted on without a meeting
Structure email, chat, tickets and handoffs around action, ownership, evidence, uncertainty and final state so readers can route, decide and execute without reconstructing the author's mental model.
Turn feedback into one behavior that can actually change
Design, give, receive and follow up on performance feedback as an evidence-to-behavior loop: observable events, proportionate impact, one next action, barriers, rehearsal and short-cycle verification.
Close the communication loop when ambiguity can become an error
Adapt safety-critical communication tools into concise handoffs, explicit ownership, escalation and plan updates that knowledge-work teams can actually use.
Build connection from small repeatable interactions, not only big social plans
Use recent 2025–2026 social-connection research to improve listening, signal openness, maintain new ties and design lightweight recurring contact without turning ordinary loneliness or friendship into a clinical protocol.
Handle a work conflict as a problem to resolve, not a verdict to win
Prepare difficult conversations around facts, impact, desired change, two-way understanding, explicit agreements, follow-up and safe escalation when informal repair is not appropriate.
Lead without formal authority: stakeholder decisions, delegation, voice, and team learning
Build lead-level behavior for cross-functional work by making decision ownership explicit, influencing with evidence, delegating bounded authority, surfacing bad news safely, and turning team experience into changed performance.
Make meetings answer a goal instead of merely occupying a slot
Use recent 2025–2026 workplace-meeting research to prepare for success, notice goal drift, preserve flow and measure whether reflection actually changes outcomes.
Train spoken communication as observable behavior
Fill the practice gap between knowing communication principles and improving actual spoken performance. The pack focuses on diagnosis, deliberate practice, recording-based review, interactive speaking and evidence-aware use of delivery metrics. Existing cards on pauses, vocal variation, presentation realism, listening, feedback, negotiation and spontaneous language samples are reused rather than rewritten.
130 ideas
State what the reader must do before giving the history
The action is part of the message, not a conclusion the reader should infer.
Read the idea TemplateMake the subject line carry state and ask
The subject line is the first routing layer.
Read the idea HeuristicLabel the message mode: decision, action, blocker or FYI
Different message modes deserve different reader behavior.
Read the idea ProtocolPut owner, output and deadline on the same line
An action is not complete until someone can point to who delivers what by when.
Read the idea PrincipleSplit a message when it asks for unrelated decisions
Bundling saves sending effort but increases routing ambiguity.
Read the idea TemplateWrite known, unknown and assumed as different states
Uncertainty becomes dangerous when formatting erases it.
Read the idea PrincipleAttach the source next to the claim it supports
A source is most useful where the reader needs to verify the statement.
Read the idea ProtocolName files for identity and state, not for your desktop history
A file name should help the receiver choose the right artifact without opening every version.
Read the idea ProtocolShow the delta when a requirement changes
Change communication should reveal the change.
Read the idea PrinciplePut the caveat beside the decision it can change
A caveat is useful only before the reader commits to the wrong interpretation.
Read the idea ProtocolPreserve the sequence when chronology explains the failure
Some problems are state machines disguised as email threads.
Read the idea ProtocolReset a long thread with a current-state block
Reply history is storage, not a current brief.
Read the idea HeuristicUse a table only when the rows answer the same question
Tables clarify comparison; they can hide narrative dependencies.
Read the idea PrincipleGive technical terms one local definition
Shared words can hide unshared models.
Read the idea ProtocolEscalate asynchronously with impact, clock and failed path
Urgency needs operational evidence.
Read the idea ProtocolClose the thread with the final state and source of truth
Closure is a state transition worth writing down.
Read the idea ConceptChoose the conflict route before choosing the words
The safest conversation can start with a routing decision.
Read the idea TemplatePrepare the facts, impact and desired change before the meeting
Prepare what happened and what should change before rehearsing the argument.
Read the idea ProtocolLet the other account exist before you rebut it
Understanding an account is not the same as accepting it.
Read the idea ConceptSplit the conflict into shared facts, disputed facts and interpretations
A conflict gets smaller when different kinds of disagreement stop pretending to be one thing.
Read the idea QuestionAsk for the future condition both sides could live with
Past accountability and future coordination are different questions.
Read the idea ProtocolTurn a verbal resolution into person, action and date
A vague truce is easy to remember differently.
Read the idea ConceptUse mediation when the relationship needs a neutral process, not another referee
A mediator owns the process, not the verdict.
Read the idea HeuristicName the unresolved point instead of forcing agreement
A precise unresolved point is better than a fake consensus.
Read the ideaExplore another topic
Negotiation and conflict
Prepare alternatives, compare possible agreements and work through disagreements.
82 ideasCareer and assessment
Prepare for assessments, build skills for your next role and show your progress with examples of your work.
96 ideasProject delivery
Estimate the work, agree on what counts as finished and check risky changes before you make them.
96 ideas