Short answer: Use McKinsey 7S to assess whether strategy, structure, systems, shared values, leadership style, staff, and skills reinforce the intended product-based direction. It is the strongest diagnostic among the choices because the problem is systemic, not merely structural.
Diagnose the Organization Before You Redraw It
A software company wants to replace regional reporting lines with product-based business units. The org chart is the visible decision. The harder question is whether the rest of the organization can make that design work.
By Michael D. Penn, SPHR SHRM-SCP · September 21, 2026
Author Expertise
Written and reviewed by Michael D. Penn, SHRM-SCP, SPHR, founder of CriticalThink HR. Michael earned all five major HR certifications in under two years and built CriticalThink HR from direct exam-prep, candidate-support, enterprise systems, and AI product work.
Updated
Short Answer
The best answer is Option C. Before recommending a product-based structure, I would use McKinsey 7S to test whether the organization's strategy, structure, systems, shared values, leadership style, staff, and skills support one another. The facts already point to cross-element friction: disputed decision rights, capability gaps, outdated performance measures, and duplicated approvals.
The framework does not choose the final design or prove that a reorganization will work. It gives the HR executive a disciplined way to identify contradictions, gather the right evidence, and avoid treating a new reporting chart as the solution to every operating problem.
- Audience
- SHRM-SCP candidates, senior HR professionals, organizational effectiveness leaders, and executives evaluating operating-model changes.
- Outcome
- A practical diagnostic sequence for separating a structural symptom from the strategy, systems, capabilities, and leadership conditions that determine whether a redesign can work.
Key Takeaways
The company may need a new structure. The scenario does not give us enough evidence to recommend one yet.
- Match the diagnostic to the problem: interdependent friction requires a whole-system view.
- Treat employee comments, SWOT findings, and job data as useful evidence within the diagnosis—not as complete substitutes for it.
- Turn the 7S findings into explicit design requirements, decision rights, measures, capability plans, and implementation tests before moving reporting lines.
The Scenario
The Options
Before recommending a design, which approach would best diagnose whether the organization’s interdependent elements support the intended direction?
A. Use SWOT
Use SWOT to classify internal strengths and weaknesses and external opportunities and threats before selecting the organization’s future structure.
B. Use an engagement survey
Use an engagement survey to measure employee sentiment about duplicated approvals and confidence in the proposed reporting arrangement.
C. Use McKinsey 7S - Defensible answer
Use McKinsey 7S to assess alignment among strategy, structure, systems, shared values, leadership style, staff, and skills before recommending a design.
D. Use job evaluation
Use job evaluation to compare the relative value of roles and establish consistent compensation relationships across the proposed units.
The Defensible Answer
The most defensible action is Option C: use McKinsey 7S to assess alignment across the organization’s interdependent elements because it directly tests whether the strategy, structure, systems, shared values, leadership style, staff, and skills reinforce or conflict with the intended direction.
CriticalThink HR™ is not affiliated with or endorsed by SHRM. SHRM is a registered trademark of the Society for Human Resource Management. This article is educational and is not legal advice.
The visible problem is not necessarily the root problem
The proposed shift sounds reasonable. Product-based units could put teams closer to customer needs and reduce the handoffs created by regional silos. But the scenario also tells us that leaders disagree about authority, current measures may reward the old model, needed capabilities may be missing, and employees experience repeated approvals. Those conditions do not disappear when boxes move on an organization chart.
That is the decision tension: leadership wants responsiveness, but it has not established what is slowing the organization or what the product model would require. Recommending a structure now would turn an untested assumption into an enterprise intervention. The stronger first move is to diagnose how the organization actually works as a system.
How to apply 7S to this decision
McKinsey describes the classic 7S framework as a constellation of interrelated factors that influence an organization's ability to change. The point is coordination, not a mechanical checklist. In this case, each element should produce questions and evidence that leaders can use to define the real design problem.
Strategy and structure
Define what “customer responsiveness” must improve, where product accountability should sit, and which decisions need global, regional, or product ownership. Then test whether the proposed structure supports those outcomes.
Systems
Map approvals, planning, budgeting, product governance, information flow, technology, and performance measures. Identify which systems create the duplicated sign-offs and whether they would follow the old logic into the new structure.
Shared values and style
Examine what leaders reward in practice, how conflict is resolved, and whether leadership behavior supports product accountability, cross-regional collaboration, and faster decisions.
Staff and skills
Determine whether the organization has enough product leadership, customer insight, commercial, technical, and change capability—and how people would be selected, developed, or redeployed.
The framework is a lens, not the finished redesign
A 7S assessment should not end with seven colored boxes and a conclusion that the organization is “misaligned.” Leaders need observable evidence: approval-cycle data, decision logs, customer-response measures, role overlaps, interviews, workflow maps, capability assessments, and examples of incentives that pull teams in competing directions. The method organizes the inquiry; the evidence supports the recommendation.
There is also a useful modern counterpoint. In 2025, McKinsey published a broader 12-element operating-model system and described it as an evolution of the classic 7S framework for a more volatile operating environment. That does not change the keyed answer: 7S is still the only option here designed to assess interdependent organizational alignment. It does remind us not to treat a classic framework as the only possible real-world diagnostic.
The output should be a set of design requirements and unresolved risks, not a predetermined org chart. For example: product leaders need defined authority over roadmaps; regional leaders need explicit market and regulatory responsibilities; shared metrics must reward customer outcomes across both dimensions; and key product-management gaps must be addressed before launch. Those are hypotheses to validate against the company’s evidence, not facts supplied by the scenario.
Why the other options are useful but incomplete
A: SWOT frames context, not operating alignment
A SWOT can summarize strengths, weaknesses, opportunities, and threats. It does not directly show how decision rights, workflows, measures, leadership behavior, capabilities, and structure reinforce or obstruct one another. Its findings can inform the 7S diagnosis, but it is not the best fit for the question asked.
B: An engagement survey locates experience, not the whole mechanism
Employee feedback can confirm where approvals, handoffs, and reporting uncertainty create friction. Sentiment alone cannot establish which governance rule, workflow, skill gap, incentive, or structural choice causes it. Use employee evidence to test the diagnosis rather than treating it as the full diagnosis.
D: Job evaluation answers a downstream rewards question
Job evaluation can compare the relative value of roles and support internal compensation relationships. It becomes relevant once accountabilities and roles are sufficiently clear. It does not tell leaders whether the proposed operating model supports the strategy.
Move from diagnosis to a decision leaders can defend
Start by defining the business outcome and the gap: what does better customer responsiveness mean, how is it measured now, and where does performance break down? Build a current-state map across the seven elements, using multiple evidence sources rather than executive opinion alone. Then define the future-state requirements and identify the conflicts between them.
Next, compare design options against those requirements. A product-based model may be strongest, but the diagnosis could also support a matrix, clearer decision rights within the regional model, shared-service changes, or targeted process repair. State the tradeoffs openly: customer proximity versus regional consistency, product accountability versus duplicated expertise, and faster local decisions versus enterprise controls.
Finally, make implementation conditional on the capabilities and systems the design needs. Assign decision owners, change the performance measures, close priority skill gaps, remove redundant approvals, and define leading indicators for a bounded transition. The sequence matters: diagnose, design, test, then scale.
Why this is a SHRM-SCP judgment question
SHRM's official 2026 certification-preparation outline places Organizational Effectiveness and Development within the Organization knowledge domain. This scenario applies that area at the senior level: HR is not merely administering a reorganization. The HR executive is defining the problem, selecting a diagnostic that matches it, challenging an attractive structural shortcut, and advising leaders on an integrated operating decision. This is an instructional alignment, not a claim that SHRM wrote or endorsed this practice question.
The same reasoning pattern appears in the performance-metrics misalignment walkthrough, where the visible personnel decision points back to the system producing it. The leadership-framework equity-audit scenario applies the sequence at a different scale: diagnose the mechanism before standardizing and expanding the intervention.
The reusable rule is straightforward: when the facts point to conflict across several organizational elements, choose the approach that can examine those elements together. Know the framework, understand its limits, and use it to make a decision you can explain under pressure.
Video chapters
Frequently asked questions
Why is McKinsey 7S the best answer in this scenario?
The question asks whether several interdependent organizational elements support the intended direction. McKinsey 7S is the only option that directly examines those elements together before leaders choose a structure.
Does a 7S assessment tell leaders which structure to adopt?
Not by itself. It helps leaders identify where the current system reinforces or conflicts with the strategy. Decision-rights analysis, workflow evidence, design options, risk analysis, and implementation planning are still needed before recommending a final structure.
Why is SWOT not the strongest first choice?
SWOT can frame internal and external conditions, but it does not directly map how strategy, reporting relationships, operating systems, leadership practices, capabilities, people, and shared values interact.
Should employee feedback be part of an organizational redesign?
Yes. Employee comments and survey data can reveal where friction is experienced and help test hypotheses. They are inputs to a broader diagnosis, not a substitute for evaluating the full operating system.
When does job evaluation become relevant?
Job evaluation becomes relevant when leaders need to compare the relative value of roles and establish internal compensation relationships. That work follows clarity about the operating model and role accountabilities; it does not diagnose strategic alignment on its own.
Disclaimer: CriticalThink HR™ is not affiliated with or endorsed by SHRM. SHRM, SHRM-CP, and SHRM-SCP are registered trademarks of the Society for Human Resource Management. This walkthrough is for educational purposes only and does not provide legal advice.
Would you redesign the chart—or diagnose the system first?
Explore how CriticalThink HR teaches the reasoning behind plausible choices, including what the strongest answer solves and what it still cannot prove. Know it. → Understand it. → Apply it under pressure.
Put this practice decision in context
This is an original educational scenario. Its answer explains the facts and choices presented, rather than a rule for every workplace. Use the official SHRM BASK to review the competency framework and verify current requirements with the relevant primary authority.
Continue with the SHRM-SCP strategic practice track or the free practice library.
For a related governance exercise, work through the hybrid-work mandate and the fair-hiring and AI-bias scenario.