Design Thinking — Vikranth Reddimasu

A human-centered approach to problem-solving that starts with empathy and ends with tested prototypes.

What is Design Thinking?

Design Thinking is a problem-solving methodology that puts the human at the center. Instead of starting with technology or assumptions, you start by understanding the people you're building for. The approach was developed and popularized by Stanford's d.school (Hasso Plattner Institute of Design) and IDEO, with people like David Kelley and Tim Brown shaping it into the form used today.

The core idea: don't fall in love with your solution. Fall in love with the problem.

I picked this up during my University Innovation Fellows training. Our UIF team then spent two years running workshops across multiple universities, reaching 5,000+ students. It's the methodology I keep coming back to.

The Five Stages

The five stages of Design Thinking — Stanford d.school

Empathize is where everything starts. Talk to the people you're designing for. Watch how they work. Ask open-ended questions and listen. The goal isn't to confirm what you already think, it's to uncover needs that people might not even be able to articulate themselves.

Define takes what you learned and frames it as a clear problem statement. This usually looks like a "How Might We" question. Good problem framing is half the work. A well-defined problem already points toward its solution.

Ideate is about generating options, not picking the right one. Quantity over quality. Techniques like crazy eights, mind mapping, or SCAMPER help you push past the obvious first ideas and find something unexpected. The best idea in an ideation session is rarely the first one.

Prototype means making your idea tangible, fast. Paper mockups, cardboard models, simple wireframes, anything that lets someone react to something real instead of an abstract description. The point isn't to build something polished. It's to build something you can learn from.

Test closes the loop. Put your prototype in front of real people, watch what happens, and listen to what they say. Then go back and improve. The stages aren't linear. Testing often sends you back to empathize or define.

Why It Works

The thing that makes Design Thinking useful for engineers is that it fights the default instinct to jump straight to building.

Engineers (myself included) tend to hear a problem and immediately start thinking about architecture, tools, and implementation. Design Thinking forces a pause. Before you build anything, you have to prove you understand the problem. And not your version of the problem, the user's actual experience.

It's also non-linear. You're expected to loop back. Testing reveals that your problem framing was wrong? Good, go redefine. Prototyping reveals a better approach? Scrap the old idea. The framework gives you permission to change your mind based on evidence, not sunk cost.

The bias toward action matters too. You don't theorize for weeks. You prototype something rough within hours and test it. "Build to think" is the phrase the d.school uses. You learn faster by making something bad and improving it than by trying to get it perfect in your head first.

How I Apply This

I didn't learn Design Thinking from a textbook. I learned it by teaching it.

Between 2023 and 2024, our UIF team ran workshops at VVIT, R.K. College of Engineering, and PVP Siddhartha College of Engineering, adapting the d.school's five-stage process for different audiences, from first-year undergrads to graduate students. When you're standing in front of 200 students walking them through empathy mapping and "How Might We" framing, you internalize it in a way that reading about it never achieves.

That experience rewired how I approach engineering. Every project now starts the same way those workshops started: who is this for, and what problem are they actually facing?

With Offline Notebook LM, the empathize stage showed that users don't want "a RAG app." They want to ask a question about their own documents and get a trustworthy answer, without anything leaving their machine. That reframing shaped every architecture decision: local-first processing, no cloud dependency, multi-format ingestion. The technology choices followed the problem, not the other way around.

We also trained student facilitators to run the workshops independently, which is its own lesson in prototyping and iteration, except the "product" is a teaching experience.

Resources

Design Thinking as described here follows the five-stage model developed by the Hasso Plattner Institute of Design at Stanford (d.school). Credit for the methodology belongs to the d.school, IDEO, and the broader design thinking community.