Menu

Jordan Ellis

  • Product Strategy Lead
  • research-led product strategy and growth

Studio profile

Jordan Ellis — Product Strategy Lead

Jordan Ellis is Product Strategy Lead, working with clients to decide where a product should go next and how they will know it is the right direction. Jordan's focus is research-led product strategy and growth, grounded in what customers do and say rather than what a team hopes is true.

Genome builds products as well as websites, including ventures that begin life in its incubation program. Those products need direction before they need design, and the studio's mix of design, engineering and commerce skills only pays off when it is aimed well. Jordan's seat exists to provide that aim, and to revisit it whenever new evidence arrives.

Growth comes up in almost every client conversation, and Jordan tends to widen the definition. It might mean more customers, but it can equally mean better retention, a healthier margin per order or a clearer niche. Jordan helps clients choose which kind they are pursuing, since each one leads to a rather different product.

Responsible research is a principle Jordan takes seriously. Participants are recruited fairly, including people with disabilities and those outside the obvious target group, and their time and data are handled with respect. Jordan is equally wary of growth that depends on manipulative design, believing that tricks which lift one metric usually erode trust.

Jordan works readily with client founders, investors, analysts and outside research agencies, bringing their views together without letting the loudest one win. Clients should leave with a strategy they can explain in a few sentences, evidence they can point to, and a team aligned on why the next step comes next.

Learn about the wider team, explore the studio services, or visit the contact page to start a conversation about your own product challenge and see how product strategy could help.

Turning research into a roadmap the team can defend

Product strategy is largely the work of deciding what not to build. Jordan opens a project by separating what the client knows from what they believe, then designing the smallest piece of research that would move the most important beliefs into the first column.

That research might be a set of customer interviews, a look at analytics and search data, a competitor teardown or a quick prototype test. The output is an opportunity map: problems worth solving, the evidence behind each, rough effort and the business outcome it connects to. For start-ups in the studio’s incubation program it usually takes the form of an assumptions list with a cheap test beside each one, because the riskiest assumption deserves attention before the most exciting feature does.

From that map comes a roadmap written as outcomes and bets rather than features with dates. Every item states what should change and how the team will measure it. The pattern Jordan steers clients away from is the departmental wishlist, where everyone gets one feature and the product loses its point. Prioritized bets go to the experience director and product designer, while the measurement plan goes to engineering so tracking is built in from the first release.

Questions from the first strategy session

  • Which customer would you most hate to lose, and why do they stay?
  • What do you believe about your market that you’ve never tested?
  • What would you stop doing if this product worked?
  • How will we know, a few months in, whether we were right?
Team

A practice built for thoughtful progress

The profile above is intentionally fictional and represents a product strategy role within a collaborative studio. Explore the services, browse the work, or read the journal to see how this perspective supports useful digital products.