Category

Team knowledge

Decisions, onboarding and shared memory for teams that move fast.

Retire old knowledge without erasing why a decision was made

Give customer interviews a useful life beyond the transcript

A shared glossary can prevent surprisingly expensive AI mistakes

Keep product requirements current while the work is changing

Make incident reviews useful to the next person on call

Give every important document an owner, not just an author

Build a project kickoff brief that survives the first meeting

Company knowledge needs an expiry date

One source of truth for an AI-first team: a list of current decisions, each with an owner and a source.

A single source of truth for an AI-first team

Knowledge silos in the AI era: sales, product and support teams each holding a different answer.

Knowledge silos in the AI era, and how to break them

Write docs your AI can actually use: an AI-readable refund policy doc with the decision, owner and scope.

How to write docs your AI tools can actually use

Async decisions for remote teams: a decision thread on the launch date, marked decided, with the team who weighed in.

Async decision-making for remote teams that use AI

Turn one person's best prompt into a skill the whole team can use

What leaders should know about the AI their teams use

The handover problem: keeping context when people change roles

Meeting notes are not memory: from transcripts to decisions

A shared brain for your team: what it is and how to start

How to keep a decision log your team will actually use

Onboarding with AI: give new hires context on day one