The Making of a Manager

1. 1Define one great outcome per meeting before scheduling it, and classify the meeting type: decision, feedback/review, idea-generating, informational, or team-bonding. Don't ask a single meeting to do more than one job.
2. 2Invite only the people necessary to reach that outcome, including representatives of any team the decision will heavily affect. Cut anyone who isn't contributing; ask to be looped into pre/post notes instead of attending.
3. 3Send an agenda ahead of time so people can prepare — the larger the meeting, the more preparation matters, because a poorly-run 500-person meeting wastes hundreds of people-hours.
4. 4During the meeting, protect the primary purpose: when a decision meeting drifts into feature suggestions, name it and steer back, offering to schedule the other topic separately.
5. 5In the last few minutes, say 'Before we break, let's make sure we agree on next steps,' and confirm ownership of each action item.
6. 6After the meeting, send a recap with a summary, specific action items and who owns each, and the next check-in date; use these follow-ups to anchor the next agenda.
7. 7Make it safe to contribute for quiet people — use structured openings (Post-it notes, Q&A, set norms) and mediate airtime so no one voice dominates.
8. 8Periodically audit your recurring meetings: cancel or revamp any that aren't valuable to anyone, and remove yourself from ones where the right outcome will happen without you.

The author ran a recurring critique meeting where each designer presented current work, briefly introduced it, then opened the floor: anyone could raise questions from the strategic ('Does the problem being solved here really matter?') to the tactical ('Should this be a grid or a list?'). The group discussed, offered new ideas, brought up similar examples to learn from, and connected the dots across different designers' projects. The presenter left with a clear list of next steps, and the process repeated for the next person. As the team hired more people, all designers kept being invited and attendance grew until the meeting became unwieldy — a sign the 'invite only who's necessary' rule was being violated. The fix is to reconsider whom the outcome actually requires rather than defaulting to inviting everyone.

• If you can't state the one great outcome for a meeting, then don't hold it — cancel or revamp it.
• If a decision heavily affects another team, then a representative of that team must be in the room, or the decision will be delayed or reescalated and re-debated.
• If you trust the right outcome will happen without you, then don't attend — ask to be added to pre/post notes instead.
• If the conversation drifts from the meeting's purpose, then name the off-topic item, offer to schedule it separately, and steer back to the agenda.
• If someone in groups over seven stays silent, then use structured contribution tools (Post-it openings, Q&A, mediating airtime) rather than assuming they have nothing to add.

• Making one meeting do too much — a decision meeting is a poor forum for generating ideas; the tell is people chiming in with new suggestions when you need a call made.
• Overcrowding the room — lackluster energy, people distracted and on their phones is the tell that too many extraneous attendees are present.
• Missing an affected stakeholder — the tell is a decision that gets delayed or re-escalated and argued again later.
• Skipping preparation and follow-up — no agenda beforehand and no recap after; the tell is that no one is sure of next steps or who owns what when the group reconvenes.
• Assuming silence means agreement or nothing to add — quiet contributors go 'ninja' in large groups; the tell is that the same few voices carry every meeting.

• ▸Great outcome: the one specific result this meeting must produce
• ▸Meeting type: decision / feedback / idea-generating / informational / bonding
• ▸Necessary attendees: who is required to reach the outcome (and affected teams)
• ▸Agenda sent by: date/time the pre-read went out
• ▸Purpose reminder: the one sentence to redirect off-topic drift
• ▸Contribution plan: how quiet people get airtime (Post-its, Q&A, norms)
• ▸Agreed next steps: action items confirmed in the final minutes
• ▸Owner per item: named person responsible for each action
• ▸Next check-in: date the group reconvenes and recap recipients

1. 1Define the outcome your team exists to produce, then measure output not activity — for a sales role, count orders (output) not calls (activity), per Grove's rule.
2. 2Judge yourself by the team's consistent results over time: a great manager's team turns a higher profit, better prepares students, or delivers concepts that wow; a bad one loses money or produces mediocre work.
3. 3Shift from additive to multiplicative contribution: stop doing the work yourself even if you're best at it, and invest hours in purpose, people, and process to raise the collective multiplier.
4. 4Double down on top talent rather than the strugglers: coaching your strongest report to a 10% gain often beats the larger percentage lift you'd need from a weak performer to match it.
5. 5Diagnose, address, and resolve weak performers' issues swiftly so they don't dominate your time, but don't let 'fixing' them consume your calendar.
6. 6Set explicit performance expectations continuously so no major disappointment ever arrives as a surprise at review time.
7. 7Run weekly 30-minute 1:1s to surface challenges early, and treat repeated 'everything is fine' as a signal to prod deeper.

