Transformation in practice
How to work through objections during a transformation

In a project meeting, a team lead says, “If we switch on Monday, we won’t be able to answer customers’ questions at the branch.” You now have something you can work with. Which questions does she mean? What happens if her colleagues cannot answer? Who can decide what is still possible before Monday?
Raising an objection in the room takes a risk. How leaders respond helps determine whether others will speak openly next time. Take the concern seriously, examine a real case and explain the decision to the people who will work with it.
Find out where the work would get stuck
Try saying, “Thank you for raising this here. Can you take us through a question your team would struggle to answer on Monday?” Ask someone who does the work to walk through the steps from the customer’s question to the answer. Information may be missing. The team might need a named person to call temporarily. Or the timing may depend on a decision nobody in the room has had the authority to make.
Let the people involved describe the situation themselves. Handle confidential or personal details in an appropriate setting. Make sure the people responsible for the decision have the information they need.
Tell people which questions are still open
A useful commitment might sound like this: “The start date is fixed. We still need to decide how to handle exceptions in the first week. We will review two recent cases with you by Thursday. Then I will tell you what support is available and what still needs work.”
If the date is open too, say so. If you do not know the answer, name who will find it and by when. An objection can reveal experience the project plan missed. It can also raise a question you have already decided. In both cases, explain what you heard, how you weighed it and what your decision means for the team.
Close the loop with the people who raised it
Before you look at the cases, agree on what would lead you to change your plan. In this example, the branch needs to be able to find the information or reach the person responsible in two common exceptions. If the trial reveals a gap, the people responsible decide what support is needed to keep the work running.
Take the answer back to the people who raised the concern. “We reviewed both cases with you. One lacked a clear owner. The back office will take those requests in the first week. On Friday we will look at the questions together and decide whether the arrangement is working.” The team can see what happened to its feedback and when it can share what it learns.
A decision record for your next meeting
- Observation. Which work situation did someone raise?
- Open question. What do we need to check in a real case, and with whom?
- Decision. Who decides, by when and against which criterion?
- Response. Who explains the decision to the people affected?
- Follow-up. When will we check together whether the situation improved?
At your next meeting, start with one concern that usually comes up after everyone has left. Invite the people who know the work. You can make and explain a clear decision even when the team was hoping for a different answer.