3rd
February
2003
“In the early and middle phases of a project, teams need a way to understand and explore the current direction of the design. The challenge is to create the openness needed for good ideas to surface, while simultaneously cultivating the feedback and criticism necessary to resolve open issues. Unlike a brainstorming meeting, where the exclusive goal is to come up with new ideas, a critique meeting is focused on evaluating a set of existing ideas, and possibly identify future directions or changes. Instead of hoping that hallway and email discussions will lead the team in a good direction, it’s generally worth investing time to set up critique meetings to drive the design forward.”
This entry was posted
on Monday, February 3rd, 2003 at 12:00 am and is filed under Usability.
You can follow any responses to this entry through the RSS 2.0 feed.
Both comments and pings are currently closed.
3rd
February
2003
“In the early and middle phases of a project, teams need a way to understand and explore the current direction of the design. The challenge is to create the openness needed for good ideas to surface, while simultaneously cultivating the feedback and criticism necessary to resolve open issues. Unlike a brainstorming meeting, where the exclusive goal is to come up with new ideas, a critique meeting is focused on evaluating a set of existing ideas, and possibly identify future directions or changes. Instead of hoping that hallway and email discussions will lead the team in a good direction, it’s generally worth investing time to set up critique meetings to drive the design forward.”
This entry was posted
on Monday, February 3rd, 2003 at 12:00 am and is filed under Web design.
You can follow any responses to this entry through the RSS 2.0 feed.
Both comments and pings are currently closed.
