As far as I can observe, every major design framework in circulation teaches you something that sits outside yourself. One framework offers a way to evaluate an idea, another a sequence to follow, a third a shape to give a project. None of them guide you to be a better practitioner.

DFV (Desirability, Feasibility, Viability). An evaluation framework. Gives you a way to assess whether an idea is worth pursuing: is it desirable to users, feasible to build, and viable for the business? An idea filter.
Design Thinking. A process framework. Describes a sequence of phases (Empathise, Define, Ideate, Prototype, Test) and advocates for applying them in a problem-solving context. A method for approaching problems.
The Double Diamond. A project model. Maps the diverge-converge pattern that well-run design work tends to follow: expanding the problem space before narrowing to a definition, then expanding the solution space before narrowing to a design. A map of a project’s shape.

Those three frameworks all address the work from the outside: what you produce, how you work, the shape of the project you are running. H3 addresses you, the person doing the work: who you are, how you develop across three dimensions of practice, and what you are capable of bringing to any situation, regardless of which framework you happen to use.

The distinction matters because process frameworks presuppose a capable practitioner. They do not produce one. Nigel Cross, studying expert designers across decades of research, found that what separates expert from novice is depth of internalised capability. Experts perceive a design situation accurately and respond to what they see rather than to what the process step requires.¹

Now imagine a designer who learns Design Thinking but has not developed the judgement to know when a phase has run long enough, when the synthesis is premature, when the brief itself describes the wrong problem. That designer will apply the process correctly and still end with the wrong solution. The process was sound, but it could not supply what the practitioner lacked.

Learn

IDEO, Design Thinking overview. The process framework and what it is built to do.
Design Council, Framework for Innovation: The Double Diamond. The original source.
Stanford d.school, “Let’s Stop Talking About the Design Process”. The abilities-over-process argument, made from inside design education.

Do

Write down the framework your team currently defaults to. Write one sentence on what it helps you evaluate, and one on what it cannot tell you about your own development.

Check

Does the framework you use help you identify your own gaps as a practitioner, or only evaluate the work?

1. Nigel Cross, Designerly Ways of Knowing, Birkhäuser, 2007. Chapter 6, “Design Expertise.” Cross draws on protocol studies across novice and expert designers. Expert designers work solution-focused rather than problem-focused. They generate a solution hypothesis early and use it to interrogate the problem, rather than following a structured analytical sequence. This form of internalised judgement is what process frameworks presuppose but cannot teach. ↩

More Than Methodhow H3 differs from the frameworks you already know