It may sound counter-intuitive to say you shouldn’t give solutions but let me explain.
All too often I talk to businesses whose starting point to a project is deciding on the system or solution they will implement. Usually this is because someone in the business has been approached by a salesperson, heard about a big-name technology solution, or even gone on Google!
What hasn’t happened is taking that step back and fully thinking about the problem you are trying to solve.
Why is that?
It can be hard to admit that you don’t have all the knowledge, especially in your field of expertise. The reality is that almost no individual will ever know or be fully aware of the entire end-to-end process and have an in-depth understanding of the problems that are being faced.
And of course, fully understanding the problem you are trying to solve will ultimately lead to accountability.
If you capture and can articulate the issue, you are faced with two options:
• Deliver a solution that solves it 100%
• Be clear that the answer will only resolve (For example) 75% or 80% of the issue.
Being prepared to admit you will achieve either of these can be uncomfortable.
The first puts an enormous amount of pressure on the project. In many situations it’s probably also undeliverable as there’s always some kind of compromise and trade-off between time, quality and cost.
The second option may mean that the project isn’t given the go-ahead. It’s easy to have the mind set of “I have a great solution to propose, so of course the business should adopt it!” This can lead to a reluctance to be honest about how effective the solution would be.
In contrast, finding a solution that will solve a problem (Even if it’s not your main problem) leaves plenty of wriggle room after delivery to say the delivery was a success. And this is an easy trap to fall into.
What can you do?
Before you even contemplate the solution, you must be clear about the problem you are trying to solve. AND THIS MUST BE COLLABORATIVE.
Someone representing each part of the end-to-end process needs to be involved. This is critical. Even if you only intend to change one part of the process, you need to be sure there are no unintended consequences of the change.
Map out the process, pick out your pain points and look for any opportunities to remove waste. You’ll be surprised about how much better you can make processes by simply talking them through in a group setting with the right people.
Once this is done, you can really drill into the problems left in the process and capture the size of it. Changes, whether system or process driven can be costly. Now’s the time to make sure the effort required isn’t going to outweigh the benefits.
This will allow you to fully articulate and define the problem you are actually trying to solve rather than he one you think you are.
You now have the foundations to document your true requirements and look for the right solution.