Spreadsheets and on-premises Microsoft Project installations are giving way to cloud work management tools. Teams are looking at Jira, Asana, Smartsheet, and monday.com (which changed its name from dapulse late last year), among others. The question we hear is “which one should we buy?” It’s the wrong place to start.

Start from how work flows

Before you open a vendor website, describe how work moves through your organization. Who requests it? Who approves it? Who does it, and who needs to know when it’s finished? Write this down for two or three typical kinds of work, such as a software release, a marketing campaign, and a facilities request.

Then list who needs what view. An executive wants a portfolio summary. A team lead wants a board of this week’s tasks. A finance analyst wants hours and costs. If you can’t state these needs, any tool demo will look impressive, because you have nothing to test it against.

Run a pilot

Choose two or three candidates and run each with a real team on real work for a few weeks. A demo shows the best case. A pilot shows what happens when someone has to set up a recurring task, reassign work while on leave, or fix a mistake.

Pick a pilot team that is neither the most enthusiastic nor the most skeptical. Ask them specific questions afterward. Did you use it daily? Did you go back to email? What was confusing in the first week?

Look past the features

Features are the easiest thing to compare and the least useful. Most tools in this category can do most of what a team needs. The differences that matter appear elsewhere.

• Reporting. Can leaders get the view they need without exporting to a spreadsheet?
• Administration. Who sets up projects, manages permissions, and handles people joining and leaving? How much does that cost in time?
• Adoption. Will people use it without being chased? A tool that looks tidy but sits unused is worse than the spreadsheet.
• Fit with your process. Does the tool bend to how you work, or does it demand you change?

Consider a regional healthcare group choosing between three tools. The clinical operations team loves one, the IT group prefers another, and neither fits finance. A pilot with all three groups often shows that the real need is a common set of fields and a shared reporting view, and that the tool matters less than agreeing on those.

A word of caution: don’t treat the tool as a substitute for process. If requests arrive by hallway conversation today, a new tool will give you a nicer place to lose them.

If you’re about to start a selection, spend the first week on the workflow notes and view list. Everything after that gets easier.