Product Manager Portfolio

Purity Uju
Aranonu

Product Strategy · User Research · Systems Thinking · AI-Assisted Execution

An aspiring product manager who uses research, systems thinking, user insight, and structured execution to solve ambiguous product problems.

Purity Uju Aranonu

02 · About

"I'm interested in complex systems, ambiguous problems, and understanding why users behave the way they do."

I approach products from an operational and systems lens, not just the interface, but the adoption, communication, workflow, and behavioral layers underneath. I work proactively, learn quickly in new domains, and find structure in messy processes.

Operating principles

Structure in ambiguity
Finding shape in unclear processes
AI as part of the workflow
Human-centered,AI-Assisted
Rapid domain learning
Healthcare, fintech, e-commerce, UX
Systems-first thinking
Users, operations, communications, behaviors
Execution-oriented
Research means nothing without decisions
High-agency learning
Team-player, resourceful, proactive

03 · My product operating system

How I think through product problems

01

Understand the user

ResearchBehaviorJourney maps

02

Find pain points

Workflow gapsEdge cases3 Whys

03

Frame the problem

System thinkingPrioritiesTrade-offs

04

Design solutions

ideationUX decisionsFrameworks

05

Quality assurance

Usability testsUX reviewsProduct reliability

Impact

OutcomesBehaviour changeEfficiency

Execution drives momentum

Speed and iteration

Efficient feedback loops Adaptability Continuous improvement

Good judgment shapes product direction

Users and tradeoffs

Prioritization Strategy Systems thinking

04 · Product investigation

HealthConnect — Telemedicine & EHR Integration

Systems coordination across 50+ hospitals · implementation planning · cross-functional execution

The challenge

Fragmented patient data systems, disconnected telemedicine infrastructure, and misaligned stakeholder incentives across a healthcare network. No single owner. No clear path.

The real product problem wasn't technical — it was coordination. Success required treating communication and trust as core product features.

How I approached it

  • Mapped stakeholder power vs interest across clinical, IT, compliance, and admin
  • Designed communication architecture as a product layer, not an afterthought
  • Structured a 12-week phased rollout with adoption checkpoints
  • Analyzed operational and compliance risks per phase
  • Balanced scalability, usability, and regulatory constraints simultaneously

Implementation roadmap

Wks 1–3
Discovery
Wks 4–6
Architecture
Wks 7–9
Rollout
Wks 10–12
Adoption

Stakeholder map

High power · high interest
Clinical leads — manage closely
High power · low interest
Compliance — keep satisfied
Low power · high interest
IT staff — keep informed
Low power · low interest
Admin — monitor

Communication flow

Discovery brief
Stakeholder sync
Phased update
Adoption review

05 · Retention analysis

Meal Planning App — The Execution Gap

Behavioral analysis · retention strategy · onboarding design for beginner users

Users weren't failing during planning.
They were failing during execution.

Research conducted

  • Feature adoption and drop-off analysis
  • User segmentation — beginners vs experienced
  • Journey mapping through Days 1–14
  • Behavioral pattern analysis at drop-off windows
  • Survey design and synthesis

Product decisions

  • Beginner onboarding flow with reduced complexity
  • "Start small" 3-meal plans for week one
  • Retention nudges during the Days 5–8 drop window
  • Grocery integration linked to completion rates
  • Adaptive customization unlocked after first win

Retention funnel

Sign-up
100%
Week 1
72%
Days 5–8
47%
Completion
28%
53%
Non-completion rate
0%
Beginner completion
Days 5–8
Peak drop-off window
Grocery
Top completion correlate

Onboarding flow (proposed)

Simple sign-up
3-meal starter
Grocery link
First win

06 · UX sprint

Temu UX Sprint — Cognitive Overload and the Trust Deficit

Design sprint · trust vs engagement tradeoffs · purchase confidence

The strategic tension

Temu optimized engagement aggressively — at the direct expense of usability, trust signals, and purchase clarity. A classic product tradeoff: short-term metrics vs sustainable conversion.

Engagement without clarity creates friction at the point of decision-making — where it matters most.

Proposed solution — "Focus Mode"

  • Cleaner visual hierarchy separating utility from gamified browsing
  • Reduced overlays and interruption patterns
  • Price stability indicator to rebuild trust
  • Distraction-free checkout path

Sprint process

HMW
Journey map
UX eval
Prototype

Sprint artifacts

HMW questions

How might we reduce decision fatigue at browse?
How might we signal price reliability?

Key insights

Gamification erodes core trust signals
Overlays block purchase intent

Solutions

Focus Mode toggle
Price anchor display

The core tradeoff

Current state

High engagement
Low purchase confidence
High friction at decision

Proposed state

Moderate engagement
Higher trust signals
Lower checkout friction

07 · Systems analysis

Chowdeck — Order Accuracy & Fulfillment Trust

Research-driven product investigation into customization failures and workflow accountability

The product question

Why were users receiving orders that didn't match what they selected? The surface problem was delivery inaccuracy. The real problem was a communication gap across the fulfillment workflow.

It wasn't a delivery failure — it was an accountability gap between restaurant confirmation and actual fulfillment.

Research foundation

  • 48-user survey on order accuracy experiences
  • Behavioral and support-ticket analysis
  • Root cause investigation across the fulfillment chain
  • Secondary reviews and pattern analysis

Solution direction

Real-Time Substitution Approval — a communication layer that brings the user back into the fulfillment loop before the order ships, reducing mismatches and rebuilding trust at the point of uncertainty.

Fulfillment workflow

User order
Restaurant
Substitution gap ⚠
Rider → Delivery

Communication breaks between restaurant confirmation and fulfillment — the user is excluded from this window.

With solution → Restaurant flags substitution → Real-time user approval → Fulfillment proceeds

Impact goals

Fewer mismatches
Real-time user approval
Trust rebuilt
Transparent fulfillment
Less support load
Fewer escalations
48 users
Research foundation

What this demonstrates

User research Workflow thinking Operational reasoning Trust systems Root cause analysis

08 · AI as part of the workflow

How I use AI as a product tool

Input

Research synthesis

Synthesizing large datasets, feedback, and competitive signals faster

Processing

Hypothesis generation

Generating, stress-testing, and refining product hypotheses rapidly

Structuring

Documentation

Organizing product specs, strategy docs, and communication clearly

Output

Iteration acceleration

Shortening feedback loops from insight to decision to next question

AI handles

Speed, synthesis, and scale

Product thinking handles

Prioritization, context, tradeoffs, and decisions that matter

Active uses in my product work

Research synthesis Information structuring Hypothesis refinement Documentation drafts User insight synthesis Communication strategy Rapid ideation support Problem structuring Execution planning

Let's build better product experiences

Purity Uju Aranonu

Product Strategy · User Research · Systems Thinking · AI-Assisted Execution

Focused on building thoughtful, user-centered products through structured thinking, research, systems analysis, and execution.