Back to resources

Product Transformation: Why Prioritization Is Critical

Product
Prioritization

19 September, 2021

Rohit Karanam
Rohit Karanam

Senior Director, Product Management at Seismic

Rohit Karanam, Director, Product Management at Teradata, shares his thoughts on product transformation, emphasizing why prioritization becomes critical and something a PM needs to do on a day-to-day basis.

Problem

We live in a fast-paced world where user needs can change overnight. Once a stellar win that served user needs impeccably now needs an overhaul. Transforming an already existing product is anything but easy. Users usually have expectations based on their previous interaction with the company, and needless to say, every target market is different. Knowing what to prioritize and being able to get the first version of a transformed product out the door quickly is one of the main concerns product leaders have.

When Apple came out with the iPhone, it was still widely considered a computer or iPod company. iPhones not only transformed their products, but their company, and I dare to say the industry itself. What were the users telling them, and what made them change their focus to what they were doing before? I am sure that every product leader deliberated over their strategy, asking themself what Apple prioritized when making this historic move: did they prioritize on design, features, user experience, or technology.

Actions taken

Before taking any actions, one should reflect and understand why they are undergoing transformation. You should be able to establish what are the three key reasons that triggered the transformation. One of the reasons could be that the existing product is not good enough for a certain target segment. Or perhaps, customers raised too many concerns that the existing product couldn’t solve. Understanding the Why of doing something and dissecting that Why into various pieces is a cornerstone of any successful transformation. Only then should one move from the Why to What and start taking action to address each of those pieces.

We should understand that transformation is all about bringing to life something new. We have to keep the baggage of the old product aside and not burden the new product with it. Sometimes we look at the new product wearing the lenses of the old product. When we do that, we are trying to solve all of the problems of the old product with the new product. That is frequently not needed because user needs are changing all time. Sometimes we need to step back, take the baggage off, and come up with something brand new that resonates with the present.

Lessons learned

-- If you are transforming a product, catering it to the same user base, be aware not to end up regressing the user experience. You should take prioritization seriously, based on extensive research that should point out what you should keep and what needs to be revamped. To set yourself up for success, prioritize smart! The question is not how to balance between important and unimportant things but between high and the highest priorities.

  • PMs need to be comfortable knowing that there will be times when they won’t get it all. They should not be emotional, because once they do, they will be losing control over the situation. During the transformation, emotions run high, and you should be able to remain calm and take it one step at a time. Also, during the transformation of a company or product, most of the things were already needed yesterday. There is not much time, and people are responding differently to these constraints.
  • A lot of times, people jump into implementation without much thinking. It is our human nature that drives us toward solving the problem even before we understand it. Sit down, keep emotions aside and try to understand why you are undergoing a transformation in the first place. Once you know the Why, keep dissecting what needs to be done into actionable items.

Discover Plato

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


Related stories

How to measure Engineering Productivity?

30 November

When you grow fast, its normal to focus on Value delivery aka "Feature Releases". Too many releases too soon will inevitably lead to piling tech debts and before you know, inefficiencies creep in, performances goes down, and ultimately any new release takes too long. Sounds familiar? Then read on..

Productivity
Prioritization
Performance
Ramkumar Sundarakalatharan

Ramkumar Sundarakalatharan

VP - Engineering at ITILITE Technologies

How I failed at my startup

14 October

There are nine specific building blocks and functional areas every org/company need to work to launch the product and provide services to customers. How effectively founders tackle them determine the destiny of the company.

Mission / Vision / Charter
Scaling Team
Building A Team
Impact
Strategy
Prioritization
Praveen Cheruvu

Praveen Cheruvu

Senior Software Engineering Manager at Anaplan

Scaling a Team in Two Parts: The Product and Manager

2 August

Viswa Mani Kiran Peddinti, Sr Engineering Manager at Instacart, walks through his experience scaling a team, product and his skills as a leader.

Managing Expectations
Product
Scaling Team
Leadership
Meetings
Viswa Mani Kiran Peddinti

Viswa Mani Kiran Peddinti

Sr Engineering Manager at Instacart

Building Up Your Technical Skills in a Fast-Paced Industry

8 July

Otavio Santana, Distinguished Software Engineer at Zup Innovation, shares his best practices for upskilling without stretching yourself too thin.

Different Skillsets
Personal Growth
Prioritization
Otavio Santana

Otavio Santana

Java champion, software engineer, architect, and open-source Contributor at Independent Technical Advisor

How Product Management Chose Me

23 June

My accidental journey into product management

Product
Personal Growth
New PM
Career Path
Michael Castro

Michael Castro

Sr. Manager, Product Management at Capital One