People Management
Moving into a Manager-of-Managers Role: Change What You Inspect and Who You Coach
Build a first-month plan for managing managers, with clear decision rights and proportionate evidence. Two completed fictional cases distinguish coaching a manager through an expectation change from owning a shared capacity decision, while retaining unresolved delivery and communication questions.
Moving into a manager-of-managers role changes the work you need to inspect. Look at how managers make decisions, develop people and handle dependencies, alongside the conditions affecting several teams. Coach managers through work they still own, and take responsibility for decisions that require your broader authority. Avoid becoming a second daily manager for everyone below them.
This LandOffer.ai guide includes a completed fictional first-month plan and two contrasting management cases. All people, schedules, observations, conversations and decisions are authored examples. Primary sources were checked on October 27, 2026. We did not inspect employee records, conduct meetings, change reporting lines or allocate anyone's real work.

Clarify the role before changing your calendar
A title does not establish your actual decision rights. Confirm which managers report to you, which teams they lead, what cross-team decisions you own and what still belongs to a peer, product partner or executive. If you retain individual-contributor direct reports, make that additional responsibility explicit rather than assuming all your work now flows through managers.
Lara Hogan's account of different management levels describes moving from managing contributors toward coaching managers and setting direction for a group of teams. She explicitly limits the account to her own experience and context. It is a useful practitioner perspective, not a universal hierarchy, staffing ratio or calendar prescription.
GitLab's Senior Engineering Manager description is a concrete employer example: its scope can include managers and/or individual contributors, strategic direction, cross-functional coordination and leadership development. The role there is not proof that the same title carries identical authority elsewhere.
Agree a short written description of responsibilities with your manager and direct reports. It should explain the decisions you will inspect, the coaching relationship, the information needed for escalation and how any direct intervention will be communicated. State whether you are asking for context or giving an instruction so the manager can respond without guessing whether ownership has changed.
Inspect decisions and systems without taking over every task
You still need enough technical and delivery context to understand risks and ask useful questions. Use that context to examine a manager's judgment and the constraints across teams. Instead of reviewing every engineer's task list, inspect whether managers can explain priorities, evidence, capacity constraints, unresolved dependencies and the next decision owner.
Ask for a small decision record or a recent example. “Which commitment changed, what did you learn and what did you tell the team?” can reveal more than a polished green status. A delayed milestone may reflect a dependency, a deliberate tradeoff or an unrealistic commitment; it is not automatically evidence of poor management.
Look across teams for repeated conditions. Are several managers waiting on the same specialist? Are two teams using incompatible assumptions about who accepts a handoff? Does a change in one team's plan leave another team's promise untouched? Investigate these potential organizational problems through the agreed decision owners before changing an engineer's assignment.
Keep people information proportionate to the management task. You do not need unrestricted copies of every one-on-one note to coach a manager. Use appropriate organizational channels for sensitive matters and distinguish reported experience from an established finding. A few visible examples are not a complete measure of team health.
Completed first-month plan: what to examine and who owns it
In fictional Clearfield Systems, Rhea begins managing Anil, Jo and Mei. Each leads a different engineering team. Their working agreement gives Rhea authority to resolve allocation conflicts within this group, while product commitments and wider staffing approvals require the relevant partners. The three-manager span is an example, not a recommendation.
Within this authored scenario, Rhea and her direct reports agree the following first-month plan; no real managers accepted these commitments:
| Period and purpose | Evidence Rhea asks to inspect | Coaching or organizational action | Boundary |
|---|---|---|---|
| Week 1: clarify responsibilities | Each manager's current commitments, one decision record and a map of external dependencies | Agree who decides priorities, technical choices, cross-team allocation and escalation | Do not reopen every engineer's assignment or replace the technical owner |
| Week 2: understand management judgment | A manager-chosen example of a changed expectation and how it was communicated | Coach the manager to separate facts, assumptions and the decision they need to make | A coaching question is not a hidden performance verdict or direct instruction to the employee |
| Week 3: inspect shared constraints | Two commitments using the same specialist, with the actual available capacity and decision owners | Rhea owns the inter-team allocation question within her stated authority | Product partners still own any required change to their commitments |
| Week 4: review what changed | Revised decision records, manager explanations and appropriately gathered wider-team context | Keep useful coaching practices, revise unclear interfaces and record unresolved risks | Do not claim a month of meetings proves healthy teams or improved delivery |
The recurring allowance is three forty-five-minute manager conversations, one forty-five-minute cross-team risk review and thirty minutes to update the shared decision record each week. That is 210 minutes weekly. Across four weeks, plus two thirty-minute wider-team conversations and thirty minutes of preparation and synthesis, the selected activities total 930 minutes, or fifteen hours thirty minutes.
This is planning arithmetic, not measured management effort or a complete role budget. It excludes many other duties and does not prescribe a meeting frequency for every organization. Rhea checks the managers' own capacity before treating the plan as agreed work.
The plan's output is a small set of clearer responsibilities and decisions. It is not a new reporting dashboard that ranks managers by ticket volume. A metric can prompt a question, but the review needs its definition, context and limits before anyone interprets it as managerial quality.
Case one: coach the manager to make the next management move
Anil asks Rhea to tell engineer Neri to finish a validation task by Friday. In this fictional case, the acceptance scope changed and an owner review has not been arranged. There is no urgent issue requiring Rhea to assume command; Anil still owns the priority and expectation conversation.
Rhea does not send Neri a second deadline. She uses this completed coaching exchange:
Rhea: What had you and Neri agreed would be complete, and what changed afterward?
Anil: I asked for the new validation cases, then another request expanded the examples. I have not separated the required cases from the extra ones.
Rhea: Which decision is yours, and what support do you need from me?
Anil: I need to choose the retained scope and arrange the owner review. I need help only if the other team's reviewer cannot accept time.
Rhea: Make that scope decision with the relevant technical owner, discuss it with Neri and bring back the accepted review plan. If reviewer capacity crosses team authority, escalate that specific conflict.
Anil's completed follow-through record says he distinguishes the required cases from the extra request and discusses the revised expectation with Neri. Neri's fictional readback identifies the retained cases and the still-pending owner review. The record does not say the validation passed or Friday delivery became certain.
Rhea's next check is with Anil: what decision was communicated, what did Neri understand and which dependency remains? She can offer feedback on Anil's clarity without taking over Neri's daily task management. If she had supplied the answer and privately assigned it, the team would have two managers issuing instructions about the same work.
This case does not make coaching the answer to every problem. A serious concern or situation requiring an established response must use the appropriate organizational route. The point is to choose the intervention required by the situation and your authority, rather than treating either permanent distance or constant takeover as a leadership principle.

