Meetings & Discussions Free · self-study ~60 min

Evaluating Operational Credibility and Service Model Rebalancing

A COO interviews a candidate for a senior operational role, focusing on how they would assess and improve service delivery, profitability, and management discipline. The candidate demonstrates a structured approach to evaluating the business's actual versus formal operating models.

 Level

What you’ll be able to do

Dialogue

Beginner version

Jordan Cole
Sam, I am happy to meet you. Alex said good things about you. He said you think carefully. But I care more about results than careful thinking.
Sam Brooks
I think we agree. I like careful thinking. But I also like to act and get things done.
Jordan Cole
Good. I want to be very clear now. Today I want to know how you work. I want to talk about service, quality, money, and risk. That is our plan. Do you agree?
Sam Brooks
Yes. I agree. That is the right place to start.
Jordan Cole
Good. Let us start with a simple question. You join the company. There is a current manager. What do you look at first?
Sam Brooks
I look at many things. First, I check the service numbers. How often do we fix things the first time? How long does repair take? Are parts ready? Then I check the money. Do we make profit? Do some customers cost too much? Then I look at the managers. Do they use data? Do they make good decisions? I also watch how people work together. Are there problems they hide? Last, I check quality. Is it real, or only on paper?
Jordan Cole
You said 'real, not only on paper.' What is the difference?
Sam Brooks
The paper shows the plan. But real life is different. When a problem happens, I watch what people do. That shows me the real way the company works. If the plan and the real way are the same, the company is strong. If they are very different, there are big problems.
Jordan Cole
Good point. This company is very good at technical work. But it is not so good at business and management. How do you change things without making people feel bad?
Sam Brooks
I do not use hard words like 'fix your culture.' That makes people angry. I say the company is good at its work. I say we want to help it grow. Good business skills protect the technical work. They do not fight it. I want both things to work well together.
Jordan Cole
That is right. Now let us talk about a real problem. Customers like us. But we do not make enough money from them. What do you do?
Sam Brooks
First I look at the problem. There are many reasons we lose money. Maybe prices are too low. Maybe we do too much work. Maybe we give too many special deals. I look at each customer. Some customers are important for the future. We keep them. Others just cost money. For them, I talk about new prices or less service. I do not make one rule for all customers. That does not work.
Jordan Cole
You said 'special deals' a few times. What does that mean for work?
Sam Brooks
Sometimes we do extra things for one customer. We do it again and again. Then it becomes normal. But it is not in the plan. For example, one customer gets a fast visit. But we never charged for it. Another customer gets free extra work. This causes big problems. We lose money. Our work is not the same for everyone.
Jordan Cole
I understand. Now let us talk about managers. Some managers have worked here a long time. They know the work well. But they do not manage people well. How do you help them?
Sam Brooks
First, I make things clear. I tell them what good work looks like. I show them the most important numbers. I say how often we check results together. Many managers just need clear rules. Second, I help them practise. I show them how to have a good meeting. I show them how to give feedback. Third, I watch how they improve. Some managers get better fast. Some get better slowly. I help them. But if they do not improve, I must decide what to do.
Jordan Cole
OK. Now a different problem. Customers are happy. But we are not good at business. We make different promises to different customers. We do not know our profits well. Some people say do not change things if customers are happy. What do you think?
Sam Brooks
Happy customers do not mean the business is healthy. We can look good outside. But inside, money is going down. People are working too hard. If we do not have good business rules, we make bad promises. We give too much. Workers get tired. So I do not change everything. But I fix the important things. I make our offers clear. I say what service we give. I make sure we know which customers make money for us.
Jordan Cole
Let us talk about reports and paperwork. Technicians do not like writing reports. They say office people made the rules and do not understand field work. How do you manage this?
Sam Brooks
I listen to them first. They are sometimes right. Bad paperwork wastes time. If the forms are too long or not useful, I want to know. So I ask: does this paperwork help us? Does it help the customer? But I am also clear: in this job, reports are not a choice. They are part of the work. The answer is to make reports easy to do. Short forms. Simple steps. If reports are hard every day, the system is wrong, not the technicians.
Jordan Cole
Good answer. Now here is a bigger question. After six months, you see this: we fix things the first time at the same rate. Not bad, but not better. Old jobs wait longer. Customers are still happy. Workers are busy. They do more extra hours. We make less money. What do you think?
Sam Brooks
I think the business is very busy. But it is not in good shape. When workers do a lot of extra hours and old jobs wait longer, we have a problem. Happy customers do not tell us everything. Inside, things are getting hard. I think we take on too much work. Or we plan badly. Or we do the same job twice. I want to know: where are the extra hours? Which customers have the oldest waiting jobs? Are our best workers doing easy jobs? I look for the real cause, not just the number.
Jordan Cole
How do you know if the problem is everywhere or just in one place?
Sam Brooks
I look at data from many places. If the same problem is in many teams and many sites, it is a big problem everywhere. If it is only in one team or one customer, it is a small local problem. I also talk to workers. If the data shows problems and workers say the same things, I know the problem is real. I need to see the business as it really is, not just as people describe it.
Jordan Cole
Now let us talk about the handover. The old manager will help you at the start. How do you use that time well?
Sam Brooks
I want to learn the real business, not just the plan. I go to meetings with the old manager. I visit customers with them. I ask about the hidden rules. Which customers need special care? Which processes are different in real life? I also write my own notes. I look at what is good and what is just an old habit. I do not change things fast. People watch how I learn. If I say everything is bad, they do not trust me. I stay curious and careful.
Jordan Cole
A harder question. One manager has worked here a long time. Workers like this person very much. But the manager does not follow up on things. They do not use the numbers well. Do you act fast or slow?
Sam Brooks
I act fast to find the problem. I tell the manager clearly what I need. I help and support them. I show them the exact things they need to do better. If they get better, I support them more. If they do not improve, I make a decision. But I am fair and clear. People here watch how I treat this manager. I want to be right, not just fast.
Jordan Cole
Some people will say: she sounds very hard.
Sam Brooks
I am hard on unclear rules and slow action. I try to be kind to people. These are two different things. People can work hard for a strong manager. But they need clear rules and fair treatment. That is what I give.
Jordan Cole
Last question about work. How do you stop yourself from changing too many things too fast?
Sam Brooks
I change things step by step. I do not try to change everything at the same time. I keep the things that make customers happy. I only change things where the reason is clear. I give people time to learn the new way. I make meetings better. I make information clearer. When people understand things better, they start to work in a better way. That is stronger than big, fast changes.
Jordan Cole
We are almost done. What is the most important thing you bring to this job?
Sam Brooks
I help the company grow in a good way. I keep what is already strong. I make unclear things clear. I change what is not working for the next step.
Jordan Cole
Good. Short and clear. I like that. Do you have questions for me?
Sam Brooks
Yes, I have four questions. First, where is the biggest difference between the plan and real work? Second, what is one thing that is really good here, and what is one thing that stays because it is old, not because it helps? Third, what do you want me to keep when I start, and what do you want me to look at and improve? Last, which number do you trust most, and which number might hide a real problem?
Jordan Cole
Those are the right questions. You want to understand the business before you change it. The biggest gap is between what we say we do the same way and what we actually do differently for each customer and manager. I want to keep our strong technical work. I want to change how we think about profit, standard ways of working, and our focus. I trust our quality numbers more than our money numbers. That tells you something important.
Sam Brooks
Yes, it tells me a lot. The problem is about work and management. It is not only about money.
Jordan Cole
Exactly. Thank you, Sam. We talked about real things. You did not use empty words about change.
Sam Brooks
Thank you, Jordan. I liked the questions. Good questions show a good company.

