Five product squads, five reinvented wheels — until they shared a workflow.
A services company with five squads each running their own AI-assisted experiments. Different repos, different conventions, no shared lessons. Praxis engagement: org-wide template, shared agent library, internal documentation portal, and a dedicated handover lead.
Situation
A services organisation had five product squads, each five to ten people. Two were strong engineering-led teams already shipping with confidence. Three were domain-led: people who knew their customers cold, building with AI tools without a developer on the squad. Each team had drifted into its own conventions, its own quirks, its own deployment story. Lessons learned in one squad never reached the others.
The CTO had tried to address it twice before with internal docs and a wiki. Neither stuck — by the time the docs were written, the world had moved on, and nobody on the front line had time to maintain them.
What we installed
A Praxis engagement, run from the strongest of the five squads outward. Org-wide template and conventions: every new repo across the organisation now starts from the same base. Shared agent library, so a planner agent improved by one squad becomes available to the others overnight. Internal documentation portal that lives next to the code rather than next to the wiki, keeping it in front of the people writing the changes.
A dedicated handover lead from our side stayed with the rollout for the full quarter. Each squad got a tailored Discovery week and a Build phase that matched their starting point — Vector-shaped for the engineering-led teams, Axis-shaped for the smaller domain-led ones, all on the same shared template.
Results
- Five squads on the shared workflow inside one quarter
- One template now governs every new repo across the org
- Cross-squad code review and agent improvements actually happening, organically, post-handover
- Quarterly review cadence keeps the workflow current as AI tools evolve
Builder’s insight
The risk in an org-wide rollout is doing the same engagement five times. We didn’t. The shared layer — template, agent library, documentation portal — was the constant. The shape of each squad’s install was a variable, picked by the squad and the handover lead together. Standardising the substrate while letting each team keep its character is what made it stick.
Multiple teams reinventing the same wheels?
A Praxis engagement gives the org one shared workflow without flattening how each team works.
or email us at alex@norai.com.au