There’s a transformation going on in many organisations. The focus is less on conventional wisdom and more on what’s actually needed to achieve targets, objectives or need.
New initiatives should always be driven by need. User needs are driven by aspirations, desires and previous experience in situations people find themselves in. In a well functioning organisation needs should stem from personal or team objectives that align with organisational purpose. Overall flow should look like one below.
Still I’m regularly asked “Do you know a tool we could use to do this?”. Default response is to “quantify and define your business problem, and state it clearly”. This is the business analysis phase where business needs to understand their problem, or what they believe is a problem. This is also a point where people often need help form an outsider who is not aware of all the intricacies of the situation or need and thus are not dismissing various options.
Many seasoned professionals tend to stick to tools or vendors they’ve used in the past rather than looking out to market for the most appropriate tool or service that meets their needs. This, however, expects needs and drivers to be identified, listed and weighted against each other, and existing tools - again, what’s your business problem? Is there perhaps a tool in the organisation that will already met this need? Will it meet 75-80% of your must-have’s and the rest can be done using something else? does this tool need to meet 100% of your need? Are you clear on your need?
Concentrating on user needs gives organisation ability to understand its current capabilities and will potentially highlight training needs.
Focusing on existing tooling limits the choice before it’s clear what drives the user need.