PM Portfolio › Case 01 › PMO Idea Tracker · Decision System
← Back to portfolio
Case Study 01 · PMO Idea Tracker · 2026

PMO Idea Tracker: from scattered submissions to a monthly leadership decision artifact

A working walkthrough of the PMO Improvement Idea Tracker. One Google Form, one deterministic priority formula, one 8-tab leadership workbook, and one monthly review cadence. Built so the dashboard is a side effect of doing the work, not a separate reporting step.

Owner · Lead PM, PMO Time-to-launch · 3 weeks end-to-end Scale · 9 ideas · 7 PMs · 4 approved Q1 Cadence · Monthly leadership review

The five-stage path, at a glance

01
The Problem
No intake
Slack · email · 1:1s
02
The Insight
One form, one formula
Impact + Effort scored
03
The Build
8-tab workbook
Pipeline · OKR · Log
04
The Outcome
Leadership dashboard
Decision-ready artifact
05
The Compounding
Cadence holds
Same template, every month
01
The Problem · Submissions without a system

Slack, email, and 1:1s as the intake

PM improvement ideas surfaced in three places at once. None ranked, none tied to a review cadence. The good ones drifted alongside the noise.

Before the tracker · 3 channels, no destination
No single inbox · no shared ranking · no cadence to land in

What it looked like

  • Ideas raised in Slack channels, 1:1s, and email. No single inbox.
  • Leadership saw a fraction. The rest died in the conversation they started in.
  • Review meetings drifted into "we'll talk about it next month."

The trigger to fix it

A leadership review opened with "what's in the pipeline?" — and the honest answer was a Slack thread. If we couldn't show the pipeline, we didn't have one.

Lesson from Stage 1
A pipeline you can't see isn't a pipeline.
02
The Insight · Run the PMO like a product

One form, one formula, one cadence

Treat the PMO operation as a product. Deterministic intake, deterministic ranking, deterministic review. Stop debating priority. Define it.

Form schema · 10 fields

Submission intake

01Email addressauto
02Timestampauto
03Idea titletext
04Current challengelong text
05Proposed improvementlong text
06Primary benefit categorydropdown
07Estimated impact1 — 5
08Estimated effort1 — 5
09Time sensitivitydropdown
10Supporting documentsattach
Priority Score
ROUND( ( Impact + ( 6 − Effort ) ) / 2 , 1 )
Scale 1.0 to 5.0. High impact + low effort = highest priority. No subjective debate at the review.

Design principles

  • One intake. No matter where the idea was raised, it has to land in the form to count.
  • One formula. Priority Score is deterministic. Reviewers can disagree with the inputs, not the math.
  • One cadence. Monthly review on a fixed date. The pipeline gets read whether anyone "feels like it" that month.

Why deterministic ranking matters

  • Removes the "loudest voice wins" effect of ad-hoc intake.
  • Creates an auditable record — which scoring patterns predict approval, and which don't.
  • Makes "no" defensible. Low-score ideas get queued by formula, not killed by personality.
Lesson from Stage 2
A formula isn't the end of debate. It's the start of an honest one.
03
The Build · The 8-tab leadership workbook

Form, pipeline, dashboard, log

The Google Form feeds an 8-tab leadership workbook. The Idea Pipeline tab is the master sheet. Every other tab is a lens on the same data, so the dashboard never goes out of sync with the underlying pipeline.

Workbook navigator · 8 tabs
📥 Idea Pipeline
Master sheet. Form responses paste in. Priority Score auto-calculates. Leadership stamps Status, Owner, Quarter.
📊 Dashboard
KPI tiles, approved-ideas callout, status breakdown, quarterly distribution, top ideas by score.
👤 Individual Tracker
Per-PM scorecard. Submissions vs approvals, approval rate, approved-idea detail.
🎯 OKR & KPI Tracker
3 measurable KRs per approved initiative. Target / actual / percent.
🗺️ 2026 Roadmap
Monthly Gantt view of every initiative across the year.
📅 Monthly Review
Leadership review log. Every cycle leaves a row: ideas reviewed, decisions, action items, owners, next steps.
📋 Instructions
Workflow guide. Anyone can run the cadence from this tab alone.
⚙️ Config
Dropdown source lists. Statuses, benefits, owners, quarters. Single point of update.

