Managing managers and organizational change
These questions examine leadership systems and transitions. Directors and executives need evidence of work through managers; ICs can discuss relevant interfaces without claiming people authority. See evaluation.
G01 — How do you help a manager become more effective?
Variants: A new manager solves everything personally and the team depends on them.
Intent: Examine manager development rather than taking over their team.
Strong answer target: Understand the manager's responsibilities, team context, and development need. Agree an observable goal and support, help them practice judgment, and inspect relevant team effects. Keep ownership with the manager while intervening proportionately if serious risk requires it.
Profile inputs/adaptation: Manager relationship, expectations, coaching, and effects. Director: actual management of managers. Peer/IC: advice and partnership only; do not present mentoring as formal accountability.
Acceptable alternatives: Shadowing, role-play, external coaching, or adjusting the manager's scope may help. More direct support can be temporarily needed.
Probes: What could the manager do independently afterward? What did you avoid taking over?
Failure modes: Becoming the team's real manager, vague encouragement, or assessing development only through the manager's confidence.
| Dimension | Weak anchor (0) | Strong anchor (3) |
|---|---|---|
| Development diagnosis | Prescribes the candidate's preferred style | Identifies a specific responsibility and observed gap |
| Ownership | Replaces the manager's judgment indefinitely | Builds capability with explicit support and boundaries |
| Effects | Equates coaching meetings with improvement | Examines changed management behavior and team effects |
Provenance: Practice extrapolation from H02 and TR04.
G02 — How do you use skip-level conversations without undermining managers?
Variants: An employee brings a concern about their manager directly to you.
Intent: Examine access to information, trust, and responsible follow-up.
Strong answer target: Clarify the purpose of listening and limits of confidentiality. Seek concrete context, distinguish patterns from isolated accounts, and explain appropriate next steps. Address serious concerns through the responsible process without creating a second chain of everyday instructions.
Profile inputs/adaptation: Reporting relationships, concern, authority, and follow-up. Manager of managers: actual oversight. A staff IC should describe partnering with the responsible people leader rather than claiming this mandate.
Acceptable alternatives: Direct discussion, mediation, or formal escalation may fit depending on safety and seriousness. Do not promise absolute secrecy.
Probes: What would you share, with whom, and why? How do you prevent retaliation?
Failure modes: Dismissing concerns to protect hierarchy, promising secrecy you cannot keep, or issuing conflicting instructions behind the manager's back.
| Dimension | Weak anchor (0) | Strong anchor (3) |
|---|---|---|
| Listening | Assumes either party must be wrong | Seeks concrete context and respects disclosure boundaries |
| Follow-up | Promises unlimited secrecy or ignores risk | Explains appropriate, proportionate next steps |
| Operating trust | Creates a parallel management chain | Preserves clear responsibility while addressing concerns |
Provenance: Editorial synthesis; listening informed by R06.
G03 — How do you clarify decision rights between teams?
Variants: Two groups each believe the other owns a recurring decision.
Intent: Examine usable interfaces and authority, beyond an organization chart.
Strong answer target: Identify the recurring decision, necessary inputs, and consequences of ambiguity. Agree ownership, consultation, escalation, and handoffs with affected teams. Check whether decisions become easier without introducing unnecessary central approval.
Profile inputs/adaptation: Decision examples, team boundaries, authority, and effects. Staff IC: technical interfaces. Director: team mandates. Executive: cross-functional rights agreed with peers.
Acceptable alternatives: A joint decision or temporary collaboration can fit when accountability is clear. Not every interface requires a formal matrix.
Probes: Who decides if advice conflicts? Which decisions can teams make alone?
Failure modes: Renaming teams without changing interfaces, everyone owns everything, or routing routine choices to the top.
| Dimension | Weak anchor (0) | Strong anchor (3) |
|---|---|---|
| Ambiguity diagnosis | Discusses reporting lines only | Identifies concrete decisions and interface failures |
| Rights | Confuses consultation with final authority | Establishes usable ownership and escalation |
| Effect | Adds approvals without checking cost | Examines flow, autonomy, and continuing gaps |
Provenance: Practice extrapolation from TP01.
G04 — How do you reduce dependence on a key person?
Variants: What is your approach to succession and continuity?
Intent: Examine shared capability without treating people as disposable.
Strong answer target: Identify critical decisions, knowledge, access, and relationships concentrated in one person. Agree practical transfer, development, and coverage with them. Create opportunities for others to act and verify continuity while recognizing the original person's work.
Profile inputs/adaptation: Dependency, knowledge transfer, responsibilities, and coverage evidence. IC: technical continuity. Director: leadership succession and management coverage within actual authority.
Acceptable alternatives: Some specialization is necessary. A succession plan can have gaps if the risk and response are explicit.
Probes: What happens during their absence? Who has practiced the critical work?
Failure modes: A document nobody can use, surprise replacement, or making the expert responsible for transfer without giving time.
| Dimension | Weak anchor (0) | Strong anchor (3) |
|---|---|---|
| Dependency | Identifies a name without critical responsibilities | Specifies concentrated knowledge, access, and decisions |
| Development | Merely declares a backup | Creates supported opportunities to gain capability |
| Continuity | Assumes documentation guarantees readiness | Checks practical coverage and remaining exposure |
Provenance: Editorial synthesis informed by enablement in TR04 and delegation in H02.
G05 — How would you integrate an acquired engineering organization?
Variants: Two organizations must work together after an acquisition.
Intent: Examine integration choices tied to the actual acquisition purpose.
Strong answer target: Understand the business thesis, commitments, talent, technical obligations, and operating differences. Decide what must integrate, what can remain independent, and in what sequence. Explain communication, ownership, risks, and how integration progress is checked.
Profile inputs/adaptation: Acquisition context, mandate, promises, and systems. Executive: shared business decisions. Director: people/team transition. IC: technical integration contribution; situational answers remain labeled.
Acceptable alternatives: Preserve independence or integrate gradually when that serves the thesis. Uniform tooling is not inherently a good outcome.
Probes: What must remain stable? Which integration assumption is least certain?
Failure modes: Immediate rewrite, dismissing the acquired team's context, or ignoring incompatible promises and ongoing customers.
| Dimension | Weak anchor (0) | Strong anchor (3) |
|---|---|---|
| Purpose | Assumes acquisition means total assimilation | Connects choices to the business thesis and obligations |
| Transition | Treats people and systems as interchangeable | Sequences work with practical ownership and risk |
| Evidence | Declares success at organizational consolidation | Checks useful integration outcomes and continuing costs |
Provenance: Practice extrapolation from L19.
G06 — How do you carry out a reorganization responsibly?
Variants: Roles and team boundaries are changing; how do you handle the transition?
Intent: Examine implementation after a structural decision, distinct from choosing it.
Strong answer target: Explain the diagnosed problem and chosen change, including uncertainty. Clarify responsibilities, reporting, continuity, and transition decisions. Give affected people usable information and feedback channels; check whether the change solves the original problem.
Profile inputs/adaptation: Authority, rationale, affected work, and transition evidence. Director/executive: actual decision or implementation role. Others: bounded transition contribution without claiming the whole reorganization.
Acceptable alternatives: Staged changes, a trial boundary, or reversing part of the change may be appropriate. Urgency can limit consultation, not eliminate clarity.
Probes: What happens to ongoing work? Which uncertainty can you acknowledge openly?
Failure modes: Announcing a chart and declaring completion, concealed responsibility gaps, or defending a change despite contrary evidence.
| Dimension | Weak anchor (0) | Strong anchor (3) |
|---|---|---|
| Rationale | Explains only the new reporting lines | Connects transition to the original operating problem |
| Continuity | Leaves roles and ongoing work ambiguous | Clarifies responsibilities, handoffs, and temporary arrangements |
| Feedback | Treats questions as resistance | Provides useful communication and checks actual effects |
Provenance: Editorial implementation synthesis informed by L07 and H05.
G07 — What changes when you become the manager of former peers?
Variants: How would you handle a promotion that changes existing relationships?
Intent: Examine role transition, fairness, and boundaries.
Strong answer target: Acknowledge changed responsibility and agree expectations with the team and your manager. Make access, feedback, and decisions consistent while retaining respectful relationships. Seek support and describe how you would address a difficult disagreement without favoritism.
Profile inputs/adaptation: Previous relationships, new mandate, and experience. First-time manager: transferable evidence plus an explicitly hypothetical plan. Experienced candidate: observable decisions from the actual transition.
Acceptable alternatives: Relationships need not become distant. Existing friendships can continue with clear professional boundaries.
Probes: What if a friend expects special information? What would you explain to the team?
Failure modes: Acting as if nothing changed, performative harshness, or relying on personal loyalty instead of fair expectations.
| Dimension | Weak anchor (0) | Strong anchor (3) |
|---|---|---|
| Role clarity | Ignores the changed responsibilities | Explains expectations and the new mandate |
| Fairness | Uses friendship as an access or decision advantage | Applies consistent information and decision boundaries |
| Support | Assumes prior technical success is enough | Seeks feedback and develops management capability |
Provenance: Editorial transition question informed by distinct career responsibilities in J01.
G08 — How do you lead change when people are skeptical or exhausted?
Variants: The team has seen several failed transformations.
Intent: Examine adoption through credible action and legitimate concerns.
Strong answer target: Investigate past experience, current workload, and what the change is meant to improve. Explain constraints and what people can influence. Reduce competing demands, try feasible steps, and use feedback to adapt rather than equating skepticism with disloyalty.
Profile inputs/adaptation: History, mandate, affected people, actions, and adoption observations. Leader: tradeoffs and resources. IC: influence and practical adoption support within scope.
Acceptable alternatives: Slow down, stop a change, or use a directive for urgent risk if its reason and support are clear.
Probes: Which concern is valid? What will you stop to make room?
Failure modes: Motivation speeches without capacity, demanding enthusiasm, or asking people to absorb another unsupported process.
| Dimension | Weak anchor (0) | Strong anchor (3) |
|---|---|---|
| Understanding | Labels all concerns as resistance | Examines history, constraints, and legitimate objections |
| Feasibility | Adds change without time or support | Makes room and offers concrete supported steps |
| Adaptation | Requires public agreement as proof of adoption | Checks actual use and responds to evidence |