Synthesized scattered product, research, feedback, accessibility, rollout, and roadmap signals into a board a team could argue with: fix, defer, sequence, change.
Fresh professional evidence / mobile product system
Employer Mobile App / EMA
The work was not finding more signals. It was making the signals useful enough to discuss what the mobile app should help employers do.
Company / context
Indeed
Role
Senior UX, product strategy, research synthesis, mobile systems
Timeframe
2023–2025 evidence source
Proof strategy
Signal synthesis and product-direction support
My role
Responsibility before artifacts.
Helped separate likely immediate fixes, sequenced product work, deferred bets, and evidence gaps before they collapsed into one overloaded roadmap conversation.
Framed app home, interview/agenda workflows, accessibility, localization, and Scout or AI opportunities as connected mobile decisions, not separate requests.
Problem beneath the brief
The hard part was not evidence. It was what to do with it.
EMA had signals everywhere: app reviews, churn, accessibility, app-home strategy, Japan rollout, interview and agenda workflows, design-library constraints, and Scout or AI opportunities. Looking at each source separately made everything feel important. The work was to make the signals comparable enough to inform mobile priorities and shape clearer product discussion.
Decision evidence
What the artifacts made discussable.
01 / Centerpiece artifact
The map should still work if the body copy disappeared.
The centerpiece carries the main story: scattered mobile-employer signals were synthesized into comparable themes, decision categories, priority discussions, and supported direction.
Belief proved: evidence is only useful when a team can use it to make a choice.
SignalsMessy evidence from many surfaces
- Vision + whiteboard → app-home ambition
- Feedback synthesis → repeated employer friction
- App reviews + churn → trust and usability gaps
- A11y + localization → inclusive rollout constraints
- Interview / agenda → time-sensitive mobile moments
- Career Scout / AI → assistance boundary questions
SynthesisTurn signals into comparable choices
- Cluster recurring themes
- Separate symptom from cause
- Map confidence and evidence gaps
- Expose tradeoffs across teams
- Connect evidence to employer decisions
DecisionsConvert evidence into product calls
- Prioritize reliability and comprehension fixes
- Sequence app-home status and next actions
- Support interview / agenda moments
- Defer unclear AI bets until boundaries exist
- Route dependencies to design-system work
Supported outputsWhat the synthesis helped clarify
- Prioritized: fix confusing mobile moments
- Sequenced: app home → interviews → assistance
- Deferred: broad automation without trust model
- Framed: roadmap discussion around employer decisions
What made it complexDifferent signal typesMobile moment constraintsRegional rollout needsDesign-system dependenciesAI boundary uncertainty
Direction
Mobile employer experience can be discussed as a product-intelligence system: app home explains status, interviews get timely support, inclusive foundations stay explicit, and AI assistance waits for clear employer control.
Signal-to-roadmap synthesis map
02 / Supported outputs
The synthesis supported four kinds of discussion: prioritize, defer, sequence, frame.
This board makes the uncomfortable question visible: so what should be prioritized, sequenced, or held back?
Supported decision output: immediate fixes, sequenced product work, deferred bets, evidence gaps, and system dependencies were made visible together.
PrioritizedReliability + comprehension fixesReduce confusing moments surfaced by reviews, churn, support signals, and feedback synthesis.
SequencedApp home, then interview momentsMake status and next action clearer before expanding the surface area of mobile workflows.
DeferredBroad AI assistance without trust boundariesKeep Scout / AI opportunities visible, but avoid placing them ahead of control, context, and confidence.
FramedRoadmap discussion around employer decisionsThe discussion could move from feature intake to decision support: what must the employer understand or do now?
Priority / defer decision board
03 / Sequencing evidence
The roadmap discussion could stop looking like a feature pile.
Sequencing helped make the direction concrete: stabilize the mobile foundation, make app home useful, support interview moments, then define where AI or Scout assistance could responsibly enter.
The roadmap logic became more discussable: fix the base, clarify the moment, then add assistance where trust and context exist.
01 / StabilizeFix confusing mobile momentsReviews, churn, a11y, localization, and design-system gaps become foundation work.
02 / OrientMake app home explain statusHelp employers understand what changed and which action deserves attention.
03 / SupportBring interview / agenda help into mobileUse time-sensitive workflows where mobile can genuinely reduce effort.
04 / BoundDefine Scout / AI assistance boundariesAssistance enters only where the product can explain, constrain, and recover.
Mobile roadmap sequencing map
04 / Final deliverable evidence
The strongest proof is what the source set helps clarify.
The last artifact makes the supported direction visible: what the source set suggests across app home, interviews, accessibility/localization, design-system dependencies, and AI boundaries.
Decision-support proof: the work informed product-direction discussion, not only insight.
Supported outputMobile product-direction discussionNot a list of findings — a decision-support path for what the employer app should help people understand and do.
InformedApp-home direction: status + next action
SupportedInterview support in roadmap logic
Made explicitAccessibility, localization, and system dependencies
ClarifiedAI / Scout opportunities need trust boundaries
Final deliverable evidence map
Decision journey
How the work unfolded.
01 / Signals
The evidence came from everywhere
Vision work, feedback synthesis, churn, app reviews, accessibility, rollout planning, interview/agenda workflows, design-library constraints, and AI/Scout ideas were all pointing at the mobile app from different angles.
02 / Complexity
Everything looked important at first
Some signals were usability problems. Some were confidence problems. Some were regional rollout needs. Some depended on mobile patterns, roadmap timing, or AI boundaries that were not settled yet.
03 / Synthesis
Make the signals comparable
The synthesis separated symptoms from causes, clustered themes, exposed tradeoffs, mapped confidence, and connected signal types to the employer decisions that mattered on mobile.
04 / Decisions
Clarify what might be fixed, sequenced, or held back
The work helped clarify what appeared to deserve immediate attention, what belonged in app-home or interview moments, what depended on the design system, and where Scout or AI needed clearer boundaries.
05 / Direction
The app needed a clearer job
The direction was not “put every signal into the app.” The synthesis helped shape discussion around how mobile could help employers understand status, act at the right moment, and trust the next recommendation.
Evidence boundary
Employer Mobile App Vision, Feedback and Research Synthesis, Vision White Board, FY25 Discovery, Interview Experience, Career Scout, app-review datasets, and mobile design-system evidence.
Portfolio status: Needs public-safety review. Claims remain bounded to what the reviewed source set can support.
What changed / what the evidence supports
The source set supports a clearer product discussion around prioritized fixes, deferred bets, sequenced roadmap work, app-home direction, interview support, inclusive foundations, design-system dependencies, and AI-boundary questions.
Reflection
My contribution was making the messy middle visible: the signals, the synthesis moves, the priority calls, the sequencing logic, and the product-direction discussion they helped clarify.