The Role Doc.

The skin and the spine

Too many job descriptions are written to attract applicants, then filed and forgotten. That leaves managers with no written answer to the most basic question on their team: what does good look like here?

The fix is to separate the two documents. The one-pager is what you post. The role doc is the real job description. The posting is the skin. The role doc is the spine, and it’s the standard every later conversation about performance, capacity and hiring gets measured against.

The ten parts

1. Title. What the job is called. Titles aren’t a retention tool.
2. The role in one sentence. The whole job, said once.
3. Summary. A short overview of the role.
4. Day-to-day. What the work looks like on a normal day.
5. Core responsibilities. What the role is accountable for.
6. Metrics and benchmarks. Pair every volume metric with a quality metric.
7. Owns and does not own. Where the role’s responsibility starts and stops.
8. Required vs preferred. If it can be taught in ninety days, it’s preferred. If it can’t, it’s required.
9. The ramp. How a new hire gets up to speed, and the career path beyond it.
10. Impact. Why the role matters to the customer.

A worked example: the Junior IT Support Technician

Johnny is a Junior IT Support Technician. Last week he closed 20 tickets. His teammates closed 45, 44 and 41. Should Johnny be worried?

Nobody can answer, because nobody wrote down what good looks like. Here’s part of his role doc once somebody does.

• Owns: tickets through resolution or a clean escalation, acknowledging monitoring alerts, and a knowledge base article for every new fix.
• Does not own: help desk automations (Systems Engineering), server changes (Engineering) and vendor contracts (the IT Manager).
• Required: clear written communication. It can’t be taught in ninety days. The specific note format your team uses can, so it’s preferred.
• Impact: every employee has the tools and support they need to take care of our customers.

With the standard written down, Johnny’s 20 tickets get read against it. Same chart, different answer. That last part, the impact, is also where leadership starts: it’s the Reason in Earn The TRUST.

Why the written version matters

Job descriptions rarely match the job. Only 10% of US workers say job descriptions always accurately reflect the reality of the role (Monster, 2026). The mismatch costs you people early: 26% of new hires say they would restart their job search over mismatched expectations (ZipRecruiter, 2026). And a meta-analysis in the Journal of Management linked role ambiguity to lower job performance (Tubré and Collins, 2000).

Draft it with AI, decide it yourself

In Session 02 of Manager Fundamentals, managers use a job description prompt that does the heavy lifting. It checks for a company template or brand voice first, asks clarifying questions before drafting, pairs volume and quality metrics, and flags missing owners and title-inflation risk.

The same rule applies as everywhere else in the program: company-approved AI tools only, placeholder names for employees, and anything touching performance, pay or separation goes through HR.