Codeo (https://codeo.com.au/) operates in a complex environment where engineering velocity and project coordination are critical. Before implementing Leo, the organization faced challenges with “tribal knowledge” drifting over time—where critical project context and technical procedures were not documented and resided only in the minds of specific individuals.
1. The Challenge: Tribal Knowledge and Tool Sprawl
The project management team identified several friction points that hindered execution speed:
- Knowledge Loss: As teams grew and changed, critical company know-how was “walking out the door” when staff departed.
- Search Friction: Project Managers (PMs) and engineers spent excessive time “asking around” or searching through messy, scattered files to find approved runbooks and workflows.
- Security Concerns: Sensitive project data, particularly financial and security controls, were often spread across unmanaged tools, creating governance risks.
- Stale Documentation: The “current way we do things” was difficult to find, leading to outdated procedures being followed during release cycles.
2. The Solution: Implementing a Role-Aware AI Hub
Codeo implemented Leo to turn scattered documentation into a structured, usable system. The PM team leveraged Leo’s core capabilities to enforce a “metric-first” development approach.
- Role-Aware Guidance: Leo ensured that PMs, developers, and security leads only saw information aligned with their permissions. For example, PMs could access project budget data and timelines, while developers focused on technical documentation and release workflows.
- Execution-Focused Workflows: Instead of a simple Q&A bot, Leo was configured to surface current procedures and controls at the “moment of work”. This ensured that PMs could guide teams through approved runbooks for incident responses and release cycles.
- Data Sovereignty: Leo kept all project data within Codeo’s private infrastructure, ensuring compliance and security-first governance.
3. The Approach: Shifting Correctness Signals Early
Following a “staged migration” strategy similar to large-scale industry experiments, the project management team at Codeo migrated the most frequent “migratable” workflows into Leo first.
- Onboarding: PMs used Leo to shorten onboarding time, allowing new joiners to contribute from day one by providing immediate access to exact project context.
- Audit Readiness: PMs utilized Leo to improve month-end cycles and audit readiness by making finance procedures and control guidance easy to find and follow consistently.
4. Impact and Results: Quantifiable Productivity Gains
Drawing on metrics validated in large-scale technical environments, the impact of Leo at Codeo can be measured through Engineering Velocity and Search Efficiency:
- Reduction in “Diff Authoring Time” (DAT): By providing instant access to approved internal knowledge, Leo reduces the time engineers take to develop changes. Similar to findings at Meta, providing high-fidelity signals early in the development cycle can lead to productivity improvements ranging from 14% to 33%.
- Thousands of Hours Saved: By centralizing code-sharing frameworks and documentation, organizations can save thousands of DAT hours annually through the reduction of redundant efforts.
- Reduced Tool Sprawl: Leadership used Leo to replace multiple individual tool subscriptions with one secure team platform, significantly reducing costs.
- Documentation Vitality: Leo reduced knowledge staleness by making the “current way of doing things” the easiest path to follow, preventing documentation from becoming a static, unused resource.
Analogy: For a Project Manager at Codeo, using Leo is like having a universal GPS for the company’s brain. Instead of managers having to stop and ask for directions at every intersection (tribal knowledge), Leo provides real-time, role-specific turn-by-turn instructions (current workflows) that ensure everyone reaches the project destination faster and via the most secure route.
