πŸ“‘ Delivery Risk Radar

Can patterns hidden across everyday project meetings provide early warning that an important project, program or contract is unlikely to be delivered as expected?
Delivery Risk Radar (DRR) is a concept currently being developed as part of the broader exploration at Who Verified This? into trusted AI-generated business information.

From Meeting Governance to Delivery Intelligence

Who Verified This? began by examining a fundamental governance question: when AI converts human conversations into transcripts, summaries, commitments and business records, how can organizations know that the resulting information can be trusted?
Delivery Risk Radar explores the next question:
Once meeting information can be captured and analyzed, can AI identify emerging evidence of delivery problems before those problems become obvious in conventional project reporting?

The Concept

Important projects generate conversations across project reviews, supplier meetings, technical discussions, steering committees and management meetings.
Individually, many comments may appear insignificant. Across multiple meetings and over time, however, they may form a meaningful pattern.
Teams Meetings β†’ AI Analysis β†’ Evidence Over Time β†’ Emerging Delivery Risk
DRR is being designed to understand these patterns rather than simply summarize individual meetings.

First: What Must Be Delivered?

Risk has little meaning without context.
DRR therefore starts by establishing what successful delivery means for the particular project, program or contract.
This can include:

  • Expected outcome
  • Final delivery date
  • Major milestones
  • Critical dependencies
  • Critical assumptions
  • Constraints
  • Key decision or stage gates
  • Budget or cost boundaries

These provide the context against which subsequent meeting discussions can be assessed.

Then: What Should Worry Us?

DRR looks for emerging evidence that conditions affecting delivery may be changing.
Examples include:

  • Schedule slippage
  • Cost pressure
  • Dependency failure
  • Supplier problems
  • Resource shortages
  • Scope change
  • Milestone uncertainty
  • Assumptions becoming invalid
  • Unresolved decisions
  • Repeated commitments not completed
  • Conflicting views of project status

Why Meetings?

Formal project reporting often records what the organisation already knows.
Meetings may contain earlier signals:
β€œWe may need another two weeks.”
β€œThe supplier still hasn't confirmed the interface.”
β€œWe're assuming approval will arrive before testing starts.”
β€œWe've moved that milestone again.”
None of these statements necessarily represents a significant delivery risk on its own.
The pattern across meetings may be much more important.

Not Sentiment Analysis

Delivery Risk Radar is not intended to determine whether meetings are positive or negative, count keywords, or score individual participants.
The objective is deeper:
Understand discussions in the context of an expected delivery outcome, accumulate evidence across meetings, and identify whether successful delivery appears to be becoming less likely.

Building in Public

Delivery Risk Radar is currently a design and proof-of-concept project.
The concept is being shared while it develops so that project, program, delivery and governance professionals can challenge the assumptions before they become product features.
The objective at this stage is not to present a finished solution.
It is to determine whether AI can provide executives and delivery leaders with something genuinely valuable:
Earlier evidence that an important project, program or contract may not be delivered as expected.