Project Design Principles
Written statements, generally in the form of imperatives like “Earn people’s trust,” that serve as guiding lights during decision-making. Good design principles are specific to the project, not general truths, and should help teams say “no” to otherwise interesting proposals or generate ideas when they’re stuck.
When to Use
- To guide decision making later in the design process.
- Using internal documents and kickoff activities, gather terms or concepts that seem significant to project goals and organizational culture.
- Using existing research, list terms or concepts that seem particularly important to customers or user groups.
- Cluster similar terms and concepts together on a whiteboard or other writing space open to everyone in the project. Name the clusters.
- Ask the team and stakeholders if they would like to add, change, or edit any concepts or groups.
- From the groups on the board, create three to five final principles. Using evidence from partner or user research, write one to two sentences in support of each principle.
- Share the principles in a place accessible to the team throughout the project, and refer to them often while making decisions.
Created by: Joe Steinkamp | Last updated by: Joe Steinkamp