Units, roles and role groups
Add units and the roles in them, describe the work in a role, and read how the hours AI could free are worked out.
The Units and roles view of the Organization page describes the company as jobs and headcount, not as named people. Three things make it up:
- A unit is a named part of the company, such as Engineering or Pod A. Units can sit inside other units.
- A role is a job defined once, such as Developer at Level 2. A role at another level is its own role, with its own work.
- A role group is a role in one unit with the number of people who hold it, whether or not they have accounts. The same role can be used in several units; changing the role changes every one of them.
People with the executive, people_manager or admin ability can make every change on this page.
Getting started#
A company with no units sees No units and three choices:
- Add a unit opens a form for the first unit.
- Start from Teams copies the name of each Team as a unit, as a starting list to rename and arrange. Teams stay as they are and keep controlling who can use what.
- Import opens Import a spreadsheet, to bring units, roles and headcount in from a file. See Import an organization from a file.
Units#
- Add a unit (at the top of Units and roles) adds a top-level unit; Add a unit inside on a unit adds one within it.
- Edit on a unit changes its name, where it sits (Inside) and its Lead, a person with an account. Delete unit removes it; a unit with units or roles inside it can't be deleted until those are moved or removed.
Adding a role to a unit#
- On the unit, select Add a role.
- Choose an existing role, or A new role and give its title, and optionally its level and family.
- Enter People in this role and select Add role.
The Role panel#
Select a role's box to open the Role panel. It shows:
- The role's family, level, hours a week and Rate band name. Amounts are never shown here.
- Used in: every unit the role is in, with its number of people.
- For the role in this unit: its people, with a field to change People in this role, the people with accounts linked to it, Link a person with an account, and Remove from the unit. Only an administrator can link or remove anyone; executives and people managers can link or remove only people who report up to them, or people not placed in the chart, and never themselves. The Link a person with an account list starts with the unit's lead (or the lead of the nearest unit above it) and everyone who reports up to that lead; type a name to find anyone you may link. A person who is already in another role shows "already in" and that role, and linking them here moves them. A warning appears when more people with accounts are linked than hold the role.
- Tasks this role does today: the role's tasks, each with its name as a heading and its share of the week today ("60% of the week today"), with Edit beside it. Under the list, Described says how much of the week the shares cover; a warning appears when part of the week isn't described, the shares are scaled to fit, or a task has no time left. New work AI makes possible is listed below, apart from today's work, each task with how much of the week a person spends on it with a Coworker; it never counts as freed hours. The share of each task a Coworker takes over is shown in How the number is worked out. Tasks brought in by an import with only the older yes-or-no answers show their share of the week and no takeover line.
- How much could AI take: a bar split into A Coworker takes over and Stays with a person, then the figures, each labelled with what it is. Potential in Pod A is the ceiling from the unit's headcount (people in the role, not just those with accounts), the hours each works and the work described, for example "129.6 h a week could be freed (4 people)". It is not a plan and not realized savings; those are shown separately. When plans cover the role there, Planned in Pod A shows the potential time savings they cover. When the role is used in more than one place, Across every place this role is used adds the places up, for example "8 people (Pod A 4, Pod B 4)". How the number is worked out is closed until you open it; it lists a line for each task (its share of the week, the share a Coworker takes over, and the hours that frees per person), then People in Pod A, People in this role everywhere (when the role is used in more than one place) and the totals. A role that still has tasks or a quick estimate in the older form also shows Automatable and Augmentable in the bar. People who can plan also see What if we add a Coworker here?; see Planning a Coworker.
- Change impact: how much the role changes (Low: tools help, the job is the same; Medium: tasks shift, expectations and skills change; High: a large share of the tasks move to AI), the Support needed for the people in it, and Who communicates the change.
Describe the role and the task, not a person: titles, job descriptions and tasks are about the job.
Describing the work#
- Edit role changes the title, level, family, hours a week and rate band, a quick estimate (Automatable share and Augmentable share, used while the role has no tasks) and the job description. Delete role removes a role that is no longer used in any unit.
- Add a task (and Edit on a task) starts with What kind of work is this?: Work
that happens today or New work AI makes possible. The two percents mean the same two things
for both kinds, worded for each:
- Work that happens today. What share of this task does a Coworker take over? is a percent from 0 to 100, and the rest stays with a person. How much of the role's week this task takes today, before a Coworker (optional) is the task's share of the week, before a Coworker takes any of it over. The task's group follows from the first answer: 100 is Eliminate, 1 to 99 is Redesign, 0 or blank is Retain. Under the share box, a line says how much of the week your other tasks use and how much is left.
- New work. What share of this task does a Coworker do? is recorded and shown, and does not change the hours. How much of the week does a person spend on this with a Coworker? (optional) is the time the new work costs. New work never counts as freed hours; the time a person spends on it is subtracted.
- Draft tasks from the job description proposes tasks from the role's job description (or one you paste), each with a suggested share a Coworker takes over (what a company could realistically hand over within a year) and a share of the week, both estimates you can change, for you to check before anything is saved. See Planning a Coworker.
How the hours are worked out (Potential)#
In the Potential lens, each role in a unit shows the hours a week AI could free.
- For a task with a share a Coworker takes over, the hours a week per person are the role's hours a week x the task's share of the week x the share a Coworker takes over. The role's figure adds its tasks, and it is one number, not a range.
- Tasks with only the older answers (from an import, or a quick estimate on the role) give a range: the low end counts the work AI could do on its own (Eliminate tasks, or the automatable share) and the high end adds the work AI could help with (Redesign tasks, or the augmentable share).
- Hours a week = people in the role x the per-person hours. Example: a Software Developer works 40 hours a week. Coding takes 60% of the week and a Coworker takes over 100% of it; Code Review takes 20% of the week and a Coworker takes over 60% of it. Hours freed per person a week = 40 x 0.6 x 1.0 + 40 x 0.2 x 0.6 = 24 + 4.8 = 28.8 hours. With 4 people in the role, that is 115.2 hours a week.
- New work costs time. A task of new work with a share, such as Reviewing third-party dependencies at 2% of the week with a Coworker doing 90% of it, has the person spend 40 x 0.02 = 0.8 hours a week. The role's arithmetic shows Gross freed (28.8 hours), minus New work uses (0.8 hours), equals Net (28 hours) per person. The figures everywhere (the chart, units, planned Coworkers and the dollar amounts) use the net hours, and a net below zero shows as 0. What a Coworker does of the new work is recorded and shown, and does not change the hours.
How the shares of the week are shared out#
Only work that happens today shares the week; new work is left out. The rules, in order:
- A share you typed counts as you typed it. A typed 0 means no time today.
- Tasks with no share split what is left of the week equally. If nothing is left, they get no time and the panel names them.
- If the shares you typed add up to more than 100%, each is scaled down so they total 100%, and tasks with no share get nothing. The panel says, for example, "These add up to 160% of a week, so each is scaled to fit." Shares are never scaled up.
- If the shares add up to less than 100% and every task has one, the rest of the week isn't described, so it stays with a person and isn't counted; the panel says how much. When some task has no share, it takes the rest and nothing is left undescribed.
Where a figure is a range, the bar under it is solid up to the low end and striped up to the high end, scaled to the largest role on the page. The card at the top adds up every role in the company.
A role with no tasks and no quick estimate is Not profiled: it gets no number and is left out of the totals, which say how many roles that is.
People with the executive ability also see the company total in dollars a year at the role's
rate band, before the cost of running the Coworker. Roles with no rate band are left out of that
amount.