Intermediate version

Jordan Cole
Sam, it's good to finally meet you. Alex spoke well of you after your first conversation. He said you think carefully about things, which is a positive sign. I'll be honest though, I care more about practical results than careful thinking alone.
Sam Brooks
I think we'll get on well then. I value careful thinking when it helps me understand a situation better, but I've never confused it with actually making decisions and taking action.
Jordan Cole
Good. Let me be completely straightforward from the start. In this conversation, I'm not trying to find out why you want this job. I want to understand how you work. We'll cover service quality, field delivery, process discipline, management, profitability, and the risks of a leadership handover. That's our agenda. Are we agreed?
Sam Brooks
Completely. I see that focus as exactly where the role becomes real and practical.
Jordan Cole
Good. Let's start with the most important operational question. When you join and are working alongside the current General Manager during the handover, what would you focus on first?
Sam Brooks
I'd want to understand the business at several different levels, because service companies often look healthier from the outside than they really are. I'd start with service performance: first-time fix rates, repeat visits, how old the backlog is, repair times, parts availability, and any early signs of SLA pressure. Then I'd look at the financials: profit by service type, how profitable individual accounts are, cost-to-serve, and whether some 'important' accounts are actually using far more resource than they generate. After that, I'd look at how management actually works: who makes decisions, how problems get escalated, whether managers are genuinely using data or just reacting to the loudest issue. I'd also look at behaviour: where people collaborate, where things get hidden, where exceptions have become routine. Finally, I'd check whether the quality system works in real life, not just in documents, how ready we are for audits, how well we trace issues, and whether compliance is built into daily work.
Jordan Cole
You used a phrase that stands out to me: 'in real life, not just in documents.' How do you tell the difference between how a company is supposed to work and how it actually works?
Sam Brooks
I watch what happens when things go wrong. The official model is what the company says it does, the written processes, the escalation routes, the KPIs, and the intended decision-making structure. The real model is what actually happens when a customer complains, a technician is missing a part, an account is losing money but no one wants to touch it, or paperwork gets delayed because people are too tired. In my experience, the gap between these two tells you almost everything about how mature the management really is. If they match, the business can grow. If they're far apart, you get inconsistency, people working heroically to compensate, and eventually margin or quality problems.
Jordan Cole
That's a strong point. Let me ask directly about the culture. Brankside Holdings has always been very strong technically. Some people would say that's what makes it special. The worry is that technical strength hasn't always been matched by commercial discipline or structured performance management. How would you bring those things in without making people feel like you're imposing a corporate makeover?
Sam Brooks
I'd avoid language like 'professionalisation', it tends to put people's backs up. Instead, I'd frame it differently: this is a company with real skills and strong customer trust, and the management structures just need to catch up with where the business wants to go next. I wouldn't set technical strength against commercial discipline. In fact, I'd argue the opposite, good commercial discipline actually protects technical excellence. When you understand which accounts make money, what it costs to serve them, and where to focus, you can invest in the right technical areas and stop quietly overpromising. The goal isn't to reduce the technical focus, it's to make sure it's financially sustainable.
Jordan Cole
That's exactly the right way to frame it. Now let's make it more practical. Say you find that customers are loyal but account profitability is weak. What do you actually do?
Sam Brooks
I'd diagnose the problem before doing anything. Loyal customers and weak profitability can come from many different causes, prices that are too low, too much service being delivered, poor control of scope, too many special deals, weak parts economics, or accounts that are being subsidised intentionally but nobody's said so out loud. I'd first break accounts into groups, because 'unprofitable' isn't one single thing. Some accounts might be worth protecting because they're strategically important. Others might just be old habits that look like relationships. Then I'd build a plan: renegotiate where the value is real but the economics are off, redesign the service where delivery is the problem, and reduce or exit where the commitment can't be justified. What I'd avoid is a blanket 'everyone must be profitable' announcement, in service businesses, that usually creates fear and short-term thinking. I'd connect profitability back to specific behaviours: how we respond, how we dispatch, how we handle exceptions, how we price.
Jordan Cole
You keep mentioning 'exception culture.' What does that mean in practical terms?
Sam Brooks
Exception culture happens when things that were supposed to be special cases become the normal way of working. For example, one account gets faster response times that were never properly priced into the contract. Another gets free repeat visits because they're politically sensitive. A third gets support for old equipment that isn't in the standard offering, because 'we've always done it that way.' Each decision might seem reasonable on its own. But when exceptions pile up without any oversight, the official model becomes meaningless. In practice, this creates hidden workload, unpredictable priorities, accounts that can't be compared fairly, and margin losses that nobody can clearly explain. It's one of the most damaging ways a service business quietly loses control.
Jordan Cole
Understood. Let's talk about managers. One realistic scenario is that some long-serving managers are technically strong, loyal, and hardworking, but they're not good at managing performance. How would you help them through a change like this?
Sam Brooks
First, by making expectations clear. A lot of managers who seem weak on performance management aren't unwilling, they're just not well-equipped, they're unsure what's expected, or they're working in a culture where priorities change before accountability has a chance to take hold. So I'd start with clarity: what results matter, which KPIs really count, how often we review performance, what a useful management conversation looks like, and where their decision-making authority begins and ends. I'd use a small, focused set of KPIs rather than overwhelming people with data. Second, I'd coach them, not with abstract leadership theory, but with practical skills: how to run a review, how to give constructive challenge, how to escalate early, and how to hold people accountable without making it personal. Third, I'd watch honestly to see who's adapting. In any transition, not everyone moves at the same pace. My job is to set direction, then support, then decide if someone isn't moving. That order matters, starting with judgment creates defensiveness, and staying in patience too long creates drift.
Jordan Cole
Agreed. Now suppose service quality looks acceptable overall, customers aren't complaining, but commercial discipline is weak. Sales promises vary, service scope differs by account, and profit visibility is poor. Some people might say, 'The customer is happy, so leave it alone.' How do you respond to that?
Sam Brooks
I'd push back on that. A calm customer base doesn't mean the business is in good health. Service organisations can look stable on the outside for a long time while quietly damaging their finances and wearing out their people. If commercial discipline is weak, the company is probably making inconsistent promises, spreading resources unevenly, and subsidising complexity in ways nobody's tracking. Eventually that shows up somewhere, technician burnout, backlog distortion, patchy documentation, poor renewal margins, or quiet dissatisfaction in key teams. So I wouldn't change everything, but I would fix the underlying issues. I'd want a clear standard offer, tighter scope boundaries, better control of exceptions, and visibility into which commercial commitments actually create value. Being responsive to customers is important, being random is not.
Jordan Cole
Let's go deeper on documentation. In many technical service companies, technicians resist strict documentation because they see it as bureaucracy created by people who don't understand field work. How would you handle that?
Sam Brooks
I'd start by acknowledging that the complaint is often partly valid. Documentation can become a burden if the process is badly designed. If technicians are spending more time filling in systems than capturing anything useful, then their resistance makes sense. So I wouldn't start by lecturing them. I'd ask: is the documentation proportionate, usable, and actually meaningful for operations? Does it support traceability, quality, and customer confidence, or has it just become a paperwork habit? That said, I'd be very clear: in a regulated service business, documentation isn't optional. It's part of what you deliver. The answer isn't to lower the standard, it's to make it practical to meet the standard. That might mean simpler forms, better workflows, clearer requirements, or stronger follow-through from managers. My principle is simple: compliance should be the easy path, not the hard one. If it takes heroic effort every day, the system itself is broken.
Jordan Cole
That's a very practical answer. Now let me give you a more complex scenario. Imagine you're six months into the role and you're seeing this: first-time fix rates are flat, not bad, but not improving. Backlog is under control, but older jobs are waiting slightly longer. Customer satisfaction is stable. Technician utilisation is high. Overtime is slowly increasing. Profitability is under pressure. What's your conclusion?
Sam Brooks
My conclusion would be that the business is busy, but probably not healthy enough. High utilisation combined with growing overtime and older backlogs usually means the business is closer to capacity limits than it looks. Stable customer satisfaction can be misleading here, customers might still be reasonably happy while the internal operation is already under strain. My main hypothesis would be that the organisation is dealing with complexity inefficiently. That could come from poor planning, repeat interventions, weak prioritisation, uneven parts availability, or commercial commitments that don't match delivery capacity. I'd then investigate the pattern: where is the overtime concentrated? Which accounts have the oldest backlogs? Are we using specialist technicians on work that doesn't need them? Is this a company-wide issue or is it focused in a particular region, customer type, or service line? Essentially, I'd move from spotting symptoms to finding the actual cause. The risk in these situations is applying generic productivity pressure when the real problem might be poor workload mix, weak prioritisation, or hidden exceptions.
Jordan Cole
And how would you figure out whether the problem is structural or just localised noise?
Sam Brooks
By looking at data, behaviour, and whether the pattern repeats. If the same issue shows up across multiple sites, managers, and reporting periods, it's likely structural. If it's concentrated around one account, one manager, one team, or one process step, it might be a local issue, though even local problems can be serious. I'd also compare what the metrics show with what people are actually saying. If the numbers show strain and the frontline is describing the same strain in their own words, late parts, unrealistic scheduling, repeat jobs, hidden exceptions, then the diagnosis gets stronger. In these environments, what matters is being able to read how the system really works, not just how it's described on paper, and then adjusting without losing control.
Jordan Cole
Moving to the handover period, respecting the outgoing manager's experience is straightforward to say. What specific steps would you take in those early weeks to make sure the transition goes smoothly?
Sam Brooks
I'd be very deliberate about it. I'd want joint account reviews, not just brief introductions. I'd want to visit customers together, not just get a list of names. I'd sit in on service meetings rather than just getting a summary afterwards. I'd also ask directly about the unwritten rules: which customers are politically sensitive, which processes are officially standard but actually flexible, which managers carry more influence than their title suggests, and which recurring problems tend to get normalised. At the same time, I'd keep my own independent notes. I'd use the handover to separate genuine strengths from things that are just old habits. Those aren't the same thing. And I'd hold back from redesigning anything too quickly. During a handover, people pay less attention to what you decide and more to how you read what you inherit. Show contempt and you lose trust. Show you're not paying attention and you lose credibility. The right approach is curious, respectful, and analytically sharp.
Jordan Cole
Good. Now a tougher people question. What if one of those long-serving managers is genuinely respected by the technicians, but is consistently weak on follow-through, KPI discipline, and accountability? Do you move quickly or cautiously?
Sam Brooks
Quickly on understanding the problem, carefully on consequences. I'd make expectations clear and specific. I wouldn't let it drift in a vague 'he's good, but...' space. I'd coach the person, support them, and be clear about the exact behaviours that need to change, late escalation, weak review habits, vague accountability, tolerating unmanaged exceptions, whatever it actually is. If I see progress, I invest more. If there's no progress, I make a decision. But that decision has to be based on clarity and fairness, not impatience. In organisations with long-serving staff, people watch closely to see whether leadership change is fair or arbitrary. So I'd rather take a little more time and have full legitimacy than move too fast and look heavy-handed. That said, I don't believe in endless patience. If the organisation is changing, managers need to change with it.
Jordan Cole
I expect you realise some people will hear that as, 'She sounds tough.'
Sam Brooks
I'm tough on vagueness and on things drifting without direction. I try hard not to be harsh with people. Those are two different things. In my experience, people can work well under demanding leadership if it's consistent, fair, and connected to a genuinely better way of working. What's really hard for people is inconsistent pressure, unclear criteria, and leaders who talk about change but accept confusion.
Jordan Cole
Final operational question. How do you avoid pushing change too far, too fast? That's a real risk in companies that need to evolve.
Sam Brooks
By sequencing things, not rushing them all at once. In a service business, trying to modernise everything at the same time tends to damage both confidence and execution. I'd avoid creating unnecessary bureaucracy or making symbolic 'new era' gestures that just unsettle the frontline. I'd protect what actually builds customer trust. I'd change things where the benefit is clear and explainable. And I'd pace the changes so people can actually absorb them. That means creating progress through better management habits, clearer priorities, and improved visibility, not through big announcements. When a business improves the way it understands itself, reviews its own performance, and makes decisions, behaviour starts to follow. That's more lasting than a dramatic transformation programme.
Jordan Cole
Agreed. We're nearly done. What's the single best summary of what you think you'd bring to this role?
Sam Brooks
I think my value is not just in managing change, but in guiding a business through a period of growth that protects what's already working, makes unclear things clear, and improves what isn't fit for the next stage.
Jordan Cole
That's concise. I appreciate that. Do you have any questions for me?
Sam Brooks
I have four questions. First, where is the biggest gap between how operations are supposed to work and how they actually work day to day? Second, which part of the current setup is a genuine strength, and which part continues mainly out of habit? Third, when I join, what would you want me to protect during the transition, and what would you want me to challenge and improve? And finally, which operational metric do you trust most, and which one might be hiding a deeper problem?
Jordan Cole
Those are exactly the questions I expected. They show you understand that the role is about diagnosing the system before changing it. To summarise: the main gap is probably between our stated consistency and the real variation across accounts and managers. I want to protect the organisation's technical strength. I want to challenge the acceptance of ambiguity around profitability, standardisation, and strategic focus. On metrics, I have more confidence in our quality indicators than in our account economics. That should give you enough to work with.
Sam Brooks
It actually tells me quite a lot. And it confirms that the challenge here is both operational and managerial, not just a commercial one.
Jordan Cole
Exactly. Thank you, Sam. The conversation was thorough and practical, and refreshingly free of vague transformation language.
Sam Brooks
Thank you, Jordan. I found the operational focus genuinely useful. It's usually a good sign when the questions in an interview are this concrete and specific.

