Your job isn’t to create a scary backlog but to create value. That’s why it’s time to change the game.
Product managers and product owners should stop:
- Doing things that don’t create value
- Letting external influences define how you work
- Taking the passenger seat
It’s time to take the driver’s seat and level up product ownership at your company.
I understand companies’ firewalls limit product owners because they haven’t experienced what it means to be a product-led organization. I’ve been a backlog owner for years, and it sucks — I wouldn’t wish it on anybody.
In this guide, I’ll teach you how to act as a product owner instead of a backlog owner. I’ll explain the difference between being a backlog owner and a true PO and share insights from my experience to help you step up your game and elevate the product owners around you.
Table of contents
- Backlog owner vs. product owner
- Moving from backlog owner to product owner
- Things to do right now
- Things to do ASAP
- Things to do continuously
- To be or not to be a product owner?
Backlog owner vs. product owner
The sad fate of product owners drives me nuts. We hire great professionals who are excited to become rockstars at their new company but quickly run into the corporate firewall. From there, they’re often demoted, so to speak, to backlog owner.
If you’re a product owner, you’ll inevitably be expected to work as a backlog owner at some point. But with the right approach, you can transform the scenario.
What I’m about to share may step on your toes; I’m sorry for that. I want to help you see the light at the end of the tunnel. I want to give you a perspective to envision what it means to be a real product owner:
- Product owners for on uncovering opportunities to create value, whereas backlog owners focus on writing specific backlog items
- Product owners continuously measure the outcome and decide what to do next based on evidence. Backlog owners put their energy into increasing velocity; they celebrate shipping features at the speed of light
- Product owners strive for partnership with business people and don’t shy away from conflicts. Backlog owners aim to please as many stakeholders as possible without stepping on toes
- Product owners have a learning mindset; when releasing features, they start with a small audience and scale gradually based on evidence. Backlog owners have an output mindset; when releasing features, they make them available to the whole audience at once and don’t spend time measuring results
- Product owners treat backlog items like milk; they remove items as often as necessary, and the backlog is always lean. Backlog owners treat backlog items like wine; they don’t dare remove them or put them on the bottom backlog. Backlogs are gigantic and outdated
- Product owners continuously review features and remove the ones that don’t create enough value. Backlog owners never review live features; once shipped, they live forever
- Product owners inspire product teams and empower them to solve meaningful problems however they see fit. Backlog owners plan by capacity, micromanage the team and provide no overarching vision
- Product owners cause discomfort with the company leadership because they don’t let anti-patterns get in their way. Backlog owners follow orders from management and strive to make them happy in the short term while ignoring anti-patterns
- Product owners are authentic leaders. Backlog owners are managers who aren’t necessarily in a position to inspire
- Product teams create value with product owners. They create features with backlog owners
If you’re currently a backlog owner, you may feel offended or overwhelmed after reading the list above; I’m sorry for that. I do feel your pain. Like I said, I’ve been a backlog owner myself.
Most product owners will, at some point in their career, land a new job and find that they’re expected to act as a backlog owner. That’s normal. Next, we’ll show you how to differentiate yourself and become an outstanding product owner instead of an ordinary backlog owner.
Moving from backlog owner to product owner
I must set clear expectations: the journey from backlog owner to product owner is long and stressful, yet rewarding. We’re talking about years, not months.
If you want to stay where you are as a backlog owner, I don’t blame you — and I’d say companies would be happy to pay you a significant salary. You may not have much fun at work, but that’s subjective.
However, if you want to become a product owner, I suggest you continue reading.
Stakeholders won’t like you once you start acting as a product owner — at least, not at first. However, if you do it the right way, they will eventually come to admire and respect you.
I’ll share a general roadmap for moving from a backlog owner role to become an impactful product owner, including:
I will share some things you can do right now, things you should tackle soon, and activities you should carry out continuously. I hope it helps!
Things to do right now
Don’t leave for tomorrow what you can do today.
Some things I’m about to share might jar you, but don’t be afraid to take a leap of faith. Taking the steps below will make your life easier:
1. Remove the clutter
You’ve got to remove old backlog items — but what does old mean?
Here’s my rule of thumb: if something doesn’t make it to a sprint in three months, you should delete it. If that’s too painful for you, you can archive these items.
2. Establish an extreme cleaning routine
Create a habit of cleaning your backlog at least once a week.
I do this every Friday morning. I have filters set up so it doesn’t take more than five minutes.
Ensure your backlog remains lean and clean.
3. Create room to understand the problem
If you’re used to writing detailed backlog items, stop. Write broken ones and focus on the problem.
Subscribe to our product management newsletter
Get articles like this to your inbox
I know developers won’t like that, but you can start small. Pick one or two items like that and gradually adapt all of them.
Thing to do ASAP
The next step is preparing the foundations for great things to happen. These steps will require more conversations and alignment:
- Establish a product direction
- Remove distractions
- Don’t gather requirements
- Evaluate current tracking
- Measure live features usage
1. Establish a product direction
I’d suggest setting a goal that business people can support and the team can commit to. This will be challenging if your organization is output-oriented.
Start small. Try getting support to use 20 percent of your roadmap for a goal and then scale up.
2. Remove distractions
Once you have defined goals, remove all backlog items unrelated to them. That will ensure you don’t waste your time with distractions.
Just do it. Important things will always come back to your plate.
3. Don’t gather requirements
Business people shouldn’t decide what you do but help you create value. What I mean is, don’t assume the business knows best what customers need.
Set a routine to talk to customers at least once a week. Yes, you read that right: once a week.
Let me be clear: you have no business without understanding your customers.
4. Evaluate current tracking
What can you learn from available data? Check your current tracking and tune it to ensure you’re ready to measure the outcome.
5. Measure live features usage
Evaluate how customers benefit from your current features. Look at available data and interview customers.
You’ll learn that some features aren’t used, and some are confusing. Retire pointless features and address necessary improvements on confusing ones.
Things to do continuously
The tricky thing about being a product owner is that almost nobody will get the point. You will continuously need to work on coaching opportunities and persuade leadership to support a different way of working.
Here are some tips:
1. Run workshops
Try inspiring people. Host workshops to show them the advantages of having an outcome mindset and applying solid product management.
Bring real-world examples. You can even try bringing external speakers. Keep sharing knowledge.
2. Focus on results
Inspiration isn’t enough; you need to bring results.
Leadership won’t support you in changing everything at once, but they might support you on a small scale. Pick your battles wisely and bring results. This will bring confidence and help you change gradually.
3. Ask questions
Master the art of asking questions related to outcomes. Help your stakeholders move from solutions to problems, from outputs to outcomes, and from wants to needs.
This attitude will help you uncover critical aspects, focus on what creates value, and drop what doesn’t.
4. Ask for support
Any journey worth taking is a challenge, but it’s always easier if you have someone to support you along the way.
Find a mentor who is two or three steps ahead of you. Eventually, you might even try getting the company to hire a consultant to help you.
This part is more complicated, but start with the cards you can play with and then step up your game.
To be or not to be a product owner?
Being a backlog owner is limiting but safe. You can succeed as a backlog owner by doing what people tell you to do. If you fail, you can always blame them.
However, in my opinion, it’s not an inspiring career; it’s just a 9-to-5 job. You won’t make the world a better place as a backlog owner. A real product owner, on the other hand, can move the needle.
It’s going to be stressful. Your days will be like a rollercoaster, full of ups and downs. It’s not a 9-to-5; it’s an exhausting job that you will often think about long after working hours. But you will be motivated because you can connect your actions to improving people’s lives.
Make your choice and make the best of it.
Featured image source: IconScout
LogRocket generates product insights that lead to meaningful action
LogRocket identifies friction points in the user experience so you can make informed decisions about product and design changes that must happen to hit your goals.
With LogRocket, you can understand the scope of the issues affecting your product and prioritize the changes that need to be made. LogRocket simplifies workflows by allowing Engineering and Design teams to work from the same data as you, eliminating any confusion about what needs to be done.
Get your teams on the same page — try LogRocket today.