The core idea
The Managerial Grid uses concern for production and concern for people, conventionally scored from 1 to 9. Five familiar positions are 1,1 impoverished, 1,9 country-club, 9,1 authority-compliance, 5,5 middle-of-the-road and 9,9 team management. The grid argues that attention to people and results need not be opposites. Its preferred high–high position is an aspiration within the model, not proof that one approach delivers the best outcome in every situation. Concern is an orientation, not a measured production or satisfaction result.
Source and attribution [1]Using it in practice
Discuss a real decision where delivery and people’s needs appeared to conflict. Ask what alternatives were considered and which constraints were assumed fixed. Examine whether a manager avoided a necessary conversation to preserve harmony, or achieved a target by shifting unsustainable pressure onto colleagues. Use the grid to explore options rather than assigning an apparently precise numerical personality score from a short conversation.
An example, not a reported case
Worked example · illustrative
A hypothetical operations manager repeatedly approves overtime to protect service and then praises the team’s commitment. Another manager avoids discussing late work because the conversation feels uncomfortable. A development session uses these incidents to examine how both delivery and people can receive more deliberate attention. Managers try earlier capacity reviews, clearer priorities and constructive feedback. They review workload and service quality together instead of assuming a high–high label demonstrates success.
What to watch for
Self-ratings can reflect aspiration more than behaviour. Different colleagues may experience the same manager differently. The framework simplifies context, power and resource constraints, and its recommended position should not be presented as a universal empirical law. Formal Grid assessments and training materials are distinct from this original explanatory sketch.
The four corners
The low–low corner prompts questions about withdrawal and minimum effort. High people/low production prompts questions about harmony at the expense of difficult decisions. High production/low people prompts questions about pressure and disregard for employee experience. High–high asks how commitment and delivery might reinforce each other. These are diagnostic prompts, not accusations to attach to named colleagues.
The middle position
Middle-of-the-road management suggests compromise between the two concerns. In a workshop, ask whether a compromise is sensible under the constraints or simply avoids a more difficult redesign. Sometimes the task can be reorganised so that quality and workload both improve. At other times a genuine trade-off needs an explicit decision.
Move from label to behaviour
Choose a behaviour that colleagues can observe: clearer prioritisation, a timely performance conversation or a better response to workload concerns. Agree what the manager will do differently and invite feedback after a comparable situation. Avoid turning the exercise into a competition for the most flattering self-description.
Check both sides
Review an operational outcome and an employee-experience indicator together. Ask whether a short-term gain has created hidden rework, exhaustion or avoidance. Keep the measures proportionate to the decision. A balanced review is more useful than claiming that a point on the grid predicts performance.
Replace self-ratings with behavioural examples
Ask what high concern for people and production would look like in a specific situation. For a service deadline, people-related behaviour might include checking capacity and support; production-related behaviour might include clarifying quality and priorities. A leader can describe themselves as high on both while behaving differently under pressure. Use examples from colleagues and actual decisions rather than relying on an aspirational position on the grid.
Examine a difficult trade-off
Imagine a manager repeatedly covering a staffing gap through overtime. They may believe they are protecting delivery, but the arrangement can affect fatigue and retention. Another manager may avoid a difficult performance conversation to preserve harmony, leaving colleagues to carry extra work. Discuss what a response attentive to both people and results would require: realistic capacity, clear expectations, support and a decision about priorities. The grid prompts that conversation but does not supply the answer.
Set one observable development action
Choose a behaviour that addresses the identified gap. A manager who avoids challenge might practise timely, specific feedback; one who overlooks workload might include a capacity check before accepting new work. Agree who will provide feedback and when. Do not turn development into a demand that every decision achieves a perfect balance. Some constraints are organisational and require escalation rather than a change in the manager's personal style alone.
Avoid treating the preferred corner as proof
The familiar high-people, high-production position is an aspiration within the model, not evidence that a leader has achieved superior results. Context, resources and competing demands matter. Use the framework alongside employee experience and operational outcomes. If using a formal proprietary assessment, follow its authorised materials; this editorial sketch is a discussion aid. Review whether the chosen behaviour helps, rather than celebrating a movement on an informal score.
Look for evidence behind each concern
Concern for people is not the same as avoiding difficult conversations, and concern for production is not the same as demanding speed. Ask what the manager does when quality slips, workloads rise or employees disagree. A supportive manager may protect a team from unrealistic work while still setting demanding standards. A manager who appears friendly but withholds useful feedback can undermine both development and results.
Test a move towards joint problem solving
Take one recurring tension, such as late handovers. Agree the service requirement, ask employees what makes it difficult and examine the workflow together. A useful response might clarify responsibilities and provide overlap time rather than alternate between pressure and reassurance. Review quality and employee experience together. The high-high position is a normative ideal within the grid, not proof that a single leadership style is optimal in every emergency, organisational context or stage of development.
Take it into your next conversation
Three useful questions.
- What does this particular situation need from the leader?
- How will colleagues experience the approach, including those with less influence?
- What evidence would tell us to continue, adjust or stop?
Related terms
Go to the evidence
Sources & attribution
Further reading: Jo Owen (2021), The Leadership Skills Handbook: 100 essential skills you need to be a leader, 5th edition, PDF pp. 80, 82, 90, 92 and 122. Edition & reading notes ↗
[1] Grid International: the Grid approach and its origins ↗
The core idea is an original summary of the cited work. Application notes, examples and sketches are our interpretations, not quotations or reproductions of the authors’ figures. Publisher records may require access to read the full original work.
Application guidance expanded on 26 September 2026. These practical suggestions and invented examples are editorial explanations; further-reading sources are not the original authors of the historical models unless expressly identified. Original overview review dates are retained.
Published 2026-09-20 · Reviewed 2026-09-22. Editorial approach