Why structure deserves its own decision
Most organizations in Qatar do not choose their structure; it accumulates. A department is added for a new project, a manager is promoted and keeps old responsibilities, a second office opens and copies the first. After a few years nobody can say why the boxes are arranged the way they are. Organization design is the discipline of making that choice on purpose, so that the structure helps the strategy instead of quietly working against it.
A structure is not an organization chart. The chart is only the picture. The design underneath it covers who reports to whom, how work is grouped, who decides what, and how teams hand work to one another.
Signs the structure is holding you back
- Decisions queue up. Routine approvals travel to the top because nobody below has clear authority to give them.
- Two people think they own the same work — or nobody does, and it surfaces only when something goes wrong.
- Managers with one or two direct reports next to managers with fifteen.
- Titles that do not match the work. Grading and pay become hard to defend because the roles underneath are unclear.
- Growth added on top. New activities were bolted onto existing units rather than placed where they fit.
- The chart on file is not the structure people actually work in.
Five design questions to answer in order
- What must the organization be good at? Start from strategy and the few capabilities that matter most. A structure designed around today's departments will protect today's habits.
- How should work be grouped? By function (finance, HR, operations), by service or product, by customer segment, or by location. Most organizations use a mix; the point is to choose each grouping deliberately and know what it trades off.
- How many layers and how wide a span? Too many layers slow decisions and blur accountability. Spans that are too wide leave people unsupported; spans that are too narrow add cost and encourage over-supervision. There is no universal number — the right span depends on how complex and how similar the work is, and how experienced the team is.
- Who decides what? Write down decision rights: what each level can approve, what it must recommend, and what it must escalate. This is where many restructurings fail, because the boxes move but the authority does not.
- How do units work together? Identify the handoffs that matter most, such as recruitment to onboarding, or sales to delivery, and assign a clear owner for each.
Common mistakes we see
- Designing around people. Building boxes to fit the individuals currently in post produces a structure that has to be redrawn at the next departure. Design the roles first, then decide who fills them.
- Copying another organization's chart. A structure that suits a different size, sector or ownership model may not suit yours.
- Changing the chart but not the governance. Without updated decision rights, approval limits and reporting routines, the old behaviour returns within months.
- Skipping the people side. Even a sound design fails if the people affected learn about it late, or do not understand why it is changing.
- Treating it as a one-off. Structure should be reviewed when strategy, size or services change, not left for a crisis.
Points that matter in a Qatar setting
Several features of the local context affect design choices. Many organizations operate in both Arabic and English, so reporting lines, titles and role descriptions need to read the same in both languages. Workforces are often made up of many nationalities, which makes clear, written decision rights more valuable than assumptions about "how things are done". Groups with several entities, sister companies or shared services need a deliberate answer on what is centralized and what stays with each business. And organizations that grow quickly, through new projects or new contracts, should decide in advance how new units will be added so the structure does not drift again.
From structure to roles, grades and pay
Organization design is the first link in a chain. Once the structure is agreed, each role needs a clear job description. Those descriptions are then evaluated and placed in a grading structure, which in turn supports pay decisions, performance objectives and workforce planning. If the structure is unclear, every later step inherits the confusion — which is why we recommend settling it first.
A practical way to start
- Document the structure as it really works today, including informal reporting lines, rather than relying on the chart on file.
- List the strategic priorities for the next two to three years and ask which of them the current structure supports and which it obstructs.
- Test two or three options against the five questions above, including a "do less" option that changes only what is clearly broken.
- Agree decision rights for the chosen option before announcing it.
- Plan the transition: communication, handover of responsibilities, updated job descriptions and a review date.
Brilyanz supports organizations in Qatar with organization structure reviews, decision-rights frameworks and the job descriptions and grading that follow from them. See our HR services or book a consultation to talk through your situation.