Transformation in practice
How to set transformation goals people can use at work

In the meeting room, the goal is “simplify customer service”. Two floors down, a colleague is explaining for the third time which documents a customer still needs to send. That is where you can examine the goal. What should the colleague be able to do differently after the change? What should the customer notice?
A useful transformation goal describes a real work situation that should play out differently. It tells people who needs to be able to do what, and how they will recognise whether the change works.
Turn the project brief into a goal people can see
“We will launch a customer portal by the end of the year” sets a deadline for delivery. The goal behind it might read: “Customers with a standard request can see what happens next. If they call, customer service gives them the same answer.” IT, customer service and their leaders can picture the same situation. They can work out what information is missing, how to keep it current and who takes responsibility for correcting it.
This is an illustrative example. In your organisation, find a situation your team recognises. Go to where it happens and ask someone to walk you through a recent case. When did someone have to improvise? Who had to chase an answer? Which decision would have made the work easier? Those observations give you a goal you can discuss together.
Agree on the starting point and how to check progress
Before the first trial, look at a small set of comparable cases. How often do people ask for an update today? Why do they call? Which requests can the team resolve straight away? Record what counts as a standard case and which periods you will compare. A simpler mix of cases can otherwise look like progress.
Agree on what you want to protect while you make the change. In this example, you want fewer calls for updates and customers with unusual requests still need to get help promptly. If the numbers improve and the team has to rescue more cases by hand, both belong in the review.
Discuss the goal in 25 minutes
- Five minutes. Someone involved in the work describes a typical case. The others ask questions to understand it.
- Ten minutes. Each person writes one sentence describing how that case should play out after the change. Read the sentences aloud and find the differences.
- Ten minutes. Agree on a sentence, a person responsible and a review date. Decide which case you will look at during the review and what you will gather beforehand.
Then take the sentence to two people who do the work daily. Ask what it means for their work and what they would need to make it possible. Different answers show you exactly where the goal needs more attention.
A template for writing your goal
By [review date], [person or team] can [observable action] in [specific situation]. We will look for [evidence]. Our starting point is [what we observe today]. [Name or role] is responsible for resolving [open decision] by then.
The template also works for culture, leadership and sales. A leadership team can agree how it will resolve a conflict between priorities and explain the decision to the teams affected. Sales colleagues can define what a customer should understand about their next step when the first conversation ends.
Take the sentence to your next meeting and ask for a recent case. If you can describe what happens today and what should happen after the change, your team has a useful starting point.