Role Architecture: Core Work

Why this matters

In most service businesses with 10-50 people, roles evolved by accident. Someone was hired to do one thing, gradually absorbed three other responsibilities, and now carries a job title that describes maybe 40% of what they actually do. Nobody sat down and designed it this way - it just happened as the company grew. The result is overlap in some areas, gaps in others, and a team where nobody is entirely sure where their responsibility ends and someone else's begins.

Role architecture is the act of designing your team structure intentionally before it accumulates by accident.

A founder you might recognise

Last year, the founder of a 48 person logistics company in Sharjah had two operations managers who both thought they were responsible for client escalations. Sometimes both responded to the same issue. Sometimes neither did, each assuming the other handled it. He also had a finance coordinator who had picked up scheduling on the side because nobody else was doing it, which meant invoicing fell behind every time the schedule got busy. The founder knew something was off, but the team was "too busy" to stop and sort it out.

The cost of role blur at this size is not abstract. Last quarter, a duplicated client response cost the firm a contract worth AED 60,000 (USD 16,340) because the client interpreted the inconsistency as a sign the company was not in control. He could not name the moment it broke. He just lost the account.

The core exercise: The role reality map

You are going to map what people actually do versus what you think they do - and then redesign from there.

Step 1 - List every person on your team. Include yourself. Write their job title and the date they were hired or last had their role redefined.

Step 2 - For each person, list their actual responsibilities. Not what is on their job description (if one even exists). What do they actually spend their time doing week to week? Be specific. "Operations" is not a responsibility. "Scheduling client site visits and confirming crew assignments" is.

Step 3 - Identify the overlaps. Where are two or more people doing the same thing? Mark these in one colour. Common overlaps in service businesses: client communication, quality checks, scheduling, and "anything the founder asked someone to handle."

Step 4 - Identify the gaps. What critical work is not clearly owned by anyone? Mark these in a second colour. Common gaps: onboarding new hires, tracking recurring client feedback, maintaining standard operating procedures, and following up on overdue invoices.

Step 5 - Redesign three roles. Pick the three roles with the worst overlap or gap problems. For each one, write a clear role card:

• Role title - what the role is actually called
• Core responsibilities - the 4-6 things this person owns (use verbs: "schedules," "reviews," "approves," not vague nouns)
• Decision authority - what this person can decide without asking anyone, and what requires escalation
• Success measure - one or two observable outcomes that tell you this role is working (not KPIs for a dashboard - simple signals like "client site visits are confirmed 48 hours in advance")
• Interfaces - which other roles this person works with most closely, and what the handoff looks like

Use the delegation map to see which tasks belong to which roles before writing your cards.

Step 6 - Review the cards with the people in those roles. Ask them: "Does this match what you think your role is? What is missing? What should not be here?" Treat it as a conversation. The card only becomes real when both of you have edited it together.

Where to focus by team size

• 10 to 19 people: Write role cards for 3 key positions. Overlaps at this size are expensive because there is no slack.
• 20 to 34 people: Every person should have a role card. Role confusion at this size is the top reason good people leave.
• 35 to 50 people: Review role cards quarterly. At this size, roles evolve faster than documentation.

---

Working prompts

Use these in the working session. They are designed to surface the parts of role design that have gone hidden because the team has been working around them.

Ownership prompts

• For every recurring task in the business, can you name the single person who owns it without hesitation?
• Where do two or more people believe they own the same outcome?
• Which responsibility falls back to you whenever the assigned person is unavailable?
• What work happens only because one specific person remembered to do it?
• Where does the team ask for permission on decisions that should be theirs to make?

Decision authority prompts

• What is the largest amount of money each role can spend without asking you?
• Which roles can hire, fire, or discipline, and which can only recommend?
• Where does decision-making bottleneck on you for things you no longer want to decide?
• Which decisions get made twice because the first owner was overruled informally?
• Where is authority granted but not actually trusted in practice?

Gap prompts

• Which client-facing work is nobody actively owning?
• Which back-office work is technically assigned but consistently neglected?
• What part of the business runs on the assumption that "someone will catch it" if it goes wrong?
• Which gap has cost you a client, a hire, or a deadline in the last 90 days?
• What would stop happening if you stepped away for a month, and is that acceptable?

People prompts

• Which team member is doing work that no longer fits their role and is quietly resentful?
• Which team member has grown into a bigger role that has not been formally recognised?
• Where is the gap between job title and actual contribution most painful?
• Which role has been filled by three people in two years, and what does that pattern reveal?
• Where does cultural friction trace back to unclear expectations the team is being asked to read between the lines of?

