Changing & Improving

You spot that a weekly report your team produces takes a full day to compile by hand, and you think a spreadsheet template could cut that to an hour. Which response would be MOST effective?

• ABuild a quick version of the template, test it alongside the current process for a week, and show the team the result✓
• BAsk your manager to commission the IT team to build a proper reporting tool, rather than relying on a spreadsheet that could break later
• CKeep compiling the report by hand, since the current process works and changing it could introduce errors
• DSuggest the idea at the next team meeting and leave it to the team to decide whether anyone has the time or interest to take it forward

Answer: Improvement is driven by people who try things: a small, tested prototype gives the team evidence rather than an opinion. Floating the idea without acting, sticking with the slow process out of caution, or asking for a large IT project all delay a change that could be proven in a week.

A new way of working is being introduced across your directorate. You can see clear benefits, but several colleagues are anxious about it and one is openly hostile. Which response would be MOST effective?

• AListen to the concerns, address the ones you can with facts or support, and feed the rest back to those leading the change✓
• BTell the colleagues that the decision has been made and that resistance will only make the transition harder for everyone
• CAgree with the colleagues that the change is being handled badly, so that they feel supported during a difficult period
• DAvoid discussing the change with the hostile colleague so as not to give their opposition more attention than it deserves

Answer: Supporting change means engaging with people's concerns: answer what you can, support where it is needed, and pass the rest to those who can act. Shutting down discussion, isolating the hostile colleague, or siding against the change all make the transition harder rather than easier.

You tried a new approach to a task and it did not work; the task took longer than it would have done the old way. Your manager asks how it went. Which response would be MOST effective?

• AExplain what you tried, what went wrong and what you learned, and suggest what you would do differently next time✓
• BSay the task went fine and return quietly to the old approach so that the failed experiment does not count against you
• CAttribute the extra time to the task being harder than expected rather than to the approach you chose
• DExplain that the new approach failed and that you will not be trying anything different again for this kind of task

Answer: Learning from failure requires being open about it: describe the attempt, the outcome and the lesson. Hiding the failure, swearing off further experiments, or blaming the task all waste the learning and discourage the kind of trial that improvement depends on.

Senior management has asked for ideas to improve a service. You have an idea that would help users but would change how a neighbouring team works, and that team has not been consulted. Which response would be MOST effective?

• ADrop the idea, because a change that affects another team's work is not yours to propose
• BDiscuss the idea with the neighbouring team first, refine it with their input, and put it forward as a joint proposal✓
• CSubmit the idea directly to senior management, since the request came from them and the other team can be consulted later
• DSubmit the idea and note that the other team may object, leaving senior management to decide whether to consult them

Answer: Good improvement ideas are shaped with the people they affect: involving the neighbouring team early improves the proposal and its chances of working. Going over their heads, abandoning the idea, or leaving the consultation to others all treat the other team as an obstacle rather than a partner.

Your team has done a process the same way for years. A new starter asks why a particular step is needed, and nobody can explain its purpose. Which response would be MOST effective?

• AExplain that the step is part of the established process and should continue to be followed until someone with the authority to do so changes it
• BFind out whether the step still serves a purpose, and if it does not, propose removing it and test the process without it✓
• CTell the new starter that questions about the process are best saved until they have been in the team long enough to understand how it works
• DRemove the step from your own work immediately, since a step that nobody in the team can justify is clearly unnecessary and only slows things down

Answer: Improvement often starts with a simple question: check whether the step has a purpose and, if not, propose and test its removal. Defending the step because it exists, dropping it unilaterally without checking, or discouraging the question all miss the opportunity.

A digital tool has been introduced to replace a paper process. It works well for most tasks but is worse for one common task, which is now taking longer. Which response would be MOST effective?

• ADocument the specific problem with examples, feed it back to the tool's owners, and agree an interim way to handle that task✓
• BTell the team the tool is not fit for purpose and ask for the paper process to be reinstated across all tasks
• CGo back to the paper process for that task without telling anyone, since the tool clearly was not designed with it in mind
• DAccept the slower task as the price of the new tool, since raising problems could be seen as resistance to the change

