“We don’t know what we don’t know.” Why do I hear this phrase so often?

Watch the video here.

Let’s say you’re a law firm about to review your case management system - you know yours isn’t working for you, you have an idea what you’d like it to be able to do, but you are not sure what is even in the market… what you could be doing. This is when I hear the phrase “we don’t know what we don’t know.” And it is a valid point, but it’s when it is applied which is key.

A project should have (ideally) six phases, based around strategy, acquiring knowledge, confirming requirements, identifying a solution, building or tailoring the solution and implementation with training.

Often, my clients have jumped straight from phase 1 to phase 4 - from strategy straight to choosing a new product. This starts a long chain of events and discussions around pricing and sales, implementation, features, benefits, but often misses out on the vital gathering of information that is needed to ensure the success of the project.

You’ve gone straight from deciding to build a house to trying to find a builder, without understanding how many rooms you want, where or or doing any research on the area.

This is why I have developed my own Digital Evolution Framework. A project management methodology where I can show you how to do the research, when to introduce “we don’t know what we don’t know”, so you can open up the possibility of solutions at the right time and collate the information and options appropriate to ensuring your IT project is a success.

I know what you don’t know.

If this sounds like a problem you have faced, I’d love to have a conversation with you and share my methodology. Please do get in touch.