Leveraging Adjacent Roles/Skills19% of the exam
Design and build collaboration across roles
How a strategy designer keeps design and build work pulling the same way: giving builders the vision's context, tailoring and starting early, knowing which stakeholder owns which question, unsticking decisions with outcomes, accessibility duties by role, whole-team prototype testing, and the agile and lean habits that keep sub-teams out of vacuums.
Given a scenario of disparate business and technical deliverables within a design/build team, facilitate productive collaboration.
~7 min read · 14 practice questions ·
What the exam expects
- Give developers and other builders the vision's context and listen to their constraints instead of handing over instructions.
- Tailor what each audience hears, share work early, and pick the stakeholder group that owns an open question.
- Move a stuck design/build decision forward by orienting around outcomes, and win over quiet critics one-on-one.
- Assign accessibility responsibilities to the right roles (product, design, front-end development, program management, testing).
- Run prototype sessions and synthesis as a whole team, and correct the belief that agile means no planning, using the lean principles.
- Key terms: key stakeholders (internal people directly affected by the outcome who actively contribute); orient around outcomes (start with value, not tactics); listening roles (team members assigned to hear feedback through their discipline's lens); post-test processing (when and how the team synthesizes insights and decides what to act on); lean principles (Salesforce's seven values taken from Lean Software Development).
Key facts
Developers want
- Detail
- What the product does and why, how features benefit the customer
Executives want
- Detail
- High-level results and outcomes for the company
Building trust
- Detail
- 1:1 conversations elicit candid perspectives
Measurement owner
- Detail
- Data and analytics stakeholders
Release priority for accessibility
- Detail
- Product managers
Time to fix and retest accessibility
- Detail
- Program managers
Listening roles
- Detail
- Each discipline hears different implications
Agile planning cadence
- Detail
- Yearly, release, increment and daily
Lean values
- Detail
- Seven, from Lean Software Development
Sources for this section (5)
- Get Stakeholders Alignedtrailhead.salesforce.com (opens in a new tab)
- Champion Accessibility at Your Companytrailhead.salesforce.com (opens in a new tab)
- Create a Prototyping Plantrailhead.salesforce.com (opens in a new tab)
- Learn the Basics of Agiletrailhead.salesforce.com (opens in a new tab)
- Learn to Use Lean Principlestrailhead.salesforce.com (opens in a new tab)
- Why did Cloud Kicks' CEO overrule the team's decision to postpone delivery tracking?
- Why can a larger group watching one low-fidelity prototype give weaker feedback?
- What did Salesforce create to eliminate waste before work starts?
- Which basic issues should testers and quality engineers know how to test for?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Platform Strategy Designer pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 17 lessons of the Platform Strategy Designer guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Practice exams purchase adds inline bank questions and topic practice (14 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Choose guide-only, practice-only, or save $4 with both