Nine Lies About Work Buckingham

1. 1Separate each team member's traits into two buckets: mass (loves, aspirations, unchangeable-feeling identity they carry situation to situation) and velocity (current and past performance record, tested certifications, skills — the how, how well, how fast, and in what direction they've moved).
2. 2Combine the two into momentum for this person and state it back to them as a present-tense reading: how much they have right now, how fast, and pointed which way — not a permanent label.
3. 3Drop the hi-po/lo-po sorting entirely; replace the question 'do you have potential?' with 'how are you moving, and where can you go next?'
4. 4Make the trajectory actionable by naming three options: accelerate along the current path, shift the path slightly, or attempt a great leap — and confirm which the person wants.
5. 5Have them identify which parts of their current career come from who they are (portable) versus which are situation-dependent (changeable if they choose), to guard against an ill-advised move.
6. 6Run it as an ongoing conversation, not a one-sided evaluation — revisit momentum periodically since it is by definition always changing and within their control.
7. 7Use Andy's method to make aspirations concrete: pair people, have them search LinkedIn for their dream roles across any company or industry, extract required skills/experiences/qualifications, and compare against what they already hold to name the gaps to pursue.

Andy, a team leader at Cisco, wanted each person to see what their future could look like without rating anyone's potential. He started with mass: he asked them to imagine and reflect on their dream jobs — their aspirations. Then he made it practical by pairing them up and giving them two hours on LinkedIn to find real jobs closest to their ideal, with no limit on company, industry, or line of work. Each pair narrowed the list to the one or two roles that excited them most. Then they analyzed those roles for the skills, experiences, and qualifications required — and compared that against the skills, experiences, and qualifications each person already had (their velocity). The gap between the two became the list of new skills each chose to go after. He wasn't sorting people into hi-po and lo-po; he was reading momentum and helping them decide where to point it.

• If a trait is something the person carries everywhere and feels resistant to change, then file it as mass; if it describes how they've performed or what they've certified, then file it as velocity.
• If you catch yourself asking whether someone 'has potential,' then stop — everyone has momentum; ask instead how much they have right now and in what direction.
• If the person is drawn to a move, then first separate portable (who-they-are) parts from situation-dependent parts before endorsing it, because closeness to our own performance breeds misguided desires.
• If a survey shows people don't feel 'always challenged to grow,' then treat it as a momentum-conversation gap, not a potential-rating gap.
• If you're tempted to buy enterprise software as a fallback for absent career talks, then invest in the team leader instead — no large-scale system replicates specific attention.

• Treating potential as an abstract, essential quality you can isolate and rate — the tell: you're asking 'do you or don't you have it?' instead of 'how, how efficiently, and in what direction?'
• Collapsing mass and velocity into one score — the tell: you can't say which parts of the person are portable and which are situation-dependent.
• Delivering a one-sided verdict and considering the person 'dealt with' — the tell: there's no obvious next career conversation, and the person has been shunted into a lo-po dungeon.
• Reading momentum as a fixed point of stasis rather than a changeable state — the tell: you speak about where they are as a category to catalog rather than a launch point for accelerate/shift/leap.
• Institutionalizing potential ratings in your people processes for the sake of predictability — the tell: you've sacrificed common sense and humanity to corporate uniformity.

• ▸Name: whose momentum you're reading
• ▸Mass — loves & aspirations: the enduring desires this person carries everywhere
• ▸Velocity — performance record: current and past record of what they've accomplished and how well
• ▸Velocity — tested certifications & skills: what they've formally proven and can do
• ▸Current trajectory reading: how fast and in what direction they're moving right now
• ▸Dream role (LinkedIn scan): the one or two real roles that most excite them, any company/industry
• ▸Skill/experience gaps: what the dream role requires minus what they already have
• ▸Portable vs. situational: which current career elements are who-they-are vs. situation-dependent
• ▸Next move: accelerate / shift path / great leap — and the first step they'll own

1. 1Set up a two-column sheet labeled 'Loved It' and 'Loathed It', then work a normal week with it open beside you.
2. 2Watch for three emotional signals: positive anticipation before an activity, flow during it (time disappears), and fulfillment after it (you want to do it again)—when all three fire, write the specific activity in the 'Loved It' column.
3. 3Watch for the inverse signals: procrastination or handing the task off as 'developmental', time dragging (ten minutes feels like an hour), and dread of repeating it—write that specific activity in the 'Loathed It' column.
4. 4Ignore the many activities that trigger neither reaction; only capture the ones with a distinct emotional valence, since most of your week won't make either list.
5. 5Name the captured red threads precisely at the activity level—not 'analysis' but 'finding patterns in data'—so they're concrete enough to recreate.
6. 6Next week, deliberately recreate, refine, and add to those red threads, weaving them through the fabric of the role rather than clustering them.
7. 7Aim for roughly 20 percent of your time on red-thread activities; treat that as a threshold to cross, not a ceiling to exceed, because past it there's no added reduction in burnout risk.

Miles the anesthetist finds his red thread in keeping a patient hovering between life and death—that activity produces anticipation, flow, and fulfillment for him. Helping patients recover, by contrast, weakens him even though he is good at it, so it sits in his 'Loathed It' column despite competent performance. His team leader can legitimately judge his performance—'you're not explaining the patterns well enough' or 'you're not doing this properly'—but cannot tell Miles that his red thread isn't a red thread, because he is the sole judge of what strengthens him. Crucially, other anesthetists the same age in the same health-care system describe entirely different red threads: one loves the bedside conversations and gently bringing a sedated patient back to consciousness without panic, another is drawn to the intricacies of the anesthetic mechanism. Same role, same system, different loves. This is why Love-in-Work cannot be assigned or inferred by a manager and must be found by the person doing the work, one thread at a time.

