Role vs. Job Description: Why Agile Teams Use Dynamic Roles

The Static Document Trap

When a team needs to hire someone, HR writes a job description. It outlines a generic title, a list of required skills, and a bulleted list of initial duties. The candidate is hired, the document is filed away in a shared drive, and it is rarely looked at again until an annual performance review. As the organisation scales and realities shift, the work the person actually does diverges entirely from that original document. This creates a “shadow structure” where no one truly knows who owns what, leading to bottlenecks and dropped responsibilities.

Role vs. Job Description Defined

To fix this structural chaos, modern organisations separate the person from the work.

A role description defines the ongoing accountabilities and decision-making domains for a specific piece of work, and it stays constant no matter who fills it. A job description, by contrast, is a static HR document used to hire, evaluate, and compensate a particular person. That single distinction — work versus person — is what keeps roles current while job descriptions drift out of date. A role is a dynamic governance unit; a job description is a personnel record.

Comparison: Jobs vs. Roles

Anatomy of a Dynamic Role

In role-based work structures, you do not assign a project to “The Marketing Manager.” You assign it to a specific, modular role. A well-designed role requires three distinct elements:​

1. Purpose: A brief statement explaining why the role exists. (e.g., “The brand is consistently presented across all channels.“)
2. Accountabilities: Ongoing activities the role is expected to perform.
3. Domains: Exclusive decision-making rights. If a role holds a domain over the “Website CMS,” no one else can alter the CMS without their explicit consent.

How to Write Role Accountabilities

A common mistake when transitioning to role-based work is writing accountabilities that look like one-off tasks. Accountabilities must be continuous, observable activities. Always start accountabilities with an -ing verb to signify ongoing action.​

Bad Examples (Too vague or project-based):

• “Be in charge of the newsletter.”
• “Redesign the pricing page.”
• “Sales.”

Good Examples (Ongoing and observable):

• “Drafting and sending the weekly customer newsletter.”
• “Optimising website conversion rates based on analytics.”
• “Defining target customer segments for Q3 outreach.”

When accountabilities are written this clearly, “who owns this?” is no longer a question that requires a one-hour meeting to resolve.

A Role Description Example

Here is what a complete role description looks like once purpose, accountabilities, and domains come together. A Content Marketing role held by one person who may well hold three others:

• Purpose: Prospective customers discover the company through useful, findable content.
• Accountabilities:
  • Drafting and publishing articles on the company blog.
  • Optimising existing pages for the queries prospects actually search.
  • Reporting on organic traffic and conversion trends each month.
• Domains: The blog content calendar and the on-page SEO of published articles.

Notice what is absent: no seniority, no salary band, no “reports to”. Those belong to a person’s employment terms, not to the work itself.

Building a Living Org Chart

You cannot manage dynamic roles in a static format. If you try to track these accountabilities in Notion or Excel, the documents will quickly suffer from page drift, and the team will stop trusting the system.​ Governance requires mechanics. When a team member feels a “tension” (a gap between what is and what could be) they need a system to propose a change to a role’s accountabilities. This ensures the organisational structure evolves at the exact speed of the market.

Keyroles is built precisely for this transition. It replaces vague job titles with a living, dynamic org chart. You can define purposeful roles, assign explicit accountabilities, and empower your team to keep the structure up to date as reality changes.

Frequently Asked Questions

What is a role description?

A role description defines the ongoing accountabilities and decision-making domains for a specific piece of work: its purpose, what it continuously delivers, and what it has authority over. Unlike a job description, it stays constant when the person changes. If the idea is new to you, start with Roles 101.

What is the difference between a role description and a job description?

A job description describes a person and their qualifications, for hiring and pay. A role description describes the work and its outcomes, for day-to-day clarity. One person usually maps to a single job description but holds several roles across different circles.

What does “role description” mean on a job application?

On a job application it normally just asks you to summarise the duties and responsibilities of a position you held. In organisational governance the term is more precise: a defined set of accountabilities and decision-making domains, uncoupled from any single person.

Is a role the same as a job title?

No. A job title is a label attached to a person (“Marketing Manager”); a role is a unit of work with its own purpose and domains. One title often spans several roles, and the same role can appear under different titles in different teams.

Can one person hold more than one role?

Yes — and they usually do. Because roles describe work rather than people, one person can hold several roles, and a single role can be shared by several people.

What is the difference between a role and a responsibility?

A responsibility is one expectation. A role is a coherent bundle of ongoing accountabilities plus the decision-making domains that back them up. A role answers “who owns this area?”, not merely “who does this task?“.

How often should a role description be updated?

Whenever someone senses a tension, a gap between what is and what could be. In practice that means roles evolve continuously, rather than once a year at review time.

Related reading

• Start with the fundamentals of purpose, accountabilities, and domains: Roles 101
• Why a Notion or Excel org chart goes stale: Static vs. Dynamic
• Put roles inside a lightweight governance model: Holacracy vs Sociocracy vs Teal
• Why roles outlive the people who fill them: Critical Roles & Vacancy Risk
• A pragmatic middle path between chaos and bureaucracy: Hybrid Governance