What needs to be finished first
A written up-to-date strategy or clear strategic goal exists so the question "Strategy fit?" can be answered.
A map of relevant internal stakeholders across hierarchies exists so the right data sources for each S can be addressed.
What needs to be ready before start
7S diagram template (six S around Shared Values in the center); strategy document; org chart; list of core processes; HR data on skills and staffing; values and culture snippets from employee surveys.
A moderator with operating model experience; four to eight participants from Strategy, HR, Operations, Engineering, and line teams; one employee representative, not only leadership; one scribe.
Strategy document for the last twelve months; org chart; engagement score and top three themes from employee survey; list of ongoing change initiatives; turnover rate in the last 24 months.
4-6 h workshop, plus 1 week of pre-work on data collection
Hang the 7S diagram with Shared Values in the center and six connected S around it. One A4 card with three guiding questions per S. Fit-to-strategy rating scale 1-5. A tension note wall for each unresolved S-to-S tension pair.
The one question this method answers
Which seven S are not aligned and which tension most strongly threatens execution of the strategy?
Marker: Phase
| Step | Duration | Action | Hint |
|---|---|---|---|
1Phase 1: Strategy as anchor | 30 min | Write the strategy in three sentences on the wall. Pull out three strategic priorities for the next 12-18 months, against which all other S are assessed. | If the strategy cannot be captured in three sentences, there is no anchor. Pause the method and clarify strategy first. |
2Phase 2: Capture hard S | 60 min | For each hard S (Strategy, Structure, Systems), describe current state, rate fit to strategy 1-5, and add rationale. Concrete evidence: org-chart anomalies, tool stack, process breaks. | Structure is more than the org chart. Reporting lines, decision rights, and interfaces are often the real issue. |
3Phase 3: Capture soft S | 90 min | For each soft S (Skills, Style, Staff, Shared Values) describe current state and rate fit to strategy 1-5. Evidence: concrete behavior examples, capability gaps, values conflicts, not abstract adjectives. | Soft S quickly turns into wishful language. Describe observable behavior instead: what actually happens in meetings, decisions, and conflicts. |
4Phase 4: Tension matrix | 60 min | Assess each 7x7 tension combination: does S-A fit S-B or create friction. Identify at least five concrete tensions and mark on the wall. Prioritize the top three. | A frequent tension is that new strategy demands speed while systems are slow and skills are missing. Tension is the key value of the method, not the individual rating. |
5Phase 5: Intervention roadmap | 60 min | For each of the top three tensions define a concrete intervention with owner, timeline, and success signal. Respect that soft S takes longer than hard S. | Anyone trying to change soft S in one quarter is planning theater. A realistic horizon is hard S 3-6 months, soft S 12-24 months. |
What comes out at the end
Structured document with strategic anchor, seven S sections (rating 1-5, evidence, data source), tension matrix with top-3 tensions, and intervention roadmap with owner and timeline.
Include date and decision circle in header. Re-diagnose yearly or during major change programs. Archive previous versions instead of overwriting. Track intervention progress separately in quarterly review.
Compact working template for McKinsey 7S with context, input, output artifacts, and next step.
Analyzes organizations through Strategy, Structure, Systems, Shared Values, Skills, Style, and Staff.
When and for what do we use this method?
Which data, observations, decisions, or materials are available?
Short notes along the runsheet.
Owner, date, and success signal.
Concrete filled scenario, fictional example
Concrete filled scenario, fictional example
Strategy: Platformization of three product lines by Q2/2027, reduction of technical debt by 40% according to Tech Radar.
Structure 2/5 — Three product tribes with self-governed platform teams, no central platform ownership. Conflict with strategy.
Systems 3/5 — CI/CD exists, but varies by tribe. Code review standards are inconsistent, onboarding takes 6-8 weeks.
Style 2/5 — Leadership remains project-driven, quarter planning is milestone-led instead of platform metrics.
Staff 3/5 — Seniority is 28%, with 60% concentrated in one tribe. Platform experience is concentrated in four people.
Skills 2/5 — Domain-Driven Design knowledge is present, but Platform Engineering skills (SRE, Internal Developer Platform) are not widely available.
Shared Values 3/5 — "Move fast" mantra conflicts with platform maturity.
Top-3 tensions:
Intervention roadmap:
Recognize symptoms and steer against them
Style or Shared Values are described with adjectives such as "trustful" or "innovative" instead of observable behavior.
Enforce three concrete scenes from the last four weeks for each soft S: what was said, what was done, what was not done.
Strategy, Structure, and Systems are discussed in depth while soft S gets only 20 min.
Reserve at least 50% of workshop time for soft S. Soft S is often the real bottleneck.
All S receive 3/5, no tension becomes visible, analysis stays politically correct.
Rate individually first, then compare openly. If spread is more than 2 points, discuss that pair separately instead of averaging.
Ratings are leadership-driven; team practice is not visible.
Ensure at least one non-leadership person contributes per soft S. Include engagement score, exit interview themes, and daily observations.
Ten actions are listed without order, owner, or timeline.
Limit to three interventions with owner, quarter, and success signal. More than three at once overwhelms the organization.
Soft S is expected to change within one quarter; plan ignores cultural inertia.
Set soft S at 12-24 months and hard S at 3-12 months. Use quarterly milestones as learning points, not finish lines.
Done signals checkable in under a minute
Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.