Sharing a Vision for the Department
In the interview, Mia outlines a strategic vision for the department, balancing ambitious growth with operational discipline. David probes how she would measure progress and earn buy-in across teams.
Dialogue12

Mia, let’s start with the larger picture. If you take over this department, what would you want it to become over the next three years, and why?
I’d want us to be known for turning complex customer needs into reliable, scalable solutions—not just launching more products. That means investing in the capabilities that let us grow without making delivery less predictable.
That sounds compelling, but growth and reliability often pull in opposite directions. How would you decide which opportunities to pursue, rather than simply saying yes to every promising proposal?
I’d assess opportunities against a few explicit criteria: strategic fit, customer impact, expected return, and the operational capacity required. If the case is strong but capacity is not, I’d make the trade-off visible rather than quietly overloading teams.
What would you measure to know whether your strategy was working? I’m less interested in a long list of metrics than in how you’d use them to make decisions.
I’d establish a small set of outcome measures: customer retention, time from commitment to delivery, and the proportion of initiatives meeting their intended business case. I’d review those alongside leading indicators, such as capacity and quality risks.
Suppose the numbers look healthy overall, but one team is consistently missing delivery commitments. How would you respond without undermining the wider strategy?
First, I’d distinguish a capability problem from a prioritization or process problem. I’d work with that team to identify the constraint, agree on a corrective plan, and set a review point; if the underlying assumptions were wrong, I’d adjust them.
A strategy can be sound and still fail if other teams see it as something being imposed on them. How would you earn their buy-in, especially when priorities compete?
I’d involve them early, before the choices are effectively settled, and be candid about the constraints. Buy-in doesn’t mean everyone gets their preferred outcome; it means people understand the rationale, can challenge the evidence, and know how decisions will be revisited.
And if the first year brings a setback—a major initiative slips, for example—how would you keep the department focused without pretending the plan is still on track?
I’d state plainly what changed, what we know, and what remains uncertain. Then I’d distinguish a recoverable delay from a sign that our approach needs revisiting, assign clear ownership, and communicate the revised milestones consistently.
Vocabulary8
- strategic fit
How well an opportunity supports the department’s broader goals. It helps explain why some promising projects are a better choice than others.
- operational capacity
The people, time, and resources available to do the work. A team may have a strong opportunity but lack the capacity to deliver it well.
- make the trade-off visible
To clearly show what must be gained or given up when making a decision. This phrase is useful for discussing limited resources openly.
- leading indicators
Early signs that can help predict future results. In this conversation, they include capacity and quality risks.
- corrective plan
A set of actions designed to address a problem and improve results. It can be used when a team is not meeting its commitments.
- buy-in
Support for or acceptance of a decision or plan. Leaders often need to earn buy-in from teams with competing priorities.
- the underlying assumptions
The beliefs or expectations on which a plan is based. If they prove incorrect, the plan may need to change.
- revised milestones
Updated dates or targets for stages of a project. The phrase is useful when a delay changes the original schedule.
Key Sentences8
- 1
I’d assess opportunities against a few explicit criteria: strategic fit, customer impact, expected return, and the operational capacity required.
This sentence shows how to explain a structured decision-making process. Reuse the pattern “assess [options] against [criteria]” when describing how you evaluate choices.
- 2
If the case is strong but capacity is not, I’d make the trade-off visible rather than quietly overloading teams.
This is useful for showing that you balance ambition with realistic resource limits. The phrase “rather than” helps contrast a responsible approach with an undesirable one.
- 3
I’d establish a small set of outcome measures: customer retention, time from commitment to delivery, and the proportion of initiatives meeting their intended business case.
This sentence presents measurable results without relying on an overly long list of metrics. Reuse “a small set of outcome measures” when explaining how you would track success.
- 4
First, I’d distinguish a capability problem from a prioritization or process problem.
This is a concise way to show that you diagnose a problem before acting. The structure “distinguish [one cause] from [another]” is useful when comparing possible explanations.
- 5
I’d involve them early, before the choices are effectively settled, and be candid about the constraints.
This explains how to build trust and invite input before decisions are final. Reuse it when describing an inclusive approach to collaboration.
- 6
Buy-in doesn’t mean everyone gets their preferred outcome; it means people understand the rationale, can challenge the evidence, and know how decisions will be revisited.
This sentence defines buy-in in a nuanced way, without suggesting that everyone must agree. The structure “doesn’t mean X; it means Y” is useful for clarifying a complex idea.
- 7
I’d state plainly what changed, what we know, and what remains uncertain.
This is a clear framework for communicating during a setback. Reuse the three-part structure to separate confirmed facts from unanswered questions.
- 8
Then I’d distinguish a recoverable delay from a sign that our approach needs revisiting, assign clear ownership, and communicate the revised milestones consistently.
This sentence combines diagnosis, accountability, and communication in a practical response to a delay. It is useful when explaining how you would keep a project moving while adapting the plan.