Organisation Design, Job Architecture and Workforce Planning

Definition. Organisation design is the process of deciding how work is divided, grouped, coordinated and governed, and aligning structure with processes, reward systems and people practices, so that an organisation can execute its strategy.

Structure follows strategy. Alfred Chandler’s study of large American companies (Strategy and Structure, 1962) showed that as companies diversified into new products and markets, their centralised functional structures became overloaded and they moved to divisional structures. The principle is that structure should be chosen to fit the strategy, not inherited.

Galbraith’s Star Model. Jay Galbraith described five design policies that must be aligned: strategy (direction), structure (where decision power sits and how units are grouped), processes (how information and decisions flow across units), rewards (what behaviour is measured and paid for) and people (the skills and mindsets the design requires). A common failure is to change structure alone: for example, forming cross-functional teams while still rewarding functional targets.

Mintzberg’s configurations. Henry Mintzberg (1979) described five typical structural configurations, each relying on a different coordination mechanism.

Mechanistic and organic structures. Tom Burns and G. M. Stalker (1961) found that mechanistic structures (centralised, formal, specialised, hierarchical) suit stable environments, while organic structures (decentralised, flexible, networked) suit changing environments. Most large organisations combine both: a mechanistic operations core and organic units for innovation.

Functional structure

Employees are grouped by specialised function (manufacturing, sales, finance, HR), each led by a functional head reporting to the chief executive. Strengths: depth of expertise, economies of scale, standard policies and clear career paths within functions. Weaknesses: silos, slow cross-functional decisions, and no single owner of a product or customer below the CEO. Fits: single-business organisations with a stable product range competing on efficiency, such as a cement or steel company. HR implication: HR is usually centralised and designs common policies for the whole company.

Divisional structure

Employees are grouped into semi-autonomous divisions organised by product (consumer and industrial divisions), geography (north and south regions; India and international) or customer (retail and corporate banking). Each division has its own functional resources and usually its own profit and loss responsibility. Strengths: clear accountability for results, faster decisions close to the market, focus on specific customers. Weaknesses: duplication of functions and cost, inconsistent practices, missed synergies between divisions. Fits: multi-product or multi-market organisations. HR implication: HR business partners sit in divisions; a corporate HR centre sets common frameworks.

Matrix structure

Employees report along two dimensions at once, typically function (for expertise and standards) and business, product or region (for delivery), so many have two managers. A weak matrix gives most authority to functional managers; a balanced matrix shares it; a strong matrix gives most to project or business managers. Strengths: combines expertise with market focus and shares scarce specialists. Weaknesses: conflicting priorities between two bosses, slower decisions, unclear accountability, and a heavy demand on managers’ influencing skills. Fits: large, complex multinationals (Procter & Gamble, Unilever, Siemens) and project-based organisations. HR implication: clear decision rights (for example, a RACI matrix), joint goal-setting and performance input from both managers.

Other forms

Indian examples

Factors that allow a wider span: similar and routine work, an experienced team, good systems and procedures, co-location, and a manager with few non-managerial duties. Factors that require a narrower span: complex or novel work, inexperienced staff, dispersed teams, high risk (safety-critical work) and a manager who is also a major individual contributor.

Typical values. Many corporate averages fall between six and eight direct reports; operational supervisors of routine work often manage 10–15 or more; senior leaders of complex functions may have fewer. Very narrow spans (fewer than four) are usually a sign of excess layers, or of managerial titles given for status.

Layers are the number of levels from the chief executive to the front line. More layers slow decisions and communication and add cost. Delayering removes layers and widens spans.

Worked example. A business unit has 1,200 employees and 240 managers, an average span of 5. Raising the average span to 7 in the parts of the unit where work is routine and teams are experienced would require about 1,200 ÷ 8 ≈ 150 managers (because each manager also counts in the total) instead of 240, freeing about 90 roles. In practice, redesign starts with the work (decision rights, systems), not with removing managers, and exits must follow the law (Chapter 10).

Job characteristics model

J. Richard Hackman and Greg Oldham (1976) identified five core job characteristics: skill variety (range of skills used), task identity (completing a whole, identifiable piece of work), task significance (impact on others), autonomy (freedom in scheduling and method) and feedback (direct information about results). The first three create a sense of meaningfulness, autonomy creates responsibility, and feedback creates knowledge of results; together these lead to motivation, performance and satisfaction.

Motivating potential score (MPS) = ((skill variety + task identity + task significance) ÷ 3) × autonomy × feedback. Because autonomy and feedback multiply the score, a job low on either has little motivating potential however varied it is.

Application. Redesigning a dispatch clerk’s job so that one person handles a customer’s order from booking to delivery confirmation (task identity), with authority to resolve delays (autonomy) and a daily dashboard of on-time deliveries (feedback), raises its motivating potential.

Definition. Job architecture is the structured framework that classifies all jobs in an organisation by job family (type of work) and level (size and complexity), with standard titles, linked to the grading and pay structure.

Level guides describe each level by generic criteria such as scope of impact, complexity of problems, autonomy, knowledge and leadership responsibility, so any job can be placed consistently.

