Back to resources

The Importance of Slow Rollouts in Product Development

Product
Feedback
Strategy
Design
Users

13 April, 2022

David Pearson
David Pearson

Sr. Engineering Manager at Square

David Pearson, Sr. Engineering Manager at Square, explains the importance of slow rollouts for launching new product features.

Releasing Features Too Fast

Years ago, I was working on an incredibly fast-paced product. We were continuously launching new features, week after week. In software development, introducing a new feature to a set of users is called a "feature rollout." We introduced our new features to everyone at once— rolling out to 100% of the users. The major problem with this approach was getting a lot of feedback that we couldn't process and address.

We'd go over a piece of feedback, fix it, and iterate. But because of the sheer mass of all the new features, we had difficulty catching up. So we couldn't adequately assess the features. We couldn't identify all the bugs and our users' thoughts about the functionalities.

Introducing Features With a Slow Rollout

As someone working in tech, you will have assumptions about how your product should or shouldn’t work. It's wise to remember that sometimes you may be wrong (and at some point, this is very likely). So I can't emphasize the importance of testing and early feedback enough.

My advice for engineering managers is to release features slowly. Start by introducing new functionalities to a small percentage of users. My go-to is between 1 to 5% of users initially, then increase when you have confidence in your feature. That is what we call a "slow rollout." Do this for every feature that you launch. It enables you to get a workable amount of feedback while not disrupting your users too much.  

Additionally, before defining a new functionality, do some user research with specifically targeted users. Take the time and opportunity to learn from your responses without impacting your entire user base.

By adopting this phased approach, you reduce the risk of failure drastically. As an engineering leader, you can take in the user feedback and manage your product on a more consistent basis with the help of your partners. Rather than overworking on shaky foundations, your developers can build on tested, approved, and needed features. Overall, a slow rollout will enable your team to execute smoother product launches with less effort and more confidence.

User Feedback Is Gold

  • Don't assume that you know what your users want. You may get it right a tiny percentage of the time, but usually, it doesn't work. Be aware of your own biases.
  • Conduct thorough testing and research to better understand your product performance and adoption.
  • Have a slow rollout for every functionality you plan to launch to reduce the risk of error and wrong assumptions.

Discover Plato

Scale your coaching effort for your engineering and product teams
Develop yourself to become a stronger engineering / product leader


Related stories

The Art of Asking Why: Narrowing the Gap Between Customers and Users

24 May

Jord Sips, Senior Product Manager at Mews, shares his expertise on a common challenge for product managers – finding root causes and solutions.

Customers
Innovation / Experiment
Product
Personal Growth
Leadership
Stakeholders
Users
Jord Sips

Jord Sips

Senior Product Manager at Mews

Streamlining Product Processes After a Reorganization

16 May

Snehal Shaha, Lead Technical Program Manager at Momentive (fka SurveyMonkey), details her short-term technical strategy to unify processes among teams following an acquisition.

Acquisition / Integration
Product Team
Product
Building A Team
Leadership
Internal Communication
Collaboration
Reorganization
Strategy
Team Processes
Cross-Functional Collaboration
Snehal Shaha

Snehal Shaha

Senior EPM/TPM at Apple Inc.

Navigating Disagreements When It Comes to Priorities

9 May

Pavel Safarik, Head of Product at ROI Hunter, shares his insights on how to deal with disagreements about prioritization when building a product.

Innovation / Experiment
Product Team
Product
Dev Processes
Conflict Solving
Internal Communication
Collaboration
Convincing
Strategy
Prioritization
Pavel Safarik

Pavel Safarik

Head of Product at ROI Hunter

Leading Your Team in Stressful Situations

27 April

David Kormushoff, Director at Koho, recalls how he galvanized his team to tackle a time-sensitive problem, sharing his tips on how to shift chaos into calm.

Goal Setting
Leadership
Conflict Solving
Deadlines
Collaboration
Motivation
Strategy
Health / Stress / Burn-Out
David Kormushoff

David Kormushoff

Director at Koho

Why You Should Take Technology Risks in Product Development

25 April

Matias Pizarro, CTO and VP of Residents at ComunidadFeliz, recalls a time in his early career when he took a technology risk that had wide-ranging benefits to his product's user experience.

Innovation / Experiment
Product
Scaling Team
Dev Processes
Matias Pizarro

Matias Pizarro

CTO and VP of Residents at ComunidadFeliz

You're a great engineer.
Become a great engineering leader.

Plato (platohq.com) is the world's biggest mentorship platform for engineering managers & product managers. We've curated a community of mentors who are the tech industry's best engineering & product leaders from companies like Facebook, Lyft, Slack, Airbnb, Gusto, and more.