Advanced version

Jordan Cole
Sam, it’s a pleasure to finally meet you. Alex shared a highly favourable impression following your initial discussion. He described you as nuanced, which is certainly encouraging. I must confess, I tend to place less value on nuance and more on tangible, functional outcomes.
Sam Brooks
Then I believe we shall find common ground. I appreciate nuance when it elucidates reality, but I have never conflated it with decisive action.
Jordan Cole
A satisfying response. Let me be unequivocally direct from the outset. In this dialogue, my objective is not to ascertain your motivation for the role, but to evaluate your operational methodology. We are examining service quality, field execution, process rigour, managerial cadence, profitability, and transition risk. That constitutes our agenda. Do we have an accord?
Sam Brooks
Entirely. I perceive that alignment as precisely where the role materialises into concrete reality.
Jordan Cole
Splendid. Let us commence with the most fundamental operational query. Upon joining and entering the transition period with the current General Manager, what would be your primary area of inquiry?
Sam Brooks
I would seek to comprehend the business in stratified layers, as service enterprises often project an illusion of robustness from a distance. Initially, I would scrutinise service KPIs: first-time fix rates, repeat visits, backlog volume and ageing, MTTR, parts availability, the balance between preventive and corrective work, and any early indicators of SLA strain. Subsequently, I would analyse the economic dimension: profitability by service segment, account-level profitability, cost-to-serve, discounting dynamics, and whether certain ‘premium’ accounts are consuming disproportionate capacity. Thirdly, I would evaluate the management architecture: decision rights, escalation protocols, review cadence, and whether managers are genuinely steering via data and priorities or merely reacting to noise and pressure. Fourthly, I would identify behavioural patterns: areas of natural collaboration, zones of concealment, where exceptions have become the norm, and where issues are surfaced early versus minimised. Finally, I would assess the quality system in practice, not merely on paper: audit readiness, traceability rigour, CAPA closure cadence, and the extent to which compliance is embedded in operations rather than existing in parallel.
Jordan Cole
You emphasised a phrase that resonates with me: ‘in practice, not merely on paper.’ How do you differentiate the formal operating model from the actual operating model?
Sam Brooks
By observing behaviour under pressure. The formal model is what the organisation professes: the documented processes, the official escalation pathways, the defined KPI structures, and the intended decision rights. The actual model is what transpires when a customer escalates, a technician lacks a component, an account is unprofitable yet politically sensitive, or documentation is delayed and fatigue sets in. In my experience, the delta between these two realities reveals nearly everything about management maturity. If the formal and actual models align, the business is scalable. If they diverge significantly, you encounter heroics, inconsistency, and ultimately margin erosion or quality risk.
Jordan Cole
Compelling. Let me challenge the cultural dimension directly. Brankside Holdings has historically been a technically formidable company. Some might argue that is its essence. The concern is that technical legitimacy has not always been complemented by commercial discipline or structured performance management. How would you navigate that without appearing to impose ‘professionalisation’ from above?
Sam Brooks
I would deliberately eschew such terminology, as it is often counterproductive and can be perceived as arrogant. I would reframe the narrative: there are enterprises with genuine expertise and strong customer legitimacy whose management architecture has not yet fully evolved to support the next growth phase. In such contexts, the imperative is less about replacing culture and more about rebalancing it. I would never position technical strength against commercial discipline. On the contrary, I would argue that robust commercial discipline safeguards technical excellence. By understanding account profitability, cost-to-serve, and service priorities more clearly, you can protect strategic technical investments, focus expert capacity where it matters most, and prevent the organisation from quietly overpromising and underdelivering. The objective is not to diminish the technical focus, but to ensure technical excellence is managed in an economically sustainable manner.
Jordan Cole
That is precisely the right formulation. Now, let us make it more operational. Suppose you identify strong customer loyalty but weak account profitability. What is your course of action?
Sam Brooks
Diagnose before intervening. Strong loyalty coupled with weak profitability can stem from diverse root causes. It may result from underpriced contracts, excessive service delivery, poor scope discipline, too many exceptions, weak parts economics, or simply the fact that a customer is strategically vital and is being subsidised intentionally without explicit acknowledgment. I would first segment the accounts, as ‘unprofitable’ is not a monolithic category. Some accounts may warrant protection due to their status as strategic anchors, OEM references, or gateways to future growth. Others may merely be legacy habits masquerading as relationships. Then, I would construct an action map: renegotiate where value is genuine but economics are weak, redesign the service model where delivery inefficiency is the bottleneck, and, when necessary, reduce or exit commitments that are no longer defensible. What I would avoid is announcing a blanket profitability mandate. In service businesses, that tends to engender fear, gaming, and short-termism. I would tether account profitability back to behaviour: response commitments, dispatch logic, parts policy, exception culture, and pricing discipline.
Jordan Cole
You repeatedly reference ‘exception culture.’ Define it operationally.
Sam Brooks
Exception culture occurs when deviations from the standard model cease to be exceptions and become the de facto model. For instance, one account receives special response times that were never correctly priced. Another receives complimentary repeat visits due to political sensitivity. A third retains legacy equipment support outside the standard model because ‘that is how we have always done it.’ Each decision may appear reasonable in isolation. However, when exceptions accumulate without governance, the formal model becomes a fiction. Operationally, exception culture manifests as hidden workload, unstable priorities, poor comparability across accounts, and margin erosion that lacks clear explanation. It is one of the most insidious ways service businesses lose control.
Jordan Cole
Understood. Let us discuss managers. One plausible scenario is that some long-tenured managers may be technically respected, loyal, and diligent, yet weak in performance management. How would you guide them through change?
Sam Brooks
First, by reducing ambiguity. Many managers who appear deficient in performance management are not unwilling; they are under-equipped, unclear about expectations, or operating in a culture where priorities shift faster than accountability solidifies. Therefore, I would begin with clarity: what outcomes matter, which KPIs truly count, what the review cadence is, what a constructive manager discussion entails, and where decision rights commence and conclude. I would employ a focused, potent KPI set, rather than an overwhelming flood of indicators. Second, I would coach them. Not through abstract leadership theory, but through practical management discipline: how to conduct a review, how to challenge constructively, how to escalate early, how to separate signal from noise, and how to hold people accountable without humiliation. Third, I would observe adaptation with honesty. In such transitions, not everyone progresses at the same pace. My role is first to clarify direction, then to support adaptation, and finally to make decisions where adaptation fails. That sequence is critical. Initiating with judgment breeds defensiveness; lingering in patience fosters drift.
Jordan Cole
Agreed. Suppose service quality appears broadly acceptable, customers are not openly disgruntled, but commercial discipline is poor. Sales commitments drift, service scope varies by account, and margin visibility is weak. Some might argue, ‘If the customer is content, do not interfere.’ How do you respond?
Sam Brooks
I would counter that apparent customer calm is not synonymous with a healthy business. Service organisations can appear stable externally for considerable periods while quietly eroding their economics and overburdening their personnel. If commercial discipline is lax, the company is likely making inconsistent promises, allocating resources unevenly, and subsidising complexity in ways that go unnoticed. This inevitably manifests somewhere: technician fatigue, backlog distortion, uneven documentation quality, poor renewal economics, or hidden dissatisfaction within key teams. Thus, I would not ‘touch everything,’ but I would certainly address the underlying mechanics. I would seek standard offer logic, clearer service scope boundaries, more disciplined exception handling, and visibility into which commercial commitments actually generate value. Responsiveness should be safeguarded; randomness should not.
Jordan Cole
Let us delve deeper into documentation. In many technical service organisations, technicians resist documentation rigour because they view it as bureaucracy devised by those detached from the field. How would you manage that?
Sam Brooks
First, by acknowledging that the complaint often contains validity. Documentation can become burdensome if the process is poorly designed. If technicians spend more time feeding a system than capturing useful information, resistance is rational. Therefore, I would not begin by moralising. I would begin by asking: is the documentation proportionate, usable, and operationally meaningful? Does it support traceability, quality, and customer confidence, or has it devolved into an administrative reflex? That said, I would be unequivocal: in a regulated service business, documentation is not optional. It is integral to the deliverable. The solution is not to lower the standard, but to make compliance executable. This may involve simplifying templates, improving workflow, clarifying mandatory requirements, or reinforcing managerial follow-through. My principle is straightforward: the path to compliance should be the easy path, not the heroic one. If it requires heroism daily, the system is flawed.
Jordan Cole
That is a highly operational response. Now, let me present a more integrated scenario. Imagine that six months into the role, you observe the following: first-time fix is flat, not terrible but not improving. Backlog is manageable, but ageing is slightly worsening. Customer satisfaction is stable. Technician utilisation is high. Overtime is rising slowly. Profitability is under pressure. What is your conclusion?
Sam Brooks
I would conclude that the system is busy, but likely not healthy enough. High utilisation coupled with rising overtime and worsening backlog ageing often indicates that the business is closer to saturation than it appears on the surface. Stable customer satisfaction can be misleading in this context, as customers may remain sufficiently satisfied while the internal engine is already strained. My primary hypothesis would be that the organisation is absorbing complexity inefficiently. This could stem from planning quality, repeat interventions, poor prioritisation, uneven parts availability, or commercial commitments misaligned with delivery capacity. I would then test the pattern. Where is the overtime concentrated? Which accounts generate the oldest backlog? Are we deploying expert technicians on work that could be better segmented? Is the issue structural across the business, or concentrated in a region, customer type, or service line? In essence, I would move from a symptom cluster to a targeted diagnosis. The danger in such situations is launching generic productivity pressure when the real issue may be poor mix, weak prioritisation, or hidden exceptions.
Jordan Cole
And how would you determine whether the problem is structural or merely local noise?
Sam Brooks
By triangulating data, behaviour, and recurrence. If the same pattern emerges across multiple sites, managers, and reporting cycles, it is likely structural. If it is concentrated around one account, manager, team, or specific process step, it may be local noise, though local noise can still be significant. I would also compare what the metrics indicate with what people report. If the numbers show strain and the frontline describes the same strain in operational terms, late parts, unrealistic scheduling, repeat work, invisible exceptions, then the diagnosis strengthens. What matters in these environments is the ability to read a system as it truly functions, not merely as it is described, and then adapt the operating model without losing control.
Jordan Cole
Turning to the handover phase, the sentiment of respecting the outgoing leader’s expertise is straightforward. What concrete steps would you take in those initial weeks to ensure a smooth transition?
Sam Brooks
I would be highly intentional. I would seek joint account reviews, not merely introductions. Joint customer visits, not just names on a slide. Exposure to service meetings, not just summary explanations. I would also explicitly inquire about unwritten rules: which customers are politically sensitive, which processes are officially standard but flexible in practice, which managers exert influence beyond their formal role, and which recurring issues tend to be normalised. Simultaneously, I would document my own observations independently. I would use the transition period to distinguish between legacy strengths and legacy habits. They are not synonymous. And I would avoid premature redesign. During handover, people observe less what you decide and more how you interpret what you inherit. If you signal contempt, you lose trust. If you signal blindness, you lose credibility. The appropriate stance is respectful curiosity coupled with analytical discipline.
Jordan Cole
Excellent. Now, a more difficult people question. What if one of those long-standing managers is deeply respected internally, particularly by technicians, but is consistently weak on follow-through, KPI discipline, and managerial accountability? Do you move quickly or slowly?
Sam Brooks
Quickly on diagnosis, carefully on consequence. I would make expectations explicit and observable. I would not allow the issue to linger in the ‘he is good, but…’ zone. I would coach the individual, support them, and make the gaps visible in specific behavioural terms: late escalation, weak review discipline, vague accountability, tolerance for unmanaged exceptions, whatever the actual issue may be. If there is movement, I invest. If there is no movement, I decide. However, the decision must rest on clarity and fairness, not impatience. In long-tenured cultures, people watch closely to determine whether management change is arbitrary or principled. Therefore, I would rather move slightly later with full legitimacy than slightly earlier with symbolic violence. That said, I do not believe in infinite accommodation. If the organisation is evolving, managers must evolve with it.
Jordan Cole
I assume you realise that some will interpret that as, ‘She sounds tough.’
Sam Brooks
I am tough on ambiguity and drift. I endeavour not to be harsh with people. These are distinct concepts. In my experience, people can endure demanding leadership if it is coherent, fair, and connected to a better system. What they struggle with is inconsistent pressure, hidden criteria, and leaders who advocate for transformation yet tolerate confusion.
Jordan Cole
Final operational question. How would you avoid overcorrecting the culture? That is a genuine risk in companies requiring evolution.
Sam Brooks
By sequencing, not shocking. In a service business, attempting to modernise everything simultaneously often destroys both confidence and execution. I would avoid destabilising the frontline with unnecessary bureaucracy or symbolic ‘fresh-start’ gestures. I would preserve what drives customer trust. I would change where the benefits are tangible and explainable. And I would sequence change so people can absorb it. This means creating movement through management rhythm, selective clarity, and improved visibility, not through grand declarations. If you improve the way the business sees itself, reviews itself, and decides, behaviour begins to shift. That is more durable than performing transformation theatrically.
Jordan Cole
Agreed. We are nearly finished. What is the single best summary of the value you believe you would bring here?
Sam Brooks
I believe my value lies not merely in managing change, but in leading a business through adaptive evolution that protects what is strong, clarifies what is unclear, and transforms what is no longer fit for the next phase.
Jordan Cole
That is concise. I appreciate conciseness. Do you have any questions for me?
Sam Brooks
I have four questions. First, where is the largest discrepancy between the documented operating model and the actual day-to-day operations? Second, which element of the current framework is a true asset, and which one persists out of habit rather than effectiveness? Third, upon joining, what specific aspects would you want me to maintain during the transition, and which would you want me to scrutinise and improve? Finally, which operational metric do you rely on most, and which one might be masking underlying problems?
Jordan Cole
Those are exactly the inquiries I anticipated. They demonstrate that you grasp the position requires diagnosing the system before implementing changes. To summarise: the primary gap likely exists between our declared consistency and the actual variance across accounts and managers. I want to preserve the organisation’s technical rigour. I want to challenge the acceptance of ambiguity regarding profitability, standardisation, and strategic focus. Regarding metrics, I place greater confidence in our quality indicators than in our account economics. That should suffice.
Sam Brooks
It conveys quite a lot, actually. And it confirms that the challenge is both operational and managerial, not purely commercial.
Jordan Cole
Precisely. Thank you, Sam. The conversation was rigorous, practical, and notably devoid of superficial transformation rhetoric.
Sam Brooks
Thank you, Jordan. I valued the operational precision of the dialogue. It is generally a strong signal when the inquiries are this substantive.