---

Founder exercise

Set aside 60 minutes. Bring a printout of your current org chart, even if it is hand-drawn on a napkin. Bring two team members who would be candid with you about how the team actually works.

Part A: List the work, not the titles (15 minutes)

For each person on the team, write a list of what they actually do in a typical week. Use verbs. "Approves crew schedules each Sunday evening." "Responds to client escalations by phone." "Reconciles supplier invoices every Friday." If a person does more than 10 things, you have already found a role that needs splitting or rescoping.

Part B: Mark the overlaps and gaps (15 minutes)

Walk through the lists with your team members. Highlight every responsibility that appears on more than one person's list - those are overlaps. Then ask the harder question: "What needs to be done that is not on anyone's list?" Capture the gaps in a separate column. Both colours tell you where the design has drifted.

Part C: Redesign three roles (20 minutes)

Pick the three roles with the worst overlap or gap. For each one, write a role card using the five fields in Step 5. Be ruthless about decision authority. If the role cannot decide anything without you, you have not designed a role - you have designed an extension of yourself.

Part D: Have the conversation (10 minutes per role, after the session)

Within seven days, sit down with each of the three people whose roles you redesigned. Walk them through the card. Ask the three questions: "Does this match what you think your role is? What is missing? What should not be here?" Adjust based on their answers. The card is only real when both of you have signed off on it.

Print the final cards. Pin them where the team can see them. A role card on a shared wall or pinned in the team channel is read. A role card buried in a folder is forgotten by the second week.

---

What success looks like

You have a clear, written role card for at least three key positions. The people in those roles have seen the cards and agree they reflect reality - or you have adjusted based on their feedback. Overlaps are resolved with a single owner for each responsibility. Gaps have been assigned. Your team can answer the question "who owns this?" without looking at you.

The signal that the work is sticking: when something falls through the cracks, the team's response is to update the relevant role card themselves instead of flagging it back to you for a decision.

Common mistakes

1. Writing aspirational role descriptions instead of realistic ones. If your operations manager is currently handling both client escalations and supplier negotiations, do not write a role card that pretends these are two separate roles unless you are actually hiring for the second one this quarter. Design for what is real now, then evolve.
2. Skipping the conversation with the team. A role card you wrote in isolation and sent by email will be ignored. The 15-minute sit-down where you discuss it together is where the actual clarity happens.
3. Trying to redesign every role at once. You will stall. Start with the three most problematic roles. Once those are clean, the pattern becomes easier to apply to the rest.
4. Confusing a job title with a job design. Promoting someone to "Senior Operations Manager" without redesigning what they own changes the salary line and nothing else. The title shifts. The work does not. The frustration grows.

Emiratisation and role design

If your headcount is approaching or past 20 employees in a targeted sector, Emiratisation compliance is a role architecture problem, not a separate HR project. The role card approach described above is exactly what makes Emiratisation work or fail.

Emirati hires placed into vague roles with no documented responsibilities, no progression path, and no structured onboarding have high turnover. When an Emirati employee leaves, your compliance count resets and the cost of replacing them, recruiting again, onboarding again, and risking a gap in your MOHRE ratio often exceeds the AED 96,000 to AED 108,000 (USD 26,140 to USD 29,410) annual fine you were trying to avoid. The fine is the floor of the cost, never the ceiling.

When you design role cards for positions that will be filled by Emirati nationals, pay extra attention to three fields: core responsibilities (make them specific and trainable), success measures (give the hire a clear signal of what good performance looks like in the first 90 days), and interfaces (make sure the rest of the team knows how to work with this role directly). A well-designed role card is the difference between a compliance hire and a contributing team member.

ARCAS lens

Role design is where the People work begins. Most of what founders call team problems are actually role problems wearing a people mask. A team member who keeps missing deadlines is often working inside a role that was never properly defined. A high performer who quits often leaves because the role grew but the title and authority did not. A new hire who never finds their footing was usually dropped into a role that nobody on the inside could describe.

At IKEA Festival City, every shift on the floor had a clear role card. The cashier knew what the cashier owned. The host at the entrance knew when to call for backup. Even the team running the play area had defined responsibilities and decision authority. The store handled tens of thousands of customers a week because the roles were designed. People could focus on the work because the boundaries were clear.

---

Start now: Quick self-assessment

Rate each statement from 1 (never true) to 5 (always true):

Score 24 or above: Roles are clean. Move to the next chapter. Score 15 to 23: There are gaps worth closing. Run the founder exercise above. Score below 15: Role blur is costing you more than you realise. Do the full working session before moving on.