PeopleOS · Organisation Design

Reduce ambiguity before adding more people.

PathWeave helps growing organisations design structures, roles, accountabilities and decision rights that match how the business needs to operate. The aim is clearer ownership, faster decisions and fewer bottlenecks around founders or senior leaders.

The design principle

Organisation design starts with work and decisions, not boxes on a chart.

An organisation chart can show reporting lines and still leave the operating model unclear. Good design begins with the outcomes the business needs, the work required to deliver them and the decisions that must move quickly.

Structure, roles, spans and governance should then make that work easier—not simply reflect legacy titles, individual preferences or the organisation the company used to be.

When structure becomes a growth constraint

The problem is usually visible in decisions before it is visible on the org chart.

Founder dependency

Routine cross-functional decisions still wait for the founder because ownership was never transferred as the team grew.

Role overlap

Two leaders believe they own the same outcome, creating duplicated work, negotiation and slow decisions.

Ownership gaps

Important recurring work sits between functions because every role description assumes someone else is handling it.

Layering without redesign

Managers are added between existing roles without redefining authority, leaving employees unsure who actually decides.

Title inflation

Titles are used to solve retention or progression issues even though role scope and accountability have not materially changed.

Cross-functional friction

Functions optimise their own work while handoffs, shared outcomes and escalation paths remain unclear.

Design components

What has to be clear for the organisation to work

01

Organisation structure

Functions, teams, layers and reporting relationships aligned to the work and growth model.

02

Role purpose

Why each role exists, the outcomes it owns and the boundaries between adjacent roles.

03

Accountabilities

Clear ownership of recurring outcomes, processes and cross-functional commitments.

04

Decision rights

Who decides, who recommends, who must be consulted and which decisions require escalation.

05

Spans and layers

Management spans and organisational layers that balance control, speed and manager capacity.

06

Role interfaces

Handoffs and working relationships across functions so important work does not disappear between teams.

How PathWeave approaches the work

Design around outcomes, then make accountability testable.

1. Map the workIdentify the recurring outcomes, processes and decisions that matter to the business—not only current reporting lines.
2. Find the bottlenecksTrace where decisions wait, where work is duplicated and where accountability is unclear or over-centralised.
3. Define roles by outcomesDescribe the result each role owns, its authority and the interfaces it must manage rather than creating activity lists.
4. Test spans and layersCheck whether managers have realistic capacity and whether each layer adds a distinct decision or leadership purpose.
5. Embed the designTranslate the new structure into hiring, onboarding, performance expectations, manager routines and HR systems.

Role clarity

A useful role charter is more than a job description.

A job description often lists tasks. A role charter should make the operating contract clearer: why the role exists, the outcomes it owns, the decisions it can make, the measures that matter, the interfaces it must manage and what sits outside its scope.

That clarity is especially important when an SME moves from founder-led work to functional leadership, when a startup adds its first management layers, or when a GCC or multi-location organisation introduces global-local interfaces.

Role clarity should then connect directly to recruitment, onboarding and Performance Management so the structure is reinforced in day-to-day management.

From design to operation

Structure only works when the surrounding people system supports it.

HR Operating Model clarifies how HR and managers support the organisation once roles and ownership are defined.

Performance Management turns role expectations into an ongoing management rhythm.

Recruitment & Talent helps translate role clarity into better hiring decisions.

Where the structure change is part of a broader people-system redesign, see HR Transformation.

For broad growth-stage people needs, see HR Consulting for SMEs.

Experience

Experience behind PeopleOS

Renu Dhanopia Sharma, Founder of PathWeave

Renu Dhanopia Sharma

Founder · leads PeopleOS

PeopleOS draws on HR leadership, consulting and outsourced HR delivery experience across organisation structures, policies, recruitment, performance management, HR operations and people systems.

About the founders

Focused first step

Start with one ownership problem.

The HR Health Check can review Organisation & Role Clarity as one focused area before a wider organisation-design exercise is scoped.

Make ownership clear enough that decisions no longer wait for the founder.

Start with the roles, interfaces or bottlenecks creating the most friction.

Discuss organisation design