Portfolio analytics

Open any tag to get a dashboard covering every project that carries it. This page explains what each panel is for, because a chart you cannot interpret is worse than no chart.

The gate wall and the headline counts sit at the top of the page. Everything else is behind the tab strip below them — timeline, risk, resourcing, distribution and blockers — with the projects table and the portfolio's comments underneath.

Headline counts#

How many projects carry the tag, and how their current gates are grading: on track, at risk, off track, and settled — plus the number of blocked tasks across all of them. The four gate counts and the settled count add up to the project total, so nothing is quietly missing from the arithmetic.

Question it answers: how big is this portfolio, and how much of it is in trouble?

Gate wall#

Every project a row, every phase a column, positioned by where it falls in that project's sequence rather than by name — a portfolio of projects built from different templates still lines up. Each cell names its phase and is coloured by gate readiness: passed, the one in flight, or not started yet. The gate score sits beside the project name, and the worst gate sorts to the top.

Question it answers: where is each project stuck, and is it the same place for several of them?

Reading down a column is the useful move. Several projects stalled at the same position means the constraint is that gate — a reviewer without capacity, a criterion nobody can meet — rather than the projects.

Distribution#

Two charts under one tab. Phase gate shows where every project sits against its gates — how far through its sequence each one is. Status shows the spread of project statuses: planning, active, on hold, completed, cancelled.

Question it answers: is this portfolio bunched at a particular gate, and how much of it is actually in flight as opposed to waiting?

A large planning segment usually means intake outpacing capacity. A growing on hold segment is the one to watch: paused projects still consume attention and still have deadlines.

Risk#

Projects scored on schedule and blocker signals, so the ones drifting stand out against the ones that are merely large.

Question it answers: which two or three projects actually need my attention this week?

Resourcing#

Two views of capacity: team workload — effort assigned per person across the portfolio, from task estimates — and project resource — how effort is distributed between projects.

Question it answers: who is over-committed, and where is the effort really going?

This is only as accurate as your estimates. If tasks routinely lack estimated hours, treat these as indicative. See managing tasks.

Portfolio timeline#

Every tagged project's phases laid against a shared calendar.

Question it answers: what lands when, and what collides?

This is the panel for launch-window conflicts — three projects whose final gate falls in the same fortnight, all needing the same approver.

Projects table#

The full list, sortable, with status, phase position, dates and owner. Where you go once a chart has told you which project to open.

Blockers#

Every blocked task across the portfolio, in one list.

Question it answers: what is actually stuck right now?

This panel is exactly as good as your team's honesty about the blocked status. If people leave work in in progress while it is waiting on someone else, this list is empty and useless. See dependencies.

Comments#

Recent discussion across the tagged projects, so you can catch up on a portfolio without opening each project.

Getting the underlying data#

Every number here derives from projects, phases and tasks that are all available through the REST API. If you need these figures in a board pack or a warehouse, pull them from there rather than reading them off the charts.