Organizational structure

The span of control is the number of subordinates who are directly accountable to (report directly to) one manager. A manager with three direct reports has a narrow span; one with twelve has a wide span.

The chain of command is the formal line of authority in an organisation that runs vertically from the most senior manager at the top of the hierarchy down to front-line employees, along which instructions are passed down and information is reported up.

Delayering is the removal of one or more levels of hierarchy from an organisational structure — typically middle-management layers — in order to cut costs, shorten the chain of command and widen spans of control.

One advantage is faster communication and decision-making: a flat structure has few levels of hierarchy, so ideas and instructions pass quickly between the agency's designers and its owner, letting the agency respond fast to client feedback — an asset in a creative business. One disadvantage is limited promotion and wider spans: with few levels there are few rungs for staff to climb, which can demotivate ambitious designers, and the owner may have too many people reporting directly to supervise each one well.

Decentralising delegates decision-making authority from head office down to individual shop managers. This can make the chain more responsive: shop managers, who know local customers and competitors, could adjust stock, promotions and staffing to local demand, improving sales and customer satisfaction, while the delegated authority motivates managers by making them feel trusted. However, it also risks inconsistency and weaker control — prices, products and service could vary between shops, diluting the brand — and it relies on shop managers being capable and well trained to use the delegated authority wisely.

A matrix structure organises staff into cross-functional project teams so each employee reports to both a functional manager (e.g. head of electrical engineering) and a project manager. Introducing it can improve coordination and the deployment of specialist skills: complex engineering projects can draw the right experts from every function into one team, improving communication across departments and speeding up problem-solving and innovation. It can also raise motivation, as staff gain varied, project-based work. However, the defining dual-reporting relationship can create real problems: employees may receive conflicting instructions and priorities from their two managers, authority over resources can be unclear, and the extra coordination and meetings raise costs. For a large engineering firm running many simultaneous projects, the matrix can therefore improve flexibility and expertise-sharing, but only if reporting lines and priorities between functional and project managers are clearly agreed — otherwise the confusion could slow the very projects it is meant to accelerate.

Widening spans of control means each manager oversees more subordinates, so the retailer needs fewer managers overall. The immediate attraction is cost: with fewer management salaries the retailer's wage bill falls, directly supporting a cost-cutting objective. Wider spans also flatten the structure, shortening the chain of command so communication and decisions become faster and more responsive to customers, and they force managers to delegate more, which can empower and motivate front-line staff who feel trusted with greater authority.

However, the strategy carries clear risks. If each manager now supervises far more people, they have less time per subordinate, so problems on the shop floor may be spotted late, standards may slip and staff may feel under-supported — especially damaging in retail, where customer service and stock accuracy drive sales. Over-wide spans can overload managers, causing stress and errors, and the flatter structure offers fewer promotions, which can demotivate ambitious employees and increase turnover. Crucially, the benefits depend entirely on capability: a wide span only works if staff are well trained and enough real authority is delegated to them. If the retailer widens spans purely to save money without investing in training, the loss of control could raise other costs (poor service, shrinkage, staff turnover) that offset the salary savings.

On balance, the retailer should widen spans only selectively and only alongside investment in training and clear delegation, targeting areas where staff are experienced and tasks are routine, while keeping narrower spans where close supervision matters (e.g. high-value or complex departments). Judged this way, moderate widening can deliver genuine, sustainable cost savings; but an across-the-board widening driven by cost-cutting alone would likely damage supervision, morale and service enough to outweigh the savings. The right decision is therefore conditional on how well the retailer trains and delegates, not on cost considerations alone.

In a small family business, centralisation is natural: the owner-founders make the key decisions, giving consistency, tight control and a clear direction that reflects their values. As the business grows, however, keeping every decision at the top can become a bottleneck. Decentralising — delegating authority to department heads or branch managers — could speed up decisions, free the owners to focus on strategy, motivate managers through greater responsibility, and let the firm respond better to local or specialist knowledge as it expands into new products or areas.

There are, though, genuine drawbacks and risks specific to a family business. Decentralisation can produce inconsistent decisions that dilute the identity and standards the family has built, and founders often find it hard to 'let go' of control, which can cause conflict if delegated managers make choices the family dislikes. It also depends on having capable, trusted managers — if the firm has promoted on family ties rather than competence, delegated authority could be misused. Coordination across newly autonomous units can also weaken without strong systems.

The right answer depends on the firm's size, culture and strategy. If growth has made the owners a genuine bottleneck and the business has, or can recruit and train, capable managers, then a gradual, partial decentralisation — delegating operational decisions (staffing, local stock) while keeping strategic and brand decisions central — would capture the benefits while protecting the family's control of what matters most. If the firm is still small, or lacks trustworthy trained managers, staying largely centralised is wiser for now. On balance, a phased, selective move toward decentralisation is the strongest recommendation for a growing family business, with the pace set by how quickly it can build a capable, trusted management team.

A project-based structure organises the firm around temporary teams that form to deliver a specific project and disband when it is complete. For a construction company this fits the nature of the work well: each building project is a distinct, time-limited task with its own site, budget and team, so a dedicated project team can focus entirely on delivering it, drawing together the right mix of engineers, surveyors and site managers. This sharpens accountability, keeps teams flexible as project needs change, and lets the firm scale staffing up or down between contracts rather than carrying a fixed overhead.

However, the structure has real weaknesses. Because teams are temporary, employees may feel little job security, which can lower morale and make it hard to retain skilled workers between projects. Valuable expertise and lessons can be lost when a team disbands, and there is a risk of duplicated effort or weak knowledge-sharing across separate projects. Coordination and consistency across many concurrent sites can also suffer without a strong central function to set standards on, say, safety and quality — which in construction is critical and heavily regulated.

Whether it is the 'best' choice depends on the firm's size, strategy and how varied its work is. A project-based structure clearly suits a construction firm's contract-driven, one-off work better than a rigid functional hierarchy would, so it is a strong fit in principle. But to be the best choice it must be combined with a permanent core — retaining key specialists, a central safety/quality function and systems that transfer learning between projects — so that flexibility does not come at the cost of consistency, retention and standards. On balance, a project-based structure supported by a stable functional core is the most suitable arrangement; a purely project-based structure with no permanent backbone would risk losing expertise and control, so the judgement rests on how well the firm maintains that core.