I need to confess something to you.
The other day, I was talking to Suzanna, a Product Owner at a major tech company. She told me something that gave me goosebumps...
She had just handed in her resignation. After 6 years as a Product Owner.
Why?
"I just can't take it anymore," she said with tears in her eyes. "Every day new requests. Each one 'super urgent'. Sales selling things we can't possibly build. Stakeholders driving me crazy. I can't sleep anymore."
Sound familiar?
Your inbox is overflowing with "urgent" requests
Your development team looks to you for answers
Sales promises the impossible
You lie awake at night, haunted by decisions
You feel COMPLETELY overwhelmed
STOP RIGHT THERE!
Because what I'm about to tell you changes EVERYTHING.
You see, after 15 years in the field and coaching over 127 Product Owners, I've discovered a system.
A system so powerful, it works even in the most chaotic organizations.
It works so well that one of my clients, Peter, within just 3 weeks:
Got his backlog under control
Slept through the night for the first time in months
Finally learned to say 'no' to unreasonable requests
Earned respect from his stakeholders
AND got his weekends back!
"Too good to be true," you might think.
That's what Michelle thought too. She worked at a traditional company. Legacy software. Strong hierarchy. "This could never work here," she said.
Guess what?
Two weeks after implementing my system, she came to me with tears of joy. For the first time in YEARS, she had control. Peace. Overview.
Here's how your do prioritize your backlog:
Step 1: Plan Ahead
If you want more peace of mind, this is your key. The current sprint is set and remains active - you can't change it anymore. This means your focus should be on the next sprint. I always plan several sprints ahead. This gives you overview and peace of mind. This way you can effectively communicate with your stakeholders.
During the upcoming refinement, prepare everything so that during the planning session you only need to verify if everything fits.
Make it clear that everyone who submits a request must do so before the refinement. If it comes in later? Then it automatically moves to a later sprint.
Step 2: Create Space
Reserve 20% of your backlog, maybe even 30% in the beginning, for research items. This literally gives you space to examine things. These are spikes where you make time for investigation. Are we working on the right things? Do we have everything we need before we start X?
This space is also necessary for overrun and unforeseen issues. It's really about working smart rather than working hard.
Step 3: Prioritize
What are the objectives? What's the strategy? This is a useful method to work with. If there isn't one, create your own product strategy. Communicate this.
Based on this, you can respond to new requests by saying: "Look, this doesn't align with our goals or strategy."
Why is this item so important that we need it NOW?
If it's truly urgent, you can consider adding it to the next sprint's backlog. Usually, it's not that urgent.
Now you have 1 or 2 sprints planned ahead. You have space to handle problems. And you're already working with a proper intake process for new requests.
Step 4: Communicate
The next step is to communicate. Include this in your reviews. This way, all stakeholders who show any interest know what's coming. During the review, ask the following questions:
Am I missing anything?
Are there any items we need to take into account?
Is there anything I can add?
Does anyone have any suggestions?
Based on the answers, you can immediately determine whether to add items to the upcoming sprint or later. This creates immediate engagement. Your stakeholders know what's coming and what to expect.
Step 5: Further Planning
You can then outline in broad strokes where you're heading.
In the review, I position the roadmap as: Now, next, later.
Where we only discuss and review NOW. I personally work on Next and Later.
This makes it clear for everyone. Plus, if anyone has opinions about it, they can ask questions. Which is exactly what a review is for.
p.s. if this does help you. Let me know other topics.
I'm happy to write about them