On Saturday, August 2nd, 2008 at 2:12 am Tartle wrote:
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?”
On Saturday, August 2nd, 2008 at 10:33 am Philip Haine wrote:
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?
[...] 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 [...]
[...] 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 [...]
[...] 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 [...]
On Saturday, August 2nd, 2008 at 2:12 am Tartle wrote:
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?”
On Saturday, August 2nd, 2008 at 10:33 am Philip Haine wrote:
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?
On Wednesday, October 1st, 2008 at 2:13 pm Picking a frame: Activities vs. Goals vs. Needs | Product Vision blog wrote:
[...] also: Design Pyramid | SSNiF [...]
On Tuesday, October 21st, 2008 at 11:37 am When Product Vision Goes Right | Product Vision blog wrote:
[...] 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 [...]
On Saturday, August 22nd, 2009 at 6:42 pm Formal Needs Analysis Part 2: Differentiating Based on Needs | The Product Vision blog wrote:
[...] 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 [...]
On Wednesday, September 2nd, 2009 at 12:36 am Quote: Philip Haine at Sushi & Robots, by Jina Bolton wrote:
[...] – Philip Haine [...]
On Monday, March 22nd, 2010 at 8:13 am Alyssa wrote:
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
On Thursday, June 3rd, 2010 at 11:48 am Iceberg analogy to design thought | The Product Vision blog wrote:
[...] 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 [...]