This step is called DEFINE PROBLEM.
The whole point of this step is to dream big and in extreme detail.
This is not something that we automatically do… but I can coach you through how to make it happen.
The issue with this step is that there is ALWAYS more hidden information, and we need to dig it up.
Think about it like doing a house walkthrough — the first time you go through you don’t notice everything, but you get a general idea.
When you go through again, you start looking behind every door a bit more carefully, and up at the ceiling.
YOU’RE NOTICING MORE.
And that’s the whole point… that by noticing MORE you are able to have a better and more thorough picture in your mind of what’s actually happening.
The trick here is to not believe yourself when you say “Oh, I’ve thought of enough things.”
It’s like peeling back an onion. There’s a layer beneath that you didn’t notice yet.
And by noticing more layers, by going deeper with it, you can save LOADS of money on software/app development.
By going deeper, there’s less confusion.
Really, at the core, it’s a very serious game of Telephone.
You have an idea in your head that the development team needs to understand, and any detail you leave out they might get wrong.
So overcommunication here is fantastic.
Overcommunication is what saves you, and helps you verify that you truly have said what you need.
Overcommunication and going over the same thought a few different times is helpful.
This is an exercise for you to use your imagination. Not like a dream, but more like just seeing pictures in your head.
Imagine you show up on the front page of your app. It’s done, it’s all finished.
Why are you there? What’s the point of why you’re here? What do you need to do?
To Do: List it out, in bulletpoints.
This is layer one. By listing it out, you’re starting to outline a foundation of the purpose of the app…
What problem it solves, who it helps, why it helps them.
You should be able to
Now, let’s go one layer deeper.
Make bulletpoints inside the bulletpoints.
This means, take an idea you’ve started, and then ask more questions around it.
If you’re building an app to help people who need to hire someone for a task, get to the core of the reasoning for what they need.
Here’s an example going 2 levels deep, by using the example app Uber (ride-sharing app)…
- People want to use this app so they can get from place to place
- And also save time
So at first, on the surface, people just need to get from place to place, but then when you dig deeper you can see that it’s not just another taxi service.
It’s a hugely efficient, simple taxi service.
So when you notice that it’s a TIME-SAVING app, then it helps get better optics on exactly what it is you’re aiming for.
User flow and speed is of the utmost importance, from day one.
To Do: Try to go at least two levels deep on the initial things you listed. Try to see the same thing for a different angle, or just ask yourself again… “Why?”