Every growing small business hits the same wall. The company doubles headcount in eighteen months, three people are doing the job one person used to do, and somehow nobody can answer a basic question: what is this person actually responsible for?
Oh sure, there’s a job description sitting in a folder somewhere. It probably says the person handles client onboarding, or manages inventory, or supports the sales team. It was thrown together to get the position posted and the offer signed, and it’s done that job. But it wasn’t built to answer the question that starts costing you money the day your team grows past a size where everyone can just ask each other what’s going on: who owns this outcome, and what happens if it slips?
That’s the gap a role description closes, and it’s the piece most growing companies skip.
The job description tells you what the position does. It doesn’t tell you what the person is accountable for.
A job description is a snapshot mixed with a wish list. It lists duties, qualifications, reporting lines. It’s full of all the skills you hope the perfect candidate has. It’s the right tool for hiring and for staying on the right side of employment law, and it should stay exactly what it is.
A role description is different. It answers what this person is expected to deliver, how their work connects to the team around them, and who has the authority to make which calls. It’s built to be revisited as the business changes, because the business will change, and if the only documentation you have is frozen at the hiring stage, your org chart stops matching reality within a year.
Here’s where it actually costs you.
Picture the conversation that happens in almost every business with fifteen to fifty employees. A deadline gets missed. The owner asks who was supposed to catch it. Two people each thought it was the other one’s job. Neither is lying — the job descriptions genuinely don’t say. Multiply that by every cross-functional handoff in the business, and you’re not looking at one dropped ball. You’re looking at a structural reason things keep dropping. It’s a game of workplace hot potato.
This is also where succession or transition planning quietly falls apart. If a key employee leaves and the only record of their job is a list of duties from two years ago, you’re not promoting or hiring their replacement — you’re reverse-engineering what they actually did from memory, emails, and Slack messages. A documented role description, kept current, is the difference between a two-week transition and a two-month scramble.
Documenting roles is a growth requirement, not an HR “nice-to-have”.
At five employees, nobody needs this written down. Everyone’s in the same room, everyone knows what everyone else is doing, and formal documentation would be overhead for its own sake. That calculus flips the moment you add layers — a manager between the owner and the team, a second location, a function that used to be one person’s side task and is now three people’s full-time job. Past that point, undocumented accountability isn’t scrappy. It’s a liability you haven’t priced yet.
The businesses that get ahead of this treat role descriptions the way they’d treat a financial forecast: reviewed on a schedule, updated when the business shifts, and used to make actual decisions — who gets promoted, where the next hire goes, which function needs to be split before it breaks. The businesses that don’t tend to find out the hard way, usually during a growth spurt or a departure, when there’s no time to figure it out calmly.
If you’re scaling and you don’t have role descriptions for your key positions, that’s not a documentation gap. It’s a planning gap. And it’s a lot cheaper to fix before you need it than after. If you don’t have the time or the staff to create the role descriptions and map your workforce planning strategy, talk to us at Beatitudo Consulting. We have people.
