CKO - Chief Knowledge Officer
Executive responsible for how a company keeps and passes on what it learns: documentation, post-mortems, onboarding, training and the tools that hold all of it.
A Chief Knowledge Officer owns the question of what happens to a company's experience once a project ends. In practice that covers documentation and where it lives, post-mortems and whether anyone reads them, onboarding material for new hires, internal training, and the search and wiki tools that hold the result.
In game development the problem is concrete. A production runs for years, a team grows and shrinks around it, and much of what was learned about an engine, a pipeline or a platform submission sits with individual people. When they move on, the next project pays for the same lessons again.
The title is rare in this industry. Studios usually hand the work to a Technical Director, a Development Director or a producer, and larger groups put it under HR or operations. Where it does exist as its own position, it tends to be at a publisher or a group with several studios that are meant to share practices.
CKO - Chief Knowledge Officer profiles (1)