Check your understanding

1. What is Jordan Cole's primary objective for this dialogue, as stated at the outset?

Show answer
To evaluate Sam's operational methodology, focusing on service quality, field execution, process rigour, managerial cadence, profitability, and transition risk, rather than ascertaining motivation for the role.

2. How does Sam Brooks differentiate between the formal operating model and the actual operating model?

Show answer
The formal model is what the organization professes (documented processes, official pathways, defined KPIs), while the actual model is what happens under pressure (when customers escalate, components are missing, or fatigue sets in).

3. What specific phrase does Jordan Cole highlight as resonating with him in Sam's initial response?

Show answer
'in practice, not merely on paper.'

Grammar practice (mixed)

Prepositionsself-check

Sam Brooks replies, 'I appreciate nuance when it elucidates reality, but I have never conflated it ______ decisive action.'

Show answer & why
with · 💡 The verb 'conflate' is standardly followed by the preposition 'with' when meaning to combine or confuse two distinct things.
Conjunctions

Jordan Cole says, 'In this dialogue, my objective is not to ascertain your motivation for the role, ______ to evaluate your operational methodology.'

Show answer & why
but · 💡 The structure 'not... but...' is used to contrast two alternatives, emphasizing the second option as the true objective.
Prepositionsself-check

Sam Brooks mentions, '...the balance ______ preventive and corrective work...'

