Building scalable monetization systems through design leadership and AI.
- Product Design Manager, Acquisition & Expansion — Adobe
- Co-owned annual strategy and roadmap with PM & Engineering
- Led checkout across Adobe.com and Adobe apps
Set boundaries on what's in and out before anyone opens a design tool. Ambiguity at the start compounds into misalignment at the end.
Teams move fast when they know who decides what. I establish decision rights early so no one waits for permission or revisits settled calls.
Push for decisions that hold up. Shortcuts become debt; good architecture becomes velocity.
Coach designers to think in platforms and patterns — not individual screens.
- Designers clone repos, write code with AI, and push to production
- AI-assisted bug fixing — reducing dependency on engineering cycles
- Design auditing and QA through AI tooling
- Research synthesis and pattern extraction at speed
- Designing AI-powered features within monetization surfaces
- Tokenized components enable faster AI feature delivery
- Building for personalization and adaptive experiences
One experience.
"I love Apple and own several devices."
"I love drawing and just bought an iPad."
"I'm in the market for a new smartphone, but don't have any specific brand in mind."
"I'm probably going to wait and test drive the new iPhone in store before deciding."
A personalized shopping experience in all contexts.
A human face on the brand & create participatory experiences.
A creative space that is approachable and actionable.
Understood the intent and benefit of the page
Card did not resonate
Categories list was useful, especially Cases & Protection
personalized and guided experience
to the broader audience and helped
increase purchase confidence.
Design Manager
Designed in partnership with Swarnima Deshmukh, Ellie Xu, and Urvi Kulkarni.
Lead to higher drop-off and make it difficult for users to complete their purchase.
No social login or Pay options — missing convenient industry-standard shortcuts that reduce friction.
Users bounced across Adobe touch points after purchase, causing delays in onboarding and value realization.
- Overall conversion rate
- Incremental ARR
- Click-through rate
- Adoption of shared components across teams
- Faster time-to-market for monetization experiments
One page, one goal — keep users moving forward without hesitation.
Reduce steps, reduce doubt — combine screens wherever it doesn't cost clarity.
Make payment feel safe with familiar patterns, clear pricing, and no surprises.
Consistent components that flex across every product team's needs.
As part of the platform team, our checkout components shipped across many Adobe products — Photoshop, Acrobat, Firefly, and more — each with its own team and roadmap.
- Brought product teams in early, before requirements were locked
- Built ongoing relationships with each team's design and PM leads
- Ran regular syncs to surface conflicts before they blocked shipping
- Balanced platform consistency with product-specific needs
Product teams treated the platform as a partner, not a blocker — faster buy-in and fewer late-stage surprises.
a program lead.
Introduced a junior designer to this work. Goal: grow them into independently leading the program.
- Clear scope and decision-making authority
- Coached toward systems thinking
- Calibrated support — pushed when ready
- Developed XFN relationships
Operates with more confidence and autonomy. Stronger Eng collaboration — no longer needs me to facilitate.
Results justified expanding scope to B2B, Students, and the rest of the checkout flow.
Tokenized components became the foundation for AI feature integration — the platform investment compounded.
Designed in partnership with the Growth design team.
- Photoshop, Acrobat, Firefly, and Illustrator each shipped their own upgrade experiences on web
- The same design, legal, and pricing requirements were re-solved from scratch by every team
- Nothing carried across — an experiment that worked for one product never reached the others
Adoption wasn't a selling problem. If the platform shipped a paywall the same way it shipped checkout — same integration path, same expectations — product teams would take it the same way.
- A configurable paywall that hands off directly into Adobe's shared checkout
- Spectrum components, so every paywall inherits Adobe's design standards
- Legal, pricing, and compliance requirements built in rather than re-implemented
- Experimentation hooks each product's growth team can run against
- Led design end to end, from platform concept through launch
- Designed the self-service configuration experience
- Defined the guardrails that keep flexibility from becoming fragmentation
- Established the component contribution model with partner teams
Copy, imagery, offers, and layout options — changed in their own CMS, on their own schedule.
The component library, design standards, legal and pricing requirements, and the handoff into checkout.
Too rigid and no one adopts it. Too loose and it stops being a platform. The guardrails are what let every team move independently without drifting apart.
An internal management system where each product team picks a template, configures the paywall, and edits the copy — without a platform ticket or a release train.
Teams start from the platform's approved layouts — the fastest path to a paywall that already meets Adobe's standards.
Plans, offers, and which options surface — set per product, and changed whenever the growth team needs a new test.
Headlines, benefit lines, and CTAs are owned by the product team, so messaging moves at their pace rather than ours.
A client team hits a gap — they need a component the shared library doesn't cover yet.
The client team designs the component against platform standards.
Two paths in, depending on where the capacity is.
The component lands in the shared library — every team on the platform gets it, without asking for it.
+ more
Self-service configuration took the platform team out of the critical path. What was a queue against one team became every product team shipping in parallel.
The component contribution model turned a single-team platform into a shared cross-product design system that partner teams now extend.
- Analytics, design reviews, and campaign setup each require a separate team and handoff
- Bottlenecks compound — slow cycle times mean fewer experiments per quarter
- PMs can't ship tests fast enough to keep up with the optimization roadmap
- Identifies funnel friction from live analytics
- Generates and prioritizes hypotheses by expected impact
- Creates design variants using Spectrum components
- Configures targeting, traffic split, guardrails, and success metrics
- Defined the product concept and end-to-end workflow
- Designed the AI assistant UX and approval interface
- Built the Control vs Challenger comparison view
- Partnered with PM and Engineering on the agentic pipeline
COMEX reads Analytics and surfaces the highest-signal drop-off points across the funnel — automatically ranked by conversion opportunity.
The assistant produces multiple design challengers using Spectrum components and shows them side-by-side with the control — no Figma required for approval.
Campaign setup — targeting, traffic allocation, guardrails, and metrics — is pre-populated and ready to approve. PM reviews the packet and ships.
Removing analytics, design, and setup bottlenecks means PMs can run more experiments — compounding conversion gains across Adobe.com.
The AI-generated experiment packet gives engineers a clear goal and suggested fix from day one — reducing back-and-forth and speeding up implementation.