

Communicating and trust building between the designer and stakeholders is crucial for bringing great value to the digital product. If you have it, impossible becomes possible. I'd like to discuss how to maintain the awesome relationship between designer and stakeholder(s), as well as share the most important rules of thumb on research, formulating hypotheses, interviewing people, and validating your design decisions while building agreements between the two parties along the way.
Watch this WaysConf session, then continue with related talks or explore the current programme.
A detailed playbook for improving stakeholder relationships by connecting design decisions to outcomes, evidence, and explicit agreement. The talk starts with opportunity-solution trees: define the effect the team wants, collect user and business opportunities continuously, and test several responses instead of defending the first idea. It then addresses opinion-driven conflict. Designers cannot remove subjectivity or organizational hierarchy, but they can bring new information, tailor communication to each stakeholder group, co-create with influential partners, and make meetings easier to follow. Effective critique asks how a proposal affects the intended outcome, uses realistic data, keeps alternatives ready, and closes with a clear decision rather than leaving acceptance ambiguous.
A measurable effect gives research, opportunities, solutions, and experiments a shared direction beyond shipping output.
Watch from 9:31Interviews, observation, analytics, tests, and team ideas reveal needs without asking customers to prescribe the product.
Watch from 13:54Designers may not own the final decision, but they can improve it by introducing user evidence, metrics, and tested alternatives.
Watch from 21:05High-interest, high-influence partners deserve close co-creation, while other groups need communication proportional to their role.
Watch from 28:26A response should connect problem, solution, user, and business value, then confirm the decision needed to move forward.
Watch from 43:00Four product-design mindsets shift attention toward outcomes, experiments, visual explanation, and continuous discovery.
An opportunity-solution tree connects research findings with candidate solutions and testable experiments.
Behavioral questions expose underlying goals that customers may not be able to express as product ideas.
Product data and usability results help teams decide which assumptions deserve attention.
The designer’s leverage comes from improving the information available to decision-makers.
Business, engineering, and product partners need different forms of context, support, and involvement.
Meeting structure, project phase, realistic data, and specific questions shape the quality of feedback.
A final formula identifies the problem, describes the solution, recalls the user, appeals to business value, and locks agreement.
These concise notes were edited from automatic captions and checked against the talk structure. They are not a verbatim transcript.
A team should begin with the effect it wants to create, not the interface it expects to ship. Research then supplies opportunities: needs, friction, and context that may contribute to that outcome. Several solutions can sit beneath an opportunity, and each can be treated as an experiment. This structure keeps discovery connected to value while preventing one early concept from becoming the project by default.
Watch from 9:31An interview is not a request for the participant to design the product. Instead of asking which qualities matter when buying shoes, ask about the last purchase and what happened step by step. Concrete behavior exposes constraints, compromises, and goals. Researchers can interpret those observations as opportunities without pretending that a direct feature request is the only valid form of customer knowledge.
Watch from 13:54A designer may care deeply about a proposal and still lose a subjective argument to someone with greater authority. The useful response is not to fight for personal ownership at any cost. Bring research, metrics, usability results, or a tested comparison that the decision-maker did not have before. The final authority may remain elsewhere, but the organization can now make the choice with better information.
Watch from 21:05Questions such as whether someone likes a design invite taste and place the designer in search of approval. Ask how the proposal would work in the stakeholder’s context, what it changes for the agreed outcome, or why an alternative might perform better. Keep explored alternatives ready so recurring suggestions can be answered with evidence instead of beginning the same debate again.
Watch from 34:05A persuasive design response first restates the problem, explains how the proposal addresses it, recalls the people affected, and connects the change to business value. That sequence is incomplete until the group confirms what has been decided. Even a simple request for agreement prevents the meeting from ending with several private interpretations and gives the project a clear next step.
Watch from 42:00