Method
A workshop to define a small set of experience principles that guide decisions, trade-offs, and quality expectations across teams.
Choose this if
This method works when defining shared design and service principles for decisions.
Pack = one session you can run now. Workspace = a saved thread for method choice, planning, and shareable outputs.
What Workspace helps you carry forward
Artifact preview
Experience principles
Align · Moderate
Decide fit before you spend session time.
The core facilitation flow, with enough structure to run the method confidently in the room.
Standard setup for Mixed in remote delivery.
Total planned time: 120 min
What happens
Review insight themes and strategic intent.
Facilitator does
Ask participants to bring two types of input: real customer feedback or observation, and examples of decisions where the team lacked a shared reference point. Without this grounding, principles become aspirational slogans. Recent real disagreements from the team's own work are the most generative starting material.
Participants do
Bring two types of input: a real customer insight, feedback quote, or observed behavior, and a recent example of a decision where the team lacked a shared reference point and diverged. Principles built without real conflict examples stay generic — the most useful input is a specific moment where the team disagreed.
Output / signal of success
Experience principles
Watch for
Principles are built from abstract values rather than from real decision conflicts the team has faced.
Recovery tip
If the evidence review produces only abstract values rather than real decision conflicts, ask: "When in the last month did the team make a design or product decision without a shared reference point?" Use that specific incident as the starting material. Principles that don't emerge from real conflicts produce slogans rather than decision rules.
What happens
Write concise principle statements and rationale.
Facilitator does
Run drafting as individual work first: each person writes one principle candidate per sticky using the format '[action verb] over [common alternative].' Collect and post all without discussion. Principle quality is judged in the stress-test step — protect generation from premature evaluation.
Participants do
Write each principle in the format "[action verb] over [common alternative]" — a statement that forces a trade-off and that a reasonable colleague could actually disagree with. If nobody would disagree with the statement, it's a value, not a principle. Bring a scenario from your own work that shows when this principle would apply.
Output / signal of success
Decision usage examples
Watch for
Principle candidates are vague statements that no one would actually disagree with.
Recovery tip
For any principle that reads as a platitude — something nobody would actively disagree with — ask: "What is the common alternative behavior this principle is arguing against?" A principle is only useful if it forces a choice. "Be clear" is not a principle. "Fewer words over complete sentences when the stakes are low" is a decision rule.
What happens
Apply principles to real decision cases.
Facilitator does
Take three real recent situations where each principle would have applied and ask: 'Would following this principle have led to a different decision?' A principle that produces no different outcome for any scenario is either too generic or already embedded in the team's behavior. Only keep principles that actually change something.
Participants do
Apply each principle to three real recent decisions from the team's own work — not hypothetical cases. For each scenario, state whether following the principle would have changed the decision, and if not, flag the principle as a candidate for removal or sharpening.
Output / signal of success
Governance owner list
Watch for
Scenarios chosen are too hypothetical to surface real tension with the principle.
Recovery tip
If the scenarios chosen are too hypothetical to surface real tension, bring in actual recent decisions from the team's work history. Ask: "Which decision from the last quarter would this principle have changed?" A principle that produces no different outcome for any real scenario is either too generic or already embedded in the team's behavior.
What happens
Select final principles and ownership model.
Facilitator does
Agree on four to six final principles, write each in a form that survives without author explanation, and name the team members responsible for applying and updating each one. Schedule a six-week review to assess which principles are being used, ignored, or misapplied.
Participants do
Accept governance responsibility only for principles you will actually apply in your area of work. A principle with a governance owner who never encounters it in practice becomes a wall poster rather than a working tool.
Output / signal of success
Experience principles
Watch for
Governance for applying principles is never assigned and they become wall posters rather than working tools.
Recovery tip
If the group can't agree on which principles to keep, use the stress-test results as the tiebreaker: the principle that produced the most different decisions in real scenarios has the highest practical value. Drop the ones that changed nothing.
Prepare the room, the evidence, and the working surface so the session can stay focused on synthesis.
A set of real, recent decisions from the team's own work where a shared principle would have been useful. Without this, the principle generation step produces abstract values rather than decision rules. Teams that can't name three recent decisions where a principle was needed probably aren't ready for this workshop — they may need more discovery work before operating principles become the right tool.
Customer insights
Optional
Brand or service values
Optional
Trade-off scenarios
Optional
Operational context note
Optional
Bring examples, pain points, or service evidence the room can point to quickly.
Remote facilitation choreography
Required
Pre-plan handoffs, breakout usage, and how people rejoin the main board.
Principle statement template
Required
Shared digital board with timer and voting
Required
Keep instructions and voting visible at all times.
Principles scorecard
Keep the output usable, then use the recovery guidance when the room starts drifting.
What this does not produce
Experience principles produce shared decision rules for the team that already has design authority. They do not produce stakeholder alignment, user insights, or a measurement plan. Teams that treat the principles as a communication tool — sharing them with stakeholders to describe their values — are using them as a brand artifact rather than a working tool.
Failure mode
Why it happens
Teams seek consensus by converging on principles that nobody objects to — which means principles that nobody actually disagrees with. "Be clear" and "put the customer first" are safe because they're universally valued. But a principle that everyone already agrees with doesn't need to exist as a principle — it produces no new decision guidance and changes no behavior.
Recover now
If this happens, for each principle candidate, ask: "Can you think of a situation where following this principle would be the harder choice?" If the answer is always "no," the principle is too safe. Replace it with the statement of what the team should choose in that harder situation.
Prevent next time
Next time, use the "[action] over [common alternative]" format introduced in Step 2 as a mandatory constraint — not a suggestion. A principle in this format forces a choice. "Fewer words over complete sentences" is a decision rule. "Be clear" is not.
Failure mode
Why it happens
The workshop produces a set of principles with genuine energy and a shared sense of completion. They get documented, shared, and posted on walls. Then the next design critique or roadmap discussion happens without any reference to them — because there's no mechanism for invoking them and no one whose job it is to do so. Principles become cultural artifacts rather than decision tools.
Recover now
If this happens, in Step 4, name the specific decision types where each principle should be invoked: "Principle 1 applies whenever copy length is being debated. Person X is responsible for raising it in those conversations." Without a specific trigger and a specific owner, the principle stays on the wall.
Prevent next time
Next time, build the governance structure into the session: for each principle, write a "when to invoke it" trigger and a "who raises it" owner before the workshop closes.
Failure mode
Why it happens
Teams want to capture all their values and add principles until the set is comprehensive. A set of 10–15 principles is too large to hold in mind during a design decision. Teams either use none of them, or use the first few and ignore the rest.
Recover now
If this happens, apply the stress-test to the full set and identify the 3–4 principles that most frequently change a decision outcome. Those are the working principles. Move the rest to a "supporting guidance" document that can be referenced but doesn't claim equal priority.
Prevent next time
Next time, set a hard cap of 4–6 principles before the session opens. Explain why: "More than six principles will be ignored in practice. We're choosing the ones that do the most decision work."
Change the shape of the session only after the fit and runbook are clear.
Standard variant for Mixed in remote delivery. Waypoint is adapting timing, facilitation emphasis, prep, and recovery guidance here, but the room still needs final tailoring to the exact stakes and participants.
Use this after you have checked the fit and know you want to carry the method forward.
The pack is the fastest way to run this now. Use the links below when you need prep, sharing, or a saved reference point.
Guides
This is the least distorting live fit because the book's core problem is how one practitioner stops being the sole carrier of quality judgment. Shared principles are the clearest live Waypoint mechanism for distributing that judgment across a low-maturity team.
Open this when you want stronger rationale before choosing the method or taking it into the workspace.
A planner-led brief on how one practitioner can use lightweight evidence, shared principles, portable artifacts, and steady coalition-building to improve decisions before a mature discovery function exists.
Sources and references used in this method page.
Nielsen Norman Group guidance on UX principles.
Facilitation approaches for alignment and shared framing.
Reviewed 2026-02-27 by Discovery Waypoint Editorial Team
Related playbooks
These pages translate recognizable external methods into Waypoint-native guidance so the team can borrow the useful part without importing the whole mythology.
