Unit 2 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.

Apply the syllabus factors to the planning gap. Demographic change can alter retirements and the age or skills available; greater labour mobility and immigration can widen external recruitment supply, while restrictions can narrow it. Flexi-time can help match staffing hours to demand and improve retention, but complicates coordination. The gig economy can provide rapid numerical flexibility, but may weaken continuity, firm-specific skills and employee commitment. Classify each influence as internal or external, then trace whether it changes the number of workers required, the skills required, the available supply or the preferred working pattern.

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.

Organisational structure describes how work is divided, who reports to whom, where decisions are made and how information moves.

Key ideas include hierarchy, chain of command, span of control, delegation, centralisation and decentralisation. They are connected: giving a team more decision authority can speed local responses but requires information, capability and accountability.

A store manager who can reorder stock locally may respond faster to demand, while headquarters keeps pricing decisions. The structure works only if the manager receives reliable sales data and knows the limit of the delegated authority.

A structure is not just a chart and decentralisation is not automatically better. Judge the fit between authority, information, risk and the organisation's objectives.

Complete the terminology map: levels of hierarchy are the management layers; the chain of command is the formal route of authority; span of control is the number of direct reports; delegation transfers authority for a task while the manager retains ultimate accountability. Bureaucracy relies on formal roles, rules and procedures. Centralization keeps major decisions near the top, while decentralization moves them downward or outward. Delayering removes management levels, often widening spans and shortening communication routes. A matrix gives employees dual reporting relationships, commonly to functional and project managers, which shares expertise but can create conflicting priorities.

An organisation chart is a model of formal reporting relationships and responsibility; it does not show every informal influence or communication path.

Tall structures usually give narrower spans of control and more layers, which can support supervision but slow upward communication. Flat structures reduce layers and may speed decisions, but managers can face a wider span and employees may need greater autonomy. Functional, product and matrix designs group expertise in different ways.

A global firm organised only by function may build specialist knowledge but struggle to coordinate a product launch across regions. A product structure may improve focus while duplicating specialist roles.

Flat does not mean unstructured, and a matrix does not remove conflict. Explain which coordination problem the chosen chart solves and what new cost it creates.

Read a chart in a fixed order: count hierarchy levels, trace each chain of command, estimate managers' spans of control, then identify how units are grouped. Grouping by function concentrates specialists; by product gives each offering clearer focus; by region adapts decisions to local markets but can duplicate functions. A flat chart has fewer layers and usually wider spans; a tall chart has more layers and usually narrower spans. The chart shows formal authority, not necessarily the real flow of influence.

The suitability of an organisational structure depends on the business's size, strategy, technology, environment and need for control or flexibility.

Ask what work must be coordinated, how quickly conditions change and where expertise sits. A stable, standardised operation may benefit from clear hierarchy; a project-based or rapidly changing firm may need cross-functional teams and wider delegation.

A small design studio can keep a flat structure while staff work directly with clients. As it grows, adding specialist leads may protect quality, but extra layers can slow creative decisions.

There is no universally best structure. A recommendation must name the context, the mechanism and the trade-off—not merely call a structure flexible or efficient.

Management plans, organises and controls resources to achieve objectives. Leadership influences people and gives direction, meaning and commitment—especially when the path is uncertain.

The roles overlap but are not identical. A manager may allocate tasks and monitor a process; a leader may build trust around a difficult change. Effective organisations need both reliable execution and willingness to adapt.

During a product recall, a manager coordinates stock isolation and customer records, while a leader explains the reason for the response and keeps staff focused despite reputational pressure.

A job title does not prove leadership. Judge the behaviour and the effect on coordination, motivation and shared action.

A leadership style is the pattern a leader uses to make decisions, communicate and involve employees—for example autocratic, paternalistic, democratic or laissez-faire approaches.

A directive style can be fast and clear in an emergency or with inexperienced staff, but may reduce ownership. Participation can improve ideas and commitment when time and expertise are available, but it can slow a time-critical decision. Delegation needs capable people and clear boundaries.

A new laboratory safety breach may justify immediate direction first, followed by a participative review of how procedures failed. The same style need not fit every stage.

Do not label one style universally best. Link the recommendation to urgency, risk, employee readiness and the objective being pursued.

