IIIOrganization & Project ManagementGuide
Documenting Processes Without Filling Binders: The One-Page Method
The process manual has 60 pages, was written for an audit, and has not been opened since. Meanwhile, new colleagues ask every day how something is done. One page per workflow solves both.
Key takeaways
- One workflow, one page. Whatever does not fit on one page is two workflows.
- Every page has eight fields: purpose, trigger, result, owner, steps, pitfalls, resources, and status.
- A page is a model that has to be practiced. Detailed procedures alone often fail to take hold in sales.
- Document first what happens often, often goes wrong, or depends on a single person.
Why does process documentation end up in binders nobody opens?
At some point someone wrote down all the workflows, thoroughly, with flowcharts and a responsibility matrix. The result is a 60-page document. It was distributed once, shown for an audit, and then filed away. Today parts of it are no longer accurate, and nobody knows which.
At the same time, documentation is missing exactly where it is needed. A new colleague asks how an inquiry is handled. The colleague covering during vacation does not know who approves quotes. And when the experienced office employee leaves, half of the workflows leave with her, in her head.
The problem is not that too little gets documented. It gets documented the wrong way: too much at once, in too much detail, in a place nobody opens in daily work, and without anyone keeping it current.
The guiding question of this guide is therefore: how do you document workflows so that the description is actually used in daily work and stays current? To answer it, we first present the one-page method and what research shows about standards that are actually lived, then write a process page in 45 minutes, and finally clarify which workflows come first and how the pages stay current.
A process description nobody reads is not documentation but an archive.
What is the one-page method?
A process is the recurring sequence of steps that produces a result. The one-page method describes each such workflow on exactly one page with eight fixed fields. The fields are the same on every page, so everyone on the team knows where to find what.
| Field | Guiding question | Length |
|---|---|---|
| Purpose | Why does this workflow exist, and what happens if it fails? | 1 to 2 sentences |
| Trigger | What starts the workflow? | 1 sentence |
| Result | How do you know it is finished? | 1 verifiable sentence |
| Owner | Who is responsible for the workflow and this page? | 1 name |
| Steps | What happens in which order, and who does it? | at most 7 steps |
| Pitfalls | What typically goes wrong here, and why is the rule the way it is? | 2 to 4 points |
| Resources | Which templates, lists, or tools are needed, and where are they? | References |
| Status | When was it last reviewed, and when is the next review? | 2 dates |
Two fields make the difference from typical descriptions. The result has to pass the one-sentence test from the article on how to visualize your sales process: a sentence an outsider could verify. And the pitfalls contain the why. The article on systematizing founder-led sales explains the reason: an instruction without a rationale is followed until the first special case comes along.
What does research show about standards that are actually lived?
Hanahara (2026) compared two Japanese companies that both wanted to standardize their sales. The reason was similar in both cases: selling depended on the abilities of individuals, and junior staff were hard to train. Both sent their employees to the same training program. One company, a well-established travel agency, developed a shared basic pattern for selling, called kata in Japanese, and practiced it in role-plays. The other, a manufacturer of specialized equipment for the healthcare sector, wrote detailed standard operating procedures and distributed them.
The results diverged sharply. At the travel agency, the salespeople afterwards worked as a team along the shared process. At the equipment manufacturer there were short-term gains, but selling based on personal skill prevailed again. The author concludes that in complex activities such as selling, a practiced model that allows variation is more effective than a detailed rulebook. These are two cases and not a statistical study. For the one-page method this means: the page is the starting point. It only becomes effective once the workflow is practiced with it.
A case study by Aggestam and Gudfinnsson (2024) shows what such a start can look like. For two and a half years they accompanied a manufacturer of screening equipment with around 25 employees that builds every machine to customer specification, with nine in-depth interviews and eight workshops. It began with a session of about two hours in which the management team sketched the workflow on a whiteboard. And in interviews with 28 small and medium-sized design and construction firms, Balaban-Ökten and Gundes (2018) found that writing down experience-based knowledge and disorganized digital folders caused the greatest difficulties.
How do you write a process page in 45 minutes?
Choose a workflow (5 minutes)
A single workflow with a clear trigger and result. Not “sales” but “answer an inquiry.”
Talk to the right person (20 minutes)
Sit down with the person who does the workflow most often. Go through the last real case together, step by step.
Fill in the eight fields (15 minutes)
Write down what actually happened, not what should have happened. At most seven steps, with the owner for each.
Add the pitfalls (5 minutes)
Ask: what goes wrong here most often? Why do we do it this way and not differently?
Outsider test
Give the page to someone who does not know the workflow. Can they complete it with the page? Every question they ask reveals a gap.
The outsider test is the most important step and costs no extra time if you combine it with the next onboarding or vacation cover. Newcomers notice immediately where the page assumes knowledge only insiders have.
What does a finished process page look like?
The following example shows a page for the workflow “answer an inquiry” in a company with a small sales team. The content is an example and has to be adapted to your own company.
| Field | Content |
|---|---|
| Purpose | Every inquiry gets a quick, qualified response. If the workflow fails, inquiries go to faster competitors. |
| Trigger | An inquiry arrives by phone, email, or form. |
| Result | The inquiry has been qualified and has a date for a first meeting or a reasoned decline. |
| Owner | Sales back office |
| Steps | 1. Create in the CRM (office). 2. Qualify on the same business day: need, time frame, decision-maker (salesperson). 3. Call back and propose a meeting (salesperson). 4. Enter the date and next step in the CRM (salesperson). |
| Pitfalls | Phone inquiries do not get recorded, so the rule is: record first, then work on it. Call back the same day, because customers usually contact several suppliers. |
| Resources | Qualifying questions for inquiries, template for the meeting confirmation, both in the shared file store. |
| Status | Reviewed in March, next review in September. |
Worked example
What is missing is notable: no exceptions for every conceivable case, no flowchart, no explanation of the CRM. For special cases, the why in the pitfalls applies. Whoever has understood it can decide the special case in the spirit of the workflow.
Which processes should you document first?
Not all at once. In most small companies there are ten to fifteen core workflows that carry most of daily work. Start with those to which at least two of the following apply: they happen often, they often go wrong, they depend on a single person, or new colleagues regularly ask about them.
Worked example: 14 core workflows, meaning 14 pages. At one page per week, the foundation is done in a little over three months.
Classic manual
- All workflows at once, often for an audit
- Many pages per workflow, with diagrams
- One author, rarely the person doing the work
- Sits in a binder or as a long PDF
- Revised when needed, which means rarely
One-page method
- One workflow per week, by urgency
- One page per workflow, eight fixed fields
- Created in conversation with the person doing the work
- Lives where the team works every day
- Has an owner and a fixed review date
If you do not yet know the sales workflow as a whole, draw it as a map first. The individual pages then describe the stages of that map in more detail. If a workflow is to be improved, the page comes before the improvement: it is the as-is analysis with which the article on process optimization step by step begins.
How does process documentation stay current?
A page goes out of date as soon as the workflow changes and nobody updates it. Three rules keep the collection alive.
- One owner per page. They change the page when the workflow changes and review it on the set date.
- Fixed triggers. New software, a complaint, a mistake with consequences, or a new person in the workflow are occasions to review the page.
- One place. All pages live in the place the team opens every day. How to reduce the number of storage places is described in the article on how to reduce tool sprawl.
To make sure a page is actually used in daily work, a finding from research on habits helps. Trenz and Keith (2024) followed 72 employees over ten working days with two daily surveys while they built a new habit at work. Those who used concrete if-then plans performed the new behavior more often, and it became more automatic over time. For the process page this means: link it to a fixed trigger. For example: when a new colleague does a workflow for the first time, they get the page and check off the steps.
Process pages and sales knowledge belong together. The answers to frequent customer questions described in the article on sales knowledge management are the resources a page refers to.
What you can put into practice right away
- Write down the ten to fifteen core workflows of your company as a list.
- Mark the three that happen often and depend on a single person.
- Sit down with that person for 45 minutes and write the first page with the eight fields.
- Have the page tested by someone who does not know the workflow.
- Decide where all pages will live and plan one page per week.
After a quarter you have a collection that fits into every onboarding, eases every vacation cover, and serves as the starting point for the next improvement. And it fits into no binder, because it lives where the work happens.
Process documentation gets used when each workflow fits on one page, has been tested by someone who does not know it, lives where the work happens, and has an owner who keeps it current. Scope matters less than regularity. One page per week carries further than a complete manual that is written once.
Frequently asked questions
How do I document processes in a small company?
With one page per workflow and eight fixed fields: purpose, trigger, result, owner, steps, pitfalls, resources, and status. The page is created in conversation with the person who does the workflow most often and is tested by someone who does not know it.
What belongs in a process description?
Why the workflow exists, what triggers it, how to recognize the result, who is responsible, the steps with owners, typical pitfalls with reasons, the templates needed, and the date of the last review. Usually nothing more is needed.
How many processes does a small company need to document?
Usually ten to fifteen core workflows carry most of daily work. Start with those that happen often, often go wrong, or depend on a single person. One page per week is enough.
How do I keep process documentation up to date?
Every page gets an owner and a fixed review date. New software, complaints, mistakes, or new people in the workflow are occasions to review the page. All pages live in the place the team uses every day.
Is a written process description enough to make the team follow it?
Usually not. A case study of two sales departments shows that a practiced model works better than a detailed rulebook. The page is the starting point. It is practiced during onboarding and in daily work.
Sources
- Hanahara, A. (2026): Standardization Efforts in Two Sales Departments: The Role of Kata Versus SOPs. Annals of Business Administrative Science, 25(3), 35-53.
- Aggestam, L.; Gudfinnsson, K. (2024): The Practice of Business Process Modeling: A Story from the Field. Complex Systems Informatics and Modeling Quarterly, no. 41, pp. 1-21.
- Balaban-Ökten, B.; Gundes, S. (2018): Knowledge Management in Small and Medium Architecture, Engineering and Construction Firms in Turkey. The Electronic Journal of Knowledge Management, 16(2), 155-169.
- Trenz, N.; Keith, N. (2024): Promoting new habits at work through implementation intentions. Journal of Occupational and Organizational Psychology, 97(4), 1813-1834.
