Skip to main content

Start Your Company Bible

(aka Organizational Wiki)

A systematic process for building a comprehensive company "bible" that captures and documents successful practices as your business grows, transforming tribal knowledge (unwritten know-how stored in people's heads) into scalable organizational intelligence.

In the age of AI, there's no excuse for not institutionalizing your wins: the specific practices that got you to the point where you can scale by hiring new people.

Practitioner-scale version

If you're an individual practitioner or leader who wants to start smaller before running an organizational rollout, see the practitioner playbook Start Your Wiki. It covers the same fundamentals at a personal scale and explains how entries graduate from a personal wiki into an organizational one once they've earned their place.

Personal and Organizational Wikis​

Both individuals and organizations can have wikis. Both can have private wikis and wikis scoped to specific audiences (team-only, advisor-only, public). A "company bible" is one specific, high-gravitas variant: the organizational wiki that every human and AI agent in the company operates from.

The practical relationship between personal and organizational:

  • Personal wiki is where a leader plays with ideas, develops vocabulary, and tests concepts informally with colleagues before committing the organization to them.
  • Organizational wiki (the company bible) is the contract. Every entry is a commitment the organization stands behind.

Ideas graduate from personal wiki to organizational wiki once they've absorbed enough feedback and proven their usefulness. Ideas can also be pulled back down (removed or archived) when the organization's understanding shifts. Git history preserves the reasoning for every promotion and demotion.

This graduation pattern gives a leader a lower-stakes playground to think out loud in, while protecting the seriousness of the organizational bible.

The Core Problem​

You've built a successful business through specific ways of doing things. Now you want to hire people, but the last thing you want is for average service quality to decline because new hires are operating on assumptions rather than your proven methods.

The gap between your success and their performance isn't talent. It's the undocumented knowledge that lives only in your head.

Why This Process Matters Now​

The AI Advantage​

Before large language models, documenting granular operational details was hard to justify (too time-consuming relative to just doing client work). Now, with AI assistance, you can:

  • Interview employees with tribal knowledge efficiently
  • Process conversations into structured documentation rapidly
  • Create training materials that work for both humans and AI agents
  • Build searchable knowledge bases from successful project examples

The Scaling Imperative​

Every successful project contains lessons that should become organizational DNA. Without systematic capture:

  • New hires guess at your standards
  • Quality becomes inconsistent across team members
  • You repeat the same explanations endlessly
  • Competitive advantages remain trapped in individual heads

The Company Bible Framework​

Think of your truth management repository as a growing company bible: a living collection that expands as your organization learns and grows. The core purpose is communicating "the way" your organization operates.

This means documenting very detailed stories of how to do certain things and what not to do:

  • How you actually care about customers (not platitudes)
  • Exemplary projects broken down step-by-step and what made them successful
  • Day-to-day procedures and relationship management approaches
  • Tricky situations navigated well with principles applied
  • What doesn't work and why
  • How to recover from mistakes
  • When standard procedures should be adapted

Implementation Process​

Phase 1: Capture Existing Wins​

  • Identify your most successful projects/outcomes
  • Record detailed conversations with people who delivered those wins
  • Identify and extract common themes and practices using AI
  • Create first version of key processes

Phase 2: Systematic Documentation​

  • Do post-mortems after every significant success to document what made it work
  • Document approaches to edge cases (when someone handles a tricky situation well)
  • Create onboarding resources from your documentation
  • Let new hires identify gaps in documentation

Phase 3: Continuous Evolution​

  • Update regularly as practices improve
  • Track changes and reasoning behind updates via version control
  • Use documentation to ensure knowledge isn't siloed
  • Create system prompts for your AI agents based on documented practices

The Biblical Parallel​

The Bible serves billions of Christians as a truth management repository, articulating how followers should act, live, and make decisions through stories, principles, and examples. Crucially, the Bible is full of both positive examples and cautionary tales.

Your company bible should follow the same pattern: document not just your successes, but also your failures and near-misses.

Success Metrics​

  • Consistency: New hires deliver similar quality to experienced team members
  • Efficiency: Less time spent on repetitive explanations and corrections
  • Scalability: Quality maintained or improved as team grows
  • Knowledge retention: Critical practices survive personnel changes
  • AI effectiveness: AI agents can operate according to company standards

The North Star​

An organization where every new hire can deliver your standard of excellence because they're operating from the same documented understanding of what excellence means. Not guessing based on their previous experience or assumptions.

Further Reading​