A recommendation is easier to question when you can see how it was made. That is a good thing.
Alongside the team, I’ve helped explain why some solutions made a shortlist and others didn’t. From the client’s side, “Why didn’t this one make the shortlist?” is a fair question. They may have used it before. It might fit a process their team already knows. Or it might simply be popular in their country.
We start with the requirements behind the shortlist. What will it cost to run the solution today? Will that cost change if the business grows and crosses a licensing threshold? Which integrations does the solution need, and what will the business need to support next?
If one option needs a custom integration, someone will have to maintain it after launch. I’d want to know who will own that work before we recommend the solution.
Making those considerations visible gives us something concrete to discuss: the trade-offs we are willing to take on, and the new information that would change the recommendation.
I want there to be room for that conversation before anyone commits to anything.
Also, I couldn’t resist using an illustration inspired by the Open Studio 17 website. I love these visuals!
