RightBuild blog

The job nobody can hold in their head

The RightBuild Catch-up report, showing a release past its date at the top followed by new Asks with AI summaries

Ask a product manager what they did yesterday and you'll get a pause. Not because they did nothing. Because they did forty small things, and most of them were someone else's idea.

A customer emailed about a bug. Sales wanted to know if the export feature is still coming in March. An engineer moved two tickets into the next release without telling anyone. Support asked a question on an old request that you meant to answer last week. The release that was due on Friday is still sitting there, not shipped, not canceled, just quietly late. And somewhere in the pile is a new request that looks a lot like one you already have, from a customer you really don't want to upset.

None of this is hard on its own. The hard part is that it all arrives at once, from different people, through different doors, and you are the one expected to remember all of it.

Six requests arriving at once from a customer, sales, engineering, support, the roadmap and a possible duplicate, all landing on one product manager

Why it gets away from you

Product management is a balancing act with no off switch. You are weighing what customers want against what the team can build. You are keeping leadership happy without promising things you can't deliver. You are trying to think about where the product should be in a year while also answering "is this a bug?" for the fourth time today.

The work that matters most, the thinking, the deciding, the saying no to the right things, needs quiet time. The work that shouts loudest is the stuff that lands in your inbox. So the shouting wins, and the important things slip.

Then come the small failures that hurt the most:

  • A customer asked you a question and you never replied. They noticed.
  • You sent someone questions about their request, and they answered, and you didn't see it.
  • A teammate changed the release notes and you shipped them without reading the new version.
  • A release went past its date and nobody said anything until a customer did.
  • Two people asked for the same thing, you logged it twice, and now the votes are split and neither looks important.

Nobody does this on purpose. You just can't hold it all in your head, and no one should have to.

Start the day with a list, not a guess

That's why we built the Catch-up report in RightBuild.

Every morning at 6am, in your own timezone, RightBuild looks across your workspace and puts together everything that needs you. If there's something on it, you get an email. You open it with your coffee and you know exactly where you stand before the first meeting starts. If there's nothing to do, you don't get an email. We're not going to fill your inbox to prove we're busy.

It isn't a feed of everything that happened. It's a worklist. Things that need a decision are at the top, things worth knowing about come after, and sections with nothing in them get out of the way.

The Catch-up report as a morning worklist, with items that need a decision at the top and items worth knowing about below

What it keeps an eye on for you

Releases past their date. Anything that should have shipped by now but hasn't been marked as shipped or canceled goes right to the top, with the Asks inside it. Either ship it, cancel it or give it a new date. Do any of those and it drops off the list.

New Asks. When a customer or a teammate raises a request, RightBuild reads it, writes a short summary and gets it ready for you to accept or dismiss. You don't have to read every word of every request to know what it's about.

Clarifying questions. Plenty of requests are too vague to act on. RightBuild drafts the questions you'd want to ask the person who raised it. You check them, tweak them if you like and send them. Any questions put to you by others show up here too, so nothing sits unanswered.

Waiting on a response. Once you've sent questions, the report remembers that you're waiting. When the customer replies, you'll see their answer in the next morning's report, so you're never left chasing replies that already came in.

Potential duplicates. If a new Ask is asking for the same thing as an older one, RightBuild points it out and says why. Link them and the votes stay together, so the real demand shows up properly.

Product value suggestions. As votes come in and you learn more, the right priority for an Ask changes. RightBuild suggests a score and explains the reasoning. Accept it, change it or ignore it. You make the call.

Feature tree suggestions. Requests that aren't attached to any feature are easy to lose. RightBuild suggests which feature in your feature tree each one belongs to, and when a few requests point at something you don't have yet, it suggests a new feature for them.

Release notes updated. If someone else changes the notes for a release, you see what changed and who changed it, so nothing goes out to customers that you haven't read.

Roadmap moves. When a teammate moves an Ask to a different release, or shifts something between Now, Next and Later, you'll know. You can see how many votes and companies it affects, and if it shouldn't have moved, you can put it back in one click.

Comments. New comments and replies on Asks, from anyone but you. Reply in the thread and it counts as read. No extra step.

Billing. If your plan is about to change and something needs choosing, it shows up here so it doesn't catch you out.

It clears itself as you work

This is the part people tend to like most. You don't tick things off the Catch-up report. You just do the work.

Answer the question on the Ask page, and it's done on the report. Ship the release from the roadmap, and it's done. Reply to a comment from wherever you happen to be, and it's done. The report keeps up with you, not the other way round. Each item tells you how it was settled: "Answered", "Replied", "Marked as shipped", "Move reverted", so you can look back and see what you got through.

Catch-up items settled as the work gets done, labeled Answered, Replied, Marked as shipped and Move reverted

And if new things land during the day, RightBuild tells you how many are waiting. You choose when to pull them in, so your list doesn't change under you while you're halfway through it.

Make it yours

Not everyone on the team needs every section. If you own the workspace but look after operations, you probably don't care about feature tree suggestions. Turn that section off and it stays off. Turn it back on whenever you like. And if you'd rather check the report yourself than get the morning email, switch the email off. The report is still there waiting for you.

Getting back on top

Being a product manager will always mean juggling. That isn't going away. But the juggling shouldn't depend on your memory, or on how many tabs you have open, or on how good your week has been.

The Catch-up report gives you one place to start every day. It tells you what is late, who is waiting on you, what changed while you weren't looking, and where RightBuild thinks you could make a better call. Then it gets out of your way so you can do the part of the job that actually needs you.

Open it in the morning. Work down the list. Get on with your day knowing nothing has slipped through.

← All posts

Spend the week on product, not admin

Create a Workspace on the Starter plan and let RightBuild keep the roadmap current while you run the product.

Sign up