Measures the design, not the diagram
An org chart shows reporting lines. The score shows whether decisions move, whether handoffs land, and whether people know what they own, which is what a design is actually for.
PR-02 + CU-01
Organizational design assessment: score your organizational structure and handoffs
Reorganizations usually change the chart and leave the problem in place. The reason is that most of what makes a design work sits underneath the boxes: who can decide without asking, where work stalls between teams, and whether anyone knows who owns the handoff. This scores those conditions before you move a single reporting line.
FLAT MONTHLY PRICE FROM $49 · WHOLE COMPANY · NO PER-EMPLOYEE FEES
SAMPLE READOUT · DEMO DATA
RUNS IN YOUR BROWSER
QUESTION OF · ANSWERED YOUR SCORE · ANSWERS
/100
DIAGNOSTIC READINESS SCORE, NOT A CERTIFIED AUDIT
67
/100
PRIORITIZED ACTION PLAN
NOTHING IS UPLOADED OR SAVED
/100
/100
YOUR FIRST THREE MOVES
This is one person's read of the company. The real report asks your people the same questions anonymously, twelve per area, and scores what they answer rather than what you assume. Your first assessment is free.
ILLUSTRATIVE SCORES. DIAGNOSTIC INPUT, NOT A CERTIFIED AUDIT.
DIRECT ANSWER
An organizational design assessment measures whether a company's current structure actually supports the work, rather than describing what the structure is. The recognized models frame the question well: Jay Galbraith's Star Model treats design as five interdependent choices, strategy, structure, processes, rewards, and people, and argues that changing structure alone rarely changes behavior. McKinsey's 7S and the Burke-Litwin causal model make the same point from different angles. What none of these frameworks give you is a measurement. Assessmentcloud scores the conditions those models say determine whether a design works: process maturity and handoff quality (PR-02), role clarity and decision-making confidence inside the culture dimension (CU-01), digital and data maturity where the workflow actually lives (DM-03), skills coverage against the roles the design assumes (SG-04), and compliance readiness (CR-05). Each returns 0 to 100 against your industry median, and the report ranks which of them is most likely to be the real constraint. Honest boundaries: this is not org-chart software and not a position-management or headcount-modeling platform. It does not draw structures, model spans and layers from HRIS records, or cost a restructure. It tells you whether the design you have is working and where it is breaking, which is the question most reorganizations skip.
Go deeper: this dimension works alongside organizational diagnosis and organizational effectiveness, and the guides on organizational diagnosis models and organizational development show the frameworks behind the scoring.
LANDSCAPE
The established organizational design frameworks, and what each one does not do
Organizational design has a strong literature and almost no measurement. The models below are genuinely useful for structuring the conversation, and three of them are free to use because they are published. What separates them in practice is not quality, it is what each one asks of you before it produces anything.
| Framework or tool | Published by | What it gives you | What it requires from you |
|---|---|---|---|
| Star Model | Jay Galbraith, in Designing Organizations and related work | Five interdependent design levers: strategy, structure, processes, rewards, and people. Its central claim is that structure alone cannot deliver a strategy, so changing the chart without changing processes and rewards predictably fails | Judgment and facilitation. The model names the levers and deliberately does not score them, so what you get out depends entirely on who is in the room |
| McKinsey 7S | Peters, Waterman and Phillips, McKinsey, early 1980s | Seven elements split into hard (strategy, structure, systems) and soft (shared values, skills, style, staff), used to test whether the elements are aligned with each other | The same facilitation cost, plus a tolerance for its age. It is a checklist for alignment, not a diagnostic instrument, and it produces no number |
| Burke-Litwin causal model | Burke and Litwin, in the Journal of Management, 1992 | Twelve factors arranged causally, separating transformational factors like leadership and culture from transactional ones like structure and systems. The most useful of the three for arguing about cause rather than correlation | Real effort. Twelve interacting factors is a lot of model, and using it well generally means a consultant who has used it before |
| Org design and workforce analytics platforms | Commercial vendors in the org-analytics category | Structure modeling from HRIS data: spans and layers analysis, scenario modeling, cost of a proposed structure, and position management. Genuinely the right tool if your question is what the new chart should look like | Clean HRIS data, an owner for the tool, and an enterprise sales conversation. These are implementation projects, not sign-ups |
| Assessmentcloud | This platform | A 0 to 100 score against your industry median on the conditions the models above describe qualitatively: process maturity and handoffs, role clarity and decision confidence, digital maturity, skills coverage, and compliance readiness, with the weakest ranked first | About 15 minutes per respondent and under 20 minutes of setup. Flat from $49 a month for the whole company, and it does not draw or cost a structure |
These are complements, not substitutes, and the sequence matters. The models tell you what to think about, an analytics platform tells you what a proposed structure would look like and cost, and a benchmarked assessment tells you whether the design you already have is working. Running the third one first is the cheapest step and the one most often skipped, because it is the only one that produces a number you can compare against after the change. Our guide to organizational diagnosis models works through Weisbord, Nadler-Tushman and Burke-Litwin in detail, and the organizational effectiveness assessment covers the outcome side of the same question.
PR-02 + CU-01
What you get
A baseline before you restructure
Score the current design first, so that after the change you can tell whether it worked. Reorganizations run without a baseline are almost impossible to evaluate honestly afterward.
Unit against unit, not one blended number
Run each function or business unit separately. Design problems are almost always local, and a single company-wide average is the fastest way to hide the one team where the structure is failing.
Flat price, whole company
From $49 a month for the entire organization, no per-employee fee, so re-scoring after the change costs nothing extra.
HOW IT WORKS
From setup to scored report
01
Set the scope
Assess the whole company or one function. Most design questions are about a specific boundary, so scoping to the two units either side of it gives a sharper read than a company-wide run.
02
Ask the people inside the design
Question sets go to the people doing the work, anonymously, in 10 to 15 minutes. The gap between how leadership and staff rate role clarity is usually the finding.
03
Read the scored dimensions
Each dimension returns 0 to 100 against your industry median, with the weakest ranked first and the evidence behind each rating shown.
04
Change something, then re-score
Fix the ranked constraint, re-run the assessment next quarter, and check the number moved before declaring the redesign a success.
DIAGNOSTIC INPUT, NOT A CERTIFIED AUDIT.
Assessmentcloud scores tell you how ready you are and what to fix. They do not certify you against SOC 2, ISO 27001, or any legal framework, and we never claim they do. Only an accredited auditor can certify you. Run the diagnostic first, walk into the audit without surprises, and spend auditor hours on certification instead of discovery.
FAQ
Questions about organizational design assessment
An organizational design assessment measures whether a company's structure actually supports the work it has to do. It looks at role clarity, decision rights, how work moves between teams, and whether the processes and skills the design assumes are really in place. The output is a read on where the design is breaking, not a description of the current chart.
Test it against four things rather than judging the chart. Can decisions be made at the level where the information sits, or does everything escalate. Do handoffs between teams complete without chasing. Does each person know what they own and who owns the next step. And does the structure survive contact with the actual workflow, or has an informal shadow structure grown up beside it. Score each, compare against a benchmark, and the weakest one is your design problem.
Structure is the chart: reporting lines, units, and levels. Design is the whole set of choices that make the structure work, including processes, decision rights, information flow, rewards, and the skills people need. Galbraith's Star Model exists mainly to make this point, that structure is one of five levers and changing it alone usually moves nothing.
Four show up repeatedly. Decisions stall because nobody is sure who has the authority. The same work is done twice in two teams, or falls between them. Meetings exist mainly to coordinate across a boundary the structure created. And there is a well-known informal route people use to get things done because the formal one is too slow. Each of these is measurable, which is the point of assessing rather than debating it.
Before a restructure, so you have a baseline to judge it against afterward. After a merger, when two designs are still running in parallel. When headcount has grown enough that the informal coordination that used to work has quietly stopped working, which for most companies is somewhere between 50 and 150 people. And roughly annually after that, because designs decay as strategy moves under them.
Not for the diagnostic step. A benchmarked self-assessment tells you which conditions are weak and how far you sit from your industry median, and that is often enough to decide where to act. Consultants earn their fee on the redesign itself, which is genuinely hard, and handing them a measured baseline makes that engagement shorter and sharper than paying them to find where the problem is.
Put organizational design assessment on your company readout
ILLUSTRATIVE FIGURES. NOT CUSTOMER DATA.
FLAT MONTHLY PRICE. NO PER-EMPLOYEE FEES.