Next: End of case studies←→
Next: End of case studies←→
Next: End of case studies←→
Next: End of case studies←→
Next: End of case studies←→
Next: End of case studies←→
Next: End of case studies←→
Next: End of case studies←→
Next: End of case studies←→
Next: End of case studies←→
Next: End of case studies←→
Next: End of case studies←→
Next: End of case studies←→
Next: End of case studies←→
Next: End of case studies←→
Next: End of case studies←→
Next: End of case studies←→
Next: End of case studies←→
Next: End of case studies←→
Next: End of case studies←→
Next: End of case studies←→
Next: End of case studies←→

Insight Bridge: Roadmap Prioritization

PROJECT TYPE

2024 ELVTR independent concept

Role

Product ideation, AI technical flow mapping, wireframes, UX flows, and the stakeholder pitch

WHAT I OWNED

Product ideation · AI technical flow mapping · Wireframes · UX flows · Stakeholder pitch

← PrevCase 01 of 00Next →
← PrevCase 01 of 00Next →
← PrevCase 01 of 00Next →
← PrevCase 01 of 00Next →
← PrevCase 01 of 00Next →
← PrevCase 01 of 00Next →
← PrevCase 01 of 00Next →
← PrevCase 01 of 00Next →
← PrevCase 01 of 00Next →
← PrevCase 01 of 00Next →
← PrevCase 01 of 00Next →
← PrevCase 01 of 00Next →
← PrevCase 01 of 00Next →
← PrevCase 01 of 00Next →
← PrevCase 01 of 00Next →
← PrevCase 01 of 00Next →
← PrevCase 01 of 00Next →
← PrevCase 01 of 00Next →
← PrevCase 01 of 00Next →
← PrevCase 01 of 00Next →
← PrevCase 01 of 00Next →
← PrevCase 01 of 00Next →

Insight Bridge: Roadmap Prioritization

MY ROLE

AI Design, Ideation

STATUS

Concept · illustrative data

← PrevCase 01 of 00Next →
← PrevCase 01 of 00Next →
← PrevCase 01 of 00Next →
← PrevCase 01 of 00Next →
← PrevCase 01 of 00Next →
← PrevCase 01 of 00Next →
← PrevCase 01 of 00Next →
← PrevCase 01 of 00Next →
← PrevCase 01 of 00Next →
← PrevCase 01 of 00Next →
← PrevCase 01 of 00Next →
← PrevCase 01 of 00Next →
← PrevCase 01 of 00Next →
← PrevCase 01 of 00Next →
← PrevCase 01 of 00Next →
← PrevCase 01 of 00Next →
← PrevCase 01 of 00Next →
← PrevCase 01 of 00Next →
← PrevCase 01 of 00Next →
← PrevCase 01 of 00Next →
← PrevCase 01 of 00Next →
← PrevCase 01 of 00Next →

Insight Bridge: Roadmap Prioritization

PROJECT TYPE

2024 ELVTR independent concept

Role

Product ideation, AI technical flow mapping, wireframes, UX flows, and the stakeholder pitch

WHAT I OWNED

Product ideation · AI technical flow mapping · Wireframes · UX flows · Stakeholder pitch

Overview

What to work on, why and when

Problem

Product teams struggle to quickly prioritize UX issues, often missing improvement opportunities while sifting through diverse data sources.

Objectives

Designed an AI-driven app to quickly identify product improvement opportunities

  • Turned omnichannel user feedback into an actionable product roadmap

  • Created a real-world AI technical architecture map

  • Developed wireframes and UX flows for core features

Audience

UX & Growth Designers.

  • Product Managers & Product Owners

  • Growth Engineers & Engineers.

  • Researchers

Overview

What to work on, why and when

Problem

Product teams struggle to quickly prioritize UX issues, often missing improvement opportunities while sifting through diverse data sources.

Objectives

Designed an AI-driven app to quickly identify product improvement opportunities

  • Turned omnichannel user feedback into an actionable product roadmap

  • Created a real-world AI technical architecture map

  • Developed wireframes and UX flows for core features

Audience

UX & Growth Designers.

  • Product Managers & Product Owners

  • Growth Engineers & Engineers.

  • Researchers

Status Quo

Manual Workflow

  1. Support: Flags rising onboarding tickets through Slack or vague Jira issues.

  2. Product: Investigates separately, without clear churn or revenue impact.

  3. UX: Lacks drop-off context, leading to guesswork and duplicated effort.

  4. Engineering: Receives incomplete bug reports, delaying investigation.

  5. Cross-functional teams: Struggle to align priorities, stalling decisions.

  6. Leadership: Lacks evidence to confidently prioritize roadmap investments.

Result: Slow, fragmented, lots of handoffs without clarity.

The idea

Proposed concept workflow

  1. Signal: An insight card links onboarding drop-off with related support tickets for investigation.

  2. Interpretation: AI suggests a possible issue, supported by example data and a confidence label, not a validated probability.

  3. Ownership: The concept routes follow-up to UX, Product, and Engineering based on the evidence.

  4. Human review: A team member accepts, refines, or dismisses the insight. Acceptance starts an investigation; it doesn’t confirm the cause.

  5. Learning: Decisions and dismissal reasons can inform future refinement, but don’t automatically retrain the model.

Intended benefit: Reduce fragmented handoffs by bringing evidence, ownership, and human review together.

Proposed AI technical mapping

NLP

Extract themes, detect sentiment, and categorize feedback with refinement options.

Sentiment Analysis

Gauge user sentiment to calculate frustration scores.

Topic Modeling

Identify recurring feedback themes and pain points.

Predictive Analytics

