Deck 25 · Project Management

OMX Innovation · Deck 25 · Project Management

A project management tool that fits OMX — same Lens design, same Snowflake stack — for ~$30k/yr less than the packaged platforms.

Tier-1 to tier-4 projects, EPMO governance, status that ladders to ExCo, one place for the work.

01 / 06

Why now

The wedge.

OMX runs a multi-tier project portfolio — Quick Tasks through full Enterprise Initiatives (memory: EPMO 4-tier governance protocol)
Packaged tools (Asana, Monday, Jira, ClickUp, Smartsheet) at OMX scale = $20-50k/yr — and most features are unused; teams pick their own tool, no rollup
The fit-for-OMX build is light: project shape + status + governance gates + ExCo rollup — same Lens + Snowflake + Postgres pattern
$30k/yr saving baseline vs packaged-tool alternative
Aligns to existing EPMO protocol — Tier 1 (Quick Task) / Tier 2 (Standard) / Tier 3 (Complex) / Tier 4 (Enterprise) — tool enforces the right ceremony per tier

02 / 06

What this covers

What's in scope.

01

Project shape

fields, milestones, owner, RAID, status — sized by tier

02

EPMO governance gates

tier-aware ceremony (Tier 1 = minimal, Tier 4 = full gating)

03

Portfolio rollup

ExCo / Steering Committee view of in-flight initiatives

04

Status reporting

RAG ratings, blockers, decisions needed

05

Resource view

who's on what; flag over-allocation

06

Dependency map

projects that block / are blocked by others (cross-deck context — many of these 21+ ideas have dependencies)

03 / 06

The problem

What's broken.

01

Tool fragmentation

every team picks their own; no rollup

02

Tier mismatch

Quick Tasks weighed down by Tier-4 ceremony, or Tier-4 initiatives run with Tier-1 rigour

03

No portfolio view

ExCo can't see in-flight initiatives in one place

04

Status reports are PowerPoint

manually assembled, days out of date

05

Knowledge lost

project ends, lessons-learned lost to email

06

Dependencies invisible

Project A waits on Project B; nobody surfaces it

04 / 06

The benefits

The value story.

Lever

Mechanism

Sizing

Annual reclaim vs packaged

Asana/Monday/Jira/ClickUp $20-50k → fit-for-OMX

~$30k/yr saving baseline

EPMO governance enforcement

Tier-aware ceremony built in

Right rigour for the right work

ExCo portfolio visibility

One rollup view

Faster decisions, less status-pack effort

Status report capacity

Auto-generated vs PPT-assembled

Hours per week per project lead reclaimed

Lessons learned compounding

Knowledge feeds Deck 21 + Deck 18 engines

Year-over-year capability lift

05 / 06

The ask + roadmap

What we need.

Now

Cover

project lead at console with portfolio rollup + status RAGs; calm + organised

P2

Problem vector grid (4)

: Tool-fragmentation / Tier-mismatch / No-portfolio-view / Status-by-PPT

P3

Headline saving

$30k/yr call-out tile

P4

Tier mapping

Tier 1-4 with corresponding ceremony / fields / artefacts

P5

Portfolio view mock

ExCo dashboard of in-flight initiatives + risk + dependency

Audience

Primary: CEO/GM + COO + Head of Strategy + EPMO Lead. Secondary: Project leads + Tier-2/3/4 initiative owners. Tertiary: ExCo (consumes portfolio rollup).

References

Memory: EPMO Operating Protocol (D:\10-CONTROLLER\jarvis\config\epmo-operating-protocol.md) — the 4-tier governance + RUN/BUILD mode framework this tool implements
Memory: Adaptive Governance — Tier 1 Quick Task / Tier 2 Standard / Tier 3 Complex / Tier 4 Enterprise (CLAUDE.md)
Memory: Project Steward supervisor + 15 specialists (CLAUDE.md) — the agent layer that uses this tool
Memory: Document Production Capabilities — python-pptx + auto-export pattern (D:\10-CONTROLLER\jarvis\docs\DOCUMENT-PRODUCTION-CAPABILITIES.md)
Memory: Deck 21 Strategic Deep Dives — lessons-learned feeds the library

06 / 06