In the lemonade stand, if you personally sell lemonade you add an additive amount to the business. Spending 30 hours training Henry and Eliza produces a small multiplier — an extra eight cups a day, recovering the 600 cups you didn't sell in under three months, and 2,000+ extra cups over a year. Recruiting Toby, who sells 30 cups an hour, produces a far larger multiplier: 21,000+ additional cups in a year. Now for coaching: Toby sells 30 cups/hour and Henry sells 10, so instinct says pour your time into Henry. But a 10% lift on Toby yields three extra cups, whereas you'd have to push Henry 33% better to match that — a harder feat. So team performance rises fastest when you double down on the projects and people already working rather than trying to get every underperformer to 'not failing.'

• If you're the best individual contributor but the team's output isn't multiplying, then stop doing the work and invest in purpose, people, and process.
• If a small percentage gain on a top performer beats the larger gain you'd need from a weak one, then spend your marginal hour on the top performer.
• If a weak performer is dragging outcomes, then diagnose and resolve it swiftly rather than letting it dominate your calendar.
• If a report isn't meeting expectations, then tell them explicitly now — not at the review — so the review only summarizes what they've already heard.
• If a report says 'everything is fine' for multiple weeks, then treat it as a red flag and prod further.

• Measuring activity instead of output — praising the manager who makes many calls or knocks out 20 tasks a day while the team's outcomes stay mediocre.
• Spending the majority of your time 'fixing' the struggling report; the tell is your calendar filling with the weakest performer while top talent, who never asks for help, gets ignored.
• Withholding performance feedback until the 360 cycle — the tell is your report having three bad explanations at review time (unfair, negligent, or dishonest manager), like Albert.
• Judging feedback meetings by whether the boss likes the work; the tell is polishing the presentation's smoke and mirrors instead of getting help that improves the outcome.
• Basing respect and support on a report's current results; the tell is your report going quiet when things get rocky because they sense your support is conditional on performance.

• ▸Team's stated outcome: the single result you exist to produce (why does our work matter?)
• ▸Output metric: the result you count (orders, profit, student readiness) — not activity
• ▸Current performance vs. goal: consistently achieving / mixed / falling short
• ▸Top performers + next growth move: who's winning and the small lift you'll invest in
• ▸Weak performers + resolution plan: who's struggling and the swift fix you'll apply
• ▸Multiplier actions this week: purpose/people/process moves that raise collective output
• ▸Expectation gaps flagged: who has been told explicitly where they stand this period
• ▸1:1 health check: any report answering 'everything is fine' repeatedly to prod

1. 1Split your evaluation of team health into two halves, following Chris Cox's framework: present outcomes (did the team produce valuable, well-crafted work?) and future potential (did you hire and develop well, and is the team happy and working well together?).
2. 2Treat regrettable attrition as a lagging signal. Track who leaves and why, and remember that when good people quit, they are usually quitting you, not just the company.
3. 3Build the trust that surfaces problems early: make reports believe you truly care about them so they will admit they're overwhelmed instead of saying 'I'll be fine' while burning the midnight oil.
4. 4In one-on-ones, actively probe for the dissatisfaction that festers beneath the surface — ask how people are really feeling rather than accepting reassurance at face value.
5. 5Diagnose whether people can do great work using Andy Grove's two-question filter: either they don't know how (a skills gap) or they know how but aren't motivated. Address the actual cause instead of guessing.
6. 6Invest your time as a multiplier, not just an individual producer — coach and develop individuals so the team's future output rises, even when that costs you personal short-term results.
7. 7Play the long game: resist quarters of amazing results built on high-pressure ultimatums or an inherited talented team, because time reveals whether people want to keep working for you.

When the author first started managing, she was uncomfortable admitting struggle to her own manager. If a project was going off the rails because she had too much on her plate, she'd frame it as 'I'm juggling a lot right now, but no need to worry, I'll be fine' — while her stress shot to eleven out of ten and she worked around the clock. This is the exact dynamic that erodes team health: dissatisfaction festers unseen until someone surprises you with a resignation. The fix is the trust relationship — reports stay honest only when they have no doubt you truly care about them. A manager who builds that trust catches early warning signs; one who doesn't gets blindsided and loses people who were quietly drowning.

