Define the role before you hire: the one-page contract that saves the seat
A job description is written to attract a person. A role definition is written to run the work, and writing it down on one page before you hire decides most of what happens after.
In Operational Alpha I tell the story of an operations coordinator seat that failed three times with three different people. Each hire was capable. Each one struggled anyway, because the job description was a Frankenstein. Part analyst, part scheduler, part project tracker, part executive support, part other duties as assigned. The role touched four functions at four different altitudes and reported to two people with different priorities. The chair was not cursed. It was undesigned.
The pattern behind that seat is everywhere in the middle market. A role gets staffed off a document that was written to attract candidates, and the questions the work will actually ask stay unanswered until a good person is already sitting in the chair. The book's first law of interface design states the fix plainly. Don't staff ambiguity. Design the seat. What follows is the working version of that law.
Why the job description fails the seat
A job description is a recruiting document. It exists to attract a person, and it usually does that job fine. The trouble starts after the person says yes, because the document goes silent on every question the work will ask from day one. Where does work enter this role? Where does it ship? Who reviews it and calls it done? What happens when the person is blocked?
A seat is not a person. A seat is a small contract between your company and reality, and those questions are the contract's terms. When the answers stay implicit, someone has to close the gaps by hand, and that someone is usually the manager. Routing is how capable managers hold an undefined seat together. In an office, proximity absorbed much of this. A hallway clarification patched what the role definition never said. Remote and offshore seats have no hallway, which is why undefined roles fail fastest there. That failure has its own anatomy, and it is written up in why most offshore staffing fails.
What a role definition needs: the six parts of a Seat Card
A role definition needs six answers, and in Operational Alpha they fit on one page called the Seat Card. The Seat Card is a contract between the company and the seat. It is written before the hire and reviewed whenever the role changes. Here is what goes on the page.
- Owns. Three to seven outcomes the seat is accountable for, described as results the company can see. A list that runs past seven is describing more than one seat.
- Does not own. Explicit exclusions, written down. This is the field that gets skipped most often and the one that protects the hire, because an unwritten boundary will not hold.
- Definition of done. One paragraph plus a link to one gold example, a finished piece of work you would happily ship again. The example calibrates quality faster than paragraphs can, and it turns feedback into “match the example” instead of mind reading.
- Cadence. The rhythm the seat runs on: a daily async update, a weekly review, a monthly retro. Once the rhythm is written, visibility stops depending on anyone asking for status.
- Escalation. A standing rule for being blocked. The book's version reads: blocked for more than 24 hours, escalate, and escalate with options. The rule tells a capable person how to ask for help without feeling like they are failing.
- Where truth lives. The seat's primary tools, and the one place where the current version of reality can always be found.
If you have used a role scorecard in hiring, the instinct will feel familiar, and the instinct is right. The Seat Card carries the same discipline past the offer letter and into how the seat runs day to day. The fillable one-page Seat Card lives in the Operational Alpha toolkit, alongside the book's other working documents. The set is free, fillable on the page, and printable.
A Seat Card doesn't replace management. It replaces guessing.
The test of a ready role
A role is ready to hire for when its Seat Card can be written in one sitting. That is the whole test, and it works because every field fails in an informative way. An Owns list you cannot finish means the role is still a pile of tasks rather than a set of outcomes. An empty Does Not Own field means the seat has no edges, and a seat without edges grows until it swallows the person in it. A missing gold example means the standard of done lives in someone's head, and a standard that lives in a head gets paid for in rework.
The book gives the far end of this failure a name. When work reaches a person as a stream of quick pings and one-off asks, there is no seat left to speak of. The role has dissolved into a human cursor, and no amount of talent compounds in that environment.
The Seat is also the one part of the operating design that only the company can supply. Whoever runs the model can build everything around the role, but only you can say what the work is and what finished means. That surrounding layer is the interface, and what the interface is and its four parts is its own article.
What changes when the role is defined
A defined seat changes who can fill it, how it gets managed, and what a failure means. It widens who can fill it, because a role with a written definition of done no longer depends on proximity and osmosis, which is what lets a seat travel beyond the building. It changes management, because a designed seat replaces detective work with coaching and replaces late surprises with early correction. And it changes what a failure means, because when a designed seat underperforms, the difference is finally attributable to skill and judgment rather than to invisible friction.
This is the design-problem argument at the scale of a single role. The instinct when a seat keeps failing is to hire differently. The higher-leverage move is usually to design the seat first, which is the heart of the case that the hiring problem is really a design problem.
Where Kayana starts
Every seat Kayana places starts with this document. Before an operator joins a client team, the seat gets designed: the ownership list, the exclusions, the definition of done with a gold example, the cadence, the escalation rule. The client owns the Seat, because only the company can define its own work. We help write it, and then we design and run everything around it. That split is the spine of how we work.
Quick answers
What is a Seat Card?
A Seat Card is a one-page contract between a company and a role, introduced in the book Operational Alpha. It records what the seat owns, what it does not own, the definition of done with a gold example, the working cadence, the escalation rule, and where truth lives. It is written before anyone is hired into the seat, and its job is to replace guessing.
How do you define a role before you hire for it?
Answer six questions on one page: what the role owns, what it does not own, where work enters, where it ships, who reviews done, and what happens when the person is blocked. If the answers fit on a page in one sitting, the role is ready to staff. If they do not, the gaps will surface later as rework, routing, and a struggling hire.
What should a role definition include beyond a job description?
A job description covers duties and qualifications. A role definition adds the operating terms: three to seven owned outcomes, explicit exclusions, a definition of done anchored to a real example, the cadence of updates and reviews, an escalation rule for blockers, and the tools where the truth of the work lives.
The Seat Card is one page of a larger design system. The full framework is in the book. Operational Alpha →
Keep reading
About the author
Chris Nolte
Founder of Kayana and author of Operational Alpha. He builds Mini-GCCs — embedded operating teams of senior remote professionals — for middle-market, PE-backed companies.