2.1 Introduction to human resource management

Human resource management (HRM) is the coordinated management of people at work: recruiting, developing, rewarding and supporting them so the organisation can meet its objectives.

HRM is not just administration. It connects workforce capability and motivation to productivity, quality, innovation and retention, while also shaping costs and employee relations. The appropriate choice depends on the organisation's strategy and context.

A growing café that promises faster delivery may need more staff, training and clearer roles. Hiring without training raises headcount but may not raise service quality; training existing staff may build capability but leave short-term capacity tight.

HRM does not automatically mean maximising output or cutting labour cost. Explain the people–objective link and acknowledge the trade-off between employee experience, flexibility and financial performance.

Human resource planning compares the people an organisation will need with the people and skills it is likely to have, then chooses how to close the gap.

Forecast demand from strategy, sales, technology and workload. Check supply using current skills, turnover, retirements and labour-market conditions. A shortage may call for recruitment or training; a surplus may lead to redeployment, reduced hiring or redundancies.

If an online retailer expects a seasonal surge, it can compare forecast orders with available warehouse hours. Temporary staff may close a short peak, whereas automation or reskilling is more relevant to a permanent capability gap.

A forecast is not a guarantee. State the assumption behind the demand estimate and distinguish a temporary numerical shortage from a long-term skills mismatch.

Employees resist change when they believe it threatens something they value or makes the future uncertain—such as job security, status, competence, routines or trust in management.

Resistance can be rational information, not simply stubbornness. A fast rollout may create fear and errors; a slow rollout may reduce disruption but allow a problem to continue. Diagnose the mechanism before choosing a response.

When a factory introduces unfamiliar software, experienced operators may worry that their expertise is being devalued. Their resistance is more likely to fall if training and a credible role in testing address that specific concern.

Resistance is not proof that a change is wrong, and communication alone does not solve every cause. Link the response to the source of perceived risk.

Change is more likely to be accepted when employees understand the reason, can influence implementation and have the capability and support to work in the new way.

Use information and consultation when uncertainty or lack of voice is the problem; use training when capability is the barrier; use participation or phased pilots when local knowledge and trust matter. A clear timetable and fair support reduce avoidable anxiety.

Before replacing a scheduling system, let staff test a pilot, train them on the workflow and publish how feedback changes the design. This addresses competence and control concerns more directly than announcing the benefits again.

No strategy guarantees acceptance. If the change genuinely removes jobs or conflicts with interests, communication may clarify the decision but cannot erase the underlying trade-off.