Approaches to staffing

Redundancy is when an employee's job is ended because the job no longer exists (1) — for example due to downsizing or automation — so the employee is not at fault (1).

Dismissal is when an employee's contract is ended because of their own conduct or poor performance — the employee is at fault, for example through misconduct or failing to do the job (Knowledge 1, applied). Redundancy, by contrast, is when employment ends because the job itself no longer exists — for example after automation or downsizing — so the employee is not at fault (Application 2). The key difference is therefore whose 'fault' it is: dismissal results from the employee's own behaviour, whereas redundancy results from the disappearance of the role, which is why redundant staff are usually entitled to redundancy pay while dismissed staff are not (Analysis 1).

Drawback 1 — weak loyalty and motivation. Insecure contracts reduce commitment (Knowledge). QuickServe's zero-hours and temporary staff have little job security, so they feel less loyal and motivated (Application). This leads to poorer customer service and high staff turnover, raising QuickServe's recruitment and training costs and creating an inconsistent experience (Analysis).

Drawback 2 — inconsistent quality. High turnover means constantly training new people (Knowledge). Because QuickServe always has inexperienced temporary staff (Application), they make more mistakes and deliver variable food quality and service, risking QuickServe's reputation and repeat custom in a competitive market (Analysis).

Treating staff as an asset looks well-suited to SkillWorks because it competes on specialist engineering skill — the ability to machine and assemble to tight precision tolerances. Investing in training, good pay and job security would raise the productivity and quality of its skilled engineers, cut defect and rework rates, help retain hard-to-replace technical experts, and generate the process innovation on which a specialist manufacturer depends — a genuine source of competitive advantage.

Treating staff as a cost would trim short-term labour spending and lift immediate profit, which matters if margins are tight. However, for precision engineering work this risks losing key technical staff to rivals, raising defect rates and lowering quality, and damaging the firm's reputation for expertise — costs that could easily outweigh the wage savings.

Because SkillWorks relies on scarce, high-skill technical labour that is expensive to replace and central to its quality and tolerances, the asset approach is more appropriate: the cost approach fits low-skill, price-competitive, easily-automated activities where labour is readily replaced, not specialist engineering. The right approach therefore depends on how the firm competes — and for SkillWorks, investing in its engineers protects the very skills its business is built on.

Outsourcing cleaning to a specialist contractor could reshape CleanCo's labour costs and rota flexibility, but whether it is best depends on the trade-offs and alternatives.

The case for outsourcing. Contracting a specialist converts CleanCo's fixed payroll and rota-management costs into variable, per-contract costs, so it pays only for the service hours it uses and can scale crews up or down with demand. The specialist brings trained operatives, industrial equipment and economies of scale, potentially delivering the service more cheaply and to a higher standard than CleanCo's own in-house labour-intensive operation, and it frees CleanCo's management to focus on its core facilities activities.

The case against / alternatives. However, outsourcing means losing direct control over service quality and the people delivering it, and the contractor's operatives may feel little loyalty to CleanCo, risking inconsistent standards at the customer touchpoint and reputational harm if a site is missed. There may be redundancies among existing cleaning staff (cost, morale and reputational impact), and CleanCo becomes dependent on the contractor, who may raise rates once embedded. Alternatives include keeping cleaning in-house but more flexible — part-time, multi-skilled staff on adaptable rotas — to retain control while improving flexibility.

Judgement. On balance, outsourcing is best for CleanCo only if the cleaning is non-core, the contractor can guarantee service standards, and the cost savings outweigh the loss of control and any redundancy costs. Where quality control and staff loyalty at the customer touchpoint are critical, keeping a flexible in-house crew may serve better. So outsourcing suits non-core, standardisable service activities where a specialist adds value, but CleanCo must weigh control and reputation against the cost and rota-flexibility gains — the answer depends on how central and quality-sensitive the cleaning is to its business.

With unpredictable, seasonal demand, how FlexiCorp staffs its operations is critical, and a flexible workforce is an obvious response. But whether it is the best approach depends on the type of work, FlexiCorp's strategy, and the trade-offs against motivation and quality.

The case for a flexible workforce. Flexibility lets FlexiCorp match labour capacity to demand: using temporary, part-time and zero-hours staff, and multi-skilling to redeploy people across roles, it can scale rotas up for peak-season throughput and down for troughs, avoiding paying permanent wages during low-utilisation periods. This makes labour a variable rather than fixed cost, protecting margins and cash flow through the seasonal cycle, and outsourcing non-core tasks can bring specialist expertise cheaply. For a firm whose demand swings widely, this adaptability is a powerful advantage and may be essential for survival.

The case against / limitations. However, heavy flexibility carries real costs. Insecure contracts weaken loyalty and motivation, raising staff turnover (and the recruitment and induction-training costs that come with it) and risking inconsistent quality and service at the customer touchpoint as inexperienced staff churn through — damaging FlexiCorp's reputation. There can be reputational and legal concerns (criticism of zero-hours contracts), and over-reliance on temporary labour makes it hard to build the skills and culture that underpin long-term performance. If FlexiCorp competes on quality or expertise, too flexible a workforce could undermine it.

Evaluation. How far flexibility is 'best' depends on several factors. It depends on the type of work: for low-skill, seasonal, easily-learned roles, flexibility fits well; for skilled, quality-critical roles, a stable, invested workforce matters more. It depends on FlexiCorp's strategy: a cost-competitive firm leans towards flexibility, a quality-led one towards permanence. And it depends on the balance — a core-and-periphery model (a permanent, skilled core plus a flexible periphery to cover demand peaks) can capture flexibility's benefits while limiting its costs.

Conclusion. On balance, building a flexible workforce is the best approach for the parts of FlexiCorp's staffing that face seasonal, unpredictable demand and low-skill work — there, matching labour capacity to demand protects margins and is often essential. But it is not sufficient on its own: FlexiCorp should adopt a core-and-periphery approach, keeping a stable, motivated, skilled core to protect quality, culture and continuity, and using flexible contracts to staff the variable, peripheral peak demand. The best staffing model therefore blends flexibility with stability, with the balance set by how skill- and quality-dependent each role is — flexibility is central to managing FlexiCorp's demand swings, but only as part of a balanced workforce.