TEST Design thinking is a hot buzzword, especially in the tech startup world where buzzwords are getting out of control. Some IT pros, particularly the old-school among us that don’t have a lot of patience for fluff, roll their eyes when they hear these new phrases. But there’s more to it: a design approach can help your IT team take a fresh look at business challenges and opportunities, identify problems more effectively, solve them more creatively, and even build better working relationships with your colleagues.
What’s the buzz?
There are a lot of definitions of design thinking floating around—I like this one over at Forbes: “Design thinking combines creative and critical thinking that allows information and ideas to be organized, decisions to be made, situations to be improved, and knowledge to be gained. It’s a mindset focused on solutions—not the problem.” The design approach might sound like something born in the creative world, but there’s something very rational about it at its core—especially since it’s a repeatable process.
This type of thinking is meant to be applied over and over again within a company, bringing diverse teams together to collaboratively solve problems, think outside the box, andinnovate in ways that create value for the business. And it’s especially valuable in situations where defaulting to the old way of doing things (because that’s the way they’ve always been done) doesn’t work anymore. I’d argue that nearly every IT shop is faced with this situation today.
Outlining the design process
At Stanford’s Institute of Design, also known as the d.school, it begins with five core actions: empathize, define, ideate, prototype, and test. All these steps put the user or the customer at the center of the process, placing a focus on their experiences and needs.
The empathy step invites you to observe users and empathize with the challenges or obstacles they may face in their day-to-day tasks. By putting yourself in their shoes, experiencing what they experience, and finding out what they really want and need, you get to the core of the problem. It’s well known that a large percentage of IT projects fail—a design approach helps protect against this by devoting big chunks of time to this first step, so when it comes time to define the issue or problem, everyone has a full understanding of the context and the users’ needs.
Next, it’s time to define the issue or problem and begin collaboratively ideating on a series of possible solutions, which are then quickly and cheaply prototyped and tested so you can quickly identify the most viable paths to success. This approach requires high tolerance for failure, so if your company is risk-averse, this could be uncomfortable at first. The good news is that the design approach builds capacity for risk-taking and experimentation, which are essential to developing truly innovative and creative solutions on a repeatable basis.