The person who knows how it's done isn't always at work
In most Norwegian SMBs, there's one — maybe two — people who actually know how things are done.
Not just what needs to be done. But how. The order of steps. The pitfalls. What you never say to that client. How to write a proposal so it actually gets read.
That knowledge isn't in any system. It isn't in any document. It's inside someone's head — and that person could hand in their notice tomorrow.
That's not being dramatic. It's a real risk in the vast majority of businesses with fewer than 100 employees.
What happens when they leave?
Research on organisational knowledge shows a consistent pattern: only around 20 percent of what a company actually knows is written down. The remaining 80 percent lives in the heads of employees — what is often called tacit knowledge.
It's knowledge that's hard to articulate because it was built through experience. It lives in the fingertips of a salesperson who has done it a hundred times, in the judgement of a project manager who has seen what goes wrong, in the instinct of a team member who just knows that this particular client needs a phone call — not an email.
When that person leaves, it's not just the role that disappears. Months or years of practical expertise go with them.
And the new hire? They typically need 6–12 months to reach full productivity. Not because they're lacking. But because no one has written down what they need to know.
There's a better place for methodology
The answer isn't longer handbooks. It isn't a new intranet. It isn't a wiki that nobody updates.
The answer is skills.
A skill is, in its simplest form, a text file. It describes how something should be done — not just what, but the process, the reasoning, the standard. Think of it as the recipe behind best practice, written in a way that's understandable to both a new employee and an AI agent.
What's new in 2026 is that AI agents can draw on hundreds of such skills in a single task — provided the skills files exist and are written clearly. That means a company's methodology is no longer just documentation for training purposes. It can be executed. Automatically. Consistently. Every time.
A company that has documented its methodology as skills hasn't just made onboarding easier. They've turned their best practice into something AI systems can actually follow.
The three levels — and where the value is greatest
Skills exist at three levels, and it's worth understanding what separates them.
Level 1 — Standards are what many companies already have in place, without calling them skills: tone of voice guides, letter templates, invoicing routines. Useful. But not what separates the good from the average.
Level 3 — Personal workflow covers individual working styles. Valuable to the individual. But not necessarily something the whole organisation should inherit.
Level 2 — Methodology is what takes new employees months to learn. Not because it's complicated, but because no one has taken the time to write it down. This is where the real value lies. This is where an organisation's competitive advantage lives.
Examples of methodology that lives inside heads in Norwegian SMBs:
- How we qualify a new client before sending a proposal
- What we do in the first 48 hours of a new project
- How we handle a dissatisfied client without losing the contract
- Which signals tell us a project is starting to go off track
None of this is secret. But in most places, none of it is written down anywhere.
Documenting methodology: how IT Buddy does it in practice
We don't help companies write handbooks. We help them identify the knowledge that actually has value — and package it as skills.
In a skills workshop, we do three things:
Identify key knowledge. We ask straightforward questions: Who would we miss most if they left? What do they know that no one else does? What do we do here that takes every new person a long time to learn? The answers tell us where to start.
Write the skills files. We help the team articulate the methodology in clear, concrete language. Not lengthy process documents — but precise descriptions of how something is done, written so they can be used directly, by people and AI alike.
Establish a system that grows. A skills library isn't finished after one workshop. It grows as the company learns. We set up the structure so it's easy to add to and keep current.
The output after a workshop: identified key knowledge, completed skills files ready to use, and a system that makes it possible to keep building.
What happens once the methodology is in place?
Onboarding gets shorter. New employees don't need six months to get up to speed — they have the skills files from day one.
Quality becomes more consistent. It no longer depends on who happens to be working that day.
The company is ready for AI. AI agents that support your team can only do a good job if they know how the job should be done. They know that when the methodology is documented.
AI doesn't start with technology. It starts with structure. And structure starts with writing down what your company actually knows.
Start with one question
Which knowledge in your business lives inside just one person's head — and what happens if that person leaves next week?
The answer to that question is the starting point for a skills workshop.
Get in touch for a no-obligation conversation → — a Skills workshop is a half-day session where we identify, document, and structure your company's key knowledge. We help you figure out where to begin.
Also read: How to implement AI in your business – a practical guide for Norwegian SMBs