Handbook Guidelines

The handbook is focused on content that helps OCV start and scale open core companies. It includes anything OCV team members and OCV founders need to do their jobs effectively. The startup advice included in this handbook is specific to Pre-Seed founders. Generic, Google-able content is out of scope.

Contributing to the handbook

We follow a handbook-first approach. When a decision or recommendation is made, the first action item is to document the change in the handbook. Decisions aren’t “final” until they are in the handbook. A handbook-first approach minimizes duplication and provides a single source of truth.

Default to making live updates as decisions are being discussed, rather than listing them as an action item for later. If an update is small (e.g., updating existing content to reflect the most up-to-date thinking), make it yourself instead of waiting for someone else to do it.

Public by default

OCV defaults to documenting in the public handbook according to the following guidelines:

  1. It’s ok to be messy. Prioritize getting relevant information into the handbook quickly and worry less about organizational structure, word choice, etc.

  2. Avoid linking to internal docs and add templates to the handbook whenever possible. Linking to internal templates may be unavoidable in some cases, like linking to a spreadsheet or legal and financial documents.

  3. Avoid naming software and systems in the handbook to prevent phishing attempts.

  4. Do not share personal, financial, or sensitive HR information in the handbook. Security-sensitive finance and HR processes should be documented in our project management tool.

Content guidelines

  1. Use headers, visuals, and charts liberally.

  2. Write concisely and be straightforward. Use an AI tool to help remove filler words.

  3. Do not share personal, financial, or sensitive HR information in the handbook.

  4. Avoid naming software and systems in the handbook to prevent phishing attempts.

  5. Avoid linking to internal docs and add templates to the handbook whenever possible.

  6. Avoid nesting pages.

Editing the handbook

We use GitBook to manage and publish our handbook content. GitBook uses a Git-based workflow for editing, reviewing, and merging changes.

Before adding content, check:

  • Does similar content already exist? Search first! You might just need to update an existing page.

  • Does this warrant its own page, or should it be a section within an existing page? When in doubt, start as a section.

Information hierarchy

The handbook is organized into 4 levels: spaces, groups, pages, and subpages. We use a flat structure to organize categories and pages; we do not nest content beyond a single subpage.

Spaces

Spaces are the horizontal tabs at the top of the page. They are the highest-level containers. They define the primary audience or major functional area. Our current spaces are:

  1. Home: Prospective and new founder space for sharing about OCV, our model, what to expect, and how we interact with founders.

  2. Startup Manual: Open core founder space for sharing startup knowledge and advice.

  3. Company Operations: OCV founder-specific space for sharing operational instructions and guidance.

  4. OCV Employees: OCV employee space for documenting internal processes and policies.

Groups

Groups are thematic collections within a Space. Groups organize related topics together, typically at least 3 related pages.

Think of groups as answering "what category of work is this?" (Fundraising, Product Development, Legal) while pages answer "what specific topic?" A good test: if you can't easily think of 2-3 other related pages that would fit in the group, it's probably just a page.

Pages

Pages contain content on a single topic or concept. Pages contain the primary content people are looking for. Examples: "Investment Thesis," "Equity Management," "Weekly Standup Process."

Subpages

Subpages are content that supports the parent page. They cover a sub-topic that is relevant to a smaller audience, and are often action-oriented (how-tos, templates, or specific implementations). Use subpages sparingly.

Avoid nesting content

Deep nesting makes content effectively invisible. The complexity creates decision paralysis at every level, fragments related concepts across multiple locations, and makes reorganization nearly impossible as simple page moves become tangled webs of broken links. Additionally, deep navigation becomes unusable on mobile devices, where many people access documentation.

When to consider restructuring

  1. You have more than 5 subpages under one parent page

  2. People repeatedly ask, "Where should I put this?"

  3. You see duplicate content in multiple locations

  4. A Group has only 1-2 pages (might not need to be its own Group)

  5. You catch yourself creating a sub-subpage

PreviousMission & Vision

Last updated

Was this helpful?