How the tabs connect

  • Idea Pipeline is the master. Every other tab pulls from it via formulas. No second source to keep in sync.
  • Status change cascades. Approved appears on three tabs at once. Completed increments the KPI tile.
  • Monthly Review log writes one row per cycle: decisions, action items, owners, next steps.

The OKR mechanism

  • 3 KRs per approved initiative with target, actual, and percent.
  • OKR overall percent is a simple mean across KRs. Visible in one cell.
  • An initiative drifting below pace surfaces on the dashboard before the next review.
Lesson from Stage 3
Make the dashboard a side effect of the work, not a separate report.
04
The Outcome · A decision artifact, not a meeting

The dashboard that runs the review

KPIs at the top, monthly trend and status distribution beneath, value mix on the side. The leadership review now opens with a tab, not a thread. Decisions get made on the page.

Team innovation scorecard with eight individual contributor donut scores for Q2 2026, showing per-PM submissions, completions, average impact, and quick wins
Innovation scorecard · Q2 2026 · per-PM contribution at a glance

What's on the dashboard

  • KPI tiles. Total, completed, average priority, contributors, quick wins. Each carries a prior-period comparison.
  • Monthly Submission Trend. Cumulative line + monthly bars. Shows whether the pipeline is alive month to month.
  • Status + Value mix. Donut shows where ideas stick. Radar surfaces benefit-category blind spots.

How leadership uses it

  • Read the KPIs. Spot the change. Decide on the page.
  • Drill in only when a number surprises — one click to the underlying pipeline.
  • Decisions logged in the Monthly Review tab same session. No "we'll send notes after."
PMO Innovation and Idea Tracker executive dashboard showing KPIs, monthly submission trend, status distribution donut, and value category mix
Executive dashboard · KPIs · monthly trend · status mix · Q2 2026
Lesson from Stage 4
Replace meeting reading with a decision-ready artifact.
05
The Compounding · Same template, every cycle

The cadence holds across teams

When the system runs itself, the patterns become visible. The pipeline table, the team scorecards, the roadmap, the matrix — all updated from the same source. Each lens reinforces the others.

What compounds, and why

  • Distribution insight. The Ideas by Business Area chart shows where the team's energy concentrates. The Impact vs Effort matrix shows where the high-leverage ideas live.
  • Time view. The Monthly Roadmap turns the pipeline into a year-long picture. The cadence becomes a shape you can see.
  • Same template, every cycle. The KPIs, the trend, the scorecards, the matrix, the roadmap — all updated from the same source. One cycle is an event. Twelve is a system.
Ideas by business area bar chart on the left, impact versus effort bubble matrix on the right
Distribution view · ideas by business area · impact vs effort matrix
Monthly roadmap 2026 showing initiative status across all twelve months with discovery, in progress, review, complete, and planned pills
Time view · monthly roadmap 2026 · all initiatives
Lesson from Stage 5
One cycle is an event. Twelve is a system.

What this case shows about how I work

The PMO Idea Tracker didn't solve a tool problem. It solved a decision problem. The build was a Google Form and a workbook; the work was making the cadence stick and the artifact decision-ready. Tools are easy. Cadences are hard.

Design for the decision

The dashboard isn't a report. It's the artifact the decision happens on. Every element earns its place by what decision it supports.

Deterministic before debate

Impact and Effort score. Priority computes. Disagreement moves up one level, from "is this important?" to "did the PM score it right?" That's a faster conversation.

Cadence as the product

The system runs whether or not the moment feels right. Twelve identical cycles in a row is what compounds into an operating rhythm.