Show answer & why
between · 💡 'Between' is used when referring to a relationship or balance involving two distinct items: preventive and corrective work.
Tensesself-check

Jordan Cole states that Alex '____ a highly favourable impression following your initial discussion.'

Show answer & why
shared · 💡 The narrative is in the past tense, describing a completed action in the past.
Conjunctionsself-check

Sam Brooks says, 'I appreciate nuance ____ it elucidates reality, but I have never conflated it with decisive action.'

Show answer & why
when · 💡 The conjunction 'when' is used to indicate the time or condition under which the action occurs.

Discussion (practise speaking)

How would you address the gap between the formal operating model and the actual operating model in a technical service environment?

🤔 Think about a time when company policies differed from actual practice in your workplace.

Show sample answer
  • Observe behavior under pressure to see where the formal model breaks down.
  • Analyze the delta between documented processes and what actually happens during escalations.
  • Identify if the business is scalable by checking if formal and actual models align.

Ask Phil: Practise describing the difference between formal and actual operating models with the Pickle AI tutor.

What strategies would you use to navigate a culture that values technical expertise over commercial discipline?

🤔 Consider how you would introduce commercial discipline without alienating technical staff in your own experience.

Show sample answer
  • Reframe the narrative to show how commercial discipline safeguards technical excellence.
  • Avoid imposing 'professionalisation' from above to prevent appearing arrogant.
  • Rebalance the culture by protecting strategic technical investments through better economics.

