Explore the model
The two essential LARA roles

Clear ownership without a new bureaucracy.

Someone must protect the meaning of organisational knowledge. Someone must make it usable. LARA makes both responsibilities explicit.

LARA Steward — Make learning trustworthy beyond the team.

The Steward helps valuable experience survive the team, tool or project that created it.

The Steward:

  • helps teams contribute knowledge with the context needed for reuse;
  • qualifies what becomes organisational learning;
  • protects meaning, relevance and traceability; and
  • challenges, updates or retires learning as evidence changes.

The Steward is not a documentation service. Teams contribute; the Steward governs what the organisation carries forward.

LARA Engineer — Make organisational knowledge usable at scale.

The Engineer translates LARA into structures and controls that work across the organisation.

The Engineer:

  • enables consistent capture, qualification and retrieval;
  • connects existing systems and ways of working;
  • preserves traceability, history and controlled change; and
  • keeps the solution sustainable across tools and platforms.

Professional implementation uses the licensed LARA system.

The Steward owns meaning. The Engineer enables the system.

Comparison of the LARA Steward and LARA Engineer roles
LARA StewardLARA Engineer
Typically client-sideOften supplied by an implementation partner
Works across teams and organisational boundariesWorks across process and technical boundaries
Governs what the organisation carries forwardEnables how knowledge is structured and sustained
Does not make the business decisionDoes not redefine organisational meaning

Decision-makers, sponsors, contributors and assurance functions keep their existing accountabilities. They are not additional mandatory LARA roles.

Explore the learning pathsBuild a LARA partner capability