Download free

Home / Use cases / Onboarding

TEAMS

Replace "ask someone" with a path through the context.

Good onboarding explains not only what exists, but how the pieces fit together.

The problem

New people learn the organization by interrupting the people who already know it. The path exists, but only as conversation.

What goes in the repository

  • First-week path
  • Glossary
  • Product context
  • Architecture
  • Team conventions
  • Important decisions
  • Common questions
onboarding/
├── index.md
├── week-one.md
├── product.md
├── systems.md
└── glossary.md

Why an open repository helps

A curated path through the repository is something a new teammate can follow without waiting for the right person to be free.

How Okide helps

Okide turns that path into linked files, so onboarding stays attached to the product, systems and glossary it points at.

Humans and agents, same files

New people and newly introduced agents can follow the same curated path into the organization.

OPEN BY DEFAULT

Keep the repository. Change the tools around it.

Asking someone still works. It should not be the only map. Okide helps you work with the repository without turning it into an Okide-only format.

Learn about Open Knowledge Format → Download Okide — free

Related use cases

TEAMS

Team handbook

Write down the defaults so the team stops re-explaining them.

team/handbook.md

Explore →

COMPANIES

Company knowledge

Build institutional memory the organization can keep.

company/principles.md

Explore →

TEAMS

Project knowledge

Give every contributor the same context.

projects/atlas/index.md

Explore →