Forecast trends like churn and prioritize UX risks.

Machine Learning

Automate behavior analysis with manual refinement.

Recommendation Systems

Deliver personalized roadmap suggestions.

Anomaly Detection

Spot deviations to flag potential issues.

Clustering & Segmentation

Group users/feedback for targeted improvements.

Jobs to be done

UX & PLG Designers

  • Identify opportunities to improve CVR and overall features.

  • Identify critical issues with existing features.

Product Managers & Owners

  • Prioritize roadmap items.

  • Address revenue-critical issues.

Engineers & Growth Engineers

  • Assess the frustration level and audience impact of issues requiring significant development investment.

Researchers

  • Tailor research scripts to explore issues identified in the app.

  • Pinpoint key areas for further research.

How I think

Close the loop: Notify users who abandoned a task due to an issue once it’s fixed to rebuild trust.

Status Quo

Manual Workflow

  1. Support: Flags rising onboarding tickets through Slack or vague Jira issues.

  2. Product: Investigates separately, without clear churn or revenue impact.

  3. UX: Lacks drop-off context, leading to guesswork and duplicated effort.

  4. Engineering: Receives incomplete bug reports, delaying investigation.

  5. Cross-functional teams: Struggle to align priorities, stalling decisions.

  6. Leadership: Lacks evidence to confidently prioritize roadmap investments.

Result: Slow, fragmented, lots of handoffs without clarity.

The idea

Proposed concept workflow

  1. Signal: An insight card links onboarding drop-off with related support tickets for investigation.

  2. Interpretation: AI suggests a possible issue, supported by example data and a confidence label, not a validated probability.

  3. Ownership: The concept routes follow-up to UX, Product, and Engineering based on the evidence.

  4. Human review: A team member accepts, refines, or dismisses the insight. Acceptance starts an investigation; it doesn’t confirm the cause.

  5. Learning: Decisions and dismissal reasons can inform future refinement, but don’t automatically retrain the model.

Intended benefit: Reduce fragmented handoffs by bringing evidence, ownership, and human review together.

Proposed AI technical mapping

NLP

Extract themes, detect sentiment, and categorize feedback with refinement options.

Sentiment Analysis

Gauge user sentiment to calculate frustration scores.

Topic Modeling

Identify recurring feedback themes and pain points.

Predictive Analytics

Forecast trends like churn and prioritize UX risks.

Machine Learning

Automate behavior analysis with manual refinement.

Recommendation Systems

Deliver personalized roadmap suggestions.

Anomaly Detection

Spot deviations to flag potential issues.

Clustering & Segmentation

Group users/feedback for targeted improvements.

Jobs to be done

UX & PLG Designers

  • Identify opportunities to improve CVR and overall features.

  • Identify critical issues with existing features.

Product Managers & Owners

  • Prioritize roadmap items.

  • Address revenue-critical issues.

Engineers & Growth Engineers

  • Assess the frustration level and audience impact of issues requiring significant development investment.

Researchers

  • Tailor research scripts to explore issues identified in the app.

  • Pinpoint key areas for further research.

Proposed technical flow map

Proposed architecture: a concept map of data flow and decision points, where AI suggestions stay available for human review. Not a verified production implementation.

Technical Flow map for AI app: Senior Design Director Yvonne Doll
Technical Flow map for AI app: Senior Design Director Yvonne Doll

AI dashboard wireframe, human-in-the-loop

This wireframe outlines a seamless flow that integrates AI insights with manual intervention, providing a user-friendly interface for efficient decision-making and improved user experience.

Hi fi wireframes AI App: Senior Design Director Yvonne Doll
Hi fi wireframes AI App: Senior Design Director Yvonne Doll

Design Musts

Cross-functional views

Each insight adapts to UX, Product, or Engineering, with a View As toggle to switch perspectives. For example, UX sees a possible copy issue, Product sees related onboarding drop-off, and Engineering sees an illustrative API error pattern.

Trust and context

AI explains why an issue merits investigation, giving teams the context to diagnose problems and prioritize work, rather than presenting an action alone.

AI-to-human handoffs

AI-generated insights are clearly labeled and retain their context. People can review, edit, or override them, with an audit trail of decisions.

Human validation

Teams Accept / Refine / Dismiss each insight. Dismissal reasons can inform future refinement but don’t automatically retrain the model.

Bias and coverage

A coverage alert could flag low-volume, high-impact issues that frequency-based analysis might miss, such as an edge case affecting enterprise customers.

Feature ideation

How I think

Close the loop: Notify users who abandoned a task due to an issue once it’s fixed to rebuild trust.

Turn customers into advocates by closing the loop. When you fix something they submitted a CS issue for, tell them when you fixed it and ask for feedback.

Weather app image
Weather app image
Weather app image
Close up view of LLM
Weather app image
Weather app image
Weather app image
Weather app image
Weather app image
Weather app image
Weather app image
Weather app image

The pitch deck

To complete the course, I created a stakeholder pitch for the concept, including a SWOT analysis. The deck argues for building it. It is not evidence of a launch or of commercial validation.

THE SHORT VERSION

Evidence, ownership and human review in one workflow, so roadmap calls stop stalling between UX, Product and Engineering.

4

AUDIENCES

5

STEP LOOP

8

AI METHODS

PROBLEM

Signals live in silos. Support flags an uptick in Slack. Product pulls analytics on its own. UX investigates without knowing where users drop. Engineering gets a vague bug.

DECISION

Map the manual workflow end to end before proposing anything.

RESULT

Slow, fragmented, lots of handoffs without clarity. Roadmap calls can’t be defended to leadership.