An Everyone Culture: Becoming a Deliberately Developmental Organization

1. 1Make your weaknesses public first: name the specific limitation you're covering (your 'backhand') rather than managing others' impressions of it—this is the 'second job' you must stop doing.
2. 2Locate your growing edge inside live work, not in a separate course or coaching session. Pick the real business dilemma sitting in front of you and treat it as the developmental terrain (Decurion's 'nothing extra' approach).
3. 3Have a 'face the truth' moment: gather evidence about whether you're engaging authentically or just going through the motions. Faking it is the disqualifier, not being bad at something.
4. 4Build an explicit practice plan naming the targeted situations where you will actively rehearse the new behavior—like practicing a backhand you've been avoiding.
5. 5Recruit peer mentors who coach you, hold you accountable, and keep you on the practice plan; do not attempt this privately.
6. 6Run diagnosis before design: when a problem surfaces, understand why it occurred as a distinct step before jumping to a solution—do not blur the two.
7. 7Reframe the pain of confronting limitations as the income, not the cost. Expect loss and suffering as part of growth (eudaemonia), and measure yourself by how fast you're learning, not how good you already look.
8. 8Cycle the loop: after setbacks, return to 'boot camp' logic—re-examine, re-plan, re-practice. Persistence through repeated rounds is the enactment, not a one-time fix.

At Bridgewater, the training team holds its 9:00 a.m. Friday meeting to diagnose a problem within the team—in the 'Sergio and the failed meeting' case. Rather than rushing to fix it, the twenty-somethings on the curriculum team run a diagnosis: understanding why the problem occurred, treating the painful problem as a 'potential improvement screaming at you.' This sits inside Dalio's five-step process—setting goals, then identifying and not tolerating problems, then diagnosis—where each step is kept distinct and not blurred. The unrelenting, transparent search for truth includes the painful truths about one's own limitations, which is precisely the enactment of a growth mindset: the point is not to look good in the meeting but to learn fast from its failure. The physical transparency (floor-to-ceiling windows, no private meetings) removes the option of covering weaknesses. The individual grows by facing the painful truth in real work, witnessed and supported by colleagues.

• If you find yourself covering a weakness or managing impressions, then you're doing the unpaid second job—stop and make the weakness public so colleagues can support you.
• If a problem is painful, then treat it as louder signal, not something to tolerate—'the more painful the problem, the louder it is screaming' that improvement is possible.
• If you're about to jump from problem to solution, then stop and run diagnosis first; diagnosis and design are distinct steps not to be blurred.
• If you're only 'going through the motions' or faking engagement, then you fail the growth test regardless of skill—authentic striving to learn about yourself is the bar.
• If you measure your worth by 'how good you are' rather than 'how fast you are learning,' then you're in a fixed frame—redirect to the learning rate.

• Treating development as an additive—outsourcing growth to a coach, course, or off-site while the person and the engine stay unchanged. The tell: 'people development' lives only in high-potential programs, not daily work.
• Going through the motions and faking the 'face the truth' moment. The tell: no genuine engagement with your own inadequacies; you dodge rather than expose blind spots.
• Making the practice plan but abandoning it without accountability. The tell: no peer mentor, no targeted situations, and the backhand never gets practiced under real pressure.
• Chasing happiness-as-pleasure (pool tables, nap spaces, unlimited vacation) instead of happiness-as-flourishing. The tell: you avoid the loss and pain that genuine development requires.
• Blurring diagnosis and design—rushing to solve the problem instead of letting the problem 'solve you' and expose deeper patterns of thinking. The tell: quick fixes that never reach root causes.

• ▸My backhand: the specific weakness I've been covering (name it plainly).
• ▸Made public to: who now knows this so they can support me.
• ▸Live work as terrain: the real business dilemma where I'll practice this.
• ▸Targeted situations: 2-3 concrete moments where I will actively rehearse the new behavior.
• ▸Diagnosis: why this limitation shows up—root cause, kept separate from the fix.
• ▸Peer mentor(s): who coaches me, holds me accountable, checks the plan.
• ▸Learning-rate check: how I'll know I'm improving fast (not just looking good).
• ▸Setback protocol: what I do when I fail—re-diagnose, re-plan, another round.
• ▸Face-the-truth marker: evidence I'm engaging authentically, not going through the motions.

1. 1Locate the individual's current meaning-making structure before intervening: determine whether they are subject to their environment and beliefs (holding them as unexamined truth) or able to take those beliefs as objects of reflection. The passages frame this as the movement from being 'subject to' toward 'taking as object.'
2. 2Stop treating development as 'something extra.' Instead of adding a coach, course, or off-site outside the work, wire growth directly into daily operations, meetings, and conversations so the work itself becomes the incubator of capability.
3. 3Build a culture that is both 'safe enough and demanding enough' so people 'come out of hiding' — stop covering weaknesses, managing impressions, and doing the unpaid 'second job.' Redirect that recovered energy into growth.
4. 4Make development an 'everyone' project, not a high-potential program. Extend growth conditions to workers, managers, and leaders alike so you do not indirectly write off the 90-95 percent labeled non-high-potential.
5. 5Provide continuous inputs, not punctuated ones. Replace occasional, thin interventions with daily practices, feedback, and coaching woven into the regular flow so learning does not face the transfer problem of returning to 'business as usual.'
6. 6Codify explicit beliefs (like Decurion's 'axioms') that assert adults keep developing past the teenage years, and design structures that 'pull people into greater levels of complexity and wholeness.'
7. 7Treat profitability and human growth as one thing, not a double bottom line — Decurion's phrasing is 'nothing extra is required.' Demand that the culture as a whole be a visible, daily force on behalf of people overcoming limitations and blind spots.
8. 8Surface each person's 'growing edge' and biggest blind spot through structured exercises, then engage the limiting assumptions and defensive routines that block capability, aiming ultimately to transcend them.

At Decurion, before a challenging theater work-group conversation, members take their seats and the room grows quiet — no one peeking at mobile devices or laptops, some settling into silent reflection. This is the culture operationalizing its axioms: work is meaningful (developing oneself, creating something excellent, contributing to others), people are ends not merely means, and adults 'naturally develop.' Dashwood brings everyone together knowing the group must join a hard conversation, putting the bedrock beliefs 'into service' rather than posting them as slogans. No member is required to believe the axioms are true, but each — especially each manager — is expected to act in accordance with them as a job responsibility. The point of dynamic entry is the organization itself, not an add-on: the meeting is the developmental practice. As Bryan Ungard, Decurion's COO, puts it, 'There is no way, really, to be a spectator here. You become a participant the second you enter.'

• If a person holds a belief as unexamined truth (subject), then create conditions to make it an object of reflection rather than arguing them out of it.
• If your development effort is delivered from time to time and outside the work, then you have a twentieth-century additive — redesign it into the daily flow to avoid transfer and cost problems.
• If growth is reserved for the 5-10 percent labeled 'high potential,' then you are writing off the other 90-95 percent — extend the conditions to everyone.
• If the culture is either too safe (no demand) or too demanding (no safety), then people stay in hiding — adjust until it is both safe enough and demanding enough for people to come out.
• If you are trading profitability against human growth as two things, then reframe: pursue them as a single whole where 'nothing extra is required.'

• Copying exemplary practices without a 'crack-the-code' understanding of the theory — the tell: practices are imported wholesale and stall because leaders can't create new ones or adapt when context shifts.
• Making the individual the point of entry (add a coach, program, mentor) while the organizational engine stays unchanged — the tell: development lives in off-sites and returns die on contact with business as usual.
• Treating axioms or values as beliefs people must profess rather than act on — the tell: statements are posted and affirmed but daily behavior and manager accountability don't move.
• Assuming adults are done developing (following literature that 'ends with the teenage years') — the tell: structures aim only at skills/knowledge, never at increasing complexity and wholeness.
• Confusing safe with soft: removing all demand so no one is challenged — the tell: comfort rises, but weaknesses stay covered and no one confronts a growing edge.

• ▸Belief held as subject: name one belief/assumption the person currently cannot see around.
• ▸Object move: how will you help them take that belief as an object of reflection?
• ▸Current daily practice: where in real work does development actually happen (not off-sites)?
• ▸Continuous vs. punctuated: is input daily and in-flow, or occasional and extra?
• ▸Reach: who is included — everyone, or only high-potentials?
• ▸Safe-enough / demanding-enough score: rate each 1-5 and note the gap.
• ▸Axiom-in-action: which stated belief must this person act on, regardless of professing it?
• ▸Biggest blind spot: the growing edge surfaced by exercise or feedback.
• ▸Profit-growth integration: how does this development also serve the business as one thing?

1. 1Diagnose the hidden cost first: estimate how much of each person's day goes to the 'second job' of hiding weaknesses, political maneuvering, and covering imperfections — this is the full-time wage you pay for part-time work.
2. 2Reject the high-potential trap. Do not consign development to executive coaching, off-sites, or 'high potential' tracks; weave development into daily operations, routines, and conversations for everyone.
3. 3Install feedback as a caring, disciplined practice. Have people present regularly in front of peers and leaders and receive detailed, tough feedback in the moment (as Busa does on Super Saturday), framing it as 'investment in loss.'
4. 4Build radical transparency infrastructure: record meetings, make recordings available across the org, and give people a heads-up when their name comes up, so there is 'no closed-door conversation' — everything becomes a historical record of what is true.
5. 5Use 'step-back moments' inside routine meetings to pause, name errors, diagnose their root causes in people's habitual thinking, and identify what each person can do to learn — probe to separate whether the problem is the person or the design of the role/workflow.
6. 6Have leaders set the field by connecting the business challenge to individual meaning and the collective power of the group (Dashwood's opening), tying the work explicitly to top-line goals and personal development at once.
7. 7Require both passions in your design: business excellence AND interest in developing people. Treat culture as strategy and measure results (profitability, retention, speed to promotability, error detection) to prove the developmental route is the superior business route.

At Next Jump, engineers present regularly in front of the company and receive live feedback. On Super Saturday, after Busa addresses forty-four applicants, CEO Kim tells him, 'I could feel your angst. You were too focused on yourself. Focus more on them,' while another listener flags material he omitted. Busa stays calm, nods, agrees, and thanks them — the common response to tough feedback there. He treats this as an 'investment in loss,' the touchstone borrowed from Josh Waitzkin: taking risks and experiencing failure creates the conditions for learning. Busa didn't start here; he first assumed the self-improvement talk was 'only talk.' His turning point came when he saw feedback as people showing they cared, and accepted 'that I have weaknesses' — the moment that changed him at Next Jump. The company had originally recruited for raw smarts and drive and ended up with 'brilliant jerks' and too many solo players, which is what the developmental culture was built to correct.

• If a problem recurs, then probe to determine whether the source is the person's habitual thinking or the design of the role and workflow before assigning blame.
• If someone's limitations are being scrutinized, then encourage them to 'design around' those ways of thinking (using reliable peers) rather than pretend the weakness doesn't exist.
• If your only reason to become a DDO is to be more profitable, then expect your interest to flag — you need both business excellence and a genuine interest in developing people to make it work.
• If a person's name comes up in a meeting they weren't in, then give them a heads-up so they can review the recording — never let it become a closed-door conversation.
• If a leader is opening important work, then set the field by connecting the business challenge to individual meaning and collective purpose, not just by restating the agenda.

• Restricting development to 'select high potentials' via coaching and once-a-year off-sites — the tell: people development is a program line item, not woven into daily conversations and operations.
• Hiring for raw smarts and drive alone and ending up with 'brilliant jerks' and solo players — the tell: individual competitiveness crowds out the leadership-team behavior you actually need.
• Treating feedback as an attack rather than care — the tell: recipients get defensive instead of nodding, agreeing, and thanking, and dismiss the culture as 'only talk.'
• Paying the cost of hidden weaknesses forever — the tell: burnout that traces not to workload but to people going too long without experiencing their own personal development.
• Pursuing DDO status as a cost or non-business agenda — the tell: interest flags because you lack the second passion (business excellence) and never connect development to top-line results.

• ▸Business challenge: state the real work situation the group must work through together.
• ▸Link to meaning: how this challenge connects to individuals' sense of meaning and the group's collective purpose.
• ▸Observed error/limitation: name the specific error or defensiveness surfacing right now.
• ▸Root cause test — person or design: is the source a given person's habits or the definition of the role/workflow?
• ▸Shared data check: confirm everyone is looking at the same facts and shared causal explanation.
• ▸Investment in loss: what risk/failure here is worth it because of what you'll learn.
• ▸Design-around action: concrete step (or reliable peer support) to work around the limitation rather than deny it.
• ▸Feedback given: the specific, direct feedback delivered — and how it was received.
• ▸Business result targeted: the metric this improves (profitability, retention, speed to promotability, error detection, accountability).

1. 1State the conviction as strategy, not benefit: declare in writing that developing everyone is how you produce business results, then treat that sentence as the organizing principle of operations, daily routines, and conversations rather than a values poster.
2. 2Refuse the trade-off framing out loud. When someone asks whether to choose the profit motive or the development motive, answer as the DDO exemplars do: 'You're presuming a tension we don't experience.' Rehearse this response until leaders give it reflexively.
3. 3Wire the conviction into evaluation. Copy Next Jump's 50/50 model — assess every employee equally on contribution to revenue and contribution to the developmental culture — so the belief has teeth in performance data, not just rhetoric.
4. 4Reframe weakness and error as assets. Establish that covering weaknesses is the 'second job' you are eliminating, and that errors and vulnerabilities become prime opportunities for growth — make this the explicit stance in feedback and meetings.
5. 5Extend the aspiration to everyone, not high-potentials. Stop consigning development to high-potential programs, executive coaching, or annual off-sites; assign 'people development' as a job everyone does and everyone builds.
6. 6Anchor edge with the other two legs. Because edge, home, and groove are a three-legged stool, pair the aspiration with a trustworthy community (safety for vulnerability) and sustained practices (habitual surfacing of limitations), or the conviction stays talk.
7. 7Watch for the edge going dull. Institute a check — whenever you catch yourself sacrificing development for profit or vice versa, name it as the warning sign that you've begun treating them as separable and correct course.

Decurion, one of the three exemplar companies, runs a theater business and makes continuous reference to specific operating numbers — it does not ignore targets. Yet when asked how it chooses between profit and development, executive Forman answered: 'For us, pursuing profitability and human development emerges as one thing. We do not see a trade-off, and the moment we consider sacrificing one for the other, we recognize that we have lost both.' That last clause is the operational test in action: the trade-off impulse itself is treated as the failure signal. Next Jump makes the same conviction measurable by evaluating every employee 50/50 on contributions to revenue and to the developmental culture, so 'develop everyone' cannot be quietly demoted when quarterly pressure rises. Together these show the aspiration is not a double bottom line or a both/and — it is a single whole where each motive spurs the other.

• If someone frames a choice as profit versus development, then reject the premise — respond that the tension is presumed, not real, and look for how each motive spurs the other.
• If your development effort reaches only high-potentials, coaching tracks, or annual off-sites, then it is not yet an aspiration — extend it until everyone does people development and everyone builds the culture.
• If you find yourself sacrificing one motive to protect the other, then treat that moment as proof you have lost both, and stop.
• If the conviction appears only in statements and not in evaluation criteria, then it is decoration — bind it to metrics (as in Next Jump's 50/50).
• If you are cultivating edge without trust/safety and sustained practices, then expect it to fail — the stool needs all three legs.

• Treating developmental aspirations as being 'better to our people' — generous benefits, work-life balance, conscious-capitalism gestures. The tell: the program lives in HR perks and never touches operations or the numbers.
• Running it as a double bottom line — two goals held as equally important but separate. The tell: leaders can name a moment they 'balanced' profit against development, revealing they see them as tradeable.
• Restricting growth to select high-potentials. The tell: development is a nomination or a track, not something everyone does daily.
• Aspiration without infrastructure. The tell: people are told growth matters but there is no safe community for vulnerability and no recurring practice that surfaces limitations, so nothing changes.
• Letting the community power distort into control — 'helping people grow' becoming social intrusion or staged rituals of self-criticism ('gold-mining weaknesses' as performance). The tell: growth talk feels coercive or cultlike rather than voluntary and trustworthy.

• ▸Written conviction: one sentence stating that developing everyone is how the business wins.
• ▸Trade-off script: the exact phrase leaders use when asked to choose profit vs. development.
• ▸Evaluation split: how development contribution is weighted alongside revenue contribution (e.g., 50/50).
• ▸Scope check: who is currently included in development — and who is excluded that must be added.
• ▸Weakness stance: how errors/vulnerabilities are named and used as growth opportunities.
• ▸'Second job' target: the specific covering/hiding behavior you are eliminating.
• ▸Loss signal: the observable moment that tells you the edge is going dull.
• ▸Three-legged check: which supporting community practice and which recurring practice anchor this aspiration.
• ▸Guardrail: the safeguard preventing growth work from becoming coercion or staged self-criticism.

1. 1Build a fixed crew for every person, from entry level to CEO: an ongoing group that meets you consistently and is charged with mirroring your blind spots, reactivity, and vulnerability — not with helping you cope. Distinguish this from a conventional support team.
2. 2Open every meeting with a check-in that welcomes the whole person, and close with a check-out where members share feelings, breakthroughs, or a stated need for more support. Make it a standing ritual so attention to individual growth becomes a habit.
3. 3'Set the field' before working the problem: name aloud how the current business challenge ties to each person's sense of meaning and to the group's collective capacity, and speak in a spirit of invitation, not command.
4. 4Create shared reflective records — an issues log for failures and a psychological-pain log for emotions and activated ego defenses — and treat non-reporting as a serious breach. Use the entries to trigger follow-up conversations that diagnose root causes, individual and organizational.
5. 5Destigmatize and even celebrate mistakes so people can experience themselves as still valuable while screwing up; frame each exposed limitation as a 'growing edge' and a company asset to be publicly engaged.
6. 6Deliberately place people in 'useful trouble' — assignments just over their heads — and pair that destabilization with the crew's holding, so the person surrenders an old equilibrium rather than restoring it.
7. 7Weight culture contributions equally with revenue (Next Jump scores each at 50 percent in salary reviews) so that supporting others' growth is structurally rewarded, not a side activity.
8. 8Use low-risk arenas — culture initiatives, giving-back programs, rotating leadership roles — as places to practice leadership and 'fail big' where failure costs less than on the revenue side.

At ArcLight, a manager new to a bigger role admits mixed feelings: excited by the promotion but dreading 'wrestling with all those feelings of inadequacy and uncertainty all over again.' In most companies 'good fit' would mean she can do the job as described, and a good team would try to reduce her destabilization and restore her equilibrium. In a DDO that would be seen as doing her no service. Instead the fit is defined as: she will run into plenty of useful trouble, will know how to learn from it, and will draw on a supportive community to help. Managers use 'energy maps' to assign each week's work to maximize both her growth and the operation's needs, and always discuss not just where to place people but why. Her crew holds her while she is 'out on a rope without a net,' so the discomfort becomes palatable — not through individual fortitude but through a culture that is extraordinarily supportive underneath its provocation.

• If a team member is destabilized by being over their head, then hold them through the vulnerability rather than helping them restore the old equilibrium — coping is not development.
• If someone exposes a limitation or mistake, then treat it as a company asset (their growing edge) to be publicly engaged, not as a failing to be hidden or guardrailed away.
• If a weakness has no realistic chance of changing, then guardrail around it and leverage strengths instead of forcing growth there.
• If you are opening or closing any meeting, then run a check-in and check-out so individual presence and humanity stay in view.
• If a person feels only accepted OR only challenged, then adjust: growth needs both being included and accepted while incomplete AND being genuinely destabilized.

• Building a 'good team' that offers moral support to reduce stress and restore normalcy — the tell: members leave meetings feeling comforted but never confronted with their blind spots.
• Treating destigmatizing mistakes as slogans while people still hide weakness — the tell: the issues log or pain log is empty or sanitized, and no follow-up conversations happen.
• Confusing 'good fit' with 'can do the job as described' — the tell: assignments are chosen to keep people in mastered routines rather than to create developmental pull.
• Rewarding only revenue contribution so culture and peer-development work quietly deprioritizes — the tell: people volunteer for meaning outside work because the job itself doesn't count it.
• Provoking without support, expecting individual fortitude to carry people through discomfort — the tell: people feel 'out on a rope' with no net and no crew holding them, and burn out or disengage.

• ▸Person / role: name and current role (entry to CEO — everyone has a crew).
• ▸Crew members: who consistently mirrors this person's blind spots and reactivity.
• ▸Growing edge: the specific limitation currently exposed and being engaged publicly.
• ▸Useful trouble: the assignment placing them just over their head this week, and why.
• ▸Check-in prompt: opening question that welcomes the whole person.
• ▸Check-out prompt: closing share of feeling, breakthrough, or need for support.
• ▸Field-setting note: how today's business challenge ties to their meaning and the group's collective work.
• ▸Log trigger: the issues/pain-log entry that should spark a follow-up root-cause conversation.
• ▸Support signal: what tells you they need the crew to hold — not reduce — the destabilization.

1. 1Name the two work streams explicitly to your team: the first job (the actual role) and the 'second job no one is paying you for' (covering weaknesses, managing impressions, hiding limitations). Groove practices exist to reclaim the energy lost to the second job, so start by making that waste visible.
2. 2Embed development into existing operations rather than bolting on extras. Take the routines you already run — meetings, feedback, role definitions — and redesign each so it doubles as a forcing bed for growth. Do not add off-sites, retreats, or a high-potentials program as substitutes.
3. 3Design each practice around the four Groove principles: destabilization can be constructive, mind the gaps, set the time scale for growth (not closure), and treat interior life as part of what is manageable. Every recurring routine should serve at least one of these.
4. 4Make the practices continuous and daily, not annual. Convert once-a-year reviews into regular, structured feedback disciplined enough to surface growing edges in the ordinary flow of work.
5. 5Anchor destabilizing practices in a trustworthy community (Home) — practices and trustworthy community nurture each other. Introduce vulnerability-surfacing routines only where rank has been stripped of its usual privileges and shared vulnerability is expected of everyone.
6. 6Treat error and weakness as operational inputs. Build the routine so that when a mistake surfaces, the next step is examining the limiting assumption or defensive routine behind it, not assigning blame.
7. 7Extend every practice to everyone — workers, managers, leaders. The Groove only works at scale; carving out development for 'high potentials' recreates the ordinary organization.
8. 8Aim practices at limiting assumptions and defensive routines, not just skills. Use them to help people uncover, engage, and ultimately transcend the assumptions that cap their capability below their own expectations.

The three DDOs studied redesigned ordinary routines into developmental practices. Rather than consigning growth to executive coaching or annual off-sites, they wove development into meetings, feedback, and how managers define their roles. Their feedback is described as disciplined — a regular practice, not an event — so a person's growing edge surfaces in the normal course of work. Notably, only one of the three had explicitly studied the developmental science; the other two arrived at effective practices through an intuitive, practical grasp of how to accelerate growth. This is why the authors insist on a 'crack-the-code' understanding of the underlying theory: with it you can invent practices that don't yet exist, rather than blindly copying an exemplar's routines. The result across all three was concrete business gains — better error detection, greater frankness in communication, and more effective delegation — because energy formerly spent hiding was redirected into the work.

• If a proposed practice happens only annually or applies only to select people, then it is not a Groove practice — redesign it to be daily and universal.
• If a routine destabilizes people but no trustworthy community holds them, then stop — shared vulnerability without Home produces threat, not growth.
• If someone surfaces an error or weakness, then treat it as a prime opportunity and a potential asset, not a performance failure.
• If you are copying an exemplar's practice without understanding the developmental theory beneath it, then you will misapply it — build the conceptual understanding first.
• If a practice pushes for quick closure, then reset it: set the time scale for growth, because development is not resolved on a deadline.

• Bolting development onto the side (coaching, retreats, high-potential tracks) while the daily fabric of work stays unchanged. The tell: development lives on a calendar or in a program, not in ordinary meetings and conversations.
• Copying exemplar practices without the underlying theory. The tell: practices are followed as ritual but no one can explain which limiting assumption or defensive routine they target.
• Introducing vulnerability-surfacing routines before Home exists. The tell: people go quiet, manage impressions harder, and the second job intensifies instead of shrinking.
• Pushing for resolution and closure too fast. The tell: growing edges get 'fixed' and closed rather than sustained over a realistic time scale, so no real development sticks.
• Reserving the practices for managers or high potentials. The tell: rank still carries its usual privileges and most people never do people development on themselves.

• ▸Existing routine to convert: name a meeting, review, or process you already run
• ▸Second-job energy it currently wastes: what hiding/impression-managing does it provoke?
• ▸Growing edge targeted: which individual or collective limiting assumption should it surface?
• ▸Groove principle applied: destabilization / mind the gaps / time scale for growth / interior life
• ▸Home safeguard: what makes shared vulnerability trustworthy here (how is rank neutralized)?
• ▸Frequency: how does this become daily/regular rather than annual?
• ▸Scope check: how does it apply to everyone, not just select people?
• ▸Error-as-asset step: what happens the moment a weakness or mistake surfaces?
• ▸Business signal watched: which outcome (error detection, frankness, delegation, retention) tells you it works?

1. 1Establish that everyone works on a weakness, from cofounders to newest hire, so no one is singled out — at Next Jump each person names a 'backhand' (arrogance/overconfidence or insecurity/overhumility). The universality is what makes disclosure safe.
2. 2Name and normalize the work with a shared vocabulary and recurring routines ('backhand,' 'gold-mining weaknesses,' immunity-to-change exercise). A named practice signals that risk-taking is the game everyone plays by the same rules, not an ambush.
3. 3Front-load the safety at entry: run a boot camp (Next Jump's three-week Personal Leadership Boot Camp) where new hires — even senior ones — identify weaknesses while doing bread-and-butter customer service, so adapting to the culture happens at the easiest moment for growth.
4. 4Model disclosure from the top down: have bosses open up about their own weaknesses first (David and Jackie opened up to each other), creating a second context where a person can question their patterns.
5. 5Design jobs to not be 'person-dependent' so no one gains status by hoarding information or being the indispensable expert — removing the incentive to protect a fiefdom removes a reason to hide.
6. 6Convert disclosure into deliberate practice with concrete micro-behaviors: an 'arrogant' person waits until the 45-minute mark to speak in an hour-long meeting; an 'insecure' person contributes within the first 15 minutes.
7. 7Create low-stakes venues for public risk (Next Jump's 10X all-staff meeting) where people present and get live feedback, so members repeatedly learn 'if I show a weakness, nothing too bad happens, I'll probably learn something.'
8. 8Assign helping-others practice (Better You / coaching) so the satisfaction of supporting others' growth reinforces the safety loop; start small and increase frequency as comfort grows.

Jackie, a Next Jump marketing manager, was voted off the company's leadership group and told her backhand was arrogance. She only reached her real weakness when she said the painful, embarrassing version out loud: 'I am selfish, and I put my success above everyone else's... I left hundreds of Next Jumpers behind in my quest to get to the top.' Her boss David created the safety by opening up about his own weaknesses first, giving her a context to describe the backhand in her own words rather than others' labels. She then declared this publicly at a 10X all-staff meeting, exposing a genuine vulnerability in front of the whole company. Rather than facing negative consequences to status, she began deliberate practice — coaching others once a month, then weekly, though 'even that was painful for me at first.' The environment where everyone is 'in it together' made the disclosure a growth step, not a career risk.

• If a person names a weakness in others' words rather than their own, then keep going — the true backhand is the version that is painful and embarrassing to say out loud.
• If only managers and leaders are working on weaknesses, then safety collapses; require that senior people (cofounders, VPs, 40-year veterans like Dashwood) are as visibly engaged in the growth journey as the newest hire.
• If someone gains advantage by hoarding information or being the indispensable expert, then redesign the job to be non-person-dependent so hiding is no longer rewarded.
• If a practice makes an outsider recoil, then ask what specifically feels at risk — the same practice reads differently when everyone is in it together versus singled out.
• If disclosure isn't followed by a named routine and repeated low-stakes practice, then it's a one-off confession, not psychological safety — attach it to a recurring venue with live feedback.

• Treating weakness-work as a leadership tool applied downward, not universally — the tell: the newest hires are 'gold-mining' but the VPs are protecting their roles and identities.
• Letting 'gold-mining weaknesses' devolve into staged rituals of self-criticism or social control — the tell: disclosures feel performed and coerced rather than volunteered, and people give you the creeps rather than tearing up.
• Stopping at others' labels for a person's weakness — the tell: the description isn't painful or embarrassing to the person; it hasn't reached their own words like Jackie's shift from 'arrogant' to 'selfish.'
• Providing safety without demand (or demand without safety) — the tell: people are comfortable but not at their growing edge, or pushed hard with no supportive community, so they retreat back into hiding.
• Skipping the top-down modeling — the tell: employees are asked to expose weaknesses while the boss never opens up about his own, so no one believes disclosure is actually safe.

• ▸My backhand in others' words: the weakness label people give me
• ▸My backhand in my own words: the painful, embarrassing version I can say out loud
• ▸Direction: am I overconfident ('arrogant') or overhumble ('insecure')?
• ▸Micro-practice behavior: one concrete meeting move (e.g., wait to 45 min / speak within 15 min)
• ▸Who models first: the senior person who will disclose their weakness before mine
• ▸Public venue: the recurring meeting where I'll share and get live feedback (e.g., 10X)
• ▸Better You practice: who I'll coach and how often, starting small
• ▸Job-design check: does anyone gain status here by hoarding info or being indispensable? Fix:
• ▸Everyone-in-it check: is this expectation applied to leaders and newest hires alike? Y/N

1. 1Name the second job out loud in your team so hiding stops being invisible. State the premise: in most organizations everyone spends time covering weaknesses, managing impressions, playing politics, and hiding limitations — and this is the biggest daily loss of resources.
2. 2Weave development into daily operations, not into annual off-sites or high-potential programs. Make disclosure of limitations a routine feature of regular meetings and conversations, so surfacing a weakness is normal work rather than an exception.
3. 3Select for the disposition that makes cessation possible. Screen candidates for humility (willing to learn from others to grow), grit, and givers-over-takers — and screen out 'brilliant jerks' who default to arrogance and self-protection.
4. 4Give everyone a shared vocabulary for their own tendencies. At Next Jump, everyone can state whether they lean toward arrogance or insecurity; naming the tendency removes the need to hide it.
5. 5Run diagnosis before solution. When a mistake surfaces, hold the group to unearthing the limitations in thinking behind it ('the deeper whys' / root causes) rather than jumping to fix the behavior.
6. 6Discuss individual reviews with the whole team in total candor so that 'nothing in a formal review comes as a surprise.' Continuous multi-source feedback means there is no impression left to manage.
7. 7Have leaders and managers redefine their roles to model disclosure first — treat errors and vulnerabilities as prime opportunities for growth, so employees see self-protection has no payoff.

At Bridgewater, the training team runs a Friday 'diagnosis' meeting centered on Sergio, whose recent review the whole group has already discussed. Sergio openly admits he 'feels an acute need, almost at random, to please others' and worries about 'pleasing whoever is in front of me' — an admission of weakness that in an ordinary organization he would hide. Earlier in the week he had led a meeting and delegated the slide deck to a teammate, Virginia, and the group uses the diagnosis to trace his actions back to that people-pleasing tendency rather than to critique the behavior alone. The point is not to solve Sergio's problem but to systematically surface the limitations in thinking behind it — the 'deeper whys.' Because individual reviews are discussed with the entire team with total candor and feedback flows daily from multiple sources, 'nothing in a formal review comes as a surprise.' This is what the cessation of impression management looks like in practice: the energy Sergio would spend hiding is spent instead on his own development, in front of his colleagues.

• If a mistake surfaces, then diagnose the limitation behind it before designing any solution — keep the steps distinct and unblurred.
• If a candidate looks technically strong but shows arrogance, self-absorption, or is a 'taker,' then decline the hire regardless of raw smarts.
• If a review's contents would surprise the person receiving it, then your feedback flow is too infrequent — increase daily, multi-source feedback until surprises disappear.
• If development lives only in high-potential programs, coaching, or annual off-sites, then it is not yet woven into operations — move it into regular meetings and routines.
• If someone discloses a weakness and it is used against them, then you have re-incentivized hiding — treat the disclosure as an opportunity for growth instead.

• Confining development to 'high potentials' — the tell is that programs target select individuals, and the rest of the workforce keeps hiding because growth support isn't for them.
• Hiring for raw smarts and drive alone — the tell is a workforce of 'solo players' and 'brilliant jerks' with plenty of arrogance who protect their image.
• Jumping from mistake to solution — the tell is the group discusses fixes without ever naming the limitation in thinking that produced the error.
• Reviews that ambush people — the tell is surprise or defensiveness in a formal review, meaning candid feedback wasn't already flowing daily.
• Leaders who demand transparency but never disclose their own limitations — the tell is that admissions of weakness flow up the org chart but never down from managers.

• ▸Hiding behavior observed: name the specific covering/impression-managing act you saw
• ▸My leaning (arrogance / insecurity): state your default self-protective tilt
• ▸Weakness I usually hide: write the limitation you spend energy covering
• ▸The deeper why: root cause in thinking behind the recent mistake, not the behavior
• ▸Diagnosis (not solution): what limitation this reveals — keep separate from any fix
• ▸Whole-team disclosure: who else needs to hear this candidly and when
• ▸Development opportunity: how this error becomes a growth prompt
• ▸Recurrence check: is this showing up in daily feedback before formal review? yes/no