Start the project right: Understand the problem
Some years ago I was entering the software development industry. I remember the thrill of my first project, making something that didn’t exist before. But that lasted until things started to act strange on most projects. Last minute changes, working overtime to fix bugs, you’ve been there too, right?
After a couple projects with stress and frustration, you may be calling for a change. It looks good at the beginning, but things go sour and you don’t even know what happened. I’ve been there, I know how it feels like. How can I change that? Glad you asked.
First, resist the temptation to fill the project with all your preconception and ideas. After, prevent all stakeholders from doing the same. Doing so will frame the solution too early.
The problem relies here, framing the solution when you don’t even know the problem that well. First you need to understand the problem, who has it, and the solution realm. Then you’re able to decide where to go.
IBM Design Thinking helps you understand the problem and explore solutions. It’s a framework of tools you can use to, with everyone involved, find the right path. Let’s have a quick look into why and how you should use it.
What is Design Thinking, anyway?
Odds are that you’ve heard about it somewhere. It’s a framework to help you think in a holistic way. It helps you empathise with the user, understand the problem, the solutions, and more.
It is an effective way to start a project, since it brings everything to the table through a new perspective. And IBM’s flavour of Design Thinking brings tools to enable it in complex organisations.
But even if you’re in a small company or independent team, take a look at the new things proposed. You might find it useful to enhance your next Design Thinking session.
Why IBM Design Thinking?
IBM’s take on it includes three main techniques: Hills, Playbacks and Sponsor Users. They make the process appealing to the modern — and sometimes complex — organisation.
Hills are a way to create specific outcomes for your team. It defines what you want to achieve and how to impress, from your customer’s perspective. Have a look at the hills.
Playbacks are meetings with stakeholders, on a regulara basis, to align everyone. It looks at the user's needs and the Hills to keep the product vision aligned. Both the stakeholders and the team participates.
When you’re starting the project, use Playback Zero. It removes the feedback side, since you’re getting started, replacing it with lo-fi prototypes. The prototypes are then used to share the product understanding and find the right path. Playbacks are awesome!
Sponsor User, the last tool, gives the final user a seat at the table. Instead of using a persona, invite a real person that’s going to use your product, and listen to them. Having a person on the table helps everyone empathise with the user. Also, it helps settle otherwise endless arguments.
If you like the concepts, give IBM Design Thinking official page a read. Everything is explained in detail and depth.
How do I begin?
First of all, you need someone to guide the workshop. He will guide everyone through the steps, asking the right questions and writing everything.
Inside IBM there’s a specific training to teach you how to do that, but don’t let that stop you if you don’t have it. First, you need the basic Design Thinking knowledge, which you can get from this book. Then, get familiar with the IBM Design Thinking methodologies cited earlier. That’s it, you’re ready to run your first workshop!
Of course the first won’t be perfect, set expectations for that. But I guarantee it’s going to be way better then not having it. And you will get better every time.
This article is part of a series that help you tear down the walls in your organisation. After you start the project right, take a look at:
