Ensure design quality and user validation

You validate direction early, surface design risks, and make sure shipped features solve real user problems. This guide takes you from a feature Brief to a scoped design or research plan that keeps you ahead of the build.

Who this doc is for

You're a designer or researcher who wants to catch the expensive problems early — the wrong direction, the untested assumption, the surface no one validated. You want your research and design thinking linked to the work so it shapes the build instead of arriving after it. Start by reading the Brief and deciding whether design is on the critical path.

Pre-flight checklist

Before you start:

• Understand the user problem. Read the Brief before you open a design tool.
• Know what research or validation you already have to draw on.
• Connect Figma so Hamster references your real designs when it drafts and refines Briefs.
• Understand the timeline and whether design is on the critical path for this feature.

Your first week

A concrete path from a feature Brief to a scoped design effort:

1. Review the Brief. Assess whether design exploration is needed, or whether you can iterate in parallel with engineering.
2. If exploration is needed, create a design Brief or research plan that captures the scope.
3. Plan your research or design-review touchpoints. You're done when eng and the PM know what design is doing and when they'll see it.

Post-creation next steps

Once you've scoped your work:

1. If design exploration is needed, create a research Brief or design Brief and set a timeline.
2. If design can iterate in parallel, work with engineering so you have early visibility into the feature as it takes shape.
3. Conduct the user research, usability testing, or design review your design risk calls for.
4. Flag design risks or scope changes to the PM and eng early, while they're cheap to absorb.
5. Link your research, wireframes, or design specs to the main Brief so your thinking travels with the work.
6. Review final designs with engineering before handoff.

Feature depth

Go deeper on the artifacts a designer or researcher leans on most:

• Briefs — scoping design or research work so it has clear boundaries.
• Plans — identifying whether design is on the critical path.
• Blueprints — the product and user context (personas, strategy, ways of working) that grounds your design decisions.
• Context Documents — attaching wireframes, findings, and Figma files so your thinking grounds the Brief.
• Figma — referencing real designs when writing and refining Briefs.
• Goals — connecting the validation you're doing to the outcome the feature is meant to move.

Sample first-week workflow

1. Monday: review the feature Brief; assess design risk.
2. Tuesday: create the research or design scope if it's needed.
3. Wednesday: begin user research or design exploration.
4. Thursday: share early findings with the PM and eng.
5. Friday: iterate based on feedback; set the next checkpoint.

Common pitfalls

"Is design on the critical path for this feature?" It depends on novelty. Outline it in the design Brief and sync with eng on the timeline so no one's blocked waiting on the other.

"I found a design issue late. How do I surface it?" Comment in Hamster and schedule a sync. If it's big, update the Brief or create a follow-up Brief so the change is on the record.