Portfolio Rollups

What this is for

Give product leaders one comparable view across products without asking every PM to rebuild a status deck.

When this helps

• Each product reports status in a different format.
• Leadership sees activity but cannot see where risk or customer pressure concentrates.
• Portfolio reviews spend the meeting reconciling numbers instead of making trade-offs.

How it works

When workspaces belong to the same organization, Specky aggregates their OKRs, at-risk OKRs, roadmap totals, in-progress and blocked work, open and high risks, and recent real signals. The rollup stays connected to the source workspaces rather than copying data into a separate report.

Before you start

• Two or more product workspaces in the same organization.
• Current OKRs, roadmap items, risk records, and real Product Graph signals.
• Consistent status fields where comparison matters.

What you should see

• Organization totals across products.
• A comparable row for each product workspace.
• Concentrations of blocked work, risk, or customer signal volume.
• A leadership-ready starting point for portfolio trade-offs.

Try it now

1. Attach the relevant product workspaces to the same organization.
2. Open Plan → Portfolio.
3. Read the organization totals first, then compare product rows.
4. Investigate products with concentrated risk, blocked roadmap work, or at-risk objectives.
5. Open the source workspace before changing a commitment; the rollup is a navigation and decision aid, not a replacement for context.
6. Record cross-product trade-offs in the Decision Log and reflect them in each affected roadmap.

A real example

Three products all report “on track,” but the rollup shows one product holds four of the organization’s five high risks and has two at-risk OKRs. Leadership moves one shared platform dependency before asking that team to absorb another initiative.

Your next move

Give each audience the right level of detail with Stakeholder Roadmaps.