Status
Where things stand.
Team Lipi landed at O&M 2026 and completed the WHY–WHAT–HOW architecture. Six pillars, each with a lead. The Project Elevate teams are building. Halfway along, and moving.
Signals and metrics from the January 2026 review
Baseline: January 2026.
Form, not color.
Every state on this page reads from its outline. No traffic lights.
- Done Filled. Done and standing.
- Moving Outlined. Under way, not finished.
- Waiting Dashed. Owed, or not started.
- Broke Terracotta outline. Exists, but not connected.
Three initiatives.
How each layer of the architecture is holding.
- Why
Project ONE
EstablishedSix pillars defined, each with a lead. The Foundation Document is complete. The vision of 'one digital language' is clear.
- What
Team Lipi
IntroducedIntroduced at O&M 2026. Concept document, implementation roadmap and all frameworks are done. Pilot team selection and first sessions are next.
- How
Project Elevate
ActiveTeams are experimenting with AI tools and building. The learning mindset is forming, but direction on what to build is missing. That's Team Lipi's job.
Pillar signals.
Honest states in words, not percentages — as of the January 2026 review.
- 01
ONE Data
ProgressNew software feeds into Spine. Teams are thinking through data integration.
- 02
ONE Process
Some progressThe AND Team runs workflow automation through its Project Elevate stack. ClickUp–Spine integration exists.
- 03
ONE View
Exists but disconnectedTableau dashboards exist but aren't centrally connected.
- 04
ONE Voice
Trainings happenedChatGPT training has happened, but unified digital thinking isn't embedded yet.
- 05
ONE List
MovementProject Hyperlink is one example. More coordination needed.
- 06
ONE Earth
SlowestGlobal urgency around AI adoption has crowded out sustainability.
Project Hyperlink
An AI-powered compliance framework (GMP Online) linking every law and guideline to specific Venus SOPs. Presented at Automa+ Vienna 2025 as an industry first. The cultural impact showed in a successful RBI audit.
The pilot, step by step.
The Team Lipi pilot in three movements, from the first session to the final call. All of it owed, so all of it dashed.
- 01
Start
- Finalize Team Lipi pilot participants
- Schedule first Team Lipi session
- Select first department focus area
- 02
Build
- Conduct first 2–3 Team Lipi sessions
- Produce initial workflow audit
- Identify top automation opportunities
- Begin first quarterly roadmap
- 03
Evaluate
- Complete Team Lipi pilot (8 sessions)
- Produce first quarterly roadmap
- Hand requirements to Project Elevate
- Evaluate pilot success
- Decide: continue, pivot, or discontinue
Metrics to track.
| Metric | Baseline · January 2026 | Target |
|---|---|---|
| Team Lipi sessions held | 0 | 8 |
| Quarterly roadmaps produced | 0 | 1 |
| Requirements handed to Project Elevate | 0 | 3–5 |
| Tools being built | Several (ad hoc) | 2+ (from roadmap) |
| Team Lipi attendance rate | N/A | 80%+ |