How to Gradually Introduce a Process Culture When Everyone is Used to 'Just Getting Things Done'
A step-by-step strategy that works even in chaotic teams.
The Problem
The team works “from memory,” agreements get lost, and tasks are funneled through one or two “knowledgeable people.” But when you try to introduce processes, resistance begins.
The reason: people are afraid of bureaucracy, “scary regulations,” and control. They don't need processes—they need clarity.
Principle #1: Start with Pain, Not Processes
The quickest way to break resistance is to tie a process to a specific problem:
- a lead was lost,
- a deadline was missed,
- a client wasn't answered,
- an employee left—and no one knows how they did their tasks.
A process isn't a piece of paper. It's a bandage on a wound.
Principle #2: One Process = One Page
This is fundamental. No “40-page regulations.”
The format:
- goal,
- trigger,
- inputs,
- 5–10 steps,
- outputs,
- owner,
- SLA.
1 page → 10x the trust. 30 pages → trash can.
Principle #3: Show the Benefit, Not the Rules
If a person sees that a document saves them 10 minutes every day, they will open it themselves.
Therefore:
- add examples,
- make the format convenient,
- integrate it into real tasks.
The document must be a tool, not a “formal requirement.”
Principle #4: Easier to Update Than to Ignore
A rookie mistake: creating a “perfect diagram” and being afraid to touch it.
A process is a living document. The rule: update in 5 minutes.
- found a mistake,
- added a step,
- clarified a trigger.
That's it.
Principle #5: Implement One Small Step at a Time
Not “we are writing processes for the whole company.” But:
- Describe one process that is causing pain.
- Make it convenient.
- Show the team: “look, it's gotten easier.”
- Take the next one.
Revolutions in processes don't work. Evolutions do.
Parallel Viewpoints
The Entrepreneur's View
Processes = less chaos, fewer losses, more predictability. The main question: “Where are we losing money due to a lack of order?”
The Operations Manager's View
Processes = understanding where work gets stuck. Minimal documents visible in Notion/Confluence are needed.
The Executor's View
Processes = how to work so I don't get blamed. The main thing is simple steps and examples.
The Newcomer's View
Processes = a map of the terrain. The document should allow a task to be completed without 5 meetings.
The Automator's View
Processes = raw material for n8n, bots, and automations. Clear steps and inputs/outputs are gold.
7-Day Mini-Implementation Plan
- Day 1: Choose the most problematic process.
- Day 2: Describe it on one page.
- Day 3: Go through the steps with the executors → correct them.
- Day 4: Implement an SLA.
- Day 5: Add an owner and a control point.
- Day 6: Show the team how it has become easier.
- Day 7: Choose the next process.
Conclusion
A culture of processes is born not from “regulations,” but from small, convenient documents that help people work. If the team sees the benefit — they start demanding processes themselves.