The destination is capability, not documentation
Knowledge existing somewhere does not mean people can use it. A process being documented does not mean judgment has transferred. Training attendance does not automatically mean learning, and learning does not automatically survive contact with the workflow.
METIS connects five areas of work that are often treated separately: Map Knowledge, Extract Expertise, Transfer Capability, Integrate Systems and Scale Performance.
The framework helps identify what knowledge drives performance, capture the reasoning and exceptions behind expert work, build learning and practice, embed knowledge into real tools and moments of need, and review whether adoption and performance are improving.
Not every project needs every stage at equal depth
- A knowledge-system project may emphasize Map, Extract and Integrate.
- An onboarding project may emphasize Map, Transfer, Integrate and Scale.
- A documentation-adoption problem may involve strong Extract work but weak Integrate.
- A broader founder-dependence or capability engagement may use the full progression.
Connected, iterative and grounded in real work
METIS is not five packages and it is not a rigid waterfall. Work can move back and forth as gaps become visible. Performance and adoption feed learning back into the map, the knowledge assets, the learning design and the systems that support execution.