Ask Phil: Practise discussing cultural navigation between technical and commercial teams with the Pickle AI tutor.

How would you handle a situation where strong customer loyalty coexists with weak account profitability?

🤔 Reflect on how you would balance customer satisfaction with financial health in your current role.

Show sample answer
  • Diagnose the root causes such as underpriced contracts or excessive service delivery.
  • Segment accounts to distinguish between strategic anchors and legacy habits.
  • Tether account profitability back to behavior like response commitments and pricing discipline.

Ask Phil: Practise explaining how to fix weak profitability while keeping loyal customers with the Pickle AI tutor.

What approach would you take to improve documentation rigour among technicians who view it as bureaucracy?

🤔 Think about how you would motivate your team to adopt better documentation practices.

Show sample answer
  • Acknowledge that documentation can be burdensome if poorly designed.
  • Make compliance executable by simplifying templates and improving workflow.
  • Ensure the path to compliance is the easy path, not the heroic one.

Ask Phil: Practise discussing strategies to improve documentation compliance with the Pickle AI tutor.

Vocabulary

tangible, functional outcomes
reveal definition Measurable results that have practical use in business operations. “I tend to place less value on nuance and more on tangible, functional outcomes.”
↗
service KPIs
reveal definition Key performance indicators used to measure the effectiveness of service delivery. “Initially, I would scrutinise service KPIs: first-time fix rates, repeat visits, backlog volume and ageing, MTTR, parts availability, the balance between preventive and corrective work, and any early indicators of SLA strain.”
↗
account-level profitability
reveal definition The profit generated by a specific customer account after accounting for all associated costs. “Subsequently, I would analyse the economic dimension: profitability by service segment, account-level profitability, cost-to-serve, discounting dynamics, and whether certain ‘premium’ accounts are consuming disproportionate capacity.”
↗
exception culture
reveal definition A workplace environment where deviations from standard procedures become the accepted norm. “Exception culture occurs when deviations from the standard model cease to be exceptions and become the de facto model.”
↗
technician utilisation
reveal definition A metric measuring the percentage of a technician's time spent on billable or productive work. “Technician utilisation is high. Overtime is rising slowly. Profitability is under pressure.”
↗
commercial discipline
reveal definition The practice of maintaining strict adherence to financial and business principles in operations. “Suppose service quality appears broadly acceptable, customers are not openly disgruntled, but commercial discipline is poor.”
↗
first-time fix
reveal definition A metric tracking the percentage of service issues resolved during the initial visit. “Imagine that six months into the role, you observe the following: first-time fix is flat, not terrible but not improving.”
↗
margin erosion
reveal definition The gradual reduction in profit margins due to inefficiencies or unmanaged costs. “If they diverge significantly, you encounter heroics, inconsistency, and ultimately margin erosion or quality risk.”
↗

Key phrases (useful expressions from the dialogue)

More Meetings & Discussions lessons

Addressing Board Concerns on Coastal Installation

A client follows up with a supplier after presenting initial product details to their board, which raises spec…

Addressing Competitive Pricing and Fulfillment Challenges

Clara and Sophie discuss competitive pricing pressures and inventory fulfillment issues to optimize Q4 sales p…

Addressing Late Reports and Budget Discrepancies in Programme Coordination

A founder discusses programme reporting delays, budget discrepancies, and workload management with a field coo…

Analyzing SEO and Social Media KPIs for Strategy Optimization

Alex and Jordan review website and social media performance metrics after a successful week of SEO and SMO cam…

Annual Performance Review and Budget Planning

An employee meets with their manager to review the first year's performance, discuss financial compensation, a…

Conducting a Systems Overhaul Needs Analysis

An IT consultant meets with an insurance CEO to identify pain points in legacy systems and plan a modernizatio…

Keep going

Practise this scenario live with Phil, and get a personalised lesson built from your own mistakes. Interactive in the browser, with a booklet to keep.

Book a lesson with Phil