A New Feature, an Old Assumption
Identified an unmet need for combining "Buy X Get Y" with add-on products, then found that the shipped feature was being used in an unexpected channel — a signal that changed what we built next.
Buy X Get Y couldn't cover a real merchant need
TODO draft Merchants using the "Buy X Get Y" bundling feature needed a way to combine it with add-on products, and the existing feature set didn't support that. We set out to understand exactly what shape that need took, and to design a way to meet it.
What was the merchant-facing symptom — support tickets, a research finding, a metric? This section needs the specific trigger that started the project.
TODO — role and team
TODO draft What was your scope on this project — research, design, or both? Who else was on the team (PM, engineers), and was this your project alone or a shared effort?
From research to an add-on feature
-
01 — TODO
Understanding the need
How did you learn what merchants needed here — interviews, support data, usage analysis? What tool or product was this within?
-
02 — TODO
Designing the add-on feature
What were the design options considered, and why did the shipped version win?
-
03 — TODO
The unexpected channel
The brief mentions an existing feature was found being used through "a new channel" after shipping — what channel, and how was it discovered?
TODO — the calls that mattered
TODO decision title
ChallengeTODO
DecisionTODO
A discovery that reshaped the roadmap
TODO — the brief says "these changes affect the product metric a lot." Which metric, and by how much? (Homepage currently claims an 18% feature adoption lift.)