The Weisbord Six‑Box Model is a practical organizational diagnosis framework used to understand how an enterprise actually functions and where performance frictions originate. It organizes inquiry into six domains—Purpose, Structure, Relationships, Rewards, Leadership, and Helpful Mechanisms—so leaders can see the whole system and pinpoint misalignments.
In plain terms, it’s a structured way to ask: Are we clear on why we exist and what we’re trying to achieve (Purpose)? Is work organized to deliver that (Structure)? Do people and units work together effectively (Relationships)? Do we reward the right behaviors (Rewards)? Are leaders orchestrating the system (Leadership)? And do our processes and tools help, not hinder (Helpful Mechanisms)?
This is an organization and operating‑model diagnostic. Consultants and executives commonly use it as a rapid, high‑signal assessment early in transformations, post‑merger integrations, and turnarounds to focus change on the few issues that matter most.
2. Origin and Background
The Six‑Box Model was created by Marvin R. Weisbord, an organizational development (OD) scholar and consultant, in the mid‑1970s. He introduced it in the 1976 article “Organizational Diagnosis: Six Places to Look for Trouble With or Without a Theory” and elaborated it in his book “Organizational Diagnosis: A Workbook of Theory and Practice” (1978). Weisbord later popularized related practices in “Productive Workplaces.”
Weisbord designed the model to help leaders and consultants diagnose organizational problems systematically without requiring a single grand theory. It distilled decades of OD practice into six accessible categories that capture both formal organization and informal dynamics. The framework spread through OD consulting, executive education, and management literature, and remains a staple of organizational diagnosis.
3. How the Weisbord Six‑Box Model Works
The model’s core logic is alignment: organizational performance depends on how coherently the six domains fit together and reinforce one another, in the context of the external environment. Misalignments—say, a customer‑centric purpose with product‑centric incentives—create friction, slow decisions, and degrade results.
Weisbord also emphasizes the interplay between formal systems (structure, processes) and informal systems (relationships, leadership norms). Diagnosing only one side misses the heart of many execution issues.
The Six Boxes
Purpose: Why the organization exists and what it is trying to accomplish—mission, strategy, goals, and success definitions. Key questions:
Is the mission clear and widely understood?
Do goals cascade into meaningful objectives at each level?
Is there alignment between stated purpose and actual priorities?
Structure: How work and decision rights are organized—groupings (e.g., product, customer, geography), spans and layers, governance bodies, and accountability. Key questions:
Is the primary basis of grouping aligned with strategy?
Are decision rights clear and at the right level?
Do interfaces between units enable value creation or create bottlenecks?
Relationships: The quality of interactions within and across teams, functions, and with technology. It covers trust, collaboration norms, conflict resolution, and people–technology fit. Key questions:
Do teams collaborate across silos to serve the customer?
Are there productive ways to surface and resolve conflicts?
Does the technology support how people actually work?
Rewards: What gets measured, recognized, and compensated—KPIs, incentives, performance management, advancement criteria, and informal recognition. Key questions:
Do metrics and incentives reinforce enterprise outcomes, not just local optimization?
Are desired behaviors (e.g., collaboration, customer outcomes) visibly rewarded?
Do people see a fair link between contribution and recognition?
Leadership: How leaders set direction, integrate the system, make decisions, and role‑model behaviors. This includes clarity of priorities, consistency, and the ability to resolve trade‑offs. Key questions:
Do leaders consistently communicate the “why,” not just the “what”?
Are leaders resolving cross‑functional tensions or deferring them?
Do leadership behaviors match stated values and goals?
Helpful Mechanisms: The processes, tools, and routines that enable work—planning and budgeting, decision cadences, information systems, meeting rhythms, and methodologies. Key questions:
Do mechanisms accelerate decisions and learning, or create drag?
Are data and systems integrated enough to support end‑to‑end work?
Are operating mechanisms right‑sized: lightweight where possible, standardized where valuable?
Considering the External Environment
While not one of the six boxes, Weisbord highlights the external environment—the market and stakeholder context—as a boundary condition. Effective diagnosis tests whether the six internal domains are fit for the current and expected environment (customers, competitors, regulation, technology, partners).
Formal vs. Informal Systems
Formal: Purpose, Structure, Helpful Mechanisms often manifest in documents, org charts, and systems.
Informal: Relationships, Leadership behaviors, and actual Reward signals (what gets praised) are experienced day‑to‑day.
Performance depends on the congruence between formal intent and informal reality. The Six‑Box Model surfaces gaps between the two.
4. When to Use the Weisbord Six‑Box Model
Use the Six‑Box Model when you need a fast, holistic read on organizational effectiveness and a way to focus limited change capacity on the few issues that matter most.
Enterprise or BU transformations: Early‑stage diagnostic to aim the operating‑model redesign.
Post‑merger integration: Compare and reconcile differences across the six boxes; target culture, incentives, and mechanisms that must harmonize.
Persistent execution gaps: When strategy seems sound but results lag and root causes are unclear.
Rapid growth/scaling: Ensure systems, roles, and leadership practices keep pace with scale and complexity.
Health and culture resets: Identify where informal norms and rewards undermine formal goals.
Especially powerful when: speed matters; data are patchy; stakeholder engagement is essential; you need a shared language for systemic issues.
Less suitable when: you need deep process engineering (use Lean/Six Sigma), detailed collaboration analytics (use organizational network analysis), or precise financial portfolio decisions (use finance and market models). The Six‑Box Model is a diagnostic lens, not a substitute for specialized toolkits.
Current practice: Modern applications combine the Six‑Box Model with quantitative org diagnostics (decision latency, spans/layers, engagement), behavioral data (ONA), and agile/OKR operating mechanisms to move from insight to concrete design.
5. How to Apply the Weisbord Six‑Box Model: Step‑by‑Step
Clarify the objective and scope.Define what decision the diagnostic must inform (e.g., target operating model, PMI blueprint, turnaround priorities). Specify the unit of analysis (enterprise, BU, function) and time horizon. Agree on success criteria and constraints.
Assemble a diverse core team.Include leaders and respected operators from key functions and geographies. Name an executive sponsor and a facilitator. Diversity of perspective boosts candor and insight, especially for Relationships and Rewards.
Gather baseline artifacts and data.Collect strategy docs, org charts, process maps, KPI trees, incentive plans, performance data, engagement surveys, and customer metrics. Where available, include decision cycle time, time‑to‑market, NPS/CSAT, and attrition/retention data.
Conduct targeted interviews and pulse surveys.Use the six boxes to structure interviews across levels and functions. Ask for concrete examples of where the system helps or hinders outcomes. Run a short pulse survey to quantify perceptions (e.g., clarity of purpose, decision speed, cross‑team collaboration, incentive alignment).
Build the Six‑Box diagnostic map.Synthesize findings into a one‑page view for each box: what’s working, what’s not, evidence, and implications. Use simple ratings (e.g., 1–5) for effectiveness and alignment. Call out contradictions across boxes (e.g., collaborative values vs. individual‑quota incentives).
Identify critical misalignments and root causes.Not all issues are equal. Use an impact–feasibility matrix to isolate the few misalignments that most constrain outcomes. Apply 5 Whys and evidence review to separate symptoms (slow approvals) from causes (unclear decision rights; misaligned KPIs).
Co‑create design principles and target shifts.Translate findings into 6–8 design principles (e.g., “push decisions to the edge,” “team‑based outcomes,” “customer journey over function”). For each box, define specific target shifts (e.g., new grouping for Structure, revised comp mix for Rewards, quarterly business reviews for Helpful Mechanisms).
Convert into initiatives with owners and metrics.Bundle related actions into initiatives with clear owners, milestones, and success measures. Examples: Decision architecture and RAPID, incentive redesign, cross‑functional portfolio council, leadership behaviors and rituals, CRM/process modernization.
Pilot, measure, and adapt.Test in a unit or region. Track leading indicators (decision cycle time, handoff defects, participation in new rituals) and outcomes (NPS, time‑to‑market, productivity). Use feedback to refine before scaling.
Institutionalize governance and learning.Stand up a transformation cadence (monthly/quarterly) to review progress across the six boxes. Refresh the diagnostic after major changes or quarterly during transformation to sustain alignment as conditions evolve.
6. Example: The Six‑Box Model in Action
Company: A $500M regional retail bank accelerating its digital transformation and struggling with slow product launches and inconsistent customer experiences.
Problem: Despite a clear aspiration to grow digital deposits and lending, new features arrived late, branch and digital teams worked at cross‑purposes, and NPS was stagnant. Leadership suspected “process issues,” but root causes were unclear.
Applying the Six‑Box Model:
Purpose: Clarified the mission as “trusted, simple banking that meets customers where they are,” set three measurable goals (digital sales mix, time‑to‑account‑open, NPS), and cascaded them to product, branch, and operations.
Structure: Shifted from a purely functional model to a product–journey structure for key customer journeys (onboarding, payments, lending) with accountable product owners; retained shared risk and compliance.
Relationships: Identified friction between risk, IT, and product; created cross‑functional squads and a weekly triage forum to resolve blockers. Established clear handoffs between branch and digital sales.
Rewards: Moved branch incentives from transaction counts to customer outcomes (account activation, digital adoption). Introduced team‑based OKRs for cross‑functional squads.
Leadership: Instituted a monthly “customer journey review” led by the COO; executives role‑modeled trade‑off decisions (e.g., fewer custom offers, more standardized journeys) and shortened approval cycles.
Helpful Mechanisms: Implemented a shared backlog, two‑week sprint cadence, and an offer lifecycle with stage gates. Upgraded analytics to provide near‑real‑time funnel visibility.
Insights: The biggest constraints were misaligned incentives (Rewards) and unresolved cross‑functional tensions (Relationships), amplified by slow decision mechanisms. Structure was part of the answer, but behavior change came from aligning rewards and leadership rituals.
Results: Within two quarters, time‑to‑account‑open dropped 40%, digital sales mix rose from 28% to 44%, and NPS improved by 8 points. The bank scaled the model to lending with similar gains.
7. Strengths and Limitations
Strengths
Simple, holistic lens: Six intuitive categories cover both formal and informal systems, making it easy to start and hard to overlook key factors.
Accelerates shared understanding: Provides a common language for executives and teams to discuss systemic issues without jargon.
Participation‑friendly: Works well in interviews and workshops, encouraging broad engagement and candor.
Flexible and scalable: Useful for enterprise‑level diagnostics and for specific functions or units.
Bridges to action: Surfaces contradictions (e.g., purpose vs. rewards) that translate directly into design and change initiatives.
Limitations
High‑level by design: Does not provide the depth of process engineering, decision design, or capability modeling; needs complementary tools.
Subjectivity risk: Without data, assessments can reflect opinion or the loudest voices; requires triangulation and evidence.
Limited explicit external focus: The environment is acknowledged but not built into the six boxes; practitioners must bring the outside‑in view.
Not prescriptive on sequence: Highlights misalignments but doesn’t dictate the order of interventions or resource allocation.
8. Common Pitfalls (and How to Avoid Them)
Treating it as a checklist, not a diagnosis.What goes wrong: Teams tick through the boxes superficially and miss root causes.
How to avoid: Demand evidence and examples; ask “why” repeatedly; prioritize by business impact.
Over‑focusing on Structure.What goes wrong: Org charts change, behaviors don’t.
How to avoid: Pair structural moves with Rewards, Helpful Mechanisms, and Leadership behaviors that reinforce the new ways of working.
Ignoring informal dynamics (Relationships).What goes wrong: Unspoken conflicts and trust issues derail execution.
How to avoid: Use interviews and safe forums to surface tensions; create explicit conflict‑resolution and collaboration mechanisms.
Misaligned metrics and incentives.What goes wrong: People optimize for local goals that contradict enterprise outcomes.
How to avoid: Rebalance KPIs and incentives to include shared outcomes; reduce measures that drive silo behavior.
Vague Purpose and cascading goals.What goes wrong: Teams can’t translate vision into decisions.
How to avoid: Make goals concrete (measurable, time‑bound) and connect them to team‑level OKRs or scorecards.
Underpowered Helpful Mechanisms.What goes wrong: Decision cadences, tools, and data aren’t upgraded, creating execution drag.
How to avoid: Right‑size mechanisms; standardize where it adds speed and clarity; invest in data and workflow integration.
One‑and‑done assessment.What goes wrong: Initial fixes drift as strategy or market conditions change.
How to avoid: Reassess quarterly during transformation and after major events (e.g., acquisitions, leadership changes).
9. How the Six‑Box Model Relates to Other Frameworks
McKinsey 7S Framework: Both are holistic diagnostics. 7S adds explicit elements for Skills, Systems, and Shared Values and emphasizes alignment among “hard” and “soft” levers. Use 7S for a deeper alignment view; Six‑Box for a fast, participation‑friendly diagnosis and conversation starter.
Galbraith Star Model: The Star (Strategy, Structure, Processes, Rewards, People) is more prescriptive for operating‑model design. Use Six‑Box to identify issues, then the Star to engineer the target design and sequencing.
Nadler–Tushman Congruence Model: Similar emphasis on fit among work, people, structure, and culture. Congruence provides a more formal “input–transformation–output” logic; Six‑Box offers a simpler, workshop‑ready lens.
Burke–Litwin Model: A comprehensive change model linking external environment, transformational and transactional factors. Use Burke–Litwin when you need to model causality across many variables; Six‑Box for rapid scoping and prioritization.
Leavitt’s Diamond: Focuses on task, structure, people, and technology. Six‑Box extends this by adding leadership, rewards, and helpful mechanisms.
Implementation tools: RACI/RAPID (decision rights), OKRs/Balanced Scorecard (metrics), ONA (collaboration patterns), and Lean/Six Sigma (process detail) often plug into Six‑Box findings to drive action.
Choosing among them: Use the Six‑Box Model when you need a fast, inclusive diagnostic to surface systemic issues and align leaders. Pair it with design frameworks (Star, 7S) and execution toolkits to move from insight to sustained behavior change.
10. Key Takeaways
The Weisbord Six‑Box Model is a holistic diagnostic across Purpose, Structure, Relationships, Rewards, Leadership, and Helpful Mechanisms.
Its value lies in surfacing misalignments—especially between formal systems and informal behaviors—and translating them into actionable priorities.
Best used early in transformations, integrations, and turnarounds to focus change energy on the few issues that matter most.
It’s a lens, not a blueprint; combine it with deeper analytics and design frameworks to engineer the target operating model.
Biggest caution: avoid superficial checklisting—demand evidence, engage stakeholders, and revisit the diagnosis as conditions evolve.
11. FAQs About the Weisbord Six‑Box Model
Is the Six‑Box Model still relevant today?
Yes. Its strength—simple, systemic diagnosis—remains highly relevant. Modern practice augments it with quantitative diagnostics (decision latency, spans/layers, engagement), agile operating mechanisms, and digital tooling to turn insights into tangible design changes.
How does the Six‑Box Model differ from McKinsey’s 7S?
Both are holistic. 7S explicitly includes Skills, Systems, and Shared Values and is often used to design or assess alignment across “hard” and “soft” elements. The Six‑Box Model is lighter‑weight and participation‑friendly, ideal for rapid diagnosis and focusing conversation before deeper design work.
When should I use Six‑Box vs. the Galbraith Star Model?
Use Six‑Box to diagnose what’s off and why—especially when causes are unclear or you need broad engagement. Use the Star Model to engineer the target operating model (structure, processes, rewards, people) once priorities are known.
Can small or early‑stage companies use the Six‑Box Model?
Absolutely. In startups and SMBs, a half‑day workshop guided by the six boxes can surface critical issues quickly. Keep it pragmatic: a short list of actions per box and owners is often enough to unlock momentum.
How long does a Six‑Box diagnostic typically take?
A focused BU‑level diagnostic can be completed in 2–4 weeks (document review, 15–25 interviews, pulse survey, synthesis). Enterprise‑wide efforts typically run 4–6 weeks, followed by design sprints using complementary frameworks and tools.
The model’s core logic is alignment: organizational performance depends on how coherently the six domains fit together and reinforce one another, in the context of the external environment. Misalignments—say, a customer‑centric purpose with product‑centric incentives—create friction, slow decisions, and degrade results.
Weisbord also emphasizes the interplay between formal systems (structure, processes) and informal systems (relationships, leadership norms). Diagnosing only one side misses the heart of many execution issues.
Use the Six‑Box Model when you need a fast, holistic read on organizational effectiveness and a way to focus limited change capacity on the few issues that matter most.