Answer: Constructive feedback makes change work: specific, evidenced problems can be fixed, and an agreed interim approach keeps work moving. Reverting in secret, suffering in silence, or rejecting the whole tool over one task all prevent the improvement that the feedback would bring.

You are leading a change that a small number of experienced staff strongly oppose. They argue that the old approach handled rare but serious cases better. Which response would be MOST effective?

• AProceed as planned but exempt the opposing staff from the change so that their objections no longer hold it up
• BExamine their examples seriously, adapt the change if the concern holds, and explain the reasoning either way✓
• CProceed as planned, since the opposition comes from a small number of people who are used to the old way of working
• DAbandon the change, because experienced staff are the best judges of what works in practice

Answer: Opposition from experienced people can carry real evidence: test their examples, adjust the change if they are right, and be transparent about the decision. Pressing on regardless, giving up entirely, or carving out exemptions all fail to engage with the substance of the concern.

You have been asked to review how your team handles requests from other departments. You suspect the process is slow, but you have no data. Which response would be MOST effective?

• ARecommend that the team be given more staff, since a slow process is usually the result of too few people to handle the volume of requests
• BTrack a sample of requests from receipt to completion, find where the time goes, and base any proposed changes on what the data shows✓
• CRedesign the process straight away based on your own experience of where the delays occur
• DAsk the other departments whether they are satisfied with the service they get and leave the process unchanged if nobody raises a complaint

Answer: Improvement should be grounded in evidence: measure the process, find the bottlenecks, and change what the data points to. Redesigning on instinct, relying on the absence of complaints, or defaulting to a request for more staff all skip the analysis that would show what actually needs to change.

Your team is asked to trial a new way of prioritising cases for six weeks. Halfway through, the results look worse than the old method. Which response would be MOST effective?

• AStop the trial immediately, since the early results show that the new method does not work
• BContinue the trial to its planned end while capturing what is going wrong, so that the evaluation is based on a fair test✓
• CQuietly revert to the old method for the difficult cases while keeping the trial running for the easy ones
• DExtend the trial by another six weeks, since the team may simply need longer to get used to the method

Answer: Improvement depends on fair tests and honest evaluation. Abandoning a trial at the midpoint, contaminating it with a partial reversion, or extending it without evidence all undermine what the trial was meant to learn.

A junior colleague suggests a change to a long-standing process that you think will not work. Which response would be MOST effective?

• AAdopt the change to encourage the colleague, even though you expect it to fail
• BExplain that the process has worked for years and that there is no need to change it
• CExplore the idea with them, explain your concerns, and if the concerns can be tested cheaply, try it✓
• DTell them to write a business case so that the idea can be considered properly

Answer: Openness to ideas means engaging with them seriously, including the ones you doubt, and letting a cheap test settle the question. Dismissing the idea, adopting it insincerely, or demanding a business case for a small change all discourage the next suggestion.

A new digital system has been introduced across the department. You can see it will improve things eventually, but your team is losing productivity in the transition and other managers are calling for it to be withdrawn. Which response would be MOST effective?

• ASupport the transition by giving your team training and time, feed specific problems back to the project, and resist calls for withdrawal that are based on short-term pain alone✓
• BSay nothing publicly and let the department decide whether the system stays or goes, since a decision of that size is well above your level and your view would carry little weight
• CTell your team quietly to use the old system where possible until the new one has been improved, since protecting their productivity is your first responsibility as their manager
• DJoin the other managers in calling publicly for the system to be withdrawn, since the loss of productivity is real, your team is suffering, and a united front is the only thing senior management will listen to

Answer: Leading change means holding the line on a sound change while working hard to make the transition bearable and feeding back what needs fixing. Joining the retreat, quietly reverting, or standing aside all fail to lead through the difficult middle of a change.