Most owners think about job clarity as something one person needs: does this employee understand their own responsibilities? Gallup's ongoing research on workplace engagement points at a piece of that question most job descriptions never touch, which is whether the people working alongside that employee understand the role too. Gallup found that among on-site employees who say they clearly know what their coworkers are expected to do, 84% also say they're clear on what's expected of them, personally, at work. Among employees overall, that number is well below half. The pattern holds for fully remote employees, at 82%, and hybrid employees, at 77%. Clarity about a role doesn't appear to stay contained to the person holding it. It travels across a team, or it doesn't happen anywhere on that team at all. Gallup's broader analysis of the same measure, drawn from more than 112,000 teams and business units, ties it to outcomes well beyond mood at work: productivity, retention, safety, and customer engagement all move with it.
The Business Owner's Playbook treats this as a strategic planning problem rather than a paperwork chore. Its chapter on strategic planning lists organization and accountabilities as one of the core components of a business plan, alongside vision, mission, and budget, with a direct instruction attached: write job descriptions for every position, and define what the business, its departments, and its individual employees are responsible for, and how each is expected to perform. That puts the job description in a different category than the version most owners are used to: one written mainly to justify a hiring post and abandoned the moment the seat is filled, known only to the person who wrote it and the person who signed it.
The leaders make their expectations clearly known.
— Gary Henson, Founder of Gary Henson Group
The Playbook's template is short enough to complete in one sitting and specific enough to settle disagreements later. It works through five sections: position title and who the role reports to, a stated objective for the role, a list of essential functions, position-specific responsibilities beyond those basics, and a closing section called Standards of Performance, framed as answers to one prompt: "You're doing a great job if you are..." That last section is the one most homemade job descriptions skip. A list of responsibilities describes what a person does. A standard of performance describes what doing it well looks like, spelled out clearly enough that two different managers would agree on whether someone met it.
That gap between task and standard is where Gallup's research and the Playbook's framework point at the same problem from different directions. Knowing which tasks fall under a role isn't the same as knowing what's expected within them, and the second one is what tends to stay undocumented. A business with fifteen employees runs into this exactly like one with five thousand: an owner assumes the standard is obvious because it lives in their head, and the employee left to guess ends up on the receiving end of a performance conversation that feels arbitrary rather than earned. Writing the standard down settles more than one job. Once several roles have one, an owner has documented accountability across the team instead of a private mental map only they can read.
of on-site employees who say they know what their coworkers are expected to do also strongly agree they know what's expected of them, compared with less than half of employees overall (82% for fully remote employees, 77% for hybrid), according to Gallup's research on role clarity. Gallup, "In New Workplace, U.S. Employee Engagement Stagnates" →
None of this calls for a consultant or new software. It calls for sitting down once per role, working through the template's five sections, and treating the finished document as something to revisit rather than file. The Playbook's broader planning framework treats revisiting it as part of the job, not an afterthought: a business plan isn't static, and a role that hasn't changed on paper in two years has almost certainly changed in practice. An outdated job description creates the same blind spot from the other side, holding an employee to a standard that no longer reflects what the business needs from them.
The Playbook pairs the blank template with a completed sample, filled out for a real position, so an owner isn't starting from a blank page the first time through. The first one always takes the longest to write. The second and third go faster once the format is familiar, and the value grows once enough of them exist to compare side by side, the same way GH Group's weekly scorecard template becomes more useful with more than one period of data to read against.
The template works best paired with what happens on someone's first day, not treated only as a hiring-season document. GH Group's piece on the 90-day window that decides whether a new hire stays covers what happens after someone accepts a role; a written standard of performance gives those first 90 days something concrete to measure against instead of a general sense of whether things seem to be going well. A job description written once, during a hiring push, and never opened again is closer to a historical record than a working planning tool. The version worth keeping is the one an owner is willing to pull out and check against reality every year, for every seat on the team, not only the ones currently posted on a job board.
