25 days until #mtpcon London, the world’s best product conference
Book now
Why does my product suck? by Jen Dante "Product people - Product managers, product designers, UX designers, UX researchers, Business analysts, developers, makers & entrepreneurs 27 June 2022 True Agile Development, Premium Content, Mind the Product Mind the Product Ltd 1091 Product Management 4.364
· 5 minute read

Why does my product suck? by Jen Dante

In this keynote session at #mtpcon SF+Americas 2022, Jen Dante, VP of Product at Ancestry examines how over and under scoping cannot be eradicated from the product process, rather we can optimise them, based on the agility of our organisation, to deliver the most effective value.

Watch this video or read on for key highlights from the talk.

Jen begins by showing how over or under scoping is an inevitable outcome of the product planning process “for the exact same reason why most product ideas don’t work […] it’s super hard to predict”. Finding ways to “balance the impact” and cost of this “over/under product management world” is crucial to delivering value, while supporting the organisation.

Hacky vs polished

During the planning process, product people must consider where upcoming work will sit on a scale of “hacky” to “super polished”. Jen recommends first questioning whether you’re really going to build a Minimum Viable Product (MVP), the smallest of a “series of investments” resulting in learning, and also whether you’ll be able to iterate on it.

An MVP should have “iteration built into the concept”. Then if it works, you can invest further or move to something new without spending time on the wrong thing. Jen describes organisations that force teams to productise half-built work and then move on to something new without iterating. If you’re in an organisation like this “you cannot build an MVP”, Jen says, and recommends instead an MLP or Minimum Lovable Product; “the smallest amount of functionality, polished”. Doing so allows you to perform the same validation and learning exercises as part of your investment, but also gives you the security that if this work becomes a permanent fixture it has a level of polish. This can mean technical or design efficiency, which does not require immediate iteration or create problems if left untouched.

Comprehensive vs limited

In planning, you should also consider how complex something needs to be on a scale of “limited” to “comprehensive” – the greater the number and complexity of use cases it covers, the greater the chance of succeeding, but with a greater total cost.

To make this decision, Jen recommends thinking about how your organisation considers the cost of failure by assessing its risk tolerance. This translates to the number of attempts you will have to build and refine an idea before needing to move to something new. “The fewer bats you’re going to get, the more comprehensive the initial build should be,” Jen says. A more comprehensive build needs to give you the certainty that you legitimately tested the idea, “because if I don’t, and the thing doesn’t work, I’ll never get to build that use case”.

Waterfall prioritisation

Prioritisation is centralised in waterfall organisations with the same group meeting periodically to review a large backlog of projects ranked their projected return on investment (ROI). While “agile tends to be seen as the shining light on the hill,” Jen admits there are times when a waterfall-style planning makes sense, for example, when multiple teams must coordinate, manage dependencies or limited capacities of specialised resources.

In general, waterfall prioritisation favours:

  1. High quality ROI analysis to ensure reliable decisions are made when choosing which “great big idea” will be successful, and won’t require iteration.
  2. Bigger projects are popular as they are more manageable and, when pitched, have more attractive forecasts due to their size.

Scope creep is common in waterfall organisations, Jen says. Teams increase scope to maximise their chance of successfully delivering a project with only “one bite of the apple”, something which is the result of being unable to iterate. It’s accepted in some ways, she says, particularly when the person pitching a large project is not the person delivering it. But there will often be someone accountable for the original scope estimate and as a result of increased work, a reduction in resource efficiency.

Jen recommends managing scope creep by adjusting expectations and potentially “sandbagging” the scope of a project by inflating estimations upfront. This gives you some flexibility, while leaving room for ‘being the hero that cuts scope later’. If you’re in a waterfall organisation, overbuilding and being successful is better than underbuilding, Jen says, allowing for some scope creep and even moving deadlines. Underbuilding and failing, as an alternative, will result in lost credibility in your delivery and future ROI predictions.

Agile prioritisation

Product planning in agile organisations is more continuous than in waterfall and happens alongside sprints or cycles. “Decision-making here is distributed,” Jen says, with teams owning their roadmaps, while strategy and KPIs are signed off at a higher level where decisions focus around moving metrics, rather than focusing on features.

Agile prioritisation favours:

  1. Multiple initiatives, as the organisation is essentially “buying an index fund, not an individual stock”.
  2. Iteration is highly valued and viewed as the best way to increase the chance of success.
  3. Data-driven decisions allow less experienced teams to make better decisions, and avoid productising things that don’t work.

In order to deliver effective agile investments, teams can under-scope on scalability and design polish Jen says. Neither are directly needed to test whether something works, however, “you can’t really get away with not having that in your core product”. Once you want to productise Jen recommends doing code-hardening and scalability work, though it’s easier to justify than design, so it’s always good to reassess whether you’ll be able to iterate.

Risk tolerance is culturally specific, Jen says, and she recommends staying agile by under-scoping and looking to move on from any project where your tests fail, provided you’re confident you did quality testing, rather than investing further. Under-building may incur design and scalability debt, but “almost all the downside is in the overbuilding”, which means fewer opportunities to measure and learn, accusations of scope creep, and less iteration.

Jen closes by reminding us “it’s literally impossible to get the scope right […] what you want to do is you want to optimise for how your organisation prioritises so the cost you pay for either having your builder overbuilt is minimised”. In waterfall it’s better to build too much than too little and deliver MLPs over MVPs, while in agile, it’s best to build too little, focusing on a true MVP. She says: “The biggest takeaway here is that the scope creep might actually be your friend.”

There’s more where that came from!

Explore more #mtpcon SF+Americas 2022 video content or use our Content A-Z to find even more product management insights

Comments 0

Join the community

Sign up for free to share your thoughts

About the author

#mtpcon LONDON | 20 OCT 2023

Join world-class product experts for a jam-packed day of inspiring talks and interactive sessions

Book now