PM leadership theory
Examine performance and group maintenance behaviors using observations and team feedback, then choose an improvement.
Jyuji Misumi's PM leadership theory considers two leadership functions: P (Performance), advancing goals and work, and M (Maintenance), sustaining the group and its cooperation. PM, Pm, pM, and pm denote higher or lower emphasis on the two functions. In this worksheet, compare concrete behaviors in a defined situation and discuss them with the team. PM here does not mean project management.
The team's goals and situation, observed delivery and leadership behavior, member feedback, and uncertainties about the assessment.
An editable context and four behavior profiles, with a tentative interpretation and proposed actions to support both delivery and collaboration.
On this page
How to use it
- Define the team situation, goals, observation period, and available feedback. Distinguish observed behavior from your interpretation.
- Review P: how goals, priorities, planning, and task progress are supported. Consider how the work is advanced, not only its deadline.
- Review M: how trust, cooperation, and asking for help are supported. Seek member feedback rather than inferring support from delivery figures.
- Use PM, Pm, pM, and pm as contrasting behavior profiles. Mark any current assessment as tentative and explain its evidence.
- Choose concrete changes that address the weaker function while retaining useful behavior. Agree a review point and check delivery and member feedback again.
Keep its limits in mind
This worksheet is a qualitative discussion aid, not the validated PM questionnaire or a calculated leadership score. Uppercase and lowercase letters distinguish the two functions; they are not permanent personality labels. One event or on-time delivery alone cannot establish a profile. Better support is a proposed change, not a guaranteed performance improvement.
Keep clear goals and make it easier to ask for help
Fictional example: Xinggang's team lead advances tasks quickly, and quarterly deliveries are mostly on time. Anonymous feedback says members are afraid to ask for help when risks arise. These observations suggest a Pm tendency, which still needs wider team feedback.
On a small screen, scroll across the diagram to read it.
Separate functions: Mostly on-time delivery is evidence relevant to P. Anonymous feedback raises a question about M; it does not establish every member's experience. The Pm interpretation is provisional.
Profiles and proposed support: Only Pm describes the tentative case interpretation. The other three cells illustrate contrasting behavior, not additional observations about this team. Weekly early risk discussions and a one-month review are proposed; no later results are supplied.
Next step: Discuss the interpretation with members, keep clear goals, and agree how to provide support during weekly risk discussions. After one month, review reporting timeliness and member feedback without assuming improvement.
Three reasons to pause before naming a leadership pattern
Use the two functions to discuss what happened in a defined team situation. Ask which actions advanced the work and which sustained cooperation or made support possible. Describe behavior and context before considering a tentative pattern. Uppercase and lowercase notation should summarize that discussion, not replace it.
Pause when one deadline is being used to classify a leader permanently. Pause when anonymous feedback is treated as every member’s experience or used to identify the respondent. Pause when a custom table is being presented as a validated questionnaire score. This page does not administer that measurement instrument or set numeric thresholds for P and M.
Keep useful task clarity while examining barriers to help-seeking. Support does not require abandoning standards, and demanding delivery does not prove that members have what they need. Discuss a change people can observe without promising that a different label will improve performance.
Choose leadership behavior, task alignment or voluntary feedback
PM here concerns leadership functions, not project scheduling. The related worksheets can help investigate a specific uncertainty, but none assigns a permanent identity to a colleague.
| Method | Material | Output |
|---|---|---|
| PM theory worksheet | Concrete goal-advancing and group-support behaviors | A tentative interpretation and support experiment |
| Need / Want matrix | Task necessity and members’ expressed willingness | Allocation and support questions |
| Johari window | Self-view and voluntarily offered feedback | A discussion of shared and differing awareness |
| GROW | A person’s goal and chosen options | A development conversation, not a diagnosis |
Worked case: a tentative Pm interpretation needs broader evidence
This continues fictional Xinggang’s quarterly case. Deliveries are mostly on time, and anonymous feedback says members fear asking for help when risks arise. Counts of deliveries, respondents and late reports are not supplied. “Mostly” cannot be converted into an invented on-time percentage, and the feedback cannot establish that every member feels unsafe.
The task record is relevant to P; the help-seeking concern raises an M question. Together they support discussing a tentative Pm tendency under the stated conditions. They do not establish a score. The other cells in the diagram are contrasts: PM combines goal progress with group maintenance; pM emphasizes maintenance while goal progress needs attention; pm suggests examining both. They are not three additional observations of this team.
The proposed change is a weekly early-risk discussion where support comes before reviewing the issue. Make that behavior concrete: ask what is blocked, what help would be useful and who can actually provide it. Do not promise a response time or resource that has not been agreed. A one-month review is planned, with no later result supplied.
| Given material | Limited interpretation | Proposed check |
|---|---|---|
| Quarterly delivery mostly on time | Some support for goal advancement | Check scope and quality, not only deadlines |
| Anonymous concern about asking for help | Possible group-maintenance gap | Invite voluntary examples without identifying respondents |
| Tentative Pm | A situational discussion label | Ask members whether the account fits |
| Weekly early-risk proposal | A behavior to agree, not implemented support | Confirm channels, available help and one-month review |
Review support and reporting, not movement between boxes
The conclusion is to keep clear goals and explore how help can be requested earlier. Ask members whether the proposed discussion is usable and what alternatives they prefer. Make room for private or written feedback without requiring public disclosure. A leader’s invitation alone does not establish that reporting is safe or that support will be available.
If the team agrees to try the change, retain the agreement’s actual scope. Record when a risk was noticed, when it was raised, what support was requested and what response occurred, where participants are comfortable providing those details. Faster reporting is not the same as fewer underlying risks. More reports could reflect better visibility rather than worse teamwork.
After one month, discuss reporting timeliness and member feedback alongside delivery and quality. Check whether support was actually provided and whether new barriers emerged. Keep missing observations visible and avoid combining responses into an unvalidated PM score. Revise or stop the experiment if it burdens the team or fails to address the concern. The original tentative interpretation remains a hypothesis, not an assessment of someone’s permanent character.
Check your work
- Are P (Performance) and M (Maintenance) assessed separately?
- Are the situation, observations, member feedback, and unknowns visible?
- Is the current interpretation tentative rather than a permanent label?
- Do the other profiles serve as contrasts instead of invented observations about this team?
- Will the proposed action be checked using both task progress and team feedback?
Framework references
References explain the framework and its scope; they do not validate the fictional example's results.
Put the framework to work
Copy the outline and add your question, evidence, and open questions.
Practice with an example
Choose a preparation route for progress, a resource or decision request, or a period review. Use one service case to inspect openings, review checks and focused guides, and keep a preparation note.
Prepare a work update: start with the purpose →