Case two: own a decision that the managers cannot settle alone
Jo and Anil each have a legitimate commitment needing specialist Ari in the same week. Anil's retained work needs four days; Jo's needs three. Ari has five available days in the fictional capacity record. Both managers have explained their needs, but neither can unilaterally decide the other team's priority.
The shortfall is four plus three minus five: two days. The numbers are chosen planning assumptions, not observed utilization or an estimate that every day of specialist work is interchangeable. Skill fit, sequencing and availability still need checking.
Rhea owns the allocation decision within her agreed scope. She brings the managers and product partner Elena into one decision record rather than asking Ari to satisfy both requests or quietly work additional days.
| Decision item | Completed fictional agreement | What remains open |
|---|---|---|
| Competing demand | Four days for Anil's work, three for Jo's, against five available days | Effort estimates can change; managers must report new evidence |
| This week's allocation | Four days retained for Anil's work and one for Jo's | The record does not prove either work item is complete |
| Remaining work | Two days of Jo's requested effort move to the next planning period | Exact sequencing and completion still need owner review |
| Product coordination | Elena accepts the revised internal planning assumption | No external promise or customer deadline is changed by this example |
| Communication | Anil and Jo explain the single agreed allocation to their teams; Ari receives one consistent plan | Acknowledgement and actual execution need later checking |
| Review | Rhea reviews the constraint and any changed estimates at the next risk check | Allocation clarity is not proof that the dependency disappeared |
Rhea's action is different from the first case. Asking each manager another coaching question would not, by itself, resolve a shared resource decision neither owns. She needs to make the decision she is authorized to make and involve the partner who owns the related commitment.
She still avoids becoming Ari's task manager. The managers and technical owners retain execution details, and the agreed record is the route for changes. If Rhea lacks the authority assumed here, her action would instead be to take the explicit options to the person who has it. A senior title is not a substitute for that check.
Use wider-team context without creating a shadow reporting line
Skip-level conversations can reveal what managers' reports understand about direction, support and work interfaces. They can also create confusion if a leader promises priorities or career decisions that the direct manager is supposed to handle.
GitLab's skip-level overview separates communication with indirect reports from managing their priorities, careers or other direct-manager duties. Its current overview also specifies its own meeting and recording practices. Confirm your organization's process rather than importing those rules or treating a conversation as automatically confidential.
In Rhea's fictional first month, a wider-team conversation reveals that two people interpret a decision note differently. She records that specific ambiguity and discusses the communication interface with the managers. She does not decide that everyone is confused, use a small conversation as a manager rating or give each person a different private workaround.
Explain what will be shared and how sensitive concerns can be raised through the appropriate route. Ask about examples and invite corrections. Silence or praise does not establish universal trust, and one critical account does not independently establish another person's conduct. Broader context should improve your questions and decisions without replacing fair, authorized processes.
Review the transition through changes in your own behavior
At the end of the month, Rhea's fictional review has a mixed result. Anil now records a clearer retained scope and next review owner; the technical result is still pending. Rhea resolved one cross-team allocation decision, while its delivery consequences remain unverified. A wider-team conversation exposed a communication ambiguity that still needs follow-up.
Those observations support specific descriptions of her work: coached a manager through an expectation decision, owned a shared constraint and identified an interface to inspect. They do not establish that she caused a team's delivery, earned a promotion or solved the organization's management needs.
Ask which decisions still arrive at your level because authority is unclear, which manager can now explain a judgment independently and which cross-team constraint you actually removed or left unresolved. Record the next decision owner and review point for each unresolved issue, then use that record to revise the next month's attention. Return to LandOffer.ai's career guides for another current-work reference, keeping managerial support, organizational decisions and team results distinct.


