Ask your team before you change how they work
By Consaya Editorial — 2026-11-16
A partner sees a demo. The numbers look good. The contract gets signed. The team finds out when the training invite arrives in their inbox.
By then, the most important decisions have already been made. The people who will use the new tool every day had no say in which problem it was supposed to solve or how success would be measured. This happens at nearly every firm because change management starts in a partner meeting, not with the people doing the work.
Gartner ran a July 2025 survey of 313 senior leaders and found that organizations that regularly adapted their change plans based on employee responses were four times more likely to achieve change success. That is a large return on a few honest conversations. With 2027 planning underway and new tools arriving daily, now is the time to ask your team before you announce anything.
What does a good day at work look like for you right now?
Start with what's working. This question tells you which parts of the job give people energy, and those are the parts you want to protect as everything around them changes. If a senior associate lights up talking about walking a client through a cash flow problem, automating the prep work around those conversations will feel like a gift to them. If your plan changes the client conversation itself, you'll know to expect resistance before you spend a dollar on implementation. You'll also avoid the worst kind of rollout failure: a tool that does its job perfectly but removes something people valued.
Where do you lose the most time?
The vendor demo shows you where time could be saved. Your team can tell you where it actually goes. The answers often point to a process problem that no tool will fix: a handoff nobody owns, a client who always sends documents late, a review step that happens twice because two people thought it was their job. A new tool aimed at the wrong friction will run the wrong process faster. Aim the change at the friction your people describe, and you'll get adoption without having to push for it.
What worries you about this change?
Ask it directly, and resist the urge to answer every concern on the spot. People will tell you what worries them only if they believe you want to hear it. Gartner warns that employees sometimes perform change, attending the training and saying the right things, without actually adopting it. If enthusiasm is the only safe answer in the room, you'll get enthusiasm in the meeting and old habits at the desk. The worries you hear before rollout are far cheaper to address than the workarounds you discover after it.
What would tell you this is working by the end of the first month?
Most firms define success at the finish line: full adoption, hours saved, a faster close. Those goals are months away, and people lose momentum long before they get there. Ask your team to name the early markers instead. The first client file finished without a workaround. The first week nobody exported the output to a spreadsheet to double-check it. When the team helps write the definition of success, they have a reason to watch for it, and you have a way to keep them engaged through the hard part of the implementation.
Who should we be asking that we haven't asked yet?
Change plans tend to be built from the opinions of whoever is already in the room. The admin who handles client onboarding, the staff accountant who fields every exception, and the remote team member who rarely speaks up in meetings often know exactly why the current process looks the way it does. This question invites your team to bring those people in. It's also the fastest way to find the person who knows about the workaround nobody documented.
What you do with the answers
Write them down. Then go back to your team and tell them what changed because of what they said, whether that's the timeline that moved, the feature you turned off, or the task you took off someone's list. Closing that loop is what makes people willing to answer honestly the next time you ask. If an answer doesn't change the plan, say that too and explain why. People can accept a decision they disagree with much more easily than one that seems to have ignored them.
At the end of the first month, check back using the markers from question four. Ask what's working, what isn't, and what needs to shift. Then make the adjustments. Before your next rollout, block an hour with your team before the training invite goes out. Ask these five questions and listen to the whole answer.
Your team knows what tools matter to them. You just have to ask first.