Synthesizing feedback and managing design changes
How to turn test feedback into managed design changes: synthesize patterns without losing one-off insights, keep facilitator bias out, write user stories with accessibility in the acceptance criteria and definition of done, respond to change the agile way, pick the right sandbox, and tell the findings as a story stakeholders act on.
Given a scenario, evaluate and manage design changes.
~6 min read · 9 practice questions ·
What the exam expects
- Synthesize test feedback: weight repeated patterns, keep one-off insights, and know when a finding sends the team back to research or ideation.
- Keep facilitator bias out of test sessions.
- Write a design change as a complete user story, and put accessibility and usability in acceptance criteria and the definition of done.
- Cite the agile values when a test result should change the plan.
- Choose the sandbox for UAT (Partial Copy) and for performance or load testing (Full), and set up continuous feedback after launch.
- Present findings as a story that pulls stakeholders' levers.
Key terms: synthesis (clustering raw feedback into themes); definition of done (everything a team must do before work is truly done); user story ("As a < who >, I want < what > so that < why >"); sandbox template (controls which records a Partial Copy or Full sandbox gets); levers (stakeholder motivations such as saving money or reducing work).
Key facts
- Detail
- Trustworthy guides; frequency shows importance
- Detail
- Go back to research or ideation
- Detail
- As a < who >, I want < what > so that < why >
- Detail
- Component specs, acceptance criteria, user stories
- Detail
- Everything required before work is truly done
- Detail
- Responding to change over following a plan
- Detail
- Metadata plus template-defined sample; UAT
- Detail
- All data; only type for performance, load, staging
- Detail
- Submission process plus periodic pilot check-ins
Sources for this section (7)
- Create a Prototyping Plantrailhead.salesforce.com (opens in a new tab)
- Learn About User Storiestrailhead.salesforce.com (opens in a new tab)
- Test for Accessibilitytrailhead.salesforce.com (opens in a new tab)
- Understand Why Salesforce Adopted Agiletrailhead.salesforce.com (opens in a new tab)
- Learn the Basics of Agiletrailhead.salesforce.com (opens in a new tab)
- Sandbox Types and Templateshelp.salesforce.com (opens in a new tab)
- Drive Long-Term Adoptiontrailhead.salesforce.com (opens in a new tab)
- Why keep a comment only one participant made?
- When should a team go back to research or ideation after prototype testing?
- Which sandbox gives UAT testers a realistic sample of production records without copying everything?
- Why does a shared definition of done stop "finished" work from resurfacing?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Platform User Experience Designer pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 22 lessons of the Platform User Experience Designer guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Inline practice questions and one-click topic practice (9 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams