Think about the most experienced project leader in your company. The one who sees the problems before anyone else does.
Imagine that person was on every project you delivered, and on every project you will deliver. Every country. Every customer. Every failure. Every recovery. Remembers not just what happened, but why. This person never leaves and is always accessible.
Now imagine this person is actually everyone in your organization.
It's your collective project intelligence.
It's Colin.
Meet Colin
What are we working on?
Suggested for Aurora
Project
Aurora 400/220 kV substation
Files and sources
Recent outputs
Colin draws on
Your projects · Colin experience · PMI standards · Research
Where Colin brings value to your teams
Anticipate
Risk register and mitigation plan
Colin builds a sharper risk register that separates the standard from the first-of-a-kind, brings forward what teams tend to overlook, and links each risk to mitigation actions.
Your risk review starts from experience instead of a blank template.
Aurora, initial risk register · draft v1
| # | Risk | Lvl | Basis |
|---|---|---|---|
| R-01 | Ambiguous approval authority (cl. 3A), late customer approvals | H | Your contract |
| R-02 | Engineering scope incomplete at bid (SLD preliminary, spares missing) | H | Tender summary |
| R-03 | Civil subcontractor advance paid without guarantee | H | Your projects |
Detect
Early warnings
Colin recognizes the early signs of known failure patterns in what your teams report, and flags them while there is still time to act.
Warnings reach the steering meeting while the options are still open.
Risks & opportunities · the living register · last update today
| # | Risk | Lvl | Mitigation | Basis |
|---|---|---|---|---|
| R-24 | Rock at 1.8 m on the transformer bay, foundation works assumed soil new today | H | Foundation works review with the geotechnical engineer, decision by Oct 29 | Project documents |
| R-08 | Customer outage window unconfirmed, 11 weeks out new today | H | Written request to the utility, escalation to the business leader if no answer in 2 weeks | Lessons learned |
| R-25 | Civil subcontractor mobilized with 60% of planned crew new today | M | Site walk with the subcontractor's owner, revised mobilization plan | Lessons learned |
Solve
Problem solving
Issues worked through with Lean discipline, from framing to root cause to countermeasures that hold.
The fix addresses the root cause, not the symptoms.
Lean problem solving · Step 4 of 7 · Root cause analysis
Week 48 is now a date with a schedule behind it, confirmed in writing. Target part one met. Here is the cause picture for your confirmation.Problem record
Learn
Lessons learned capture
Tell Colin what happened. It asks the right follow-up questions, structures the lesson down to root cause, and captures what worked and what didn't, so the next project starts ahead.
Lessons are ready for the next bid before this project closes.
Lesson · L-08 · Delta Wind · waiting for approval
Never pay a subcontractor advance without a bond of the same amount
An intelligence layer