35+ frameworks and tools for building organizations where people can do meaningful work — tested and refined across my 20+ years of practice.
Execution Capacity
01Execution CapacityVariable commitment
OKRs & Goal Setting
Here's something I've noticed across a lot of organizations: most people are working incredibly hard in directions no one has formally agreed to. OKRs and goal-setting frameworks create a shared, transparent picture of where you're actually headed — and give managers a simple structure for the conversations that matter most: are we doing the right work? The right framework is not the most sophisticated one. It's the one your organization will actually use.
Before You Start
Leadership alignment needs to be underway before any goal-setting framework will hold. The framework also needs someone who owns the process and a check-in rhythm to keep it alive. Start by diagnosing the specific problem you're trying to solve — because goals aren't clear, teams are pulling in different directions, or strategy exists but doesn't connect to daily work all point to different interventions. Start with the lightest version that will actually hold. One working layer is worth more than three broken ones.
Intensity Spectrum
Light
Strategic Priorities. A short list — six to eight things — of what the organization is working toward this year. Leadership drafts them, shares them with all staff, and grades them honestly at year end. Lightweight and surprisingly effective as a first step toward shared direction. Start here when alignment is fragile or the organization hasn't tried structured goal-setting before.
Medium
OKRs. One Objective per team or initiative per quarter. The Objective is qualitative, directional, and time-bound. Three Key Results per Objective — measurable and outcome-based. Monthly check-ins. 70% completion is a win. Appropriate when alignment is established and the org is ready for more structured accountability.
Deep
Cascading OKRs. Team-level objectives explicitly connect to org-level objectives, creating visible line of sight between someone's daily work and the organization's most important priorities. Appropriate for orgs at full operational maturity who need cross-team alignment.
How to Run It
1
Diagnose the specific problem first. Goals aren't clear? Start with Strategic Priorities. Teams misaligned? Introduce OKRs with explicit cross-team dependencies. Strategy exists but doesn't connect to daily work? The issue is likely the check-in rhythm, not the framework.
2
If starting with Strategic Priorities: draft the list with leadership, make it genuinely short, share it with all staff, and schedule an honest grading session at year end. The grading conversation is as important as the drafting.
3
When you're ready for OKRs: draft one Objective per team or initiative. The Objective should be qualitative, directional, and time-bound — not "improve fundraising" but "build the infrastructure that makes contributed revenue sustainable at $2M."
4
Write three Key Results for each Objective. Here's the test: if you can check a box to complete it, it's a task, not a Key Result. "Launch the new grant reporting system" is a task. "85% of program staff report having the information they need for grant compliance within 48 hours of a deadline" is a Key Result.
5
Bring the draft to the leadership team with one question: does this reflect our actual priorities? Then ask the harder question: is there work happening that connects to none of these OKRs? If yes, that work is either missing from the OKRs or it shouldn't be happening.
6
Publish them. OKRs that live in one person's folder don't exist. Post them in your all-staff channel, share them in a shared drive, consult them in every check-in that involves prioritization. The visibility is the mechanism.
7
Build a monthly check-in rhythm. In each check-in: current status of each Key Result, what's blocking completion, and what needs to change. The framework doesn't do the work. The conversations it structures do the work.
8
Score honestly at quarter end. 70% completion is a win. 100% means the targets were too easy. 30% means something structural went wrong. At the end of each cycle, run a retrospective: what happened, what didn't, and what did you learn about how you set goals?
What Good Looks Like
People start using the framework as a filter for decisions rather than a reporting obligation. Managers reference goals in check-ins without being prompted. When someone asks "why are we doing this?" the answer connects to a Key Result. Goal-setting becomes a rhythm embedded in the operating calendar rather than an annual event followed by months of drift.
Watch Out For
The check-in rhythm. Without it, OKRs drift into dusty documents within 60 days. Every single time. Also watch for Key Results that are actually tasks dressed up in measurement language — they feel rigorous but they're not measuring whether anything changed. And watch for choosing the most sophisticated framework rather than the one the organization will actually use. If you've run OKRs twice and they keep dying, that's not a discipline problem. It's a fit problem.
Every organization I've worked with has them: projects and initiatives that aren't really dead but aren't really alive either. They show up on meeting agendas without producing anything. They consume attention without receiving resources. They exist in a kind of organizational purgatory because nobody wanted to be the one to name them as done — or even remembers they exist but might still be taking staff time. This is how you name them.
Before You Start
Leadership must be genuinely willing to publicly end things. This process only works if it produces real endings. A list of concerns without decisions is just a complaint session. Also required: enough psychological safety for staff to name zombie work without political consequence. In most organizations, surfacing a zombie is a small act of organizational courage.
How to Run It
1
Name the pattern before trying to fix it. In most organizations, zombie work accumulates because people become emotionally attached to ideas and have a hard time letting go. Opening the session by naming this dynamic — including the leader's role in it — shifts the conversation from blame to honest diagnosis.
2
Open a submission process: any staff member can nominate work they think might be a zombie — something they can't confirm is still active, something nobody seems to be prioritizing, something that appears on meeting agendas but never moves. A simple form or dedicated Slack channel works.
3
Collect submissions for one to two weeks without filtering. Let everything come in.
4
Bring the full list to leadership for a dedicated two-hour session. For each item, ask two questions: Is this still active? If yes, who owns it and what is the next concrete action by when? If it can't answer both questions, it's a zombie.
5
Sort everything into three categories: Active (clear owner, clear next action), Paused (intentionally shelved with a specific revisit date), Dead (officially ended).
6
Communicate results to all staff: here is what we've decided to end, here is what is still active and who owns it, here is what is intentionally paused and when we'll revisit. This communication is as important as the decisions themselves.
7
Build a Quarterly Loose Ends Audit into the operating calendar as a standing agenda item at every quarterly offsite. New zombies accumulate constantly.
What Good Looks Like
People report feeling relieved. The ambient cognitive load of "I'm not sure if we're still doing that" lifts. Teams can pursue fewer things with more intention. Meetings stop carrying the ghost of old initiatives.
Watch Out For
Running a zombie process that doesn't produce any actual endings. A facilitated discussion that results in everything being "paused for further consideration" is not a zombie process. If leadership won't commit to killing things, don't run the process.
The Onion ran a headline once that read: "Company Employees Spend Entire Day Touching Base." The joke was that it's hard to tell if that's satire or a Tuesday. Most organizations have more meetings than they need, and fewer of the right kind. The Meeting Architecture isn't about having fewer meetings. It's about having the right meetings for the right purposes — so that when you're in a room together you're doing something that actually requires being in a room together.
Before You Start
Leadership buy-in that the disruption of redesign is worth it. Shared goals to anchor the cadence. A weekly tactical without shared goals becomes a status update parade within 60 days. The architecture and the goals need to be designed together.
How to Run It
1
Audit every recurring meeting. For each one: what is the stated purpose? What does it actually do? Would the organization function better if this meeting didn't exist? Be honest. Try not having it for a quarter and see what happens.
2
Separate by type and function. A daily check-in is 10–15 minutes: blockers and coordination, no problem-solving. Weekly tactical is 60 minutes: current week's priorities, decisions that need to be made, issues that need resolution. Monthly strategy is 2–3 hours: one strategic question, no operational content. Quarterly offsite: reflection, planning, and team health. Annual all-staff: culture, direction, acknowledgment, and celebration.
3
Map your current meetings against these types. What's missing? What's doing double duty? What meeting would everyone be relieved to cancel?
4
Make one change first. Don't redesign all meetings simultaneously. Start with the meeting everyone dreads most and make it better.
5
Give every recurring meeting a consistent agenda. An agenda is a signal about what the meeting is for. Without one, every meeting becomes whatever feels most urgent that day.
6
Build a standard close for every meeting: last five minutes, three questions. What did we decide? Who is doing what by when? When do we check back on this?
7
Use the WSS meeting templates as starting points. Templates for Regular Team Meetings, All-Staff Meetings, and Visiting Professionals Series are available.
What Good Looks Like
Fewer meetings and better ones. People come prepared because they know what the meeting is for. Decisions get made rather than deferred.
Watch Out For
Redesigning the meeting architecture without OKRs to anchor it. A weekly tactical without shared goals becomes a status update parade. The architecture and the goals need to be designed together.
Most organizational knowledge lives in people's heads. Which would be fine if people stayed forever, but they don't — and then we act surprised when things fall apart after they leave or it takes enormous effort to get new people up to speed. The Duties and Responsibilities Checklist is how you make the implicit explicit before the moment of crisis makes it impossible to do carefully.
Before You Start
Identify the highest-risk roles first: the most specialized, the least redundant, the ones whose departure would cause the most immediate chaos. This works best when there's a concrete event: someone is leaving, going on sabbatical, getting promoted, or a new role is being defined. In the abstract it feels like bureaucracy. Attached to a real moment, it becomes essential.
How to Run It
1
For each role you're documenting, sit with the person currently in it. Start with this question: if you left tomorrow, what are the ten things that would fall apart immediately? That's your starting point, not a job description template.
2
Map responsibilities across four dimensions: what the work is, how frequently it happens, how important it is relative to other responsibilities, and where the relevant files and relationships live.
3
For job description drafting, use the checklist output as your first draft. The checklist surfaces what the role actually requires before anyone starts wordsmithing a posting. It prevents posting a job that describes the person who's leaving rather than the role the org actually needs.
4
For leave planning — parental, sabbatical, medical, or military — the checklist becomes a transition document. The checklist makes the implicit explicit before the stress of departure makes careful thinking impossible.
5
For arrivals, build a reading list from the checklist output. Not just links — annotated links: "Read this because it explains how we make decisions about X." That addition turns a link dump into an orientation.
6
Test it. Have someone unfamiliar with the role try to follow the documentation for one week's work. Where do they get stuck? Those gaps are what you fill before anyone actually needs to use it.
7
Update it twice a year at minimum, or at any significant role change. An outdated checklist actively misinforms at the moment someone most needs accurate information.
What Good Looks Like
When someone goes on leave or departs, their replacement describes feeling set up for success rather than dropped in. New hires can find things. Institutional knowledge that used to live in one person's head now lives somewhere others can access.
Watch Out For
Trying to document every role simultaneously. This project dies from scope creep every time. Document the three roles whose absence would hurt most. Get those working well. Expand from there.
Managing people is one of the most consequential jobs in any organization, and we prepare people for it roughly the way we prepare people for most consequential things: we don't. Someone does a good job as an individual contributor, so we promote them into a role with completely different demands and then act surprised when it's hard. The Managers Support Group is a peer cohort that combines a structured HR knowledge curriculum with space to bring real situations, learn from each other, and not feel alone in the hardest parts of the job.
Before You Start
Executive buy-in that manager development is a real organizational priority, not a scheduling nice-to-have. Protected time in managers' schedules. And critically: leadership modeling the behaviors it's asking managers to practice. If the executive team doesn't have difficult conversations early, doesn't document performance concerns, and doesn't manage consistently, sending managers to a support group asking them to do those things is asking them to do something the organization clearly doesn't actually value.
How to Run It
1
Identify who actually carries management responsibility. Not just people with "Manager" in their title, but everyone who holds performance accountability for other people, whatever their title says.
2
Run a quick needs assessment: a short survey asking managers where they feel least prepared. Answers cluster around three areas almost every time: difficult conversations, legal basics, and understanding what to handle versus what to escalate.
3
Build the support group structure first. This is not a class with a teacher. It's a cohort of peers who meet regularly — managers only. The peer dynamic is the product. People share real things in a room of peers that they would never share in a mixed room.
4
Weave HR knowledge through the peer sessions rather than front-loading it as lectures. Core HR knowledge areas: legal obligations of supervisors, documentation practices, leave administration basics, how to structure a difficult conversation, what constitutes harassment and discrimination under the law, and the difference between what's yours to handle and what requires escalation.
5
Between formal sessions, maintain a channel where managers can bring real situations as they happen. The day-to-day texture of management is where most learning occurs.
6
Pair with the Behavior Dashboard (Tool 32) so managers have a shared, visible picture of what strong performance looks like at this specific organization. The support group builds the skill; the dashboard provides the standard.
7
Revisit the curriculum content annually. Employment law changes, org context changes, and what managers need in year two differs from year one.
What Good Looks Like
Difficult conversations happen sooner. Managers stop escalating everything upward because they've built the judgment to know what's theirs. Performance issues get addressed before they become crises. And managers describe feeling less isolated in the role.
Watch Out For
Expecting managers to model behaviors the executive team doesn't practice. The fastest way to undermine a Managers Support Group is to hold managers accountable to standards leadership exempts themselves from.
In a lot of organizations, someone became responsible for HR the way people become responsible for a lot of things: not because they were prepared for it but because it needed to happen and they were there. This curriculum is for that person. Not a full HR certification. Just enough legal knowledge, practical tools, and values-based framework to stop doing accidental harm and start doing intentional good.
Before You Start
This is a bridge tool, not a permanent solution. It buys responsible time for an organization that has grown past the point where accidental HR is safe. Identify who is actually doing HR work right now and build the curriculum around their actual responsibilities. Have the honest conversation about whether the org has grown past the point where this bridge is enough.
How to Run It
1
Audit what HR work is actually happening and who is doing it: hiring, onboarding, leaves, performance management, offboarding, benefits administration. For each, ask honestly: is this being done with enough knowledge to avoid legal exposure and treat people fairly?
2
Map the highest-risk gaps. Legal exposure clusters around leave administration (FMLA, ADA, state-specific paid leave), hiring compliance (what can and cannot be asked in interviews), and terminations (final pay timing, notice requirements, documentation).
3
Phase 1 is HR Essentials: employment law basics, leave administration and documentation, hiring process compliance, performance documentation, and knowing when to escalate to legal counsel.
4
Phase 2 is Values-Based HR Practices: how we operationalize commitments rather than simply state values. It's a lens applied to every HR decision.
5
Phase 3 is Practical Application: tools, templates, and scenarios. Participants leave with things they can use next week.
6
Identify a trusted employment attorney or certified HR professional before you start. The goal of the curriculum is to know when to handle something yourself and when to pick up the phone. A relationship with legal counsel is a prerequisite for doing HR responsibly at any scale.
7
Build in a refresh cycle. Employment law changes. The curriculum needs a designated owner and a review schedule.
What Good Looks Like
The person doing HR work feels grounded rather than improvising. Legal exposure decreases. HR processes become more consistent. People describe being treated more fairly.
Watch Out For
Treating this as a substitute for the HR hire the organization actually needs. This curriculum buys time. It doesn't replace the strategic conversation about whether the org has grown past the point where accidental HR is a responsible model.
One of the things I appreciate most about the self-assessment framework is the underlying premise: none of us are at our organizations forever. And one of the disservices organizations do is pretend otherwise, which makes the conversation about where people want to go feel like a threat rather than a natural part of working together. This process is designed in part to normalize that conversation.
Before You Start
Role expectations need to be clear, and nothing in the self-assessment should be a surprise. Feedback should be happening throughout the year. The Duties and Responsibilities Checklist and Behavior Dashboard need to be in place. You can't self-assess against a standard you don't understand.
How to Run It
1
Start with the design question: what do you actually want people to reflect on? The answer should cover three things: accomplishments against shared goals and role responsibilities; values in practice (not just what you did but how you did it); and a forward look where people want to be professionally in three to five years and how current work can help them get there.
2
Add a question that normalizes eventual departure: "Where do you want to be professionally when you grow up?" This question signals that the organization sees staff as whole professionals with careers. It opens real dialogue and surfaces retention risks early, when there's still time to address them.
3
Build in manager calibration. Managers complete their own assessment of each direct report before the conversation, then compare it with the self-assessment. The gaps between the two documents are the most useful data in the process.
4
Run the cycle annually at minimum. For roles with significant change or development trajectories, semi-annual is better.
5
After the first cycle, review the aggregate data, anonymized: what themes are emerging? Where are the gaps between stated values and observed practice? This is your culture signal at scale.
6
Iterate the process based on what you learn. The first cycle reveals what the template is actually measuring. The second cycle, you redesign based on that.
What Good Looks Like
People come to the conversation rather than dread it. The "where do you want to be" question generates real dialogue about career direction. Managers describe being less caught off guard by departures because the forward-looking questions surface signals early.
Watch Out For
Running this process when role expectations are still unclear. Self-assessment against an ambiguous standard produces either performance theater or anxiety. Clarity of role comes first.
Most organizations describe themselves as strategic about hiring. And then you look at what actually happens when someone leaves or a new need surfaces, and it's largely a scramble. The When to Hire Rubric is a simple discipline that slows that scramble down enough to ask: is this actually the right hire, and are we defining the right role?
Before You Start
The rubric only works if leadership commits that no hire proceeds without completing it first. Not sort of commits. Actually commits. A rubric that can be bypassed when someone feels urgency is not a consistent approach. One person needs to own the process.
How to Run It
1
Before any "we need to hire someone" conversation gains momentum, pause and complete the rubric with the hiring manager. Core questions: Is this work permanent or temporary? Full-time, part-time, fractional, or contracted? What specific problem will this role solve? Is this work currently being done, and if so, by whom and why isn't that working? Are we hiring another role as a workaround to someone who isn't doing what we need them to do?
2
Ask the harder question: what would happen if we didn't make this hire? If the honest answer is "nothing we can't live with for another quarter," the hire probably isn't urgent. If the answer is "specific critical work would stop happening," that's a real hire.
3
Define the role based on the rubric output, not on a recycled job description from a prior iteration. The rubric answers change the job description.
4
Identify the hiring process before the search begins: structured interviews, skills assessment, work sample, panel review. These decisions get made before applications arrive, not improvised during screening.
5
Document who makes the final hiring decision and what their authority is. Ambiguity about who decides is the source of more hiring process failures than almost anything else.
6
Check back against the rubric before extending an offer. Did the role we ended up hiring match the role we defined? If it shifted significantly, name why and whether that shift was legitimate.
What Good Looks Like
Hiring feels like a discipline rather than a scramble. Managers start thinking structurally about how work gets done before they think about who will do it. Job descriptions become honest about what the role actually requires.
Watch Out For
Completing the rubric as a formality and then proceeding with the hire that was already decided. The rubric's value is specifically in the constraint it creates. The friction is the feature, not a bug.
Traditional onboarding is transactional and siloed: meet everyone briefly, set up the portals, learn the systems, complete the compliance trainings, then spend the next several months figuring out the rest on your own. It's also typically designed in service of acquainting the new employee to the full spectrum of the organization and their job as quickly as possible — "we know you're drinking from a firehose, but while you're at it, please also create the budget." Exponential onboarding starts from a different premise: what if the onboarding process were designed as a way to learn about the organization on the job, in service of the key objectives of the role?
Before You Start
Someone needs to own the onboarding process actively — not in addition to twelve other things. Basic knowledge documentation needs to exist before you can build a meaningful onboarding experience. Start with the roles where slow or shallow onboarding is most costly: leadership positions, senior roles, and highly specialized positions. And reconsider the 90-day assumption. In many organizations, it actually takes a full year before the patterns start to repeat — programming and budgeting cycles, seasonal hiring — and someone can truly learn from experience rather than through it.
Traditional vs. Exponential
Traditional Onboarding
Exponential Onboarding
Transactional approach to meeting the team, often unaware of how the new supervisor's positional power shapes the process
Relational approach that promotes inclusivity, compassion, humility, and respect
A learning checklist to cover "all the bases" in a short time period
Relevant, incremental learning and collaboration based on real-time priorities and emerging understanding
Drinking from a firehose
Building the plane while you're flying it
Promotes hierarchical power dynamics: new leader reviews materials, may or may not conduct a listening tour, then communicates their plan
Considers how power and influence flow in the team and organization, and builds structures to invite diverse perspectives to inform a shared plan
Urgency prevails. The new leader is swept off and rolling without time to reflect and implement intentional foundations
Development of realistic work plans with consistent feedback loops to regularly review, reflect, and reframe learning and the path ahead
Guiding Principles
Transparency
Making relevant information available as early as possible, and as needed throughout the process, respects the time, energy, and investment of the new team member and those they interact with.
Curiosity
Approaching the goals of onboarding with curiosity allows you to imagine approaches to the work you might not have otherwise considered.
Consistency
Learning during one onboarding process can inform and be replicated for others coming into the organization. Onboarding does not have to be a choose-your-own adventure.
Diverse Perspectives
Mechanisms to invite diverse perspectives throughout the process surface and challenge assumptions, and encourage critical thinking that leads to creative but data-informed decisions.
Distribution of Power
Awareness of traditional power dynamics and development of strategies to share power more equitably promotes a sense of safety and builds relational trust.
How to Run It — Three Phases
Phase 1 — T-30: Before Day One
What can and should be done before an official start date to make it feel different? Rather than someone being "shot out of a cannon" on Day 1, what questions and conversations can begin in advance so the first official day feels like an exciting but natural extension of work already underway? Consider how to kickstart relationships, make the new person a familiar presence, and invite them to begin informing their own understanding before the role officially begins. Set up the decision and meeting type frameworks in advance. Focus pre-start meetings on getting to know each other and big-picture context — save tactical coordination for after the start date.
Phase 2 — Day 1–30: Wayfinding
Phase 2 shifts to the new team member being onsite: figuring out the physical ins and outs of space and community, getting to know people in person, understanding the informal power and influence dynamics among direct reports and across the team. Big questions for this phase: how do we look for and integrate moments to pause and begin testing alternatives? How can the new leader employ meeting and decision frameworks so every coffee or lunch doesn't feel like the weight of the role rests on it? Assign an onboarding buddy who is not in the direct management chain — someone new staff can ask basic questions without worrying about how they'll be perceived.
Phase 3 — Day 31–90: Decisions of Consequence
After the rush of wayfinding, Phase 3 is when someone in an executive role is often expected to begin making "decisions of consequence." Rather than defaulting to the traditional heroic-leader model — take in information, rapidly pronounce decisions — what processes and practices signal a values-centered approach? Where are the recurring pain points and moments to pause? How are feedback loops operating? Build formal check-ins at 30 days and 60 days with a consistent question: what's confusing, and what's missing from what you've been given? Use the answers to iterate the onboarding system. Archive the whole thing in one accessible location.
+
The 12-month arc. Consider the full year as the true onboarding arc. It's at the 12-month mark that many patterns first repeat — programming and budgeting cycles, seasonal hiring — and where learning from the last cycle can be absorbed and replicated or adapted. Build a rhythm of check-ins and reflection into the full year, not just the first 90 days. For complex roles, create short screen-capture videos (3–5 minutes each) for any procedural processes that require it. Once made, these pay dividends on every subsequent hire.
What Good Looks Like
New hires describe feeling set up for success rather than dropped in. Time to first independent contribution decreases noticeably. Managers report spending significantly less time on basic orientation questions. The onboarding experience becomes a model worth replicating for others entering the organization.
Watch Out For
Building onboarding infrastructure for all roles simultaneously when capacity is limited. Build it for your highest-impact or highest-turnover roles first. Also watch for the traditional urgency trap: the organizational instinct to sweep new leaders into full operational mode immediately. The moments of pause built into this process are not inefficiency — they're the mechanism for getting it right.
Organizations spend a lot of energy trying to retain people while rarely asking where those people want to go and grow. Which creates a strange dynamic where we try to hold onto someone's presence without engaging their actual aspirations. Career Camp is built on a different premise: if you invest genuinely in where someone wants to go, the ones who want to go there with you will stay — and the ones who don't will leave with gratitude rather than resentment. Both outcomes are better than the alternative.
Before You Start
Basic organizational stability is required. Participants should be in their second year or beyond. Most importantly, leadership needs to be genuinely supportive of staff developing toward roles that might be outside the organization. If the unspoken message is "we want you to stay," Career Camp will feel patronizing.
How to Run It
1
Identify the cohort. Career Camp works best in groups of six to twelve. Mix seniority levels if possible; the cross-level dialogue is often the most valuable part. Participants should be at or past the two-year mark.
2
The curriculum runs monthly over three months. Core topics in rough sequence: career mapping and values alignment (what do you actually want?); skills inventory and gap analysis; building mentorship outside the organization; job search mechanics as a skill set, including resumes, networking, and interviewing; negotiation; and navigating transitions with integrity.
3
For each participant, recruit an external mentor whose work connects to their stated goals. Someone in a different sector is often more valuable than someone in the same field. The outside perspective breaks assumptions.
4
Between sessions: short reflection exercises and at least one individual coaching conversation per participant per month. The sessions establish direction; the between-session work is where actual development happens.
5
The final session focuses on one concrete next step per person: a specific action with a specific date attached.
6
Track outcomes at six months. Are participants more engaged? Have some moved on to great next roles? Both are healthy. Stagnation and disengagement is the failure mode.
What Good Looks Like
Participants describe feeling seen as professionals with careers, not just employees filling roles. The ones who stay do so with renewed intentionality. The ones who leave do so with clarity and gratitude rather than exhaustion and resentment.
Watch Out For
Treating departure as a program failure. Career Camp is designed to help people figure out what they want. Sometimes what they want is elsewhere. That's a success.
Most organizations say they invest in people's development. Some have a budget line that proves it. Far fewer have a culture where development actually happens — where people are visibly growing, where learning is something you talk about in the same breath as the actual work because it is part of the actual work. The gap between stated commitment and lived experience is where this tool lives.
Before You Start
Role clarity first. Budget for development. Someone to coordinate. Don't invest in learning infrastructure before people understand what their job actually is. The simplest version — an annual allowance with minimal bureaucracy — is also the fastest to implement and the most credible signal. Start there if nothing exists.
How to Run It
1
Establish the current baseline honestly. Is there a PD allowance? For everyone? A policy? An informal norm? Start from the real baseline, not the aspirational one.
2
If nothing exists, implement the simplest responsible structure: an annual PD allowance per person with minimal approval process. The signal matters as much as the amount. An org that gives staff $250 and trusts them to use it well sends a message about professional respect.
3
For a more developed structure, design two tracks: self-directed (what each person identifies as their priority) and employer-directed (what the organization needs people to develop to achieve its strategy).
4
Managers review individual learning plans annually as part of the performance conversation. The question is not "did you spend the money" but "what are you working on and how can we support it?"
5
Add the Visiting Professionals Series (Tool 31) as the employer-directed component. External guests sharing how high-performing teams approach their work is high value at relatively low cost and creates mentorship relationships that outlast the sessions.
6
Track patterns. What are people developing? Where are the gaps between individual interests and organizational needs? That gap is the strategic learning and development roadmap.
What Good Looks Like
People use their PD allowance and share what they're doing and learning. Development becomes part of how the organization describes itself, not a once-a-year checkbox.
Watch Out For
Creating a PD allowance that sits unspent because no one promotes it or the culture signals that people are too busy to develop. The permission and the pace have to match the investment.
There's something a little ironic about organizations that invest heavily in developing their front-line and mid-level staff while leaving their executives to figure out their own growth. The assumption seems to be that you reach a certain level and development happens on its own. Both assumptions are worth questioning. The people at the top set the development culture for everyone else.
Before You Start
Psychological safety for leaders to honestly name where they're less effective than they want to be. CEO support and visible modeling. If the CEO doesn't have a development plan, no one else's will be taken seriously.
How to Run It
1
Begin with a forward-looking development conversation, not a backward-looking performance review. Coaching questions: where do you feel least confident in this role right now? What feedback do you receive consistently? What does the organization need from this role over the next two years that you're not yet fully delivering?
2
Identify two to three genuine growth areas. These should come from the leader themselves, not be handed to them. If someone can't name their own development edge, the conversation hasn't gone deep enough yet.
3
For each growth area, identify specific resources: a particular book, a course, a mentor relationship, a peer learning partnership, a stretch assignment. "Read more" is not a development plan. A specific title with a deadline and a reflection conversation scheduled is.
4
Set timing. By when will you engage with each resource? When will you bring a reflection back to your accountability partner?
5
Establish the accountability structure. Who is outside the management chain who will check in on this? For a CEO, this is often a trusted board member or a peer executive in another organization.
6
Revisit quarterly. Quarterly review produces actual development.
7
Connect to succession. What does this leader need to grow into for the organization to thrive at its next stage? Development plans that connect to succession are organizational investments.
What Good Looks Like
C-level leaders talk openly about what they're working on. The development culture at the top creates permission for development culture everywhere else.
Watch Out For
Plans created because someone asked for them, then never actually used. The commitment is the thing, not the document.
Most compensation systems weren't designed. They accumulated. Someone got hired at a certain salary based on what they negotiated or what the market was at that moment, and that salary became the reference point for the next hire, and so on for years. The result is a system coherent only in the sense that you can trace how each number was arrived at. This tool runs in two phases: first a review of current state, then the design of a principled model to replace it. Running the design phase without the review first produces a principled system disconnected from reality.
Before You Start
Budget to act on what you find — this is the most critical prerequisite. A compensation review that produces findings and stalls at the board is measurably worse than no review. It confirms that equity conversations at this organization produce reports, not change. The intent to act has to be real before the review begins. For Phase 2: compensation review completed first, board and leadership aligned on philosophy, budget clarity, legal review of the proposed model, and a communication plan ready before implementation.
Phase 1 — Compensation Review
1
Establish or reaffirm the compensation philosophy before touching any data. How does the organization think about pay? What market percentile are you targeting and why? How do you handle tenure, geographic differentials, skill scarcity, and role scope?
2
Collect current compensation data for all roles: base salary, benefits, and total compensation including any bonuses or stipends.
3
Select appropriate benchmarks. For mission-driven organizations, sector-specific surveys tend to be more useful than general market data.
4
Conduct the internal equity analysis. Compare compensation across similar levels and role types, controlling for legitimate differentiators. Look specifically for patterns that correlate with race, gender, or other demographic dimensions. Anti-racism in compensation is not just a policy — it's a lens applied to every decision.
5
Identify outliers: people significantly above or below market, and people at similar levels with meaningful, unexplained pay gaps.
6
Bring findings to leadership and board with specific, costed recommendations: here's what we found, here's the significance, here's what we recommend addressing in what sequence, here's the budget required.
7
Communicate to staff — not necessarily individual numbers, but the process, what was examined, and what commitments the org is making.
Phase 2 — Equitable Model Design
1
Write the compensation philosophy: one page that explains what the organization believes about pay and why. What justifies differentiation between people at the same level? What is the relationship between pay and market rate, performance, tenure, scope, and equity goals?
2
Choose the model type. Fixed tier: everyone at a given level earns the same salary — structurally equitable, minimal administrative complexity, no room for negotiation differentials. Criteria-based: salary within a band, calibrated by documented criteria — more flexible, more complex, requires strong governance.
3
If criteria-based, define each criterion, how it's measured and by whom, and the salary impact of each. The model is only equitable if the criteria are visible, consistently applied, and audited over time.
4
Test the model against current staff before implementation. Who would move up? Who would move down? What is the cost of making everyone whole?
5
Implement with a communication plan that explains the model, individual outcomes, and the philosophy behind both. People need to understand not just what changed but why.
6
Plan for annual review. Market rates shift, role scopes evolve, and the model needs to stay calibrated to reality.
What Good Looks Like
When a staff member asks "why do I make what I make?" there is a clear, principled answer grounded in visible criteria — not in negotiating leverage, managerial favoritism, or historical accident. The org has a current, clear picture of its compensation position.
Watch Out For
Two failure modes: the review that surfaces important findings and then stalls because the board isn't ready to fund corrections (document the inequity instead of fixing it); and designing a principled model and then not applying it to actual hiring decisions, so the model exists on paper only.
Most organizations have a hiring process in the same way they have a strategy: it exists somewhere, influences outcomes, and varies dramatically depending on who's running it. A systematized hiring process produces consistent quality regardless of which manager happens to be running the search or how much time pressure they're under. For senior and executive roles, that process takes on additional dimensions — the experience the organization creates for candidates communicates something about what the org values and how it operates. A search process that is opaque, slow to communicate, and structurally biased toward people who already know how to navigate it will find a certain kind of candidate. A well-designed one finds a different, better one.
Before You Start
Leadership commitment to following the process consistently, including when there's pressure to move faster. Someone designated to own and maintain the system. The When to Hire Rubric (Tool 13) completed first — the hiring system assumes you've already confirmed you should be hiring. For executive searches: full search committee commitment to the process and timeline. Bandwidth to run it properly. Budget for candidate care, including honoraria for finalist candidates. This process takes more time than traditional search, and the additional time is the mechanism of the improved outcomes.
How to Run It — Standard Process
1
Document current practices by reviewing one recent hiring process that went well. What actually happened, in what sequence? That's your starting template. Build from real practice, not from a theoretical ideal.
2
Build the full architecture in sequence: When to Hire Rubric completed before anything else; job description with explicit distinction between required and preferred qualifications; posting strategy; application screening criteria developed before applications arrive; structured interview format with consistent questions across all candidates; scoring rubric developed before interviews begin; reference check protocol; offer letter template with approval process; onboarding handoff checklist.
3
Structured interviews with a pre-developed scoring rubric are not bureaucracy. They are the most reliable way to reduce the influence of affinity bias on hiring outcomes and consistently compare candidates on equal footing.
4
Test the system with the next two to three hires. Where does it break? Where does it create unnecessary friction? Revise before treating it as final.
5
Train every person who will run a search. A documented system that people haven't been trained on isn't a system.
6
Audit quarterly: are managers following the process? Where are the variations? Where can we iterate?
Executive Search — Additional Layers
1
Convene the search committee for alignment before anything is posted — not just on the job description but on what success looks like 18 months into the role. What does this organization need that it doesn't currently have?
2
Build a candidate-facing microsite or detailed page including the role description, organizational context, what the committee values, how the process will work, the timeline, and who to contact with questions. Transparency at this stage signals what kind of organization this is.
3
Source actively from specific communities and networks. Posting and waiting produces the applicant pool of people already paying attention. Active outreach reaches people who weren't looking.
4
Conduct introductory interviews with a wide range of staff before the search begins. Understanding the organizational dynamics from multiple perspectives allows the search to be represented honestly to candidates.
5
Communicate with candidates at every stage. Silence is the most common candidate experience in searches and it's corrosive. Every candidate at every stage should know where they stand.
6
After the hire, conduct a candidate experience survey including candidates who were not selected. Their experience is free improvement data.
What Good Looks Like
Candidates from different networks receive a consistent experience. Hiring decisions are defensible. New hires report that the organization they encountered in the hiring process is the organization they found when they started. For executive searches: the applicant pool is meaningfully larger and more diverse. Finalists describe the process as one of the stronger search experiences they've had.
Watch Out For
Building a rigorous system that managers bypass when they're in a hurry — simplify until the system is easier to follow than to work around. For executive searches: committing to an inclusive process and then reverting when a strong internal candidate appears early. Bypassing a process you publicly committed to is more damaging to organizational trust than having run a transparent traditional search.
There's something clarifying about hearing someone from a completely different field describe how they solved the same problem your organization is wrestling with. The outside frame makes visible the assumptions you've been working inside without knowing it. The Visiting Professionals Series creates that experience on a regular basis — which is rarer than it should be.
Before You Start
Someone to recruit and coordinate guests. A quarterly meeting slot. Basic operational stability. This is the first thing that gets canceled when things get busy, and the consistency is the value.
How to Run It
1
Define the framing: every guest answers some version of "what have you learned about building organizations and teams that actually work?" A hospital executive talking to a nonprofit arts organization. A technology leader talking to a social services org. The outside frame is the point.
2
Recruit through existing relationships first: board members, donors, peer executives, former colleagues. Ask each to recommend one more. The network extends quickly.
3
Structure the session using the WSS Visiting Professionals Series template: brief context-setting (5 minutes), guest shares their experience and perspective (20–30 minutes), open Q&A with staff (30 minutes). Prepare staff to ask substantive questions.
4
Invite broadly. Not an executive perk. Staff at any level should feel welcome.
5
Follow up with guests personally. A handwritten note, a brief written reflection from staff, a specific observation about what landed. Ask staff to sign a bottle of champagne using a silver Sharpie. These relationships compound over time.
6
Block dates for the full year in advance, before the calendar fills with operational priorities.
What Good Looks Like
Staff come away with a broader sense of the field and new relationships outside the organization. Mid-tenure staff who were starting to feel intellectually isolated feel re-engaged. The series creates a steady input of outside perspective into the organization's thinking.
Watch Out For
Letting the series drift when operational pressure increases. The consistency is the value proposition. One strong session creates goodwill. A consistent series over two years creates culture.
The most common failure in promotion and performance conversations isn't that managers are unfair. It's that "who's ready" is held as a form of intuition rather than a set of observable behaviors — which means the same person can look ready to one manager and not ready to another, and nobody knows why they're disagreeing because neither has articulated the standard. The Behavior Dashboard is how you make the standard visible.
Before You Start
Leadership alignment on what "good" actually looks like at each level. Managers who know how to use the dashboard in real performance and promotion conversations. Willingness to have honest conversations about gaps, including with current staff who may not be where the dashboard says they need to be.
How to Run It
1
Start with one level. Not all of them simultaneously. Pick the level where advancement criteria are most opaque or contested.
2
For that level, identify four to six behavioral dimensions grounded in the actual work: decision-making quality, communication across stakeholder groups, how they handle ambiguity, contribution to team effectiveness.
3
For each dimension, write descriptions of excellent performance that are specific and observable. The test: could two people observing the same person over the same two-week period agree on whether this behavior is present? If not, the description isn't specific enough.
4
Write "not yet" descriptions for each dimension. This is what prevents the dashboard from being used only to confirm promotions and keeps it useful for identifying development needs.
5
Test against real people before publishing. Do the descriptions ring true? Are there meaningful behaviors missing? Do any "excellent" descriptions describe nobody currently at this level?
6
Publish and use in actual performance and promotion conversations. A dashboard that lives in a folder is not a dashboard.
What Good Looks Like
When a manager says someone is ready for the next level, they can point to specific observable behaviors. When someone asks why they weren't promoted, there is a specific, honest answer. The promotion process feels more legible and more fair.
Watch Out For
Writing descriptions so polished that everyone sounds excellent. If every dimension reads as flattering, the dashboard won't surface the real gaps it was designed to identify.
When people in an organization can no longer have a functional working relationship, management tends to respond with one of two moves: pretend it's not happening, or try to fix it internally. Neither usually works. The reason the org can't also be the mediator is structural: the organization is already involved, which means it can't also be neutral. That's what the external mediator is for.
Before You Start
Both parties must be genuinely willing to engage — not willing to appear cooperative. Coerced mediation produces polished surface agreements that quickly fall apart. If the conflict has a structural root, such as unclear roles, misaligned decision rights, or resource scarcity forcing competition, that structural issue needs to be addressed in parallel. Mediation handles the interpersonal layer, not the system underneath.
How to Run It
1
Recognize the signal. Mediation is appropriate when parties can no longer have productive one-on-one conversations, when their conflict is showing up as subtext in team meetings, or when decisions are being blocked because of the dynamic between them.
2
Contract an external mediator. Don't run this internally, even if someone on staff has mediation training. The moment the org is involved, the org can't also be neutral. The mediator needs to be someone neither party has a relationship with.
3
Brief the mediator with organizational context. Be deliberate about not pre-positioning them toward one party's view. Give them structure, not a story.
4
Pre-mediation interviews: the mediator meets separately with each party to understand their experience, what they need, and what they're willing to commit to. These conversations are confidential from the org.
5
Joint session: the mediator facilitates structured conversation toward specific, behavioral, documented agreements. Not "we'll try harder" but "when X happens, we will do Y."
6
Set a 45- to 90-day check-in. Are the agreements holding? Has the dynamic shifted?
7
If structural issues are driving the conflict, address them separately after the mediation process. Mediation resolves interpersonal friction. It does not redesign org structure.
What Good Looks Like
Parties can work together productively. The subtext in meetings shifts. People describe being able to have functional working conversations again. The documented agreements create accountability without surveillance.
Watch Out For
Calling this mediation when it's actually performance management. Mediation requires genuine good-faith willingness from both parties. If one person is being managed toward an exit, that's a different process entirely, and calling it mediation is unfair to everyone involved.
Most organizations have an implicit policy about negative patron interactions that goes something like: be professional, de-escalate, figure it out. Which sounds reasonable until you realize it places the entire burden of navigating abusive or unsafe interactions on the individual staff member, in the moment, without any organizational backing. This protocol makes the backing explicit and public.
Before You Start
Leadership must be genuinely prepared to back staff decisions to disengage, even when the patron is a significant donor or long-standing community member. That's the critical test. The first time a staff member follows the protocol and leadership overrides them to preserve a relationship, the protocol is effectively dead. This is definitely not "the customer is always right."
How to Run It
1
Identify where negative interactions actually happen: patron-facing roles, front desk, program staff, customer calls, social media, anyone who receives communications from the public. Map the actual contexts before designing the protocol.
2
Co-create the protocol with the frontline staff who will use it. They know what they encounter and how it tends to show up. Ask: what does a negative interaction look like in your specific role? What authority do you wish you had in those moments?
3
Design a tiered escalation protocol with three to five clear steps. Example: first, name the behavior and set a limit; second, if behavior continues, offer to pause the interaction; third, if it continues, disengage and document; fourth, supervisor notification; fifth, structured debrief within 24 hours.
4
Write specific language for each step. Not "de-escalate." Actual sentences staff can say. The goal is to remove the in-the-moment judgment call about what words to use, so all cognitive capacity goes toward staying safe and calm.
5
Publish the protocol externally so members and patrons know it exists. Making it visible shifts the dynamic from "we hope this doesn't happen" to "this is how we operate" in alignment with our values.
6
Train every staff member who intersects with it, including a practice run with scenarios. Role-play is uncomfortable. It's also the only way to learn what it feels like to say the words under pressure before the time comes.
7
Debrief after every real use. What worked? What needed adjustment? The protocol should improve over time based on actual experience.
What Good Looks Like
Staff describe feeling backed up by the organization when difficult situations arise. The cognitive load of "what am I supposed to do here?" is replaced by "I know exactly what to do here."
Watch Out For
Publishing the protocol and failing to back it up in practice. The first override signals to every staff member that the protocol was theater. One override is harder to recover from than never having created the protocol at all.
I've watched teams argue for hours about accountability, or transparency, or innovation — and eventually realized they weren't arguing about the thing itself. They were arguing about what the word means, and more specifically their different definitions of it. Which is a different problem entirely, and also a more easily solvable one. The Misunderstood Words Exercise is how you find out whether you're actually disagreeing or just using the same word to mean different things.
Before You Start
Enough psychological safety to admit confusion. You can also run the "Can't Say Words" variation, where people try to describe a concept without using the contested word itself — which often reveals the definitional gap faster than any direct discussion. The facilitator modeling willingness to say "I'm not sure what I mean when I say that" is what makes this work.
How to Run It
1
Before the session, spend a week listening for the words that generate the most friction in meetings. Which words come up when people seem to be talking past each other? Common candidates: accountability, collaboration, equity, strategic, leadership, transparency, urgency, community, fail, success. The facilitator guide includes a "50 Most Misunderstood Words" list as a starting resource.
2
In the session (60–90 minutes), give each participant the same word. Without any discussion, everyone writes their private definition.
3
Share. The differences will be immediate and often surprising. People who have worked together for years and used the same word in the same meetings sometimes have definitions that barely overlap.
4
Facilitate the conversation around one question: which definition best serves what we're trying to do? Not who was right — which definition do we want to operate from going forward?
5
Document the shared definitions in a simple, accessible glossary that becomes a living document.
6
Build a team norm for flagging real-time misalignment: "I think we might be using that word differently — can we pause?" This is a more valuable output than the glossary itself. Normalize the interruption.
7
Share the glossary with all staff. Invite additions. Add it to your Core Curriculum.
What Good Looks Like
Meetings stop circling back on the same arguments. When familiar tension resurfaces, people can name it: "I think we're using 'accountability' differently again." That naming interrupts the cycle before it completes itself.
Watch Out For
Believing that agreeing on definitions has solved the underlying problem. Often the reason people define words differently is because they hold genuinely different values or assumptions. The glossary names that gap. It doesn't close it. But naming it is the prerequisite for everything else.
Every dryer has a lint filter. You're supposed to clean it before each load. Most people clean it occasionally, if they remember, when the dryer starts running hot. The lint that accumulates isn't dramatic. It builds up slowly, from ordinary use, until one day the machine stops working well and you wonder why. Teams accumulate lint the same way. Usually it's not the big blowup that causes the most damage — it's the small things that never quite got addressed: the comment that landed wrong and was never named, the decision that felt exclusionary and was never discussed, the pattern of behavior that everyone sees and nobody has said out loud. Each piece is individually minor. Collectively, they clog the filter and reduce the team's capacity to do anything well.
Before You Start
The research puts the behavioral half-life of most one-time conflict training at two to three weeks. After that, people return to their default patterns regardless of what they learned. The gap closes only through repeated practice. External facilitation is strongly recommended. Seven months. Multiple lenses. The invitation at every stage: try this on.
How to Run It
1
Month 1 — Under the Hood, Team Regulation: introduces how teams regulate and dysregulate together. The Team Regulation Map helps participants identify their own stress responses and how those responses interact with others'. Reference Card: Recognition Cues.
2
Month 2 — The Voice in Your Head, Facts versus Stories: the distinction between what happened and the story we're telling about what happened. This is harder than it sounds and more useful than almost anything else in the curriculum.
3
Month 3 — The Art of Really Listening, Looping Practice: reflecting back what you heard before responding. One of the fastest ways through conflict is not force or logic or clever argument — it's making the other person feel genuinely understood first.
4
Month 4 — Repair: how to have the conversation after the thing that shouldn't have happened happened. The Repair Conversation Prep Sheet structures a conversation that most people improvise badly.
5
Month 5 — Not All Conflicts Are the Same: the V Model Conflict Map distinguishes conflict types. Misdiagnosing conflict type is the source of most failed resolution attempts.
6
Month 6 — Accountability That Connects: how to hold people accountable in ways that strengthen rather than damage relationships.
7
Month 7 — What We Build Going Forward: integration and forward design. The Culture Commitments Center: what specific commitments does this team make about how it will handle conflict going forward?
What Good Looks Like
The team can disagree productively without the relationship fracturing afterward. Hard conversations happen earlier, when they're still manageable. The dynamic in team meetings feels qualitatively different — less performative, more honest.
Watch Out For
Treating month seven as the finish line. Teams that complete Clean the Lint Filter and then stop maintaining the practice revert within 18 months. The curriculum builds conflict capacity. The ongoing practice is what makes it permanent.
People typically aren't making bad decisions out of spite. They're making the best decisions they're able to with the information, context, and understanding available to them at the time. Which raises a useful question: how much of the anxiety and misaligned decision-making in your organization exists because people don't have the context they need? The Podcast(ish) Series is a low-production way to give them that context through honest conversations they can learn from.
Before You Start
Leadership must be genuinely willing to be transparent, not just willing to say they are. Staff recognize the difference immediately. A scripted executive delivering talking points builds less trust than no video at all. Always pair with a Full Staff Q&A. The series creates the transparency deposit that the Q&A draws on.
How to Run It
1
Choose a first process worth making visible. Pick something people have questions about that nobody is answering. The budget process is a common starting point. The criterion is simple: where is there an information gap that anxiety is filling?
2
Record a 20-minute conversation between two people who actually run that process. Keep it informal. Slightly messy is better than polished. "Here's what we know, here's what we don't, here's how we're thinking about it" is exactly the right register.
3
Build an anonymous Google Form with one field: "What questions do you have about this?" Publish the recording and the form simultaneously. Give staff 48 hours to submit questions before the next all-staff meeting.
4
At the all-staff meeting, answer every question publicly. If you don't know the answer, say when you'll find out. The questions are your culture data.
5
Record the next episode. As the series builds, you can go deeper on the same process with different voices, or move to a new process. The pattern: make something visible, invite questions, answer everything, repeat.
6
Maintain a running Google Doc of all questions received, shared with all staff. This becomes one of the most important transparency documents in the organization over time.
7
Archive everything. New staff can watch past episodes as part of onboarding. This is institutional memory building in real time.
What Good Looks Like
Staff start submitting substantive questions rather than logistical ones. Skepticism decreases measurably after two or three cycles. People describe feeling less in the dark.
Watch Out For
Recording one episode and calling it transparency. The trust deposit builds through repetition. One episode is an announcement. A series is a commitment. Scripted or overly polished videos actively undermine trust — the informal conversation format is not a production shortcut. It's the thing that makes it work.
People aren't making bad decisions out of spite. They're making the best decisions they're able to with the information, context, and understanding available to them at the time. The Full Staff Q&A is the simplest mechanism I know for improving that information. Anonymous questions, answered publicly, every all-staff meeting. Low effort. High signal. Builds trust faster than almost anything else you can do.
Before You Start
Leadership has to commit to answering every question submitted, including the uncomfortable ones. This is a real commitment, not a signal of intent. An unanswered Q&A is measurably worse than no Q&A. It confirms the transparency was performative. If leadership isn't ready to answer hard questions in public, this tool will backfire.
How to Run It
1
Set up a Google Form with one field: "What's your question?" Configure it to be anonymous — no login requirements. Anonymity is the whole thing. If it feels traceable, people won't use it honestly.
2
Send the link to all staff 48 hours before the all-staff meeting. Keep the framing direct: "Any question for the CEO" or "Any question about our annual budgeting process."
3
At the meeting, answer every question aloud. If you don't know the answer, say so and name when you'll find out. Invite people to resubmit the question next time if the answer is insufficient. If a question reveals a structural concern, name that rather than hedging around it.
4
Keep a running Google Doc of all questions received and answers given, shared with all staff. This becomes one of the most valuable cultural documents in the organization over time.
5
After a few cycles, review the questions by theme. What keeps coming up? That data is more reliable than any formal survey because the questions come when something is actually on people's minds.
6
If no one submits questions the first time, don't read that as "everything is fine." Read it as "people don't trust the anonymous format yet, or they don't believe leadership will actually answer." Keep running it. Trust builds through repetition.
7
Make this a permanent slot at every all-staff. Not a one-time exercise. The rhythm is what builds trust.
What Good Looks Like
The quality of questions changes over time. Early sessions produce logistical and safe questions. By the fourth or fifth cycle, people are asking real things — about strategic decisions, about the gap between stated values and what they observe. That shift in question quality is the signal that trust is building.
Watch Out For
Answering questions with corporate hedging. "That's a great question and we're looking into it" is not an answer. It's a way of appearing responsive while communicating nothing. Vague non-answers to honest questions erode trust faster than no Q&A at all.
Peer-to-peer recognition is designed to be a public monthly system where staff acknowledge each other's values-aligned contributions — making values language a living part of everyday work rather than a once-a-year or opaque exercise only a few know about.
Before You Start
This is a compensation and benefits decision before it's anything else: legal review completed, platform selected, budget allocated, policy designed, communication plan ready, executive approval secured. Also the culture needs to already be functioning at a reasonably high trust level. Peer-to-peer recognition in a low-trust environment becomes a popularity contest or political tool within weeks. This tool accelerates cultures that are already working.
How to Run It
1
Complete all structural prerequisites before any communication to staff: legal review, platform selection, budget allocation, policy design, and a communication plan. These steps happen before launch, not in parallel with it.
2
Define the parameters with explicit leadership approval: monthly points allotment per person, what points can be redeemed for, public visibility settings, and how recognition connects to organizational values.
3
Tie recognition explicitly to values. Not "great job on that project" but "this reflects our value of [X] because you did [Y]." The connection to values is what differentiates this from a popularity system.
4
Launch with an all-staff conversation. Cover the policy, the spirit behind it, and what kinds of recognition will feel meaningful. Ask staff how they want to be recognized. The answers often surprise leadership.
5
In the first month, leadership should visibly model the behavior. The recognition patterns of leaders set the template for what everyone else does.
6
At all-staff meetings, share patterns: which values are appearing most frequently in recognition? Which are absent? That data is your culture dashboard.
7
At 60 to 90 days, audit distribution. Are the same people always recognizing the same people? Are some people never receiving recognition? Uneven patterns are a signal worth investigating.
What Good Looks Like
Values language starts appearing in everyday conversation, not just formal performance cycles. People use the vocabulary of recognition to describe what they notice in each other's work. The system feels lightweight because it is. The recognition is genuine.
Watch Out For
Deploying this in a low-trust environment. It will feel like a popularity contest within weeks and will actively make things worse. You can't fast-track culture with a recognition system.
The days an organization chooses to observe as paid holidays are a quiet expression of whose calendar, whose history, and whose traditions the organization sees as worth marking. Most organizations inherited a calendar they've never examined. Examining it is a simple act of values alignment that costs very little and tells people a lot about whether the values on the wall match the operations in practice.
Before You Start
Some trust and transparency foundation needs to be in place first. This works as a values-alignment credibility signal when the organization is already building trust. It reads as performative optics when it isn't backed by deeper culture work. Don't lead with this. Follow with it.
How to Run It
1
Pull the current holiday calendar. List every paid holiday. For each one, ask honestly: does observing this day reflect our stated values? Does it contradict them? Does it have no meaningful relationship to them?
2
Identify gaps. Are there observances aligned with the organization's values that aren't currently recognized? These decisions should follow the organization's values statements, not default to conventional or majority calendars.
3
Bring a specific proposal to leadership: what you're proposing to add, what if anything you're proposing to change, and why each decision connects to an organizational value.
4
Involve staff before the decision is final. A process with genuine input builds more credibility than an announcement.
5
Communicate the rationale alongside the change. "We added this observance because it reflects our commitment to X" does substantially more trust-building work than a calendar update alone.
6
Build the holiday calendar into onboarding and culture orientation. New staff should hear about these decisions as examples of values in practice.
What Good Looks Like
Staff describe feeling seen in the organizational calendar. New hires hear about holiday decisions during culture orientation as concrete examples of values in practice.
Watch Out For
Doing this as a standalone gesture without the culture work behind it. A calendar change in a low-trust environment often actively makes trust worse. The calendar is a small thing. The culture it sits inside is the big thing.
New hire experience varies wildly depending on which team they're on, what manager they happen to have, and what that manager's schedule was during week one. In some organizations, this means one new hire gets a thoughtful orientation while another spends their first two weeks trying to figure out where the files are. A Core Curriculum makes the important stuff systematic and intentional rather than accidental.
Before You Start
Key knowledge documentation must exist before you can build the curriculum. Someone must own both production and ongoing maintenance. A curriculum with an absent caretaker becomes outdated and actively misinforms new staff. Start with the highest-priority modules.
How to Run It
1
Map what every new hire needs to know. Organize into categories: who we are and why we exist (values, history, mission); how we operate (key policies, decision-making processes, tools and systems); and what your role connects to (how the work fits into the larger picture). Aim for 15 to 35 modules total.
2
Start with the three to five most important modules that set people up for success. Build the full curriculum over time, not in one sprint.
3
Record each module as a short video, structured written guide, a deck, or standard operating procedure. Informal and authentic beats produced and polished.
4
Build a simple hosting structure with a clear path, not a library to browse. A new hire on day one should be able to see where to start and what comes next.
5
Designate specific owners for each module. The curriculum is only evergreen if there are actual humans responsible for keeping specific sections current.
6
Test with actual new hires: at the end of week one, ask what questions they still have. Those unanswered questions are your missing modules.
7
Build the maintenance schedule. Outdated information in a curriculum is much easier to update than to create from scratch — but someone has to own it.
What Good Looks Like
New hires can describe the organization's values, key policies, and how decisions get made after their first week — not because a manager happened to tell them, but because there's a system that ensures it.
Watch Out For
Building without a maintenance plan. A curriculum that was accurate 18 months ago and hasn't been updated tells new hires things that are wrong. The maintenance plan is not optional infrastructure.
One of the more interesting things about organizational culture is that the same organization can look completely different depending on where you're situated inside it. What the executive team experiences as high trust might register as moderate on the front lines. The Culture Wheel is a way to surface those different experiences, understand where the organization wants to go, and have an honest conversation about what levers you can pull to get there.
Before You Start
Some psychological safety is required. Leadership needs to be genuinely ready to hear honest data about current culture, not confirmation of what they hope is true. The instruction is explicit: rate where you are, not where you aspire to be. That distinction is harder to hold than it sounds — and it's the whole thing. For organizations with lower psychological safety, consider starting with a fictional company before applying the exercise to your own. The fictional framing creates enough distance for honest conversation.
How to Run It
1
Introduce the eight dimensions: Healthy Conflict, Transparency, Alignment and Accountability, Resilience, Trust and Vulnerability, Psychological Safety, Clear Commitments, and Balance of Input.
2
If the group has lower psychological safety, begin with a fictional company: describe a hypothetical organization and have participants rate it on the eight dimensions. This builds familiarity with the framework and the rating process before anyone is rating their own organization.
3
Individuals rate their own organization on each dimension from 1 (lowest) to 5 (highest), based on current reality. Privately first. This is where you are, not where you wish you were.
4
Now participants create a second wheel: where do we want to be in two to three years? Rate each dimension again, this time reflecting the culture you're trying to build. This future-state wheel becomes the destination.
5
Map both wheels. Place current ratings and future-state ratings on the same radar. Three things become visible: where scores are clustered today, where people disagree on current reality, and how large the gap is between present and aspiration on each dimension.
6
In the facilitated session, surface the two or three dimensions with the greatest gaps — both between participants' current ratings, and between current and future state. The disagreements about current state are often more interesting than the averages.
7
Introduce the levers question: for each dimension where you want to move from current to future state, what levers can you pull? Sort levers by sphere: what can individuals do? What can teams do? What requires leadership action? What requires governance or policy change? This question prevents the conversation from collapsing into either "leadership needs to fix this" or "everyone just needs to try harder."
8
Commit to specific actions at each level — small, testable, within 90 days. Return to both wheels in 90 to 180 days. What moved? What didn't? Which levers had traction and which didn't?
What Good Looks Like
Participants leave with shared language for what culture means at this specific organization, a concrete picture of where they want to go, and a set of levers that feel owned rather than assigned. The conversation shifts from ambient complaint to specific, actionable diagnosis — and each person understands what they can do to move the needle.
Watch Out For
Treating completion of the exercise as culture change. The wheel is a diagnostic and a starting point. It generates insight. What happens after the session — particularly whether people follow through on their identified levers — is what changes culture.
People typically aren't making bad decisions out of spite. They're making the best decisions they're able to with the information, context, and understanding available to them at the time. Which makes the question worth asking: how much of the anxiety, conflict, and misaligned decision-making in your organization exists because people don't have the context they need to make good choices? The Radically Transparent Budget Process is one answer to that question.
Before You Start
A CFO or finance lead willing to be genuinely transparent. Leadership aligned on what to share. The foundational belief here is that transparency is an investment in better organizational decision-making across the board — not a PR exercise or a concession to staff demands.
How to Run It
1
Start with a Budget Backgrounder conversation for leadership: the plan, types of budgeting, the players, process phases, what it looks like, trade-offs, predicting the future, tracking and adjusting. This is the foundation for any meaningful budget transparency effort.
2
Record an initial podcast-style conversation between the CFO and CEO about the decision architecture of the budget process. Who sets the parameters? What constraints exist? Who gives input? When does the board review?
3
Publish the conversation with an anonymous Q&A form. Collect and answer everything.
4
Build a timeline narrative at the start of every budget cycle: "In September, this happens. In October, this group gives input. In November, the draft goes to the board." Make the calendar visible before the cycle begins.
5
Share drafts at meaningful stages — after the first pass, before board review, and after final approval — with notes on what changed between versions and why.
6
Create a short CFO video explainer: "Here's what our budget tells us about organizational health." Numbers without narrative create anxiety. Numbers with narrative create understanding.
7
Build budget literacy into onboarding. New staff should have a basic understanding of how the organization's finances work before the end of their first 90 days.
What Good Looks Like
Staff stop filling silence about money with anxiety. Budget conversations become a normal part of organizational dialogue. People start asking substantive questions about financial choices rather than worrying about them privately.
Watch Out For
Sharing numbers without the context to understand them. A spreadsheet of actuals dropped into an all-staff meeting creates more anxiety, not less. The CFO's job in this process is to make the financial story legible, not just visible.
A lot of what we experience as interpersonal friction is actually working style differences that nobody ever named. Someone isn't necessarily difficult to work with. They just process information differently, or need 24 hours before they can respond meaningfully to feedback, or communicate through writing rather than improving in the moment. The User Manual is how you surface and share those differences before they harden into stories about who people are.
Before You Start
Some level of psychological safety needs to exist. This tool surfaces working style differences and asks people to be honest about how they operate under pressure. Probably don't run this when there's active interpersonal conflict — people will write careful, managed answers that look like progress and aren't.
How to Run It
1
Each team member completes the User Manual template individually before the team session. The Work Shouldn't Suck template covers: how you prefer to get information and communicate, how you like to receive feedback, what helps you do your best work, what drains you, how you show up under stress, and where your work-life boundaries are.
2
Distribute completed manuals to the full team before the session. Give people time to read them in advance, not cold in the room together.
3
In the team session (60–90 minutes), don't have everyone present their own manual. That turns into a performance. Instead, surface two or three notable differences across the team and make them concrete: "We have four people who want feedback in the moment and three who need 24 hours to sit with it. What does that mean for how we give feedback as a team?"
4
Translate differences into working agreements. Not "we'll be more aware of each other's styles." That's aspirational, not actionable. "For feedback on draft work, we'll always share in writing at least 24 hours before any conversation about it" is a working agreement.
5
Write down the agreements. Two or three is enough. Add them to the team's shared space where they'll actually be seen.
6
Revisit when the team composition changes. A new person changes the whole picture, and old agreements may no longer fit.
What Good Looks Like
People stop attributing intent to working style differences. "She never responds quickly" becomes "oh right, she processes asynchronously." The friction doesn't disappear but it becomes legible — which means it's navigable.
Watch Out For
Using this as a substitute for real structural fixes. If there are role conflicts, decision rights ambiguity, or active interpersonal tension, the User Manual produces careful, managed answers that look like progress and aren't. Get the structural clarity first.
"Design your team or accept what shows up. If you don't design, you default." I think about that a lot when I watch teams that are clearly capable of doing great work and are producing a fraction of it because nobody ever explicitly agreed on how they'd work together. This tool is the conversation you have before the friction becomes the story.
Before You Start
Willingness from all team members to engage honestly about how things are actually working, not just how they're supposed to be working. Surface the real state of the team, not the aspirational one. Both are data.
How to Run It
1
Start with an honest current-state assessment. Use a structured conversation or brief survey to surface where the team actually is: trust levels, role clarity, how decisions get made, communication patterns, and how conflict currently gets handled.
2
Map what each person brings: not just skills but working style, natural contribution, and orientation. Understanding the diversity of approaches prevents teams from overvaluing people who look or work like the majority.
3
Design working norms together across four areas: communication (how, how often, through what channels), decision-making (what gets decided how and by whom), conflict (how do we surface disagreement before it calcifies?), and pace (what does urgent mean, what can wait).
4
Document the agreements in a short, accessible document. Not a policy. Something people will actually reference when they're navigating a real situation.
5
Set a 90-day check-in: are the norms holding? Where are they being tested? What needs to be revised based on what the team has actually experienced?
6
When team composition changes, return to the beginning. The team you designed norms with at one composition is a different team after a departure or arrival.
What Good Looks Like
Decisions move faster because the team has already agreed on how decisions get made. Conflict surfaces earlier, when it's still manageable. People describe knowing how to work with each other even under pressure.
Watch Out For
Treating the norms conversation as a one-time event. Norms that go unreviewed for a year are usually not actually being followed.
The hybrid workplace created a policy problem that most organizations are still solving through improvisation. Managers are making one-off decisions about availability, meeting participation, and performance standards that differ from each other in ways invisible to anyone looking across the organization. The result is inequity that feels like flexibility. This is how you make the improvisation explicit and consistent.
Before You Start
Leadership committed to consistently applying whatever policy gets written. Clarity on what the hybrid model actually is for this organization right now. You cannot write policy around an arrangement you haven't defined.
How to Run It
1
Conduct a policy inventory: list every HR policy that the hybrid environment might affect. Remote work expectations, meeting attendance requirements, equipment provision, availability norms, compensation differentials, equipment and home office stipend, performance standards, documentation requirements.
2
For each policy, ask: does this still make sense given how we actually operate? For every role? Is it being applied consistently? What situations is it not covering that managers are currently handling ad hoc?
3
Identify the highest-friction areas first. They usually cluster around meeting participation norms, availability expectations, and performance standards for people whose work you don't observe directly.
4
Draft updated policy language against this quality standard: two managers and one non-manager, reading the policy independently, should reach the same conclusion about what it means in a specific real situation. If they reach different conclusions, the language isn't clear enough.
5
Run the draft through a review group: a manager, a non-manager employee, and legal counsel.
6
Communicate changes with the rationale. Not just what changed but why. Provide a transition period for significant changes so people can adjust.
7
Update the employee handbook to match. If the handbook doesn't reflect how the org actually operates, the handbook is not the policy. Improvisation is.
What Good Looks Like
Managers stop making inconsistent one-off decisions because the policy covers the common scenarios. Remote and in-person employees describe more equitable experiences.
Watch Out For
Policy that contradicts how people actually work will be ignored or worked around.
Teams don't end up in friction because they're made up of difficult people. They end up in friction because they often don't know how to work with the differences that exist between them. Someone keeps proposing bold half-baked ideas. Someone keeps asking for more details. Someone keeps eyeing the time to finish the thing already. WorkStyles is an attempt to make those invisible forces visible, so you can work with them rather than around them.
Before You Start
"Design your team or accept what shows up. If you don't design, you default." The willingness to name honestly how you actually work — not how you think you should work — is harder than it sounds and needs to be stated at the start.
How to Run It
1
Each team member completes the WorkStyle assessment individually. The six dimensions: Decision-Making (intuition versus structured analysis), Creativity versus Implementation (do you generate ideas or build systems?), Risk and Stability (how do you weigh novelty against predictability?), Learning Edge (how do you prefer to grow?), Ambiguity Comfort (how do you navigate unclear situations?), and Adaptability (how do you respond to change?).
2
Score and map each person to their WorkStyle archetype. The framework includes ten archetypes. The pop culture case studies — including the Avengers, Abbott Elementary, Ted Lasso, and The Bear — are optional but useful for making the framework concrete and memorable.
3
Generate the team heatmap: where are people clustered? Where are the significant differences? The heatmap shows you both team strengths and potential blind spots — dimensions where the team has no representation.
4
In the team session, name the two to three most significant differences and make them concrete: "We have three people with high ambiguity comfort and two with low. What does that mean for how we scope projects and communicate about uncertainty?"
5
Design working agreements for the tension points. Use the WorkStyle Pairing Insights and Conflict Guide from the framework.
6
Run scenarios and simulations. Three are included in the facilitator guide. Scenarios surface how WorkStyle differences play out under pressure — which is when the differences matter most.
7
Build a 30-day check-in and a 60-day deep dive into the plan before leaving the session.
What Good Looks Like
People stop interpreting working style differences as character flaws. "They're being obstinate" becomes "oh, they have high structured-analysis preference and need the data before they can decide." The friction doesn't disappear but it becomes navigable.
Watch Out For
Treating this as a one-time event. WorkStyle agreements expire when team composition changes, and when they go unreviewed long enough, people drift back to their defaults while technically still having agreements on paper.
Most organizational risk conversations focus on financial risk. Which makes sense, because financial risk is measurable and boards understand it. But the risks that actually stymie organizations are often the ones that weren't in the risk register: a reputational risk tied to leadership behavior, an equity risk embedded in how decisions get made, a mission integrity risk from a funder whose values don't quite align. This framework is designed to surface all of it, not just the parts that fit neatly on a spreadsheet.
Before You Start
Some operational stability is required. Willingness from board and leadership to name real risks honestly, including politically sensitive ones. Don't run it during active crisis. Use it to build the capacity to respond before the next one.
How to Run It
1
Introduce the core principle that distinguishes this from standard risk management: risk management with an equity lens means asking not just "what could go wrong?" but "who bears the burden of this risk, whose interests are most exposed, and what are the equity implications of our response?"
2
Start with a leadership-only session. Ask each person independently: what are the five risks you're currently carrying? Write privately, then share. The differences between lists are often more revealing than the lists themselves.
3
Introduce the full risk spectrum: legal exposure, financial vulnerability, reputational risk, mission integrity, operational dependencies, and equity risks. Organizations that only see risk through a financial lens miss some of the most consequential ones.
4
Plot each named risk on a likelihood vs. impact matrix. The goal is shared understanding, not a formal risk register.
5
For the highest-priority risks, conduct a response readiness assessment: what would happen if this materialized tomorrow? Who decides? Who needs to know within the first hour? Who owns the risk?
6
Build a living risk tracker — a shared document updated at least quarterly. Track: the risk, likelihood, impact, current mitigation, and designated owner.
7
Bring the board into a risk conversation at least annually. Board members often perceive organizational risk differently than staff. That gap is important data.
What Good Looks Like
The organization develops shared language for risk and shared clarity about what risk levels are acceptable. When something goes wrong, the response is more coordinated because people have already rehearsed the thinking.
Watch Out For
Using the framework to avoid the risks that actually matter most. If everyone is comfortable with the resulting list, it probably isn't complete.
Here's something I've watched happen enough times to consider it a pattern: organizations work hard to change something, celebrate the change, and then six months later find themselves back where they started — often without quite knowing how they got there. The name for this is snapback. The cause is usually not a lack of willpower. It's a lack of structural anchors. Change held together by individual intention reverts. Change held together by structure persists.
Before You Start
A named change initiative the team is committed to. Leadership aligned on what they're trying to hold over time. Genuine willingness to name specifically what will pull it back. This is a program for the implementation phase of change, not the planning phase.
How to Run It
1
Session 1 — Setting the Stage: introduce the concept of snapback and hedonic adaptation — the process by which people normalize changes over time. These two forces together explain most failed change efforts. Ask participants to identify where their organization is already snapping back.
2
Session 2 — Self-Assessment: where are we snapping back already? This session surfaces the old patterns that are re-emerging after recent changes. Facilitation tip: this session tends to produce either relief ("finally we're naming this") or defensiveness ("we're doing fine"). Both responses are data.
3
Session 3 — Scenarios and Simulations: no-right-answer simulations that reveal which patterns people default to under pressure — which is when the differences matter most.
4
Session 4 — Designing Structural Anchors: the core session. Three levels. Micro anchors are individual habits. Intermediate anchors are team practices. Macro anchors are org or governance level changes that make reverting structurally difficult.
5
Session 5 — Future-Proofing and Action Planning: an action planning matrix, communication strategy, guardrails and checkpoints, personal commitments, and an ongoing check-in schedule.
6
Set a 90-day drift check on the calendar before anyone leaves the room. Name who facilitates it and what questions it will ask.
7
At six months, run a full retrospective. Did the change hold? Where did it drift? What needs to be redesigned?
What Good Looks Like
The change is still in place 12 months later — including after a crisis or leadership transition — because it was designed into structure rather than held together by good intentions.
Watch Out For
Doing the intellectual work of designing anchors and never implementing the micro level. Leaders often design the framework, feel like they've done something, and never build the individual habits. The micro anchors are where change lives or dies.
Work feels different now than it did five years ago — different in a lot of ways simultaneously — and the old frameworks for making sense of it often don't quite fit anymore. Co-Creating Clarity is designed for that gap: the moment after the change happens but before the new norms are fully established, when people are trying to figure out what their role actually is and what the organization is actually asking of them.
Before You Start
This guide is for leaders trying to build alignment in teams where expectations and workloads have become tangled, and for organizations navigating constant uncertainty with limited resources. Enough psychological safety for honest conversation is required. Leadership willing to say "I don't know yet" where that's true.
How to Run It
1
Open by naming the change directly. Not with spin. "Here is what has changed, here is what it means for this team, here is what we genuinely don't know yet." Premature reassurance deepens distrust. Accurate acknowledgment of difficulty builds it.
2
Introduce the SCARF framework: Status, Certainty, Autonomy, Relatedness, Fairness. Ask participants to identify which domains feel most threatened, privately first, then in discussion.
3
Run a Resource Reality Check: what resources does each person actually have to navigate this change? Time? Clear expectations? Access to decision-makers? Support? Naming the gaps honestly shifts the tone of the conversation.
4
Introduce Job Crafting. Within the changed environment, what can each person adjust about how they approach their work — which tasks they emphasize, which relationships they invest in, how they find meaning in what they do? Job Crafting restores a sense of agency within constraints that can't be removed.
5
Surface the Unwritten Contract: what did people expect from this role and this organization that may have shifted? These implicit expectations drive the deepest anxiety about change and are almost never stated directly until someone names them.
6
Close with specific, bilateral commitments: one thing leadership will do differently, and one concrete thing each participant will try in the next 30 days.
What Good Looks Like
People feel heard rather than managed. The anxiety doesn't disappear, but it becomes legible — and legible problems can be worked with.
Watch Out For
Using this as a substitute for structural clarity when roles are genuinely unclear after the change. If people don't know what their job is, no amount of SCARF mapping will help. Clarify the structure first.
Here's a pattern worth noticing: leadership teams often have the same argument, repeatedly, over years, in different forms. The people involved change their minds that it's a strategy argument, then a values argument, then a personality conflict, then back to a strategy argument. The Competing Values Framework is a way to name what's actually happening: different people in the room have different default orientations toward what the organization should prioritize, and those orientations are in genuine tension. Not wrong. In tension.
Before You Start
Enough trust for honest self-assessment. Willingness from leaders to consider that the tension between them might be structural rather than relational. This is not the right first move when trust is already broken. Relationship repair has to come first.
How to Run It
1
Introduce the framework. Organizational culture operates along two axes: internal versus external focus, and flexibility versus stability. These produce four quadrants: Collaborate (do things together), Create (do things first), Compete (do things fast), Control (do things right). Every organization operates in all four, but every person and function tends to have a primary orientation.
2
Ask each leader independently: where does our organization currently spend most of its cultural energy? Plot it on the map without discussion.
3
Ask a second question: where does the organization need to spend more energy to succeed over the next two to three years? Plot that separately.
4
Share the maps. The differences between leaders are usually immediately visible. This is not a failure. It's information.
5
Facilitate the key reframe: these different orientations are not character flaws. They reflect genuinely different but valid organizational needs. The question is not who's right — it's how to hold the tension productively.
6
Connect back to real decisions. "When we disagreed about X last month, we were actually disagreeing about whether to prioritize Create values or Control values. That's a legitimate strategic debate about tradeoffs. It was not a personality conflict."
7
Optionally, map specific functions. Finance tends toward Control. Product tends toward Create. Understanding the structural logic of each function's orientation helps leaders stop taking each other's defaults personally.
What Good Looks Like
Leaders stop attributing disagreements to personality and start attributing them to structural orientations. Meetings produce clearer decisions because people can name the type of tradeoff they're navigating.
Watch Out For
Running this when trust is broken or interpersonal conflict has overtaken the structural disagreement. People won't engage honestly with a framework when they're in active conflict with the person in the room.
There's a version of shared leadership that's actually just unclear hierarchy with extra steps. Everyone nominally has a voice, but some voices count more, and nobody has made that explicit — and the gap between the stated model and the actual model creates friction and resentment. The Shared Leadership Framework is an attempt to do the real thing: genuinely distributed decision-making, with clarity about who decides what, and real accountability that doesn't just diffuse into the group.
Before You Start
Executive-level trust and alignment must exist first. This is not a substitute for that alignment — it's what becomes possible after it. Role clarity and basic decision rights already established at the executive level. The organization can't be in crisis. And genuine willingness from all parties to share power — not just a willingness to appear to share power.
How to Run It
1
Map the current decision landscape for the specific team. List the decisions made regularly. For each: who currently makes this? Who is affected? Who has relevant expertise that's currently not in the conversation?
2
Sort decisions into three categories. Centralized decisions are high stakes, irreversible, and have significant legal or financial implications. Distributed decisions are within someone's clear domain, reversible, and low organizational risk. Collective decisions benefit from genuine shared input.
3
Design a decision rights grid. For each decision category: who decides, who advises, who needs to be informed and when, and who holds a veto if anyone. Ambiguity about who decides is the source of more conflict than any other single organizational variable.
4
Pilot with one decision category. Choose something low-stakes and reversible. Practice the model for 90 days before expanding it.
5
Build accountability structures. Shared leadership does not mean diffuse accountability. It means accountability is distributed rather than concentrated.
6
Establish communication protocols: when decisions are made, how are they communicated, to whom, and by when? Shared leadership without clear communication creates the worst of both worlds.
7
At 90 days, assess the pilot honestly: what worked, what created confusion rather than clarity, and what needs more structure before expanding?
What Good Looks Like
Team members describe feeling like genuine contributors to direction rather than executors of someone else's decisions. Decision quality improves because the people closest to the work have meaningful input.
Watch Out For
Confusing shared leadership with consensus decision-making. Undefined "we all decide" degrades into either paralysis or hidden hierarchy — where one person still decides but everyone pretends otherwise, which is worse than acknowledged hierarchy.
