60 minutes to a better plan with Obo

What can you do to improve your product plan in just 60 minutes? A lot, actually. Plus, you’ll learn some great “pro tips” along the way.

With Obo, you understand, validate, and communicate clear choices based on expected impact of features against business objectives. Here are the four steps for improving your product plan in just 60 minutes:

Step 1: Set up your drivers

You’ll start using consistent business drivers to evaluate feature value.

  • Consistent drivers align the product team and stakeholders with business objectives.
  • Drivers are ranked by importance and weighted to reflect what matters most now to your business and product.

Step 2: Import feature candidates

You’ll import feature candidates with cost estimates and rate them using your business drivers.

  • Drivers are a “common currency” that helps you to resolve conflicting feature priorities – and any resulting political conflicts.
  • Feature value ratings can be based on stakeholder input and are clear to all, so product plan discussions focus on expected feature impact, not personal agendas.

Step 3: Rate features against drivers

You’ll create your first product plan scenario that shows you the highest-value combination of features that fits your budget/time constraints.

  • The optimal combination is computed using both value and cost of each feature.
  • You now have your first baseline for planning discussions.

Step 4: Create plan scenarios

You’ll create additional product plan scenarios that show you the highest-value combination of features that fits your budget/time constraints as well as other constraints, such as required features that you pin in or out. Feel free to create and compare additional plans, too. (Pinning features in and out and then clicking Optimize to see the results is especially fun.)

  • Compare what-if plan scenarios that you create in real time.
  • Easily see and communicate the impact of feature trade-offs.

Optionally, create a plan report from a scenario – including why you pinned features in or out, driver set you used, cost allocations, and more – by choosing Commit from that scenario’s More menu.

What’s next?

Now you can continue to improve product planning so you can put your best product forward™ with Obo:

  • Review Driver Sets and Drivers with the extended product team and executive leadership. Get clarity and buy-in up front on what matters most so your Drivers are aligned with business objectives. Modify them in Obo accordingly.
  • Import more features and rate them with colleagues. You may want to revisit the ones you rated the first time around too. This is a great way to get stakeholders involved. Instead of making a case for a particular feature, you’re all evaluating features against the criteria that matter most (and that you already agreed on).
  • Enter feature dependencies. Obo uses these when it creates plan scenarios.
  • Run a collaborative planning session. Create a new Planner, add your feature candidates, and review results with the product team. Try different Driver Sets.
  • Run internal surveys to validate feature value. The best place to start is by using Obo’s in-context surveys. From any feature’s Drivers tab, click Survey Stakeholders to run a quick survey and see how others rate that feature.
  • Use Obo Surveys to run a preference survey to your customers or your market.
  • Choose your best scenario and commit the product plan to get a plan report.

Ready to power up?

There’s more to Obo. Try compound feature costing – break down cost estimates by skill or team. Export your product plan to Jira. Invite colleagues to Obo so they can view your completed product plans and see the “why” behind product decisions.

You can read about product planning best practices and learn more about Obo here, at obo.pm.

Haven’t tried Obo yet? Sign up to request a 14-day trial and start making better product planning decisions in less than an hour.

Put your best product forward™ with Obo.

5 steps to sell your product plan to your stakeholders

Getting agreement on your product plans can be an uphill,...

Read More

Lies, damned lies, and the 4 levels of validation

Dante’s Inferno has nine circles of Hell. Fortunately, product...

Read More

Are idea portals a bad idea?

Idea portals aren’t a bad idea -- but they aren’t necessarily a...

Read More

Have a comment?