Identify tensions between business requirements and user friction during the Define phase. Generate dual-side solutions that satisfy both stakeholders and users. Facilitate balanced discussions to prioritize features without compromising user experience.
Learning Objective: By the end of this lesson, learners will be able to resolve conflicts between business goals and user needs by generating dual-side solutions and facilitating balanced stakeholder discussions.
Conflicts typically surface when you consolidate business requirements and transition from the Define phase into the Design phase of your project. You need to actively note any requirements that might clash with user needs, especially those demanding personal data like email addresses. These requests often create significant user friction because people resent the time spent filling out forms or worry about privacy. They may also feel interrupted from the larger task they are trying to accomplish at that very moment.
Treat these potential conflicts as excellent topics for exploration during your user research phase to dig down to the roots of needs. By identifying these tensions early, you can prevent them from becoming costly problems later in the product design process. This proactive approach allows you to understand the underlying motivations behind both business goals and user behaviors before committing to specific features.
Key Points:
Conflicts arise during the consolidation of business requirements and the transition from Define to Design phases.
Actively note requirements that may conflict with user needs, such as gathering personal information (email addresses) causing user friction.
User friction stems from time required to fill forms, security/privacy concerns, or interruption of larger tasks.
Treat these potential conflicts as excellent topics for exploration during user research to dig down to roots of needs.
You take those identified conflicts and use them to generate ideas that satisfy both business and user sides simultaneously. It’s about finding the overlap where a single feature can serve two masters without compromising either goal. Consider the tension between capturing email addresses for marketing and the user friction caused by intrusive data capture forms. Instead of forcing a direct form, you might suggest a “send to a Friend” feature as a hybrid solution. This approach captures the necessary email address for the business while providing genuine convenience and value to the user. You then capture these innovative ideas as requirements to be put in the mix for prioritization. These solutions live in that crucial overlapping area between the Define and Design phases, bridging the gap. When you reframe conflicts this way, you turn potential dead ends into opportunities for better product design. This sets the stage for handling those stubborn disagreements that don’t resolve so easily.
Key Points:
Use identified conflicts to generate ideas that satisfy both business and user sides simultaneously.
Example: Instead of a direct data capture form, suggest a 'send to a Friend' feature.
This hybrid solution captures the email address (business need) while providing convenience to the user (user need).
Capture these ideas as requirements to be put in the mix for prioritization, living in the overlapping area between Define and Design.
When you hit a wall and a conflict remains stubbornly unresolved, you execute a specific three-step recovery process to break the deadlock. First, review the overall goals and objectives of the initiative to realign the team on the primary success metrics that truly matter. This step prevents getting lost in minor tactical disagreements while losing sight of the strategic vision driving the project forward. Second, represent the most actionable user insights available, or suggest specific ways to gain missing insights if your current data is lacking. You fill the evidence gap by proposing targeted research methods, which grounds the debate in reality rather than speculation. Third, ensure there is a balance in the viewpoints being considered, actively preventing either the business or user perspective from dominating the conversation. This deliberate equilibrium maintains good tension and keeps the discussion productive, setting the stage for facilitating balanced stakeholder discussions.
Key Points:
When conflicts are not easily resolved, execute three specific actions: review overall goals, represent actionable insights, ensure viewpoint balance.
Review the overall goals and objectives of the initiative to align on primary success metrics.
Represent the most actionable user insights available, or suggest specific ways to gain missing insights if data is lacking.
Ensure there is a balance in the viewpoints being considered, avoiding dominance by either business or user perspectives.
To facilitate balanced discussions, you must first assemble a team that includes a persona representing the business viewpoint, such as a stakeholder or analyst. This ensures the business perspective is present alongside user personas. You then tell the team the purpose is to understand features needed to meet both needs and focus future design efforts. This clarity aligns everyone on the primary success metrics.
Next, present the answers to relevant questions and the list of scenarios you have prepared. Encourage the team to switch perspectives and consider both user and business needs as much as possible during the discussion. This deliberate shifting maintains good tension, preventing the group from settling into a single, biased viewpoint. It forces a deeper examination of the trade-offs.
When requirements represent larger efforts, prioritize them independently to avoid skewing the broader assessment. For instance, separate GPS-related requirements from other features to evaluate their impact accurately. This separation allows for clearer decision-making without conflating distinct technical challenges. You are now ready to navigate common pitfalls.
Key Points:
Assemble a team including a persona representing the business viewpoint (e.g., business stakeholder or analyst).
State the purpose: understand features needed to meet both needs and focus future design efforts.
Encourage the team to switch perspectives and consider both user and business needs to maintain 'good tension'.
Prioritize requirements independently if they represent larger efforts, such as separating GPS-related requirements.
Strong execution means you actively avoid three specific pitfalls that derail the process. First, failing to balance viewpoints creates blind spots, so ensure a business viewpoint persona is present alongside user personas. This maintains good tension by forcing the team to switch perspectives during discussions. Second, conflicts often remain unresolved due to a lack of data, which stalls progress. To recover, represent the most actionable user insights available or propose specific methods to gain those missing insights. Third, treating conflicts as dead ends kills innovation. Instead, reframe conflicts as opportunities for hybrid solutions, like the send to a Friend feature. Finally, manage separate conflicts related to new technologies where development teams may be uncomfortable making estimates. By applying these recoveries, you resolve conflicts between business goals and user needs effectively. You now have the tools to facilitate balanced stakeholder discussions and generate dual-side solutions. When you next face a tension between data collection and privacy concerns, remember to look for the hybrid opportunity.
Key Points:
Pitfall: Failing to balance viewpoints. Recovery: Ensure a business viewpoint persona is present alongside user personas.
Pitfall: Conflicts remain unresolved due to lack of data. Recovery: Propose specific methods to gain missing insights.
Pitfall: Treating conflicts as dead ends. Recovery: Reframe conflicts as opportunities for hybrid solutions.
Manage separate conflicts related to new technologies where development teams may be uncomfortable making estimates.