02 — The Opportunity
Competing on more than meals.
The business saw an opportunity to turn recurring shipping and premium-meal friction into a predictable membership—and potentially transform ordering from a weekly decision into a habit.
The strategic bet
Competitors such as CookUnity had introduced paid membership programs that bundled free shipping and premium benefits. Factor+ explored whether the same mechanism could strengthen retention, increase frequency, and protect market share.
The MVP focused on mid-loyalty customers: engaged enough to understand Factor’s value, but with room to increase their ordering frequency.
Why this wasn’t a simple UX problem
Factor already had a Rewards program. A second loyalty mechanic raised questions about customer mental models, overlapping benefits, cannibalization, pricing, technical feasibility, and whether the proposition created enough incremental value to justify another subscription.
Before optimizing the interface, I wanted to understand whether we were solving the right problem.
“Were we designing the right product—or just designing the brief well?”
03 — Challenging the Brief
Before designing the solution, I pressure-tested the strategy.
I built a living analysis that combined customer behavior, competitive research, historical product work, financial modelling, behavioral science, technical constraints, and the existing Rewards experience.
The goal wasn’t to prove the brief wrong. It was to make the trade-offs visible before we committed to building.
My initial recommendation was to explore integrating premium benefits into Rewards rather than launching a fully standalone paid program. That position was debated directly with Product and Engineering, challenged with additional data, and refined as the team aligned around what the MVP needed to prove.
One important correction came from the team: an early premium-spend calculation used the wrong denominator. I updated the analysis rather than defending it—and kept pushing on the broader experience and systems questions that remained unresolved.
04 — Designing the Experience
Making a second subscription feel simple, transparent, and useful.
Once the team aligned on testing the standalone model, my focus shifted from debating the strategy to designing the clearest possible version of it.
05 — Shipping at Startup Speed
High velocity without turning design into decoration.
The Gen AI squad was set up to move faster than a conventional product team. That made prioritization—and design judgment—more important, not less.
06 — Designing the Experiment
Success had to mean more than “people subscribed.”
A paid membership can look successful while simply discounting behavior customers would have done anyway. We needed to separate adoption from incremental value.
07 — Results
The membership created real lift—but not equally for everyone.
By the July performance read, mature cohorts showed that Factor+ could increase engagement and customer value. The same data also revealed a clear profitability cliff among the most loyal customers.
The most important result was not a single uplift number. It was learning where the model stopped working.
08 — What Changed Next
Use the learning to narrow the product—not declare victory.
The performance read led to a more segmented strategy and a clearer roadmap for where Factor+ should—and should not—scale.
09 — Staff-Level Impact
The feature shipped. The operating model travelled further.
The most durable outcome was not a single interface. It was a way of moving from ambiguity to evidence quickly—without separating strategy from craft.
What I contributed
I led the product design end to end, challenged the initial strategy with evidence, helped convert disagreement into testable hypotheses, designed the membership lifecycle, partnered through technical and operational constraints, and stayed accountable to the product after launch through measurement and iteration.
What scaled beyond me
The Gen AI squad model and rapid-build framework developed through this work are now reusable across HelloFresh and available to the subsequent brands operating under the broader portfolio.
The goal wasn’t to be the person with the right answer. It was to help the team reach a better answer faster.
10 — Reflection
What this project changed about how I design.
Challenge the premise early
A polished solution cannot rescue a weak product assumption. The earlier design engages with economics, customer behavior, and system constraints, the more useful it becomes.
Disagreement is part of the work
My analysis contained assumptions that were challenged and corrected. That made the work stronger. Seniority is not about defending every position; it is about knowing which questions still matter after the correction.
Execution is still essential
Strategic skepticism did not remove the responsibility to design an excellent MVP. Once the decision was made to test, my job was to make the test as clear and credible as possible.
Metrics complete the design story
The most interesting outcome was not that customers subscribed. It was understanding how the product changed behavior, where value became incremental, and where the model broke down.
Takeaway
Case study takeaway: Factor+ taught me that Staff-level design is not strategy instead of craft. It is using craft, systems thinking, evidence, and influence together to improve the quality of the decisions a product team makes.