• If an activity produces anticipation before, flow during, and fulfillment after, then it's a red thread—log it and protect time for it.
• If you're good at an activity but it drains you, then it's a weakness, not a strength—don't let competence keep it in your week.
• If red threads occupy less than ~20 percent of your time, then increase them; once past 20 percent, the extra burnout-reduction benefit stops, so weave rather than max out.
• If a manager comments on your work, then accept feedback about performance (quality, usefulness, delivery) but reject any claim about what does or doesn't strengthen you—you are the only judge of that.
• If a teammate shares your exact role, then assume their red threads differ from yours—don't copy their loved activities as your own.

• Defining strength as 'what you're good at': the tell is you keep a draining task because you excel at it, mistaking competence for love.
• Letting a manager or colleague assign your red threads: the tell is your loved-activity list reads like a job description or a strengths rating someone else gave you.
• Chasing an 'entirely red quilt': the tell is you're trying to eliminate all disliked work instead of hitting the 20 percent threshold, then wondering why nothing improves past it.
• Logging threads too vaguely ('analysis', 'leadership'): the tell is you can't recreate the activity next week because you never named the specific thing that lit you up.
• Assuming same-role teammates share your loves: the tell is you build a team plan on identical red threads and people quietly disengage from the parts that drain them.

• ▸Activity (name the specific task at the two-foot level, not the category)
• ▸Before signal (did you anticipate it eagerly or procrastinate/hand it off?)
• ▸During signal (did time fly or drag—did ten minutes feel like an hour?)
• ▸After signal (do you want to repeat it or hope you never do it again?)
• ▸Column (Loved It / Loathed It / neither)
• ▸Percent of week (estimate share of time spent on this activity)
• ▸Recreate plan (how you'll bring it back next week and refine it)
• ▸Red-thread total (sum of Loved-It time—is it at or above ~20%?)

1. 1Administer all eight precisely worded items exactly as written—do not paraphrase. The wording is validated; changing 'I have the chance to use my strengths every day at work' into 'Do you use your strengths?' breaks the measurement.
2. 2Ask only about the respondent's own feelings and experiences. Never ask team members to rate you or the company on abstract qualities—people are unreliable raters of others, and such answers reveal the rater, not the rated.
3. 3Score the four odd items (We) and four even items (Me) separately so you can see whether your gap is in shared/communal experience or in individual experience. Look for items where high-performing teams strongly agree and yours does not.
4. 4Attack the We items with recurring collective rituals. The Poland team's lunching together and huddling together is what builds 'my teammates have my back' and a shared sense of excellence—install the everyday interactions, not a culture statement.
5. 5Attack the Me items person by person: set clear expectations, position each person to use their strengths daily, catch people doing excellent work and recognize it, and frame each person's growth challenge. These are within your control as the team leader.
6. 6Because trusting the team leader makes members twelve times more likely to be fully engaged, treat trust in you as the multiplier—build it through frequent, reliable one-on-one attention rather than one-off events.
7. 7Re-measure on a short cadence. Treat scores as a snapshot of an everyday, local experience, and check whether your rituals and one-on-ones actually moved the specific low items.

Recall Lisa at Company A: she called her teams 'fair, supportive' and said the culture 'showed up in the teams I worked on for sure,' while acknowledging colleagues on other teams 'didn't see these things.' Her own explanation is diagnostic: whether the experience appears 'is a question of whether each team leader believes in the culture'—same company, different teams, different engagement. Translated to the eight items, Lisa's teams scored high on We items like 'my teammates have my back' and 'people who share my values,' driven by her leaders living the culture daily. The lesson for you: the team, not the company, is 'the sun, the moon, and the stars' of the experience, so the eight items must be measured and acted on at the team level. If you inherited a Lisa-style team where the leader didn't 'get' the culture, you'd expect low We scores and would rebuild them through shared rituals and consistent presence.

• If your low scores cluster in odd-numbered items, then the gap is in shared/communal experience—install recurring team rituals (huddles, shared meals, joint work) rather than individual coaching.
• If your low scores cluster in even-numbered items, then the gap is individual—work person by person on expectations, daily strengths use, recognition, and growth challenge.
• If trust in you as the leader is low, then fix that first, since it makes members twelve times more likely to be fully engaged and it multiplies every other item.
• If someone works on multiple teams, then don't assume the score is uniform—the most engaged workers sit on five distinct teams, so measure per team.
• If you're tempted to ask members to rate the company or you directly, then stop and reword to their own experience, because ratings of others reveal the rater, not the target.

• Rewording the eight items for 'flow.' The tell: your item text no longer matches the validated wording (e.g., 'clearly understand what is expected'), so scores stop predicting sustained performance.
• Measuring engagement at the company level. The tell: a single average hides that culture 'showed up in the teams I worked on' but not others—Lisa's own point that experience varies team by team.
• Asking people to rate the leader's empathy, vision, or strategic thinking. The tell: results correlate more with the rater's personality than the leader's behavior.
• Treating engagement as a perk problem—cafeteria, parental-leave policy, brand. The tell: you focus on things outside your control while the within-your-control levers (clear expectations, strengths, recognition, growth) go untouched.
• Running a one-off event instead of everyday rituals. The tell: We-item scores spike then decay, because the communal experience is built by frequent back-and-forth (lunching, huddling), not a single offsite.

• ▸Team name & member count: name the specific team; note who sits on multiple teams.
• ▸Me-item scores (2,4,6,8): record strongly-agree % for expectations, strengths, recognition, growth.
• ▸We-item scores (1,3,5,7): record strongly-agree % for mission, shared values, back, confidence.
• ▸Lowest item: circle the single item with the widest gap versus a high-performing benchmark.
• ▸Category verdict: mark whether the gap is mostly Me (individual) or We (communal).
• ▸Trust-in-leader check: note whether members would say they trust you (the 12x multiplier).
• ▸Weekly ritual to add: name one recurring shared interaction targeting the low We item.
• ▸Per-person action: for each member, one move on expectations/strengths/recognition/growth.
• ▸Re-measure date: set the short cadence to recheck the same item wording.

1. 1Set clear expectations for each person: state what the work is, what good looks like, and what you are relying on them to own—so confidence in you starts from knowing where they stand.
2. 2Position each person to play to their strengths every day, not occasionally; watch which tasks they gravitate toward and load more of that into their week.
3. 3Flood the team with real-time, accurate information about the world they face; be vigilant about accuracy (sort signal from noise) rather than packaging data into a tidy story.
4. 4Trust your people to make sense of the data themselves—provide context and connectivity, then let front-line members interpret and take initiative rather than handing interpretation to a select few.
5. 5Praise the team for excellent work when it happens, so reliance on you is reinforced by recognition, not just direction.
6. 6Help each person grow their career by connecting present work to where they want to go.
7. 7Do these things daily and repeatedly; trust is built over time through the accumulation of these lived experiences, not a single gesture.
8. 8Live the culture yourself—team members who see their leader genuinely believes in and gets the culture end up 'fortunate'; those whose leader doesn't, don't.

Lisa did six months of research on Company B—Google, Glassdoor, two months prepping interviews, talking to as many people there as she could—and concluded it checked enough boxes to join. Yet she left after two years, and the single point of failure was her manager: 'What happened is that I met my manager.' During interviews the manager's style struck Lisa as severe, formal, and hierarchical, but Lisa dismissed it as a 'game face.' Once on the job she 'saw her true colors,' and things went wrong. Notably, Lisa's confidence didn't hinge on brand, location, or pace of innovation—the factors she'd researched exhaustively; it hinged on whether she could rely on the person leading her. This mirrors the finding that team members who trust their team leader are twelve times more likely to be fully engaged. The company Lisa loved (Company A) she described as trusting, fair, and supportive—but only where each team leader actually believed in that culture.

• If a team member doesn't know what good looks like on their task, then stop and set the expectation before anything else—trust cannot form on ambiguity.
• If you find yourself interpreting the data and issuing the plan, then reverse it: provide the context and let them decide.
• If someone consistently gravitates toward certain data or tasks, then increase the volume, depth, and speed of exactly that—don't dilute it into generic reporting.
• If your instinct is to package information to make it simple, then redirect that effort toward making it accurate instead.
• If your company invokes culture or 'the direction we want to go' to silence dissent, then treat that as a warning that the culture is being used for evil, not lived.

• Reading a manager's off-putting style as a mere 'game face'—the tell is Lisa rationalizing severity and hierarchy during interviews, then discovering 'true colors' on the job.
• Relying on company-level signals (brand, perks, Fortune rankings, Glassdoor) to predict your daily experience—the tell is exhaustive research that still fails, because trust lives at the team, not the company, level.
• Hoarding interpretation in a 'select few' who analyze data and hand down a plan—the tell is front-line people executing decisions they had no context to shape.
• Chasing simplicity and coherent narratives over accuracy—the tell is polished dashboards that people quietly stop trusting because the signal is buried in noise.
• Assuming culture is uniform across the company—the tell is 'I was fortunate,' meaning others on worse teams didn't see the inclusive, trusting behaviors at all because their leader didn't get the culture.

• ▸Person's name: who this entry is for
• ▸Clear expectation set: state exactly what good looks like on their current work
• ▸Strengths in play: which daily task lets them do what they naturally gravitate toward
• ▸Real-time info supplied: what accurate, current data they need about their world
• ▸Interpretation ownership: what decision you're leaving them to make with that context
• ▸Recent praise given: last excellent work you named and when
• ▸Growth connection: how today's work links to where they want to go
• ▸Culture check: one behavior you modeled this week that proves you live the culture
• ▸Trust signal: one thing they did that shows they're relying on you (or a gap if none)

1. 1Stop trying to acquire the full list of abstract leader competencies. You will fail at the first hurdle—authenticity. Instead, treat leadership as your idiosyncratic way of creating eight emotional outcomes in followers.
2. 2Measure followership, not yourself. Ask each team member to rate their own experience against the eight items (enthusiasm about mission, clarity of expectations, shared values, using strengths daily, teammates having their back, recognition for excellent work, confidence in the future, being challenged to grow). Never ask people to rate you on abstract qualities—people are unreliable raters of others.
3. 3Read the scores as a range, not an average. Because experience varies more within a company than between companies, your team's scores tell you about your leadership specifically. Look at the scatter of responses, not a rolled-up culture number.
4. 4Cultivate confidence in the future—the item that most directly reduces follower uncertainty. Do this not through detailed long-range plans (which are obsolete by the time they're written) but through frequent, present-tense attention to the real work.
5. 5Install the weekly check-in as your core ritual. Check in with each team member every week about their near-term work. Frequency beats quality: a mediocre weekly check-in outperforms a twice-a-year high-quality one.
6. 6Right-size your span of control to the number of people you—and only you—can check in with every week. If you can't check in weekly, you have too many people.
7. 7Validate your effect over time: reliable followership scores should predict lower voluntary turnover, fewer lost work days, and higher performance. If they don't move those outcomes, you're not creating followership.

Take the Mission Health data on the seventh item, 'I have great confidence in my company's future.' A single company has, in theory, only one future, so this response should be identical across all 1,002 teams. It isn't. Responses vary significantly team-to-team: different team, different level of confidence in the future. That variance is the proof that followership is created locally by the team leader, not delivered by the company. Chuck Robbins at Cisco knows this—he sits thousands of miles and several org levels from the daily reality of his teams and admits there's a limit to what he can control from the center. So the confidence-in-the-future spike that produces followership is built by the immediate leader through weekly attention, not by corporate strategy decks.

• If you're tempted to model yourself on a leadership competency checklist, then stop—refine your own authentic way of producing the eight feelings instead.
• If you can't check in with every team member every single week, then your team is too large; reduce it.
• If a follower score has no range (everyone clusters at one end, or the curve was forced through calibration), then the data is contaminated—discard it.
• If your future-confidence item scores low, then increase check-in frequency and real-time attention to the work, not the volume of long-range planning.
• If someone claims a leadership measure is valid, then require proof it predicts a different real-world outcome (turnover, lost work days, performance)—reliability first, then prediction.

• Rating leaders on abstract traits like empathy, vision, or strategic thinking. The tell: your survey asks people to judge someone else rather than report their own experience—the data is unreliable.
• Treating 'culture' as a uniform company-wide experience. The tell: you cite one engagement number for the whole company while team-to-team range is actually larger than company-to-company range.
• Betting confidence in the future on elaborate plans. The tell: the September plan is obsolete by November and unrecognizable by January—you're planning for the near-term past, not the future.
• Saving up for twice-a-year, super-high-quality coaching conversations. The tell: infrequent check-ins and low team 'intelligence,' regardless of how polished each session is.
• Blaming team leaders' lack of coaching skill for low engagement. The tell: you focus on check-in quality when the data only shows that check-in frequency drives engagement, performance, and retention.

• ▸Team member name — one row per person you personally lead
• ▸Weekly check-in done? (Y/N) — mark every week; frequency is the metric
• ▸Mission enthusiasm (1-5) — their own rating, not your guess
• ▸Clarity of expectations (1-5) — self-reported understanding of what's expected
• ▸Confidence in the future (1-5) — the uncertainty-reduction item; watch this closely
• ▸Score range across team — record spread, not average; flag clustering or forced curves
• ▸Span-of-control check — can you check in with everyone weekly? If no, note whom to reassign
• ▸Outcome link — track voluntary turnover / lost days against scores to confirm validity

1. 1Define what performance means in your specific business unit before measuring anything: name the concrete outputs — high productivity, high innovation, high customer satisfaction, low voluntary turnover, low lost work days, low accidents — that actually matter for your team.
2. 2Split your teams into two groups: one from teams already scoring high on those performance outcomes, one from teams scoring low or average. This contrast is the whole engine — without it you can't isolate what distinguishes the best from the rest.
3. 3Ask both groups the same questions about their inside experience, and keep only the items where high performers strongly agree and mid-to-low performers do not. Discard any item that both groups answer the same way — it has no discriminating power.
4. 4Ask people only about their own feelings and experiences, never to rate the team leader or company on abstract qualities. Ratings of others tell you more about the rater than the rated, so they corrupt the data.
5. 5Deploy the eight validated items as your team pulse, treating item 4 — 'I have the chance to use my strengths every day at work' — as the master lever, since it is the single most powerful predictor of productivity.
6. 6Act on the strengths item at the role level: identify each person's strengths, then tweak their specific roles and responsibilities so their daily work calls on those strengths. Keep the word 'every day' in view — a mere 'good fit' at lower frequency breaks the link to performance.
7. 7Re-run the pulse repeatedly over time rather than once; these findings are provisional, and you are looking for sustained performance, not a snapshot.

Chuck Robbins, Cisco's CEO in San Jose, wants an enthusiastic, committed workforce across roughly 140,000 employees and contractors, but he sits thousands of miles and several organizational levels away from the fifteen-person team that is extremely productive and highly engaged in the field. He can't control their day-to-day experience from the center, so the real question is what he asks each local team leader to focus on. The rigorous answer isn't more corporate culture initiatives — day-care, 20 percent time, solar panels — because none of those are within a team leader's control. Instead it's the eight experiential items measured team by team, with the strengths item treated as decisive. On the best teams the leader has quietly reshaped roles so each person exercises their strengths daily; when that fit exists, recognition, mission, and clarity all work better, and when it's absent, no amount of money, title, or cajoling compensates. That is how a leader thousands of miles from headquarters produces sustained productivity where the CEO cannot.

• If an item is answered the same way by high and low performers, then drop it — it doesn't sort the best from the rest.
• If a survey question asks someone to rate another person's abstract quality (empathy, vision, strategic thinking), then discard the data — it reflects the rater, not the rated.
• If team members feel work-strengths fit only sometimes rather than 'every day,' then the performance link vanishes — treat daily frequency as the threshold, not occasional good fit.
• If you've tried money, title, cheerleading, or cajoling and performance hasn't moved, then check the strengths lever first — nothing else compensates for its absence.
• If a driver of culture (day-care, referral bonuses, off-site songs) isn't within the team leader's control, then don't hold the leader accountable for it — hold them accountable for the eight experiential conditions.

• Measuring performance with a single generic metric instead of naming the specific outcomes (productivity, innovation, customer satisfaction, turnover, lost work days, accidents) — the tell: you can't say what 'high performing' concretely means for your unit.
• Skipping the high-vs-low comparison and just surveying everyone — the tell: your 'drivers' are things everyone agrees with, which discriminate nothing.
• Asking people to rate the leader or company — the tell: your scores swing with who's filling out the form, not with actual conditions.
• Dropping 'every day' to make the strengths item feel more reasonable — the tell: the correlation with team performance disappears and you conclude strengths don't matter.
• Holding leaders accountable for culture commitments made by the executive committee — the tell: leaders wonder precisely what they're responsible for, since little of what's written about the company is in their job description.

• ▸Performance definition — list the concrete outcomes that mean 'high performing' for this unit
• ▸High-performer group — name the teams scoring high on those outcomes
• ▸Low/average group — name the teams scoring low or average
• ▸Discriminating items kept — record which of the eight questions high performers strongly agree with and others don't
• ▸Strengths-fit score — capture agreement with 'I have the chance to use my strengths every day at work'
• ▸Role tweaks — note the specific responsibility changes made to raise each person's daily strengths use
• ▸Rater check — confirm every item asks about the respondent's own experience, not a rating of someone else
• ▸In-control vs out-of-control — flag which improvement levers the team leader actually owns
• ▸Re-run date — schedule the next pulse to confirm sustained, not one-time, performance

1. 1Stop treating retention as a company-identity problem. The data shows engagement varies more within a company than between companies, so intervene at the team level, not through corporate branding or company-wide perks.
2. 2Measure the four attrition-predicting Engagement Pulse items in each team, ranked by predictive power: 'I have a chance to use my strengths every day at work,' 'In my work, I am always challenged to grow,' 'I am really enthusiastic about the mission of my company,' 'I have great confidence in my company's future.' Prioritize the first two — they carry the most predictive power.
3. 3Anchor every team leader on a weekly check-in with each team member, focused on near-term work and where they can use strengths. Frequency beats quality here: a leader checking in 52 times a year gets higher engagement and lower voluntary turnover regardless of coaching skill.
4. 4Cap span of control at the number of people a leader can genuinely check in with every week. If you can't check in weekly with everyone, you have too many people — redistribute reports.
5. 5Put contractors, gig, and virtual workers on real teams fast. Team membership erases the isolation penalty and gets you the retention of traditional work with the flexibility of gig work.
6. 6Use company-wide events (like Cisco's monthly all-hands) to feed the 'mission' and 'future confidence' items — but recognize these two still vary team to team, so pair events with the leader's local reinforcement of purpose.

Cisco used termination and Engagement Pulse data from a single fiscal year, building a population of team members who either stayed or voluntarily left within that year. Using Pearson's correlation, multiple regression models, and the bootstrap method to confirm stability, they isolated four items that significantly predict voluntary attrition, ranked from most to least powerful, with the two strengths-and-growth items ('use my strengths every day,' 'always challenged to grow') on top. The finding: the more positively people feel about using their strengths now and in the future, and about the company's mission and prospects, the more likely they stay. Crucially, even enthusiasm about company mission varied team to team — your experience of the company is mediated by your experience of your team. The stated implication: above all else, a team leader's focus on helping each member play to their strengths insulates the team against attrition.

• If you want the single highest-leverage retention move, then have leaders help each member use their strengths daily — it's the top predictor of staying.
• If a leader can't check in weekly with every direct report, then their span of control is too large — reduce it.
• If you're using contractors or gig workers, then place them on a real team as fast and genuinely as possible, or expect lower engagement and retention.
• If engagement scores vary widely between teams in the same company, then trust that variation over company-level narratives — the team is where retention lives.
• If mission and future-confidence scores are low, then run company events but reinforce locally through the leader, since those items still vary team to team.

• Treating retention as a branding or company-culture issue. Tell: leadership talks about company mission and perks while ignoring that within-company variation exceeds between-company variation.
• Chasing high-quality biannual coaching conversations instead of frequent ones. Tell: 'twice-a-year super-high-quality' reviews — as absurd as twice-a-year teeth-brushing; low check-in frequency means low team intelligence.
• Loading leaders with too many reports so weekly check-ins are impossible. Tell: leaders say 'I'd love to check in weekly but I have too many people.'
• Isolating gig, virtual, or traveling workers. Tell: virtual-but-teamless or heavy-travel workers show the lowest engagement (travelers at 9% Fully Engaged vs 15% non-travelers).
• Blaming leaders' coaching skill for attrition. Tell: 'our team leaders aren't skilled enough to coach' — the data links frequency, not quality, to retention.

• ▸Team member name — who you're assessing
• ▸Strengths-use score — do they get to use strengths every day? (top predictor)
• ▸Growth-challenge score — are they always challenged to grow? (second predictor)
• ▸Mission enthusiasm — enthusiastic about the company mission? (varies by team)
• ▸Future confidence — confident in the company's future? (varies by team)
• ▸Weekly check-in status — checked in every week this quarter? yes/no
• ▸Team membership — are they genuinely on a team (esp. if gig/virtual/travel)? yes/no
• ▸Next strengths action — one thing you'll do to shift their work toward their strengths

1. 1Inventory every information source you touch — dashboards, reports, customer signals, field observations, metrics — and list which ones your team currently cannot see on demand.
2. 2Liberate as much of that information as possible, as fast as possible: default to open access rather than 'need to know.' Don't pre-package, simplify, or weave it into a story before sharing.
3. 3Instruct team members to share what they know about the world frequently, so raw real-world detail flows both up and sideways, not just down.
4. 4Run a frequent (weekly) check-in where the team looks at current, raw, detailed information together and makes sense of it collectively — the ritual replaces the annual plan as the coordinating mechanism.
5. 5Watch carefully which data your people actually use, and prune or promote sources based on real usage rather than assumed usefulness.
6. 6Focus your effort on accuracy — sorting signal from noise — because that, not simplification, is the hard and valuable part; complexity is something teams already handle.
7. 7Push decision authority to the front-line members ('controllers') who now hold accurate real-time data, so they send effort where they know the situation is, rather than executing a stale plan.
8. 8Treat coordination as continuous and real-time, not as a document produced quarterly; the check-in scopes what's true now, individual judgment picks the solution.

In late 1940 the RAF faced an enemy it couldn't predict, with too few Spitfires and Hurricanes to patrol the entire English coastline continuously. The accepted model — guessing where attacks would come and flying patrols — produced a 'good' interception rate of only 30 to 50 percent, hence 'the bomber always gets through.' Rather than build a better plan, Hugh Dowding built a room: the Battle of Britain Bunker, networked with identical rooms across the country and fed by many information systems. It acted fast on current, raw, and detailed information instead of slow, stale, summarized data, and front-line controllers exercised their own judgment to send forces where they knew the enemy actually was. Interception rates rose to an average of 90 percent, often 100 percent — doubling the effectiveness of the defending force. The Dowding system wasn't a planning system; it was an intelligence system, and it was the force multiplier that saved the country.

• If information helps your people understand their real world in real time, then share it — don't withhold it on the grounds they might not understand it.
• If you're tempted to summarize and package data before releasing it, then stop — the challenge isn't sense-making, it's accuracy; spend that effort sorting signal from noise instead.
• If a plan is more than a few weeks old, then treat it as a description of the near-term past, not a guide to the future — use it to scope the problem, not to dictate the solution.
• If the people making the decisions sit far behind the front lines, then move the decision to the front-line members who hold the current detailed data.
• If a data source goes unused week after week, then cut it; if one gets used heavily, then feed it faster.

• Restricting information to those who 'need to know' — the tell: your system looks like a planning system, with data gated by hierarchy instead of flowing freely.
• Optimizing the planning cycle for speed instead of replacing it — like McChrystal's 'awesome machine' that ran raids faster but still arrived to find the target already gone, because the loop was still too slow to beat spontaneous, decentralized events.
• Over-packaging data into a tidy coherent story — the tell: you spend time weaving narrative while accuracy (signal vs. noise) goes unaddressed.
• Confusing planning with knowing what to do — the tell: after long analysis you understand the scale and nature of the challenge but have learned nothing about what action makes things better.
• Keeping decisions with distant planners rather than empowering front-line judgment — the tell: people execute action items they no longer recognize and turn up where the situation used to be.

• ▸Information sources I control: list every feed, report, dashboard, and signal I have access to.
• ▸Currently gated: which of these my team cannot see on demand, and why.
• ▸To liberate this week: which gated sources I open now, unpackaged.
• ▸Team-shared signals: what front-line members will report frequently about the real world.
• ▸Accuracy check: for each key source, how I verify signal from noise.
• ▸Weekly check-in slot: fixed day/time the team meets to make sense together.
• ▸Decision rights: which choices front-line members now make with this data.
• ▸Usage watch: which data people actually used last week (keep) vs. ignored (cut).
• ▸Stale-plan flag: any plan older than a few weeks I'm still treating as truth.

1. 1Start with meaning, not values-language: decide what you actually want people to feel and do differently, then work backward to how you'll show it. Cathy started from 'reserve Sunday as rest,' Facebook from 'facilitate real human connection.'
2. 2Set your expressed values by choosing what people physically bump into at work, not by writing a list. Ask: what do they see when they walk in and turn left? Facebook uses Sun Microsystems logos, posters, and 'Hacker Company' signage instead of generic words.
3. 3Audit your existing rituals — the things you do repeatedly — because they already communicate whether you intend them to or not. Track meeting arrival time, dress, whether you catch up on personal lives or launch into business, who speaks first, whether you cut people off.
4. 4Convert one recurring behavior into a deliberate ritual that carries your meaning. Zuckerberg/Sandberg hold a weekly all-hands where any employee can ask any question and leaders commit to answering; Chick-fil-A stops all work on Sundays.
5. 5Tell stories at gatherings that celebrate the specific meaning you want lived, naming real people. At Chick-fil-A's annual Seminar, the best operators are brought on stage one-by-one to have their story told.
6. 6Make your meaning exclusionary on purpose: state plainly who will NOT find meaning here. Facebook tells people 'if you want beauty, carefully considered, perfect beauty, then Facebook is not for you — go work for Apple.'
7. 7Repeat across all three levers relentlessly and consistently over time; alignment comes from the pervasiveness, not from any single announcement.

Truett Cathy cascaded meaning at Chick-fil-A without imposing goals. His expressed value was closing on Sundays — a physical, unmissable fact of the business — flowing from his devotion to the biblical day of rest, even though the extra day would boost sales and profit. He built rituals into the very structure of the franchise agreement: unlike McDonald's largest franchisee Arcos Dorados with over $4.5 billion in sales across two thousand locations, a Chick-fil-A operator cannot own two thousand locations no matter how much capital they bring. This deliberately forgoes brand-growth capital in exchange for tens of thousands of local leaders who embrace Cathy's meaning. He reinforced it with story: at the annual Seminar, the best operators are brought on stage one-by-one to have their story told, with a magazine-worthy spread celebrating each operator's contribution to their community. The result is the most profitable and fastest-growing quick-service restaurant company in the world, built on a chicken sandwich rather than network effects or a search monopoly.

• If your values list contains generic words like integrity, innovation, or teamwork, then scrap it and instead show what you value through what people encounter — those words are 'about as meaningful as Muzak.'
• If a proposed ritual costs you something (sales, an extra open day, capital) but signals your meaning clearly, then keep it — the sacrifice is what makes it legible, as with closing Sundays.
• If you can't state who would be repelled by your meaning, then it isn't specific enough — clear meaning both attracts and excludes.
• If a behavior repeats every week, then treat it as a message already being read by your team, and make it deliberate rather than accidental.
• If you want alignment, then reach it through cascaded meaning, not cascaded goals — no research shows goals set from above raise productivity, and the weight of evidence says they limit it.

• Writing a literal values list and expecting it to change behavior — the tell is a plastered wall of 'integrity/innovation/teamwork' and leaders wondering why nothing shifted.
• Treating rituals as optional — the tell is a leader who shows up late, cuts people off, and launches into business, unaware the team is drawing conclusions from all of it anyway.
• Cascading goals to create alignment instead of meaning — the tell is a yearly goal-setting process that feels mechanical, fake, and demeaning to the people in the trenches, disconnected from actual work.
• Trying to please everyone, so the meaning is watered down to attract all and repel none — the tell is a culture no one can describe in a differentiating sentence like 'you'd rather be surfing' or 'you'd rather be winning.'
• Doing it once and stopping — the tell is a single launch event or memo, when the passages emphasize meaning cascaded 'deliberately, relentlessly, precisely, and pervasively' over time.

• ▸Core meaning (one sentence): what matters most here and what should feel different because of it
• ▸Who this attracts: name the person who will find meaning here
• ▸Who this repels: state plainly who should not work here
• ▸Expressed value on the wall: what physical thing will people see and bump into (not a word list)
• ▸Left-turn test: what they encounter when they walk in and turn left, and what it tells them about you
• ▸Deliberate ritual: one repeated action that carries the meaning, and its cost that proves it's real
• ▸Meeting-ritual audit: your arrival time, who speaks first, and what it currently signals
• ▸Story to tell at gatherings: the specific person and act you'll celebrate by name
• ▸Repetition plan: how often and across which of the three levers you'll reinforce this

1. 1Measure the right thing: ask team members to rate the item 'I have the chance to use my strengths every day at work,' not whether they feel a general 'good fit.' The everyday-ness is the active ingredient; drop it and the link to team performance vanishes.
2. 2Identify each person's idiosyncratic strengths — the activities that make them feel strong — rather than scoring them against a standardized 'well-rounded' model. Strengths are personal and specific to that individual, so surface them per person.
3. 3Tweak roles and responsibilities to the person: move the work toward what makes each member feel strong, instead of forcing the person to conform to a fixed job description. Fit the work to the person.
4. 4Run a weekly check-in with every team member asking 'What are your priorities this week?' and 'How can I help?' Use it to spot where their week does or doesn't call on their strengths and adjust in real time.
5. 5Pull the master lever first: get strengths-role fit right before spending energy on recognition, mission, or clarity — because these all work better once fit is in place and fall flat when it isn't.
6. 6Re-fit continuously across the year's fifty-two sprints. Because roles and action items written in September are unrecognizable by January, treat strengths-role fit as an ongoing weekly adjustment, not an annual assignment.

The passages state the master-lever mechanism directly: on the best teams the leader is 'able not only to identify the strengths of each person but also to tweak roles and responsibilities so that team members, individually, feel that their work calls upon them to exercise their strengths on a daily basis.' When a leader does this, 'everything else—recognition, sense of mission, clarity of expectations—works better.' When they don't, 'nothing else that he or she tries, whether in the form of money or title or cheerleading or cajoling, can make up for it.' The check-in is the operational tool: a leader who checks in weekly sees on average a 13 percent increase in engagement, while one who checks in only monthly sees a 5 percent decrease — literally worse than useless, because monthly talk stays in generalities. So the leader uses each ten-to-fifteen-minute weekly conversation, rooted in the specifics of the member's situation and strengths, to keep adjusting the work so daily strengths use never lapses. The contrast is the design flaw the passages name: companies instead 'measure us against a standardized model, and then badger us to become as similar to this model as possible' — built around the lie that the best people are well-rounded.

• If you can only fix one thing on the team, then fix strengths-role fit first — it is the master lever that elevates or diminishes everything else.
• If a member reports strengths use as occasional rather than daily, then treat it as a failing item and re-tweak the role — everyday-ness is the condition of high performance.
• If you're tempted to close a gap with money, title, or cheerleading, then stop — none of those compensate for missing strengths-role fit.
• If you're checking in less than weekly, then increase frequency to weekly — monthly check-ins produce a 5 percent engagement decrease because they force generalities.
• If someone lacks a strength the role demands, then reshape responsibilities around what makes them feel strong rather than sending them to become well-rounded.

• Measuring 'good fit' instead of 'strengths every day.' The tell: your survey item no longer predicts team performance because you dropped the everyday-ness.
• Forcing well-roundedness — measuring people against a standardized model and badgering them toward it. The tell: development plans focus on shoring up weaknesses to match a template.
• Substituting incentives for fit — reaching for money, title, or cajoling. The tell: engagement stays flat despite bonuses because the master lever was never pulled.
• Check-ins too infrequent, drifting into generalities. The tell: conversations happen monthly or every six weeks and are 'useless,' and members would rather you leave them alone.
• Treating strengths-role fit as an annual planning event. The tell: the roles you defined at the September off-site are obsolete by November and unrecognizable by January, but nobody re-fits weekly.

• ▸Team member: name of the individual
• ▸Their idiosyncratic strengths: the activities that make this person feel strong
• ▸This week's priorities: what they say they're focused on (their words, not your to-do list)
• ▸Strengths called upon this week: which priorities draw on their strengths daily — mark yes/no
• ▸Fit gap: any task this week that pulls against their strengths
• ▸Role tweak: one adjustment to responsibilities to raise daily strengths use
• ▸How I can help: the specific obstacle to remove or tip to offer right now
• ▸Fit rating: their agreement (1-5) with 'I have the chance to use my strengths every day'

1. 1Establish a weekly one-on-one check-in with each team member — a frequent, one-on-one conversation about near-term future work. Frequency is the point: like brushing teeth, what matters most is that it happens every week, not that any single one is masterful.
2. 2Set your span of control by the check-in. The right number of people to lead is the exact number you, and only you, can check in with every week. If you can do eight but not nine, your span is eight.
3. 3Open each check-in by asking about the work ahead — what the person loved and what they loathed since you last talked, and what their priorities are now. Keep it future-focused, not a retrospective audit.
4. 4When you catch someone doing something right, replay it. Notice the specific moment that worked for that individual and name it back to them, rather than defaulting to their lowest scores or 'development areas.'
5. 5Anchor attention on strengths — activities that make a person feel strong (positive anticipation before, flow during, fulfillment after). Feed the appetite ingredient, because appetite is what drives the practice that produces skill.
6. 6Resist the competency-model reflex that tells you a person's lowest scores are where growth comes from. Do not run relationships like the feedback robot that generates prose in complete ignorance of whether the person actually does the thing.
7. 7Practice through repetition, not through waiting to be excellent. Even a leader who is 'no Pat Summitt' gets 51 more reps per person per year and gets a little better; the team member still gets something really positive out of it.

A team leader in the mold of the book's research checks in every week with each of her eight team members — a brief, one-on-one conversation about the near-term future. She doesn't wait for the annual review or a super-high-quality twice-a-year session, because goals set at the beginning of the year are irrelevant by the third week. In one check-in she notices a team member lit up while walking a customer through a thorny issue — she names that specific moment back to him as something that worked. Because she does this 52 times a year, her early clumsiness matters less than her frequency; she practices 51 more times per person and gets a little better each round. The result mirrors the data: teams whose leaders check in weekly show higher engagement, higher performance, and lower voluntary turnover — regardless of the leader's natural coaching talent. Contrast this with the automated feedback robot that clicks out 'Barbara puts thought into her budget requests,' indifferent to whether Barbara does any such thing.

• If you can't fit everyone into a weekly check-in, then you have too many people — cut your span of control to the number you can actually reach every week.
• If you're tempted to focus on someone's lowest scores as their path to growth, then stop — treat those as the competency model's fiction and replay what makes them feel strong instead.
• If the activity produces anticipation-before, flow-during, and fulfillment-after, then it's a strength worth feeding, not merely something they're good at (ability without appetite is not a strength).
• If you're worried your check-in isn't skilled or polished enough, then do it anyway — frequency beats quality, and the team member still gets something really positive out of it.
• If you find yourself defaulting to negative feedback because it feels rigorous or 'radically transparent,' then reconsider — pervasive review at every turn is a Bridgewater ideology, not evidence of better performance.

• Substituting twice-a-year high-quality feedback for weekly contact. The tell: you can name your review cadence in months, not weeks, and your team's intelligence about its own work is stale.
• Managing too many people and calling weekly check-ins impossible. The tell: you say 'I'd love to but I can't' — which is the signal your span of control is already too wide.
• Anchoring attention on 'development areas' and lowest scores. The tell: your feedback reads like the robot's — generic competency prose disconnected from what the person actually does.
• Confusing ability with strength — assigning more of what someone is merely good at. The tell: the person performs briefly but is bored, cold, or drained rather than filled up and proud.
• Chasing polish over frequency and never starting. The tell: you postpone check-ins waiting to become a better coach, forfeiting the 51 annual reps that would have improved you.

• ▸Team member: name of the one person this check-in is for.
• ▸Date / cadence marker: confirm it's within 7 days of the last one.
• ▸What you loved last week: an activity that showed anticipation, flow, or fulfillment — replay it back specifically.
• ▸What you loathed last week: name the draining task so you can rebalance it.
• ▸This week's priorities: 1-2 near-term, future-focused pieces of work.
• ▸A moment I caught you doing right: the specific instance that worked, named concretely.
• ▸Support I'll give: one thing you'll do to feed the strength or clear the path.
• ▸Span check: total people I check in with weekly — confirm this name still fits inside that number.

1. 1Decide first whether you're measuring a state or a trait. States (mood, engagement, skill, knowledge) change over time and are measured by self-report survey or a scored test; traits (extroversion, empathy, competitiveness) persist for life and require a validated personality assessment. Never mix the two.
2. 2For any survey item, write it so the rater reports only their own experience or intended action. Convert 'Rate your leader's empathy' into 'My teammates have my back' — the rater becomes the sole authority on the answer.
3. 3Use first-person, present-tense, absolute phrasing that the rater alone can verify. Prefer 'I have the chance to use my strengths every day at work' and 'At work, I clearly understand what is expected of me' over abstract quality ratings.
4. 4Strip every item that asks one person to judge an abstract quality (vision, strategic thinking, empathy) in another person. Such responses tell you about the rater, not the rated, and produce the Idiosyncratic Rater Effect.
5. 5Anchor self-assessments on a strongly-agree-to-strongly-disagree scale, or use situational judgment tests where the taker picks the response that fits her best. These are the two prevalent, reliable formats.
6. 6Run factor analysis on your instrument to confirm what the items actually measure — how many distinct clumps exist. At Cisco this split the eight items into a 'company' factor (items 1 and 7) and a 'team' factor (the other six).
7. 7Validate the items against sustained team performance before deploying, and keep the wording precise; the eight items work because they are precisely worded, not merely well-intentioned.

The eight engagement items are the model. Instead of asking team members to rate their leader on recognition or growth-planning, each item asks the member about their own experience: 'I know I will be recognized for excellent work' and 'In my work, I am always challenged to grow.' The members never directly rate the leader or company on any abstract quality — they report only their own feelings and experiences, because people are horribly unreliable raters of others. Factor analysis on these items across many companies found a single 'engagement' factor for years, until the Cisco data surfaced a second factor: items 1 ('enthusiastic about the mission') and 7 ('great confidence in the company's future') clumped separately as a 'company' factor. This is what reliable, variable, valid self-report data looks like — it survives factor analysis and predicts performance. The design choice — asking about self, not others — is what makes the data usable at all.

• If you're tempted to ask person A to rate an abstract quality in person B, then rewrite it as a first-person self-report or drop it — A cannot know B's inner quality any more than B's voting preference.
• If the thing you're measuring can change with training or time, treat it as a state and use a survey or scored test; if it persists across life, treat it as a trait and use a validated personality assessment.
• If an item's answers tell you more about the rater than the person being rated, then the item is measuring the Idiosyncratic Rater Effect, not the target — discard it.
• If a competency like 'strategic thinking' can't be resolved into either a state (test/survey) or a trait (personality assessment), then you cannot reliably measure it and shouldn't have peers rate it.
• If factor analysis shows items clumping unexpectedly, then trust the data and re-label the factors rather than forcing your original single construct.

• Asking managers or peers to rate you on empathy, vision, or strategic thinking. The tell: no team leader is ever blessed with perfect objectivity, and scores of the same person differ wildly by rater.
• Treating a trait as a state (or vice versa) and choosing the wrong instrument. The tell: you gave a survey for something inherent, or a personality test for something training could change.
• Writing items that ask for a judgment of another person's abstract quality. The tell: response variance tracks who is doing the rating, not who is being rated.
• Assuming your instrument measures one thing without running factor analysis. The tell: two items 'behave differently' in one slice and you ignore it until a second factor forces itself into view.
• Loosening the wording for readability. The tell: items stop predicting sustained performance because the precision that made them valid is gone.

• ▸Target construct: name the exact thing you want to measure
• ▸State or trait?: mark which — determines survey/test vs. personality assessment
• ▸Rater = subject?: confirm the rater answers only about their own experience/actions
• ▸Abstract-quality check: does any item ask A to judge B's inner quality? (yes = rewrite)
• ▸Item wording: first-person, present-tense, absolute phrasing the rater alone can verify
• ▸Scale: strongly-agree-to-strongly-disagree, or situational-judgment options
• ▸Factor test: run factor analysis; note how many clumps appear
• ▸Validity link: which performance outcome does this item predict?