agree the outcomes
If asked, most people will describe what they want as opposed to what they need; this confusion can lead to the wrong solution and therefore differentiation is essential.
Once the issues are defined, it’s possible to ask "what would you rather have happen?" These represent the outcomes that should ideally be expressed in business terms rather than a technical solution and can be executed in one or more ways.
A well formed outcome is one that satisfies certain reality tests. Outcomes which aren’t well formed are usually difficult or even impossible to achieve. These are essential in defining your business requirements. In fact, they are (or should be) the requirements that form the foundation of the specification.
All too often one hears "we need a database / piece of software / faster communications" as proposed outcomes. They’re not. They are solutions to an (undefined) outcome.
If you like to get in touch, please telephone our offices on
+44 (0) 1364 582017 or complete our
on-line form and we'll get back to you
as soon as possible.
Stay in touch with what we're up to at Ayrmer Software by following us on one of our
social media feeds: we'd be delighted to welcome you as a follower on
become friends on facebook
or add us to your circle on Google+.
You'll also find us on Linkedin, of course.
Find out more about how we ensure that we have a clear understanding of the scope of the project, enabling us to present a solution that will meet your business requirements.
identify the issues
People rarely think with sufficient clarity, because they are too close to the business, this can make it difficult for the business to be objective. Find out how we tackle this to ensure that we can identify teh issues and not just the symptoms.
recommend a solution
The solution is dependent on resources that may also restrict outcome being implemented. For each outcome there will be an effect; what will it be like after the solution is implemented?