Dual career ladder. Organisations with deep technical work (R&D, engineering, technology) create a professional track that rises to senior levels equivalent to management grades, so experts can progress without managing people.

Why organisations build job architecture

Building job architecture

1. Collect job data through job analysis and existing job descriptions.
2. Define job families and sub-families.
3. Write level guides for each track.
4. Map every job to a family, sub-family and level, using job evaluation where needed.
5. Rationalise titles to a standard set (merging titles for the same work, splitting titles that cover different levels).
6. Link levels to grades and pay ranges.
7. Load into the HRIS and set governance: who approves new jobs, titles and re-levelling.
8. Communicate, especially where titles change, because titles carry status.

Definition. A competency is an observable, measurable combination of knowledge, skills, abilities and behaviours that distinguishes effective performance in a role. A competency framework is the organised set of competencies for an organisation or job family.

Structure of a competency. A definition, behavioural indicators and proficiency levels, for example: 1 Basic (applies with guidance), 2 Intermediate (applies independently), 3 Advanced (handles complex situations and guides others), 4 Expert (shapes practice across the organisation). Each role specifies the required level for each competency.

How frameworks are built. Through job analysis and expert panels; the critical incident technique (examples of very effective and ineffective behaviour); and behavioural event interviews with high and average performers, an approach developed by David McClelland and later Lyle and Signe Spencer, which identifies the behaviours that distinguish superior performers. Many organisations adapt commercial libraries such as Korn Ferry’s (Lominger) competency library.

Uses: competency-based interviews (Chapter 1), the “how” of performance (Chapter 3), training needs analysis (Chapter 4), succession and assessment centres (Section 6.10), and career paths.

Pitfalls: too many competencies (more than eight to ten per role becomes unusable), vague definitions without behavioural indicators, frameworks that are never used in actual decisions, and generic frameworks copied without validation.

Definition. Workforce planning (traditionally human resource planning, HRP) is the process of forecasting the organisation’s future demand for people and skills, assessing future supply, and planning actions to close the gaps, so that the right people with the right skills are available at the right time and cost.

Horizons. Operational workforce planning covers the next 12–18 months, linked to the budget and headcount plan. Strategic workforce planning looks three to five years ahead, focusing on capabilities the strategy requires, such as digital or AI skills.

Process

1. Scan the environment and strategy: growth plans, new plants or markets, technology, regulation (for example, the Labour Codes), labour-market conditions.
2. Forecast demand: how many people, with what skills, where and when.
3. Forecast supply: the current workforce projected forward after attrition, retirements, promotions and transfers, plus the availability of external talent.
4. Analyse gaps: shortages and surpluses by role, skill, level and location.
5. Plan actions to close gaps (the 6 Bs below) and integrate them with recruitment, development and budgets.
6. Monitor and adjust at least quarterly.

Demand forecasting

Ratio example. A quick-commerce company plans 120 new dark stores next year. At one store manager, two shift leads and 25 pickers per store, it needs 120 store managers, 240 shift leads and 3,000 pickers, before allowing for attrition. If annual picker attrition is 80%, keeping 3,000 positions filled requires about 2,400 additional hires during the year.

Supply forecasting

• Skills inventory: a database of employees’ skills, qualifications, experience and aspirations.
• Replacement charts and succession plans: who could replace each key role holder, and when.
• Markov analysis: a transition-probability matrix that projects how employees move between levels and out of the organisation.

Markov example. Current workforce: 200 executives, 60 managers, 15 senior managers. Annual transition probabilities (from history):

Process.

1. Identify critical roles: high impact on results and hard to fill, not only senior roles (for example, a kiln process specialist).
2. Define success profiles: experiences, competencies and attributes needed.
3. Assess potential successors through performance history, 9-box talent reviews (Chapter 3), assessment centres and 360-degree feedback.
4. Classify readiness: ready now, ready in one to two years, ready in three or more years.
5. Develop successors through stretch assignments, rotations, coaching and leadership programmes.
6. Review at least annually in talent councils.

Measures. Bench strength is the percentage of critical roles with at least one ready-now successor. Others include the internal fill rate for critical roles, the success rate of internal appointments and the diversity of succession slates.

Talent pools. Because roles change and named successors leave, many organisations develop pools of high-potential people for families of roles, rather than one replacement for each position.

Dave Ulrich’s model (Human Resource Champions, 1997) defined four HR roles: strategic partner (aligning HR with business strategy), change agent (leading transformation), administrative expert (efficient processes) and employee champion (representing employees’ needs). It was later applied as the “three-pillar” or “three-legged stool” operating model:

Criticisms. Hand-offs between the three pillars confuse employees about whom to contact; HRBPs get pulled into transactional work; CoEs design programmes disconnected from business reality; and shared services can feel impersonal. Newer approaches add employee self-service and chatbots, treat HR offerings as products designed around employee experience, and use agile cross-pillar teams for priority projects.

HR-to-employee ratio. The number of HR staff per 100 employees is a common efficiency benchmark; it varies widely with size, industry and the level of outsourcing and automation.