Signals, not slideshows

Article Oversight & portfolio view ~8 minutes

When leadership only sees screenshots rebuilt every Thursday, oversight depends on the analyst’s overtime. Better programmes prefer persistent signals — KPIs and lists that come from the same registers the field uses — so “red” means something a supervisor would also recognise.

Slideshows are useful for narrative and stakeholder theatre. They are a poor exclusive brain. Copy-paste packs lag reality, invite vanity metrics, and turn colour into decoration when nobody can open the list behind the tile.

What good practice looks like

Signals beat festivals of slides when:

• Dashboards read live project truth — or near-live — from operational registers.
• Drill-down lands in the module that owns the problem, filtered to the rows that caused the colour.
• Portfolio views compare projects without five incompatible packs.
• Status language matches what site supervisors recognise — open means open.
• Manual narrative explains exceptions; it does not invent the counts.
• Refresh habit is weekly (or better), not only pre-steer.

PMO frameworks talk about single sources of truth and exception-based management. Site translation: if the tile cannot open the list, it is a poster.

Good practice still uses packs for decisions that need story. It refuses to wait for pack night to discover yesterday’s overdue pile.

Where projects slip

• Vanity metrics that move while risk stays still.
• Manual copy-paste packs that lag reality by a week.
• Red/amber/green without the list behind the colour.
• Different definitions of “open” between contractor, client, and PMO.
• Analyst heroics that collapse when someone is on leave.
• Leadership rewarded for slide beauty over signal honesty.

The cost is late sight. By the time the screenshot is perfect, entitlement conversations have already started on facts the pack almost showed.

How Cynilo supports the practice

Project and portfolio dashboards roll up from the work — so oversight can be a habit, not a monthly festival of slides. Tiles are doorways into filtered truth. Help How-tos cover reading the boards. Learn’s line beside Seeing the whole programme without drowning in noise: signal first, story second.

What good looks like in a week

On a programme that prefers signals:

• Monday skim finds pressure before Thursday pack build.
• A red tile opens a list someone can work.
• Pack preparation starts from signal, then adds narrative — not the reverse.
• Definitions of overdue are shared enough that meetings do not begin with translation.
• Leave cover still works because the dashboard is not trapped in one laptop’s PowerPoint.

The weekly test: can a director explain last week’s top three pressures from live tiles without waiting for a rebuilt pack? If not, slideshows still own foresight.

A short story from a client PMO

A client PMO prided itself on beautiful monthly packs. One month a package’s quality “green” hid a rising unverified-closed pattern the register already knew. The pack author had smoothed the story for readability. When a snag wave hit, leadership discovered the register had been louder than the slide for weeks.

The rule changed: pack colours must cite the live tile and link the filter. Smoothing became an explanation of residual risk, not a silent edit of counts. Signal trust rose. Pack meetings got shorter because argument started from shared lists.

Closing

Persistent signals respect everyone’s time. Next is agreement that one job has one primary rollup — so client and contractor stop arguing about which masterpiece is real.

Previous: Seeing the whole programme without drowning in noise