• If a manager posts strong results but relies on ultimatums and midnight-oil burnout, then discount those results — time will reveal the truth as good people leave.
• If a report says 'I'll be fine' but shows signs of overload, then treat it as a warning, not reassurance, and dig deeper.
• If someone isn't doing great work, then determine first whether it's a skills problem or a motivation problem before intervening — the remedy differs.
• If a talented person resigns, then assume they may be quitting you and examine the relationship, not just the compensation or role.
• If you can multiply the team's future capability by coaching instead of doing the work yourself, then take that trade even at the cost of personal output.

• Judging a team only on this quarter's output and ignoring whether it's set up for the future — the tell is impressive short-term numbers alongside rising quiet dissatisfaction.
• Accepting a report's 'no need to worry' at face value — the tell is a sudden resignation that blindsides you.
• Treating attrition as normal churn rather than a signal about you — the tell is repeatedly losing your best people while assuming it's about the company.
• Assuming poor work means low motivation when it's actually a skills gap (or vice versa) — the tell is repeated interventions that don't fix the underlying problem.
• Prioritizing your own high-value individual contribution over developing others — the tell is a team whose output never grows beyond what you personally can produce.

• ▸Present outcomes: did we produce valuable, easy-to-use, well-crafted work this period? (yes/partly/no + evidence)
• ▸Future strength: am I hiring and developing individuals well? (name growth for each report)
• ▸Team satisfaction: is the team happy and working well together? (rate + what's the signal)
• ▸Regrettable attrition: who left, why, and were they quitting me?
• ▸Hidden overload: which report is likely masking stress with 'I'll be fine'?
• ▸Skills vs. motivation: for anyone underperforming, which of Grove's two causes applies?
• ▸Trust check: does each report believe I genuinely care about them?
• ▸Multiplier action: what one coaching investment raises future output this quarter?

1. 1State the purpose as the why, not the what: answer "why does our work matter?" and "what would be different about the world if your team were wildly successful?" in language the whole team can repeat.
2. 2Test whether the picture is actually shared, not just declared. Ask each person to describe the team's goal in their own words; where descriptions diverge, you have found unshared purpose to reconcile.
3. 3Rank the team's goals for the period and force the choice: "If I could only achieve one goal this half, which would it be?" Make the top priority explicit so effort concentrates on the minority of causes producing the majority of results.
4. 4Separate purpose from progress proxies. Name the metrics you track, then repeatedly connect them back to the outcome they stand for so people don't mistake the proxy for the point.
5. 5Check the team's place in its hierarchy of needs before choosing a horizon. If the organization is in survival mode, purpose collapses to "do whatever it takes to survive"; only beyond survival do you invest in longer-term vision.
6. 6Repeat and reinforce the purpose in the recurring venues you already own — one-on-ones and status meetings — so the shared picture stays current as the work evolves.
7. 7Watch for behavior that reveals a purpose gap: when someone spends energy on things you consider wasteful, treat it as evidence they hold a different picture of success, and re-align rather than just correct the task.

Zhuo's lemonade-stand example shows purpose failure in miniature. Your vision is a lemonade stand on every block, starting in your city and expanding nationally — that is the why. But your employee Henry believes the stand should be a popular neighborhood hangout. Because that picture was never made shared, Henry starts doing things you find unimportant or wasteful: buying lawn chairs, working to make the spot social. Neither of you is lazy or incompetent; you simply hold different definitions of success, so his effort flows toward the wrong outcome. The fix is not to scold Henry for the chairs but to make the expansion vision explicit and confirm he can describe it the same way you do. Once the purpose is genuinely shared, his energy reallocates on its own.

• If team members describe the goal differently when asked, then stop and re-establish the shared picture before pushing on execution.
• If your organization is on the verge of collapse, then set vision aside and act on survival — rally the troops, pitch in, extinguish the flames — because lower needs trump higher ones.
• If you are treating a metric as the goal itself, then re-anchor it: name the outcome the proxy represents and confirm the team still sees the difference.
• If you have several goals for the half, then force the single-most-important choice and pour disproportionate energy there — results count, not spread-thin effort.
• If a report is doing work you find wasteful, then read it as a purpose mismatch first and realign the why before correcting the task.

• Stating the what instead of the why. The tell: your purpose statement lists activities or outputs and no one can answer "what would be different about the world if we succeeded?"
• Assuming purpose is shared because you announced it once. The tell: mismatched expectations and conflicts surface downstream, exactly the symptoms the passages predict when purpose is missing or unclear.
• Conflating progress proxies with purpose. The tell: the team optimizes a metric while drifting from the outcome it was meant to represent.
• Spreading effort across too many goals. The tell: average effort into many things instead of superior thought into a few; nothing at the top of the list is decisively done before you move down.
• Preaching vision while the team is in survival mode. The tell: you invest in long-term picture-painting while the organization is on fire, ignoring that lower-level needs must be met first.

• ▸Why statement: one sentence on why this work matters
• ▸Success picture: what is different about the world if we're wildly successful
• ▸Team's own words: each member's description of the goal (note divergences)
• ▸Top priority this period: the one goal you'd keep if forced to choose one
• ▸Metrics vs. outcome: proxies we track and the real outcome each stands for
• ▸Hierarchy-of-needs check: survival mode or beyond? adjust horizon accordingly
• ▸Misalignment signals: current work that looks wasteful and the belief behind it
• ▸Reinforcement venue: where/when you'll restate purpose (one-on-ones, status)

1. 1Diagnose your own triggers before coaching others: ask when someone last annoyed you more than others around you, what your closest friends would name as your pet peeves, and what made you wary of someone on first meeting. Triggers you can't name will distort feedback.
2. 2Run one-on-ones as the person's meeting, not yours: come with priorities to cover but reserve time to ask questions and surface what's blocking them (family issues, health, stress) so you can provide stability, not just status.
3. 3Coach to strengths, not to gaps: identify each report's distinctive strength (StrengthsFinder-style) and structure their role so they play to it, rather than trying to remediate everyone into an average.
4. 4Give task-specific feedback frequently and tie it to clarified expectations of success, so people know concretely what is or isn't going well and what promotion or improvement requires.
5. 5Hire the anchors first: when forming or growing a team, pour energy into filling the single most critical role before the rest, and screen hard for the 'asshole' who will poison the team.
6. 6Prepare and rehearse hard conversations (saying no to a lead request, telling someone they're not meeting expectations, a firing) out loud—Zhuo practiced in front of her bathroom mirror—so you defuse rather than escalate.
7. 7Invest in the manager-report relationship deliberately: build trust through social events and one-on-ones, because when mistrust runs as an undercurrent, every decision becomes a wave that erodes the working relationship.

Zhuo describes two of her reports both asking to lead an exciting new project, forcing her to say no to one. This is the people-focus test in miniature: the decision isn't just about the project, it's about the relationship and the individual's development. She didn't wing it—she practiced the conversation in front of her bathroom mirror at home, imagining every terrible scenario, so she could deliver the disappointing news steadily rather than escalate tension. The move models coaching to strengths (choosing the lead best suited to this work) while providing the emotional stability the passages say managers must offer. Contrast this with her Pit story: with a new colleague on an important initiative, she and the other person butted heads on strategy, and an undercurrent of mistrust—'you aren't listening,' 'it's my decision, not yours'—turned minor product details into long combative emails. There, the relationship work was skipped and the working relationship became a flimsy sandcastle. The lesson: people decisions demand deliberate preparation and trust-building, not reactive emotion.

• If your first reaction to '70% of your day in meetings' is dread rather than energy, then reconsider whether a people-focused manager role suits you—the job is fundamentally spending time with others.
• If you're annoyed by something more than everyone else around you, then treat it as a personal trigger and check your feedback for distortion before delivering it.
• If you have five open roles, then pour energy into filling the single most critical one first (hire the anchor) rather than spreading average effort across all five.
• If a candidate or teammate reads as an 'asshole,' then keep them off the team regardless of talent, because they poison team conditions.
• If the conversation is emotionally charged—a firing, a 'no,' bad news—then rehearse it out loud beforehand so you provide stability instead of escalating.

• Spreading average effort across too many people and priorities instead of superior effort on the few that matter; the tell is a to-do list that's never ranked and roles filled in no order of importance.
• Letting an unnamed trigger drive your feedback so it's really about you, not them; the tell is you feel more worked up than the situation warrants and later regret overreacting.
• Coaching everyone toward the average by fixing weaknesses; the tell is you can't name any report's distinctive strength or the role built around it.
• Improvising hard conversations; the tell is escalation, defensiveness, and long combative email chains full of 'you aren't listening' and 'it's my decision.'
• Neglecting relationship and trust investment until mistrust is already the undercurrent; the tell is every minor decision feels like a giant wave crashing on a flimsy working relationship.

• ▸Report name — who this is about
• ▸Distinctive strength — the one thing they do better than most; how their role uses it
• ▸Current expectations of success — what 'meeting the bar' concretely looks like now
• ▸Most recent task-specific feedback — what went well / didn't, given by when
• ▸My trigger check — is my read of them colored by a personal pet peeve? (y/n + note)
• ▸Relationship investment — last one-on-one and last social/trust-building touch
• ▸Hard conversation pending — what I need to say, and where I'll rehearse it
• ▸Top priority for them this half — the one goal if I could pick only one

1. 1Sort your daily tasks into three buckets—purpose, people, process—so you can see which lever each meeting or decision pulls; process work is the how of getting work done smoothly and efficiently.
2. 2Before designing any process, check your team's place in the hierarchy of needs. If the organization is 'on fire,' abandon long-term process work and do whatever extinguishes the flames; only when survival is secure do you invest in refining how the team works.
3. 3Order every list you make by importance. For a status meeting, team goals, or open roles, force the question 'If I could only achieve one, which would it be?' and make sure the top item is handled before venturing down the list.
4. 4Classify each recurring meeting by its actual function—one-on-ones, reviews (feedback meetings), status meetings, mediating meetings, or Q&A—and run each to its purpose rather than blending them into an undifferentiated block.
5. 5In mediating and one-on-one meetings, lead with questions rather than pronouncements; questions surface the real disagreement (as in the product-strategy conflict) instead of hardening 'it's my decision, not yours' positions.
6. 6Build shared vision explicitly so everyone holds a similar picture of why the work matters; when purpose is unclear, people default to divergent assumptions and generate work you consider wasteful.
7. 7Establish a retrospective/postmortem rhythm so process itself evolves—treat how you work as something to refine after each cycle, not a fixed ritual.
8. 8Balance short-term outcomes against long-term investments deliberately, and watch for conflating progress proxies with the actual purpose.

Zhuo describes the lemonade-stand vision conflict as a process-and-purpose failure. Her stated vision is to get a lemonade stand on every block, first in the city then nationally. But her employee Henry believes the stand should be a popular neighborhood hangout, so he starts buying lawn chairs and trying to serve pizza—things she considers unimportant and wasteful. The breakdown isn't Henry being lazy; it's that the two of them never established a shared picture of why the work matters. The process fix is to make purpose explicit so everyone holds the same 'why,' which then makes decisions and prioritization coherent. Without that alignment, you get exactly the conflicts and mismatched expectations she warns about. The tell that process is broken here is effort pointed in contradictory directions.

• If your organization is on the verge of collapse, then set aside long-term process design and do whatever it takes to survive; if you're beyond survival mode, then invest in the higher-level process work.
• If a list has more than one item, then rank by importance and complete number one before number two—because effort doesn't count, results do.
• If two people keep escalating with 'you aren't listening' or 'it's my decision,' then move from asserting to asking questions in a mediating conversation.
• If team members are producing work you find wasteful, then the failure is likely an unclear or missing shared purpose, not individual judgment—fix the vision first.
• If you spend a little today expecting bountiful rewards later, then confirm the organization isn't on fire first; that longer-time-frame logic only holds when survival isn't at stake.

• Treating the manager's job as a list of activities (have meetings, give feedback) rather than the outcome those activities produce; the tell is you can list what you do but not why it matters or whether the team is winning.
• Putting average effort into too many things instead of superior effort into a few; the tell is a long to-do list with nothing ranked and top priorities unfinished at day's end.
• Refining process and planning ahead while the organization is actually in survival mode; the tell is elaborate long-term plans while the immediate 'fire' spreads unchecked.
• Letting meetings run as undifferentiated time blocks instead of matching format to function; the tell is a 'status' meeting that never surfaces the decision or feedback it needed to.
• Skipping shared-vision work so team members act on divergent assumptions; the tell is people doing things you consider unimportant or wasteful (the lawn chairs and pizza) while believing they're helping.
• Fixing process as a permanent ritual with no retrospective; the tell is the same coordination problems recurring cycle after cycle with no evolution.

• ▸Survival check: Is the organization on fire right now? (yes = drop process work and stabilize)
• ▸Team purpose in one line: why does our work matter, stated so everyone shares the picture
• ▸Top priority this half: 'If I could only achieve one goal, which?'
• ▸Meeting inventory: list each recurring meeting and its single function (one-on-one / review / status / mediating / Q&A)
• ▸Prioritized to-do: rank today's tasks by importance; confirm #1 done before #2
• ▸Purpose-drift scan: any work happening that seems wasteful? (flag as vision-misalignment)
• ▸Short vs. long term: one long-term investment you're protecting from short-term pressure
• ▸Retrospective date: when will you run the next postmortem to evolve this process
• ▸Decision protocol: who decides what, so 'it's my decision, not yours' never gets litigated live

1. 1Attribute failures to process, not people: in retrospectives say "our process failed" instead of "Leslie made a mistake" — this sets the tone that talking about errors is safe.
2. 2Model vulnerability first, before asking it of your team. As Brené Brown notes, "Vulnerability sounds like truth." Admit your own mistakes and knowledge gaps openly (the manager who let peers answer her "n00b-ish" questions) so reports see candor is rewarded, not punished.
3. 3Recognize that the manager title strips away transparency automatically — reports "were wary of bothering me or coming across poorly" — so actively work harder to rebuild the trusting relationships you had as a peer.
4. 4Run one-on-ones that deliberately create room for hard truths. Expect them to "feel a little awkward"; the awkwardness is the signal that real interpersonal risk is being taken.
5. 5After each retrospective, write down the learnings and share them widely so mistakes make the whole organization stronger, converting individual error into collective, blame-free knowledge.
6. 6Reject the asshole standard: per Sutton, an asshole leaves people feeling belittled and de-energized. Screen it out of yourself and the team, because a single person who makes others feel demeaned kills the safety to take risks.
7. 7Deliver candid feedback without cruelty — Welch's warning is that withholding truth is "false kindness." Distinguish honesty in the person's interest from brutality that shreds trust.
8. 8Test whether your decisions actually carry the team by watching for buy-in, not compliance. If work "trudges along, lacking heart and soul," people don't feel safe to tell you they disagree.

The author had a product idea arrive "fully formed" while driving home — the pitch, the design, why people would love it. She sketched it, called a team meeting, and asked the designers to build out her sketch. When she checked in days later, progress was slow: people interpreted the sketch differently and lost hours in circular debate. She assumed she'd explained it poorly and clarified; another week passed with no better results. The real root cause was that none of the designers believed the idea would succeed — and they didn't feel able to say so directly. The absence of psychological safety showed up not as open dissent but as stalled, heartless work. The lesson: a team that can't safely voice "I don't think this will work" pays you in slow, soulless output instead of honest objection.

• If a mistake is discussed, then frame it around the process ("our process failed") rather than the individual, so blame doesn't chill future disclosure.
• If a report suddenly shares less or goes quiet after you became manager, then treat it as the normal title effect and invest more in the relationship — not as a sign they have nothing to report.
• If you're withholding hard feedback to be kind, then recognize that as Welch's "false kindness" and deliver the truth, because silence damages trust more than candor does.
• If work is progressing slowly and debate keeps circling, then check whether the team is actually sold on the direction and privately dissenting rather than assuming your instructions were unclear.
• If someone consistently leaves colleagues feeling belittled or de-energized, then act on it directly (Sutton's No Asshole Rule), because one such person destroys everyone's willingness to take interpersonal risks.

• Naming individuals in postmortems ("Leslie made a mistake") — the tell is people going silent or defensive when errors come up, so future mistakes get hidden.
• Assuming your title makes you a trusted leader. The tell: reports stop venting near you, go sheepish when you walk in, and stop telling you when they're struggling. Leadership "must be earned; people must want to follow you."
• Mistaking compliance for buy-in. The tell is work that "trudges along, lacking heart and soul" and circular debate — dissent you never heard because people didn't feel safe voicing it.
• Confusing brutal honesty with candor, or confusing false kindness with care. The tell: either people feel demeaned (asshole behavior) or you're avoiding hard conversations entirely.
• Keeping learnings private after a retrospective. The tell: the same mistakes recur across teams because the safe-to-discuss error never became shared, repeatable knowledge.

• ▸What happened (process framing): describe the event as a process outcome, no names.
• ▸Root cause: state the systemic gap, not the person.
• ▸Where did the process fail: identify the specific step or handoff.
• ▸Learnings to codify: what repeatable playbook or checklist this becomes.
• ▸Share-with list: who outside the team should get these learnings.
• ▸Silent-dissent check: was anyone unconvinced but didn't say so? How do you know?
• ▸Candor audit: what hard truth am I currently withholding as "false kindness"?
• ▸Trust action: one concrete step to strengthen a report relationship this week.
• ▸Awkward but honest: the uncomfortable topic to raise in the next one-on-one.

1. 1State the purpose in one sentence answering "why does our work matter?" — specific ("make every customer who calls feel cared for") or broad ("bring the world closer together") — and confirm you personally understand and believe it before asking anyone else to.
2. 2Share that purpose at every opportunity, not once: writing emails, setting goals, one-on-ones with a single report, and large-scale meetings. Repetition is the mechanism of alignment.
3. 3Surface hidden pictures of success. Ask each person to describe what they think the team is trying to accomplish; compare answers to yours and name the gaps (the "Henry buys lawn chairs" problem) before they produce wasted work.
4. 4Diagnose whether the person's own values match what the team cares about. Ask what they find motivating; if the fit is off, test a move to a different problem within the org before concluding parting ways is best.
5. 5Check the motivation layer against Maslow: if the organization is on fire, alignment on long-term vision is moot — stabilize survival needs first, then return to purpose.
6. 6Verify each person is set up to do great work: right skills, right environment, and motivation to do it — the "people" bucket. Missing any one produces problems even with a clear purpose.
7. 7Don't demand belief. You cannot order someone to care about the vision; if they think it's stupid they'll disengage or leave for a venture they care about. Make the case, then accept genuine mismatch.

Zhuo promoted her most talented, experienced designer to manager because everyone naturally went to her for advice — Zhuo assumed "obviously she should be a manager" and patted herself on the back for increasing that person's impact. A year later the designer quit. She admitted that every morning in bed she dreaded going to work managing people; her curious spark had become glassy-eyed exhaustion. The misalignment was invisible to Zhuo because the role looked like a reward, but the designer was at her core a maker who wanted long uninterrupted time to go deep and build something tangible. The individual work (managing) never matched what actually motivated her, so no amount of skill compensated. The lesson Zhuo drew: when someone says they want a role, understand what they find appealing and whether it matches the actual day-to-day — motivation must fit the real work, not the imagined one.

• If a team member starts doing things you consider wasteful or unimportant, then their picture of success differs from yours — realign the purpose before correcting the behavior.
• If someone is motivated to play a specific craft role rather than achieve outcomes through others, then don't move them into management no matter how skilled they are.
• If a person's values and working style clash with a teammate's, then separate them onto different projects; both will be happier and more productive.
• If the fit is off, then try a move within the same organization first (new environment, different problem); only if that fails treat parting ways as the best outcome for everyone.
• If the organization is on the verge of collapse, then set purpose-alignment work aside and address survival needs first — long-term investment only pays when you aren't on fire.

• Assuming skill and being sought-for-advice equals fit for a role — the tell is glassy-eyed exhaustion and dread, not enthusiasm, weeks after the change.
• Sharing the purpose once and assuming it stuck — the tell is teammates confidently pursuing goals you never set (lawn chairs, pizza with the lemonade).
• Demanding belief in the vision instead of earning it — the tell is quiet disengagement or a departure to a venture they care more about.
• Taking every departure as personal failure — the tell is treating misalignment as your mistake rather than a values/fit mismatch that a move might have solved.
• Working on long-term alignment while the org is actually in survival mode — the tell is planning months ahead while the immediate crisis (debt, collapse) goes unaddressed.

• ▸Team purpose (one sentence): why does our work matter?
• ▸Do I personally believe it? Yes/No — if No, resolve before proceeding
• ▸Each member's stated version of success: capture in their words
• ▸Gaps vs. my version: where do pictures diverge?
• ▸What this person finds motivating: outcomes-through-others, or a specific craft role?
• ▸Does their day-to-day match that motivation? Yes/No
• ▸Values/working-style clashes with teammates: who and where
• ▸Fit action: reinforce / move to new problem / move within org / part ways