> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# How to prepare an operation for fast headcount growth
- URL: https://blog.jestor.com/prepare-an-operation-for-fast-growth/
- Published: 2026-09-16T18:55:53.000Z
- Updated: 2026-09-16T18:55:53.000Z
- Author: Bruno Bannach

To **prepare for fast growth**, the things to fix first are the ones that depend on everyone knowing each other. Informal coordination works beautifully at fifteen people and fails predictably somewhere around forty, usually without warning.

## Why growth breaks operations suddenly

A small team coordinates by conversation. Everyone knows what everyone is doing, decisions happen in the room, and process documentation would genuinely slow things down.

That model does not degrade gracefully. It works, and then within a quarter it does not, because the number of relationships grew faster than the headcount.

What breaks first:

- Onboarding that depends on sitting next to someone
- Decisions made informally with no record
- Permissions granted because everyone is trusted
- Process knowledge held by individuals
- Reporting assembled by asking people

## What to establish before you need it

| Element                | Why before growth                     |
| ---------------------- | ------------------------------------- |
| Structured onboarding  | Cannot scale by apprenticeship        |
| Role based permissions | Individual grants become unmanageable |
| Documented processes   | Knowledge stops fitting in heads      |
| Named process owners   | Ambiguity multiplies with size        |
| Live reporting         | Asking people stops working           |
| Approval thresholds    | Informal approval stops being visible |

## Step by step to prepare

1. **Document the processes** that new people need most.
2. **Move permissions to roles**, before individual grants accumulate.
3. **Build a structured onboarding path**, so it does not depend on one person.
4. **Name process owners**, while there are few enough to assign easily.
5. **Set approval thresholds**, converting informal judgment into rules.
6. **Build live reporting**, so information does not come from asking.
7. **Make the first hires in a growing team document as they learn**.

## Why the new hires should write the documentation

The people who have been there longest cannot see what is unwritten, because they know it. Someone in their first month encounters every gap. Asking new hires to document what they had to ask about produces better documentation than any effort by the incumbents.

## Why choose Jestor

In **Jestor**, permissions are role based per field and action, onboarding paths can be generated per hire from a template, documents attach to the processes they describe, approval thresholds route automatically, and dashboards read live data so information does not depend on asking.

## Frequently Asked Questions

### What breaks first when a team grows quickly?

Onboarding by apprenticeship and informal decision making. See [jestor.com](https://www.jestor.com/?ref=blog.jestor.com).

### Who should write process documentation?

The newest people, since they are the only ones who can see the gaps.

### When should permissions move to roles?

Before individual grants accumulate, which happens faster than expected.

## Video Tutorial: Step by Step

With **Jestor**, you can automate workflows, connect teams, and build internal systems your way, all without code and powered by **AI**. Discover Jestor at [jestor.com](https://www.jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.