Taylor's scientific-management approach emphasizes standardized tasks, close measurement and financial incentives; Maslow proposes a hierarchy from physiological and safety needs through belonging, esteem and self-actualization; Herzberg separates hygiene factors that prevent dissatisfaction from motivators that create satisfaction.

Taylor may raise output where tasks and individual results are measurable, but can understate social and intrinsic needs. Maslow helps managers consider unmet needs, but people do not always move through a fixed sequence. In Herzberg's model, pay, policy and conditions are mainly hygiene factors, while achievement, recognition, responsibility and growth are motivators; improving hygiene can remove dissatisfaction without necessarily creating lasting motivation.

For repetitive packing work, a piece-rate bonus may increase effort as Taylor predicts, safe conditions may address a lower-level Maslow need, and enriched responsibility plus recognition may add Herzberg motivators. The best intervention depends on whether the problem is low pay, insecurity, weak belonging or an unchallenging job.

Do not treat the theories as universal laws or assume pay is irrelevant in Herzberg's model. Diagnose the employee, task and source of dissatisfaction, then evaluate evidence and implementation costs.

Financial rewards include pay, bonuses, commission, profit-related pay and benefits. They can attract staff or focus effort, but the metric rewarded may distort behaviour.

Ask whether the reward is individual or team-based, short- or long-term, and whether performance is measurable without encouraging unsafe or low-quality shortcuts.

A sales commission can increase volume, yet a customer-retention bonus may better support a subscription business.

Higher pay does not guarantee motivation, and an incentive that changes one metric can damage another.

Distinguish the syllabus reward types. Salary is fixed annual pay; wages are based on time or output (piece rate); commission links pay to sales; performance-related pay links it to assessed targets; profit-related pay shares organizational profit; employee share ownership gives employees an ownership stake; fringe payments are benefits such as insurance or a company car. Match the measure to controllable performance: piece rates or commission can sharpen effort but may sacrifice quality, cooperation or customer fit, while profit or shares align longer-term interests but weakly connect one employee's effort to the final reward.

Non-financial rewards include recognition, responsibility, development, flexible work and a supportive environment. They can improve intrinsic motivation and retention when they meet a real employee need.

Select the reward that changes the relevant experience: autonomy for ownership, development for progression, recognition for contribution, or flexibility for work–life constraints.

Offering a skilled analyst ownership of a client dashboard may motivate more than a generic “employee of the month” award.

Non-financial does not mean cost-free, and the same reward will not fit every employee or role.

Job rotation moves employees among tasks to build variety and breadth; job enlargement adds tasks at a similar responsibility level; job enrichment adds autonomy, challenge and responsibility. Empowerment grants authority to make decisions. Purpose or the opportunity to make a difference connects work to valued impact, while teamwork can add belonging, mutual support and shared problem-solving. Choose the mechanism that addresses the actual need: adding more routine tasks is enlargement, not enrichment, and may increase workload without increasing motivation.

Training develops knowledge or skill; induction helps a new employee enter safely, on-the-job learning uses the workplace, and off-the-job learning creates protected practice.

Start with the capability gap, choose a method that fits risk and complexity, then check transfer through observed performance. Training without time, tools or follow-up may not change behaviour.

A new machine operator can learn procedures in a supervised simulation before a competency check on the production line.

Attendance is not learning. Evaluate whether the new capability appears in the job and whether the benefit exceeds the training cost.

Formal communication follows recognised channels and records; informal communication spreads through relationships and conversation. Both can carry useful information.

Choose a channel for the purpose: a safety instruction needs clarity and traceability, while an informal conversation may surface concerns quickly. Good communication also needs feedback, so the sender can check what the receiver understood.

A manager can publish a new process formally, then hold a short team discussion to discover a practical problem before implementation. The second channel does not replace the first; it improves the loop.

More messages do not mean better communication. Judge accuracy, reach, speed, feedback and the risk of an unrecorded or misunderstood decision.

A communication barrier prevents a message from being received, understood or acted on as intended.

Common mechanisms include jargon or language differences, information overload, status and cultural assumptions, poor timing, noise, and a channel with no feedback. Diagnose the point of failure before choosing a fix.

If a technical team sends an acronym-heavy update to frontline staff, the message may be delivered but not understood. A plain-language summary plus a check-back can repair meaning more effectively than sending the same document again.

Silence is not proof that communication succeeded. Check understanding and distinguish a channel problem from disagreement with the decision.