Luka Lugaric
AI-enabled PMO

Less sifting.
More deciding.

I build AI-assisted PMO tools in iterations and tune them to what each programme needs. The manual work of sifting, summarising and organising information is almost completely gone. The time goes to reading, critical thinking and acting.

A worked example

From checkpoint meeting
to decision-ready view.

Illustrative only: an invented programme with invented data. Nothing on this page is sent anywhere.

What goes in

Checkpoint transcript Programme Atlas · Tue 10 Mar

Test lead Cycle 2 is 61% executed. We can’t start cycle 3 until the migration load for site B is in.

Data lead Site B has slipped. Master data cleansing needs another week, so the new date is the 19th.

Programme manager That pushes cycle 3 past the Gate 3 review on the 27th. Could we run cycle 3 in two waves?

Test lead Possible, but I need a decision by Friday to re-plan the testers.

Training lead Separately, trainer availability for the north region still isn’t confirmed. I’ll chase it by Wednesday.

Data lead I’ll send the revised load plan tomorrow.

Programme manager The cutover rehearsal venue was booked last week, so that action can close.

Workstream plan extract

Site B migration load12 Mar

Test cycle 3 start16 Mar

Gate 3 readiness review27 Mar

Open action log

A-009 Share interface test evidencedue 20 Feb

A-014 Book cutover rehearsal venueopen

A-017 Confirm trainer availability, northdue 6 Mar

What the tool does

  1. Reads the sourcesTranscript, plan and action log together.
  2. ExtractsActions, owners, dates and decisions raised.
  3. Matches and flagsChecks against the plan and the existing log. Flags conflicts and lapsed items.
  4. Waits for reviewI read, challenge and edit the draft before anything is shared.

What comes out

Run the example to see the output.

Decision neededReviewed

Run test cycle 3 in two waves?

Site B load moves from 12 to 19 Mar. A single-wave cycle 3 would run past the Gate 3 readiness review on 27 Mar.

Owner
Programme manager
By
Fri 13 Mar
Plan conflictReviewed

Site B migration load: 12 Mar → 19 Mar

Affects test cycle 3 start (16 Mar) and the Gate 3 readiness review (27 Mar).

Action logReviewed
  • NewA-018 Send revised site B load planData lead · Wed 11 Mar
  • UpdatedA-017 Confirm trainer availability, northTraining lead · Wed 11 Mar (was 6 Mar)
  • ClosedA-014 Book cutover rehearsal venueConfirmed booked
  • FlagA-009 Share interface test evidenceDue 20 Feb, not discussed. Confirm or close

Select an item to see where it came from.

What changes

The manual work goes.
The thinking stays.

Before

  • Sifting through transcripts, plans and logs
  • Summarising what was said and agreed
  • Organising it into something easy to digest

Now

  • Reading a prepared, traceable view
  • Critical thinking: challenging gaps and conflicts
  • Acting: decisions, escalations and follow-up
How I build these tools

Built in iterations.
Tuned to the programme.

01 /

Start from the programme’s needs

Each tool is shaped around the information this programme’s teams and leadership need, and the sources it already produces.

02 /

Iterate in use

I build in iterations and keep tuning the tool as the programme’s needs become clearer.

03 /

Keep a person accountable

Output is reviewed before it is shared. Applied where client permissions and data policies allow.

Want this on your programme?

Tell me what your teams spend time collecting and summarising today. We can discuss what a tuned tool could take over.

Discuss an engagement
Discuss an engagement