What you own, influence, and observe
Design Thinking is a team process. The PM's role is specific and different from the designer's role. Knowing the boundary prevents conflict and prevents gaps.
Own
You make the decision
•The research brief: what questions the team needs to answer
•The go/no-go decision: is there sufficient empathy to move to Define?
•Writing and signing off the problem statement
•Problem sizing: frequency × severity × user count
•Assumption mapping and deciding what to test first
•Applying the strategic filter in Ideate: viability and north star alignment
•Prototype type selection and the Build vs. Buy vs. Partner decision
•Writing test success criteria before any session begins
•The Pivot / Persevere / Stop call after testing
Influence
Your input shapes the decision
•Research methods selected by the UX researcher
•Participant recruitment criteria and user segment definition
•Ideation technique chosen for the brainstorm session
•Prototype fidelity and visual execution
•How test findings are synthesised and presented
•Sprint allocation and timeline for discovery work
Observe
Not your call, but you need visibility
•How individual user interviews are conducted and facilitated
•Specific visual and interaction design execution
•Technical feasibility assessments by engineering
•UX writing and microcopy choices
•Specific usability test session facilitation
•Accessibility compliance review by design
PM vs. Designer - Where the Boundary Sits
The PM Owns
The what and the why. The problem statement. The decision to proceed or stop. The strategic filter. The business case for solving the problem at all. The success criteria that determine whether the test worked.
The Designer Owns
The how of the research and prototype. Interview facilitation technique. Prototype execution and visual quality. The craft of turning the PM's problem statement into a testable artefact. UX quality decisions throughout.