site logo

Tettra Academy

Structuring your knowledge base

Developing a high-quality organizational plan for your internal knowledge base is just like building the foundation of a building. Taking the time to spec out the structure of your knowledge base will make it easier to know where to put things, which makes it easier for your teammates to navigate and find what they need without asking.

Here are some tips from customers on how they structure their information.

General Setup 

Tettra is built on the following hierarchy: Categories > Subcategories > Pages. 

While the way you want to organize your information within this hierarchy is up to you, weโ€™ve found the best ways to structure your account are either departmental, project based, topic based, or a mix of all three.

Structuring by department

A departmental structure means that you break down your categories by department within your org. For example, you could have categories for Marketing, Sales, Support, Engineering, and HR/Operations.

Once youโ€™ve setup categories by department, you can break down subcategories within each category by a sub topic or team. 

Hereโ€™s an example structure for a Sales team:

  • ๐Ÿ“’ Sales
    • ๐Ÿ“ Processes & Policies
      • ๐Ÿ“„ What to do after closing a sale
      • ๐Ÿ“„ Refund policy
    • ๐Ÿ“ Scripts
      • ๐Ÿ“„ Outbound call script
      • ๐Ÿ“„ Inbound call script
    • ๐Ÿ“ Personas
      • ๐Ÿ“„ Marketing Mary
      • ๐Ÿ“„ Owner Ollie


  • Helps your team know exactly which subcategory to find relevant information
  • Makes it very clear which category to store a page in


  • Sometimes pages donโ€™t fit into any category or are owned by multiple departments, which can cause arguments about where to store a page or create deferred responsibility
  • The same subcategory name can be used across two different teams, which can cause confusion 

Structuring by project or client

Structuring categories by project (or client) can be beneficial if youโ€™re teams tend to work cross-functionally or donโ€™t need access to everything else in the knowledge base often.

Some companies tend to do this for projects like weekly/monthly recurring meetings, competitive research, fundraising, testing, onboarding materials, or business development. You can also structure by client, with a category for each client and subcategories for each topic:

Hereโ€™s an example structure for a client-based approach:

  • ๐Ÿ“’ Dunder Mifflin
    • ๐Ÿ“ Quarterly Client Reports
      • ๐Ÿ“„ Q3 2019 Report
      • ๐Ÿ“„ Q4 2019 Report
  • ๐Ÿ“’ Stark Industries
    • ๐Ÿ“ Quarterly Client Reports
      • ๐Ÿ“„ Q3 2019 Report
      • ๐Ÿ“„ Q4 2019 Report
  • ๐Ÿ“’ Cyberdyne Systems
    • ๐Ÿ“ Quarterly Client Reports
      • ๐Ÿ“„ Q3 2019 Report
      • ๐Ÿ“„ Q4 2019 Report


  • Lets new teammates get ramped up on projects/clients quickly
  • Creates a more standardized sub-skeleton across categories


  • Have to recreate each subcategory/page in each category
  • Doesnโ€™t provide as much flexibility as other approaches

Structuring by topic

Finally, you can always organize by topic. 

This tends to be most useful if youโ€™re using Tettra with just a single team or youโ€™re planning on only putting one type of information (e.g. an employee handbook) inside of Tettra.

  • ๐Ÿ“’ Hiring
    • ๐Ÿ“ Sourcing
    • ๐Ÿ“ Interview Process
      • ๐Ÿ“„ Scheduling interviews
      • ๐Ÿ“„ Interviews questions
    • ๐Ÿ“ Offer
      • ๐Ÿ“„ Offer Letter template
      • ๐Ÿ“„ Welcome baskets
  • ๐Ÿ“’ Onboarding
    • ๐Ÿ“ Tools & Accounts
      • ๐Ÿ“„ Account setup checklist
      • ๐Ÿ“„ The tools we use
    • ๐Ÿ“ Your First Day
      • ๐Ÿ“„ Reading list
      • ๐Ÿ“„ Getting to know your new teammates
  • ๐Ÿ“’Planning & Decisions
    • ๐Ÿ“ Recurring meetings
      • ๐Ÿ“„ Weekly team meetings
      • ๐Ÿ“„ Monthly recaps 
      • ๐Ÿ“„ Quarterly all hands
    • ๐Ÿ“ Decisions Making & Goals
      • How we make decisions
      • How to set goals
  • ๐Ÿ“’ Mission & Culture
    • ๐Ÿ“„ Our Mission 
    • ๐Ÿ“„ Operating Principles


  • Allows for a deeper hierarchy structure
  • Makes it clear which subcategory to use to learn about a specific topic


  • Takes more time to think through topics
  • As your team grows, itโ€™s likely youโ€™ll need to move a departmental approach

Mixinโ€™ it up

Donโ€™t feel like you need to stick to one strict approach. Many teams use a mix of all three organizational structures. 

In fact, we use all three approaches at Tettra (the company) for our own Tettra (the product). For example, we use categories for departments (Sales, Engineering, Support) and for Topics (Company Updates, Office & Ops, Weekly Planning). 

Sometimes if a subcategory becomes really important, weโ€™ll elevate it to the category level to make it easier to access. Thatโ€™s exactly what happened to our Weekly Planning category, which started off as a subcategory inside of Company Updates.

Thereโ€™s really one right way to organize your hierarchy for your Tettra account. Just do whatever feels right to start, and make tweaks as you go.