Comments on: The Design Pyramid

By: Zhou Maojie

Zhou Maojie — Thu, 04 Aug 2011 00:19:11 +0000

I would suggest revise the order.

Top layer: Knowledge and understanding
Vision and strategy for your product
Concept design and roadmap reflect your vision
Detail design specification

By: Iceberg analogy to design thought | The Product Vision blog

Iceberg analogy to design thought | The Product Vision blog — Thu, 03 Jun 2010 18:48:11 +0000

[...] described the Design layer of the Design Pyramid as being the visible tip of the iceberg. These folks used the same analogy to describe Design [...]

By: Alyssa

Alyssa — Mon, 22 Mar 2010 15:13:45 +0000

eww there is not even a pyramid there is just a thing explaining what you need to do frist befor you make it now how you do

By: Quote: Philip Haine at Sushi & Robots, by Jina Bolton

Quote: Philip Haine at Sushi & Robots, by Jina Bolton — Wed, 02 Sep 2009 07:36:53 +0000

[...] – Philip Haine [...]

By: Formal Needs Analysis Part 2: Differentiating Based on Needs | The Product Vision blog

Sun, 23 Aug 2009 01:42:27 +0000

[...] us mastery over the competitive field. This is part of the Understanding level at the base of the Design Pyramid. You cannot go through the needs exercise without gaining clarity on your personal or your [...]

By: When Product Vision Goes Right | Product Vision blog

When Product Vision Goes Right | Product Vision blog — Tue, 21 Oct 2008 18:37:54 +0000

[...] that competitors leave behind. (These are key elements of the Understanding layer of the Design Pyramid.) This insight leads to great product visions. Important unmet customer needs are addressed far [...]

By: Picking a frame: Activities vs. Goals vs. Needs | Product Vision blog

Picking a frame: Activities vs. Goals vs. Needs | Product Vision blog — Wed, 01 Oct 2008 21:13:22 +0000

[...] also: Design Pyramid | SSNiF [...]

By: Philip Haine

Philip Haine — Sat, 02 Aug 2008 17:33:40 +0000

Thanks for the thoughts, Tartle… here is how I paraphrase it:

- Uncertainties over what to do lead to indecision and therefore lack of “boldness” on the vision and therefore mediocre products.

- The “old guard” tends to use outdated criteria to judge ideas

- Involve the product team in defining the vision to re-invigorate everyone

- Define the vision in terms of user needs. This is starting with the end in mind, rather than defining the next product relative to where we are now.

- If the team drifts back towards incrementalism, offer the reality check question: is this bold enough to fulfill our vision?

By: Tartle

Tartle — Sat, 02 Aug 2008 09:12:47 +0000

Thoughtful article:
In my view
Co-creating the Vision of how the ‘work-product’ will benefit the users seems to be the strongest ‘barrier’ to mediocre/incremental design that delivers little value (to anyone- developers, users, etc.). As people’s uncertainties press them to be less radical the vision can be used to re-invigorate the team…and challenge gatekeepers who are using yesterday’s criteria to measure tomorrows winner…we can ask “good idea but are will it be adventurous enough to achieve our vision?”