Portfolio Monitor
Multi-portfolio explorer with persona-contextual views for CIOs and portfolio leaders.
The Portfolio Monitor is the executive view, the surface a CIO or Portfolio Leader uses to understand the health of everything in flight. The earliest versions had three rows of controls. The brief from Sid (CEO) after v13: "less is more." That directive drove the next 23 iterations.
Before any of those iterations, there was a research foundation: who is this person, how do they actually spend a Monday, what do they need to see first, and why does every enterprise PPM tool get abandoned for Excel the night before the board meeting. That research is what follows.
The IT Portfolio Leader
Not a project manager. Not a delivery lead. A governance role, accountable for asking "are we doing the right things?" not "are we doing things right?"
Govern a large book of work to maximise delivered value, with no surprises. "Are we doing the right projects?" is always the question.
Being surprised by a failure in a board meeting. A number they can't defend. Strategic spend that delivered nothing.
No surprises. A defensible narrative. Faster invest, kill, and rebalance decisions. Board questions answered in real time.
Skeptical but open. Trusts transparent, bounded, reversible assistance. Will not bet their credibility on a black box.
Internal EPMO: dozens to hundreds. IT services delivery VP: accounts rolled up by vertical.
The data-gathering tax: reconciling Excel, PPM tools, Jira, and finance systems before every review.
Managing is doing projects right. Governing is doing the right projects. This feature is a governance instrument.
Governs internal change initiatives organised as a governance hierarchy.
50–300 active projects. Asks: are we aligned, on budget, delivering value?
Owns a delivery portfolio of client engagements, each with its own P&L.
1,000+ engagements. At this scale: exception-first, rollup-driven. No one reads 1,000 rows.
A day in the life
They don't open a tool because they're curious. They open it because something demands attention, or to prepare for a room where they'll be questioned.
Portfolio ops review. Walk reds and ambers. Assign actions.
Steering committee. Portfolio governance board. Financials review.
QBR. Re-prioritisation. Fund or defund decisions. Re-forecast.
Portfolio planning and budgeting. Strategic alignment refresh.
Information architecture, ranked
Not everything at once. Signal first, then synthesis, then summary, then drill-down. The density preference is a cascade, not a wall.
The missing dimension: temporal state
The portfolio is not one view, it's three completely different mental modes. This is absent from every current PPM tool. It's a major design opportunity.
Why current tools fail
Planview, Clarity, ServiceNow SPM, Jira Align: all powerful. All abandoned in favour of Excel the day before the board meeting.
The spreadsheet trap
Even orgs that own enterprise PPM tools export to Excel and PowerPoint for the actual review. The tool is built for analysts, not executives. The narrative can't be expressed in it.
Stale and distrusted data
Status is self-reported and lagging. Numbers conflict across systems. "The tool says green, but I know it's red." When data is doubted, no decision can be made from it.
Fragmentation
Portfolio truth lives across PPM, finance system, Jira, email, and spreadsheets. Reconciling them is manual, slow, error-prone, and repeated every governance cycle.
Alert fatigue vs. missed signals
Either too many undifferentiated alerts that train leaders to ignore them, or the one signal that mattered was buried in a table they didn't scroll to.
No narrative layer
The tool cannot tell the story. It shows tables and charts but cannot synthesise "here's what's happening and here's what it means." Hence the PowerPoint habit.
Configured for analysts, not executives
Heavy, deeply configurable, requiring training and analysts to operate. The executive who needs to decide is never the one who built the view, and they can tell.
Moving up the value chain
The shift from "show me the data" to "tell me what changed, why it matters, and what to do." Four rungs, and Tango needs to reach all four.
Here are your 1,000 projects. Here's their RAG status. The VP still has to scan, interpret, and connect the dots. All the cognitive work is theirs.
Here is your portfolio table with 847 rows.Since last Monday, 7 projects flipped red, 3 flipped green, 2 missed a milestone. The VP doesn't scan 1,000 rows, they look at 7 things.
7 programs changed status since your last review.Of those 7 that went red, 5 are isolated and recoverable. But 2 are connected: they share the same team lead. If she stays over-allocated, both miss Q2.
2 of those 7 share a dependency. One failure cascades.Option A: extend the lead's contract by 6 weeks, both projects recover. Option B: descope the Phase 2 milestone. Option C: pull a contractor from the bench. The VP decides; Tango did the investigation.
✦ 3 options ready. Tango recommends Option A. Your call.The trust contract
This persona is politically exposed. Every number they present, they must be able to defend. Tango's authority depends on three non-negotiables.
Cited evidence
Every Tango insight links to source data. The VP can click "why?" and see the milestone, the cost variance, the resource utilisation figure. They can read it out in the board meeting.
Confidence
Tango says "83% likely to miss Q2 if no action." That qualifier matters. They're not told a certainty, they're given a weighted signal to decide how hard to act on.
Human override
Tango drafts the decision. The VP owns it. Nothing happens automatically on fund, kill, or rebalance, the executive reviews, adjusts, and approves. Their name is on it.
The five core scenarios
When do they open the portfolio? What are they trying to accomplish? Design for these, nothing else is priority.
Orient after the weekend. Find what changed and what's at risk before the week begins. Fast, async, exception-first.
Walk the reds and ambers with the team. Decide corrective actions. Assign owners. Clear blockers. Requires drill-down to specific programs.
Where am I over-committed? What can I reallocate? Simulate a change: if we shift this team from X to Y, what happens to the portfolio?
Draft the state-of-the-portfolio narrative with evidence. Generate the deck. Make it defensible and ready the night before, not the morning of.
Answer a CFO or board question in real time, during the meeting. Pull the source data instantly. The number must be traceable in under 10 seconds.
Three design bets
These are the decisions that determine whether this feature beats Excel and PowerPoint, or becomes another tool people export out of.
Lead every view with a one-paragraph, cited "state of the portfolio." Tango writes it. The VP reads it. It is the wedge against the spreadsheet and PowerPoint default. If the VP can walk into any meeting armed only with this brief and be confident, the feature has won.
Support both the deep internal governance hierarchy (Portfolio → Program → Project → Demand) and the wide services account roll-up (Vertical → Account → Engagement). The same dataset, multiple views. A CIO and a delivery VP both get what they need from the same platform.
Every Tango recommendation shows evidence, confidence, and reversibility. Human confirmation gates on high-stakes moves. This is what converts a skeptical, politically-exposed executive into a daily user. Without this, any AI feature is decoration.
Not one screen. Three distinct purposes, each needing a different visual posture.
Signal-first exception feed and portfolio-health bento. Tango opens with the brief. The VP reads and orients, no scanning required.
Drill-down, what-if simulation, and action assignment. Tango proposes rebalances with evidence. The VP approves or overrides.
Auto-assembled, editable, evidence-linked board narrative generated from the live portfolio. Exportable, but also defensible live in the room.
The experience we're building toward
Not a chat interface. Not a traditional dashboard. A living briefing surface with a conversation layer, like a financial newspaper that knows you, updates in real time, and you can talk back to. Tango is the editor. The workspace is the publication.
The VP never stares at a blank interface or a wall of data. They read a brief that orients them.
The input lives inside the surface, not in a sidebar panel. Like the update input in Project Live, elevated to portfolio scale.
When the VP asks something, the content area reshapes around the answer. It doesn't add a chat bubble, it becomes the answer.
The VP can pin views, rearrange what's in their workspace, and decide what their brief emphasises. Control without requiring it.
"Tango's job is to be the VP's best analyst: one who already read everything, connected all the dots, drafted the options, and is waiting at 8am Monday with a one-page brief and three recommended moves, but who knows the VP is the one who signs off, and always shows their working so the VP can defend the call in any room."
One unified control bar replacing three rows, with dynamic portfolio headers.
Three rows of controls created visual noise that made the executive feel like they were operating a cockpit, not reading a portfolio. Collapsing to a single bar forced us to prioritise: what does a CIO actually need in the first 10 seconds? The header became the answer, changing based on which portfolio you're viewing.