Managing a Design Process: Discovery, Stakeholders and Testing
A design project succeeds or stalls less on the interface itself than on how decisions are made around it. In a 35-minute conversation, UX expert Paul Boag and host Brett Harned explain why the project manager often has the greatest influence over the eventual user experience, and how to use that influence without becoming a bottleneck.
Why the project manager shapes the experience
Digital work is different because information is plentiful and the materials needed to build a prototype or test an idea cost little. That makes change relatively inexpensive, but it also means a project can drift if nobody sets direction. Boag compares the digital project manager to a conductor: the manager may not play every instrument, yet the coordination, pacing and shared understanding shape the whole performance. In practice, that coordination can affect the user experience more directly than a single interface decision.
Start with a short, focused discovery phase
Boag recommends a discovery phase for every project, however small. Even a two-hour session should produce a prioritised set of goals, measurable KPIs, user research, a clear picture of the audiences involved and an understanding of the competitive context. The point is not paperwork for its own sake. It is to agree, before design begins, what success looks like and whose needs take priority when trade-offs appear.
Learn stakeholders one at a time
Group meetings often surface disagreement before anyone understands its roots. Meeting each stakeholder individually first lets the project manager learn what each person values, what concerns they hold and how they prefer to be persuaded. When the group later meets, the manager can connect the proposal to each person's priorities rather than presenting one generic argument. Boag also advises anticipating familiar objections in advance, so stakeholders can support the direction without feeling their concerns were ignored.
Separate problems from solutions
Roles need to be explicit before feedback starts. The client or stakeholder describes the problem and its context; the designer is responsible for proposing solutions. When that boundary blurs, feedback turns into competing design opinions and the project manager is left refereeing taste. Keeping the distinction clear does not dismiss stakeholder input. It directs that input toward the problem, where it is most useful, and leaves solution choices to the people accountable for them.
Test instead of debating
Because digital decisions can usually be revised, prolonged argument is rarely the fastest route to confidence. Boag's alternative is to test with real users: evidence from use settles questions that a long internal debate cannot. A practical checklist for the project manager is to confirm the discovery goals and KPIs, map each stakeholder's priorities, agree who owns problems and who owns solutions, and replace unresolved disputes with a defined test and a date to review the results.
What else the conversation covers
The episode also covers the difference between a general project manager and a digital project manager, how digital projects operate, how to run discoveries, how project managers can extend their role, and how to manage the parts of the design process and stakeholder feedback. Resources mentioned include Paul Boag's Digital PM Master Class and Jared Spool's article on convincing executives to invest in UX.