Organizing / RolesWork that survives a handoff

When someone leaves, their work should not leave with them.

A charter is one team’s editable account of its purpose, work, measures, authority, roles, and guidelines. A role names one durable contribution inside that team and shows who or what currently fills it.

People move, teams change, and agents join. The role keeps the work, its decisions, and its relationships visible through the handoff.

You knew to ask Priya about launches. Then Priya left.

Your org chart shows who manages Priya. Her job description lists broad responsibilities. The work itself lives in local memory: ask Priya about launches, let Priya review the promise, and bring Priya in before the date changes.

That arrangement works until Priya changes teams, takes leave, delegates part of the job, or leaves. Hiring someone with a similar title may refill the seat while the relationships, judgment, authority, measures, and recurring obligations disappear.

Particulars starts with the contribution. The role sits inside a real team, names the work in plain language, and stays in place when its filler changes. Priya remains a whole person; the organization keeps a usable account of the work.

Separate the work from the title and the person.

These objects solve different problems. Keeping them distinct makes the work easier to route and the person less reducible to a box on a chart.

01

Title

Describes level, discipline, employment category, or market position. It supports career and compensation systems.

02

Person

Has history, capability, interests, relationships, and several possible contributions. A person may hold several roles.

03

Job description

Supports hiring and classification with qualifications, broad expectations, and possible responsibilities.

04

Role

A named contribution with a clear focus, current fillers, home team, and connections to authority and evidence.

Name the contribution, not the importance.

01

Use a functional name

Names such as Launch readiness, Measure stewardship, Editorial stewardship, and Market exception review help a colleague route work. Strategic thought leader, executive champion, and senior stakeholder confer status without locating a contribution.

Add a one- or two-sentence focus statement. “Responsible for marketing” is a territory. “Turns product and customer evidence into a clear market promise and coordinated path to demand” names a contribution.

02

Keep the role coherent

Keep work together when the same attention and judgment make it better. Split it when two parts pull in different directions. A Product lead role may own product direction and roadmap administration today, then move roadmap administration into a new Operations role when the coordination load grows.

The charter can say, “Roadmap administration removed from this role; receiving role not yet filled.” That visible gap is safer than leaving everyone to assume the old filler still owns it. Authority stays in decision rights, measures stay with the team, and guidelines hold the recurring rules.

03

Show the fillers without confusing them with the work

One role may be filled by one person, several people, an agent, or nobody. An explicit open role is more useful than work everyone assumes somebody else carries. Shared filling can include a lead, a rotation, or a visible division of focus.

A person and an agent may co-fill the role while contributing differently. The person can retain judgment and accountability while software prepares evidence or repeated work. The role keeps the contribution whole.

Changing fillers then becomes a deliberate handoff. The team can name what transfers immediately, what needs a transition period, and which relationships should be reintroduced, while the role’s history remains attached to the work.

FIG 3.1

One role, several fillers, explicit divisions of work

A role card keeps the focus stable while fillers change. The current arrangement can be singular, shared, assisted by an agent, or deliberately open.

Authority, measures, and rules remain distinct objects connected to the role. A handoff can replace the filler without rewriting the contribution from memory.

Product Operations · role2 fillers

Portfolio planning

Maintains the shared view of commitments, dependencies, capacity assumptions, and decision dates.

Shared
M
Maya ChenLead · decides the planning format
Planning AgentSupporting · drafts dependency updates
Open workRoadmap administration removed from this role; receiving role not yet filled.
The role persists; the people and software filling it can change.

See missing work and overloaded people before a handoff fails.

Once work has a shape, the organization can see an open role, a person holding several high-consequence roles, or a contribution that has grown large enough to become a team. These are prompts for judgment, not automated staffing scores.

Clear roles also make transition more deliberate. The organization can preserve what the work was, who filled it, which relationships mattered, and what changed when the role moved or divided.

  • Move a person without making their former contribution disappear.
  • Name agent assistance without hiding the human accountability relationship.
  • Keep a visible gap visible until the team chooses how to fill or redesign it.

Roles let the organization respect two truths at once: the work needs continuity, and the person is larger than the work.

— The Particulars thesis
Start with one team

Make the work readable. Keep it close to the work.

Start with one team