# Six hours of design thinking that stop you building the wrong thing

> Jeanne Liedtka's Darden course on Coursera is built on four questions worth asking a client before you write a line of code.

Original: https://fdetimes.net/en/books-courses/design-thinking-course-before-discovery/

An engagement can fail even when the code runs perfectly: all it takes is for the team to build what the client *says* rather than what the client *needs*. A course of about six hours on Coursera gives you a set of questions to head off that mistake from the very first meeting.

The course is Design Thinking for Innovation, from the Darden School of Business at the University of Virginia, part of the Leading the Modern Day Business specialisation.

The specialisation's name sounds aimed at business people, but the course page insists that anyone, at any level and in any organisation, can use design thinking to come up with new ways of working.

For FDEs that is good news: you already know how to build systems. What is often missing is the way of asking that tells you what to build.

## Who teaches it, and why trust her?

Jeanne M. Liedtka is a professor emerita at Darden and a former chief learning officer at United Technologies Corporation. At Darden she has worked with MBA students and senior executives alike on design thinking, innovation and leading growth.

Notably, she has also written books on the subject. The classic is *Designing for Growth: A Design Thinking Tool Kit for Managers*, co-written with Tim Ogilvie and published by Columbia University Press in June 2011. Her most recent is *Experiencing Design: The Innovator's Journey*, co-written with Karen Hold and Jessica Eldridge.

## Four questions form the spine of the course

The course is built around a four-question model: what is?, what if?, what wows?, what works?. Each module teaches one tool: Visualization, Storytelling, Mind Mapping and Learning Launch.

Take the model into a familiar situation. Imagine a logistics company asks you to build an agent that reads supplier invoices. The engineer's instinct is to ask straight away about PDF formats and which model to use.

Liedtka's model forces you to stop at what is? first: who reads the invoices today, how long it takes each week, where the errors occur, and who has to fix them when they do.

You might discover that the bottleneck is not reading at all, but matching invoices against purchase orders. At that point what if? opens up options quite different from the original request.

The remaining two questions, read as an FDE would apply them, can serve as two filters. What wows? is the moment to ask which option end users would genuinely want to use; what works? is the moment to pull the group back to a small, measurable trial rather than a large project.

**Key point:** The first question on a client's site is not "what should we build?" but "how does it work today?"

## Three ideas worth keeping after six hours

The first is the discipline of what is?. This question is almost identical to customer discovery. If you apply only one thing, spend the opening of every meeting describing the current state without proposing any solution. Clients usually feel better heard, and you get real data to work with.

The second is Visualization and Storytelling as engineering tools. FDEs tend to persuade with system architecture; clients are persuaded by a story about a specific user on a specific day.

A whiteboard sketch of the current process, paired with a story such as "the accountant opening her 40th invoice of the day", often clarifies scope faster than a long requirements document.

The third is an FDE reading of Learning Launch and the what works? question: treat the first trial as a way to learn, not to prove yourself right. The concrete advice is to write down before the pilot what would make you change course. When the numbers come in, the conversation with the client will be about lessons, not failure.

## Who should take it, and in what order?

The course is Beginner level, so it suits engineers with two to four years' experience who are about to face a client for the first time, or software engineers moving into FDE work with no client-facing background. If you have done solutions engineering or consulting for years, most of it will be familiar; skimming it for the shared vocabulary is enough.

The sensible order is to take the course first, then read *Designing for Growth* when you want to go deeper. The publisher describes the book as teaching design thinking as the ability to turn abstract ideas into practical applications for business growth, so it sinks in more easily once the four-question framework is already in your head.

The final assignment asks you to choose a tool, write a reflection and peer-review three other learners' submissions; you must pass it to complete the course. Do not just go through the motions.

Imagine you are about to build an internal document search assistant for a customer support team. After five interviews, instead of a page of messy notes, you use Mind Mapping to group the complaints into clusters: finding the wrong document, outdated documents, not knowing whom to ask.

From there, a short story such as "the night-shift agent spent 15 minutes looking for the returns policy" is enough for both sides to agree which cluster to tackle first. That is exactly the kind of real experience worth bringing into the reflection.

Use the tool with a real client or internal team, then turn the reflection into a line on your CV: which discovery session, which tool, and how the project's scope changed.

When applying for FDE roles, put that concrete example ahead of the certificate line, because it shows the reader you know how to ask before you build.

Six hours will not make you a designer. But it is enough that the next time a client says "we need an agent", your first question back is "who does that work today?"

**Try this week:**

- Take the overview module on the four questions, then rewrite the notes from your latest client meeting under four headings: what is?, what if?, what wows?, what works?
- In your next discovery session, spend the first 20 minutes on what is? alone: propose no solutions, just redraw the client's current process
- Pick one tool from the course, use it with a real client and write a one-page reflection, as the final assignment requires

## Sources

- [Design Thinking for Innovation (Coursera, University of Virginia)](https://www.coursera.org/learn/uva-darden-design-thinking-innovation)

- [Jeanne M. Liedtka — Darden School of Business faculty profile](https://www.darden.virginia.edu/faculty-research/directory/jeanne-m-liedtka)

- [Designing for Growth — Columbia University Press](https://cup.columbia.edu/book/designing-for-growth/9780231158381/)
