Technology Needs Definition.

Define what a tool must genuinely do, from the work it will serve and the limits you actually have, so you choose against your needs rather than a salesperson’s feature list.

First in Get the Right Technology in Place, before you look at a single product. Start from the process the tool will serve, not from what is on the market.

What the tool must do

The process this tool is meant to serve (map it first if you have not)

Must-haves: what it genuinely has to do for the work to run

Nice-to-haves: what would help but is not essential

Must work with: what you already use that it has to fit alongside

Your real limits

What you can spend up front, and every year to keep it running

How much staff time you have to set it up and learn it

How technical your people are, and how much support they will need

Never buy a tool to fix a process you have not defined; software laid over a broken process just makes a faster mess. Separate must-haves from nice-to-haves before you shop. This is your yardstick; measure every option against it, not against how impressive the sales pitch is. Feeds the Selection Scorecard.

Your answers stay in your browser on this page and are never sent anywhere. Use Save or print to keep your copy.

Back to Get the Right Technology in Place, or start over from the welcome page.