L5M1 Managing Teams and Individuals — Paper 1

Sample Answer (~750 words):

Organisational culture can be described as the character and personality of an organisation — the sum of its values, traditions, beliefs, behaviours, and shared assumptions about how things get done. Charles Handy, in Understanding Organisations (1976, refined in 1985), proposed one of the most widely used taxonomies of organisational culture, identifying four distinct culture types: Power, Role, Task, and Person. Each carries implications for how authority is exercised, how decisions are made, and how team members relate to one another. For a procurement function — which by its nature sits across the organisation and interacts with multiple stakeholders — the dominant culture profoundly shapes how the team operates.

Power Culture is centralised around a single leader or small group at the centre of a 'spider's web'. Authority radiates outward, formal procedures are minimal, and decisions can be made very quickly. Power cultures often emerge in entrepreneurial start-ups or family-owned businesses, where the founder retains personal control. In a procurement team operating in a Power Culture, buyers must align closely with the leader's preferences; sourcing decisions may be made informally through personal influence rather than documented selection criteria. Speed is the strength here, but consistency, transparency, and audit trails can suffer.

Role Culture is hierarchical and rule-based, often visualised as a Greek temple where each pillar is a specialised function and the pediment above is co-ordinating management. Authority derives from position, not personal capability. Procedures, job descriptions, and reporting lines are clearly defined. Public-sector organisations, large utilities, and traditional manufacturers tend to be Role Cultures. A procurement team in this environment will follow well-defined sourcing processes, contract standing orders, and approval workflows — UK Local Authorities operating under Public Contract Regulations are a good example. The strength is consistency and accountability; the weakness is rigidity, slow decision-making, and limited innovation.

Task Culture is project-oriented and team-based, often visualised as a net or matrix. Power flows to whoever has the relevant expertise for a given task, regardless of formal seniority, and teams form and dissolve around objectives. Consultancies, technology firms, and project-based organisations tend to operate this way. A Task Culture procurement team would form cross-functional sourcing teams pulling in engineering, finance, and operations expertise as needed; collaboration is strong and innovation can flourish. The downside is that resources can be hard to control, and it can be difficult to embed standardisation or build deep specialist expertise in any one area.

Person Culture is the rarest of the four, found where the organisation exists primarily to serve the interests of its individual professionals — barristers' chambers, GP partnerships, and academic departments are typical examples. Authority is distributed and consensual; the organisation provides infrastructure rather than direction. A procurement team within a Person Culture would likely struggle to enforce category strategies or supplier consolidation, since each professional may insist on choosing their own preferred suppliers.

The dominant culture shapes procurement behaviour in several practical ways. In a Power Culture, the procurement team's success depends on building rapport with the leader. In a Role Culture, success depends on mastering and respecting the documented process — innovation must be channelled through the right approval routes. In a Task Culture, the team must be comfortable with ambiguity and excel at cross-functional collaboration. In a Person Culture, the team must rely on persuasion and shared interest rather than hierarchical authority. The same procurement intervention — say, a category-management initiative — will be received and executed quite differently in each environment.

It is important to recognise, however, that Handy's four-type model is a simplification. Most real organisations contain elements of all four, and culture varies between functions and sites. A Local Authority's procurement function may be strongly Role-based, while its policy-development teams operate as a Task culture. The model also says little about how cultures change over time or about the influence of national or sector culture. Despite these limitations, Handy's framework remains a powerful diagnostic tool: by identifying the dominant culture, a procurement leader can choose interventions that will succeed in that context rather than fight against the prevailing grain.

📋 LO: 1.0 — Understand, analyse, and apply management and organisational approaches
📐 AC: 1.4 — Evaluate influences that shape organisational behaviour
📑 Indicative content: 1.4.4 — The cultural environment and methodologies for assessing cultural types

Sample Answer (~800 words):

Herzberg's Two-Factor Theory was developed by the American psychologist Frederick Herzberg in The Motivation to Work (1959), based on his now-famous study of around 200 engineers and accountants. He asked them to recall workplace incidents that made them feel especially good or especially bad about their jobs. From the patterns in their responses, Herzberg concluded that the factors that produce satisfaction and motivation at work are different in kind from the factors that produce dissatisfaction — they are not opposite ends of a single continuum, but two separate dimensions.

He labelled the satisfiers motivators — these are intrinsic to the work itself and include achievement, recognition, the work itself, responsibility, advancement, and personal growth. When present, motivators drive higher performance, engagement, and creativity. When absent, employees are not actively dissatisfied — they are simply not motivated.

He labelled the dissatisfiers hygiene factors — these are extrinsic to the work and include company policy and administration, supervision, working conditions, salary, peer relationships, and job security. When deficient, hygiene factors cause real dissatisfaction and disengagement. But improving them above an acceptable threshold does not produce positive motivation — it merely removes the source of dissatisfaction. Salary occupies a special position: a low salary is a hygiene problem, but a generous salary is not, on its own, a motivator.

The implication of Herzberg's framework is that managers cannot motivate by removing dissatisfaction alone. They must first ensure hygiene factors are at an acceptable level, then build motivators into the role itself.

Application by a procurement manager. A procurement manager seeking to improve team engagement should think in two parallel streams.

First, address hygiene factors so demotivators are removed. Salary should be benchmarked against the market for comparable procurement roles — if the team is materially under-paid, no amount of intrinsic enrichment will compensate. Working conditions matter: providing decent workspace, modern e-sourcing tools, and access to supplier-management software prevents frustration. Company policies that hinder procurement professionals — convoluted approval workflows, opaque budget processes, or poor communication from senior leadership — should be challenged and streamlined. Relationships with peers and supervisors deserve attention through respectful management, regular communication, and a supportive culture. Once these hygiene foundations are in place, the manager has the conditions for motivation, but has not yet produced motivation itself.

Second, and crucially, the manager must introduce motivators by enriching the work. Achievement can be cultivated by giving team members responsibility for end-to-end sourcing projects rather than fragmenting the work into low-visibility tasks; a buyer who runs a category from market analysis through to contract signature gains a clear sense of accomplishment. Recognition should be specific, timely, and visible: a thank-you in a team meeting after a successful negotiation, or a written commendation copied to senior leadership, costs nothing and matters more than money. The work itself can be made meaningful by linking sourcing decisions to organisational outcomes — explaining how a sustainable-sourcing initiative supports the company's net-zero targets, for example, gives the work purpose. Responsibility can be increased by delegating supplier-relationship ownership, granting authority within defined value thresholds, and trusting buyers to make decisions without micromanagement. Advancement and growth can be supported by funding CIPS qualifications, sponsoring attendance at industry conferences, and creating a clear career pathway from buyer to senior buyer to category manager.

Practical examples bring this to life. A procurement manager who notices declining engagement might first refurbish a tired open-plan office (hygiene) and then assign each buyer a strategic category to own end-to-end with quarterly board exposure (motivator). The hygiene investment alone would have moved the team from 'fed up' to 'neutral'; the motivator change is what turns 'neutral' into 'engaged'.

Herzberg's theory has been criticised. The original 1959 study sample was small and limited to white-collar male professionals in a single industry — its generalisability has been questioned. The theory also assumes a fairly static set of needs across individuals, when in reality what one person finds motivating (autonomy, variety) may be hygiene for another. The strict separation between motivators and hygiene is also an oversimplification — salary in particular can act in both registers. Nevertheless, the framework's enduring usefulness lies in its central insight: removing pain is not the same as creating pleasure. A procurement manager who internalises this distinction will allocate effort more wisely than one who assumes that paying more or holding more meetings will, on its own, produce a more engaged team.

📋 LO: 2.0 — Understand and apply approaches to managing individuals
📐 AC: 2.3 — Analyse motivation theories and approaches
📑 Indicative content: 2.3.4 — Content theories of motivation

Sample Answer (~750 words):

Tuckman's group-development model was first proposed by Bruce Tuckman in 1965 with four stages, and later expanded with Mary Ann Jensen in 1977 to add a fifth. It remains one of the most widely used models for understanding how groups mature from a collection of individuals into a high-performing team, and is particularly valuable to managers who form project teams, cross-functional sourcing teams, or supplier-development working groups.

Forming is the initial stage when group members come together. Behaviour is typically polite, tentative, and dependent on the leader for direction. People focus on understanding the task, learning each other's names and roles, and avoiding controversy. Productivity is low; uncertainty is high. The manager's role is to provide clear objectives, define roles, and create psychological safety.

Storming follows once members feel safe enough to express disagreement. Personalities emerge, conflict surfaces over priorities, working methods, and informal hierarchy, and some members may challenge the leader. This is the most uncomfortable stage but also a necessary one — without storming, real norms cannot form. The manager must facilitate constructive disagreement, mediate where conflict becomes destructive, and resist the temptation to suppress all dissent.

Norming emerges as the group settles its disputes and develops shared expectations about behaviour, communication, and decision-making. Trust grows, members begin to identify as a team rather than as individuals, and there is a collective sense of 'how we do things'. Productivity rises noticeably. The manager's task shifts from refereeing to coaching — reinforcing the agreed norms and removing remaining obstacles.

Performing is the stage where the team operates with high autonomy and high effectiveness. Members understand each other's strengths, communication is fluid, and the team can take on complex problems with confidence. The manager can step back into a more strategic, supportive role — providing resources, removing organisational barriers, and championing the team externally.

Adjourning (Tuckman & Jensen, 1977) is the final stage when the team disbands, either because the project is complete or because reorganisation breaks it up. There can be a sense of loss, especially in long-standing teams; a thoughtful manager will mark the ending — celebrating achievements, capturing lessons learned, and supporting members into their next assignments.

Belbin's team-roles framework complements Tuckman by addressing not the time dimension of team development but the composition dimension. Meredith Belbin, working at Henley Management College in the 1970s and 1980s, identified nine preferred behavioural roles individuals tend to play in teams: Plant (creative ideas-generator), Resource Investigator, Co-ordinator, Shaper (driving force), Monitor-Evaluator, Teamworker, Implementer, Completer-Finisher, and Specialist.

Applying Belbin during storming. The storming stage is where Belbin's diagnostic value is highest. Conflict often arises because people misread each other's behaviour: a Shaper's drive can be experienced as aggression; a Plant's stream of ideas can frustrate an Implementer who wants to get on with the existing plan; a Monitor-Evaluator's measured scepticism can be heard as obstruction. By having team members complete a Belbin self-perception inventory and sharing the results openly, the manager can reframe conflict as a difference in role-preference rather than personal failing. A Shaper can be told 'your drive is exactly what we need at the start of a sourcing project, but please give the Monitor-Evaluator time to surface risks before pushing for a decision'. This shifts the conversation from blame to design.

Applying Belbin during norming. As the team begins to form shared norms, the manager can use Belbin to ensure those norms accommodate the team's actual composition rather than an idealised one. If the team lacks a Completer-Finisher, the agreed norm should explicitly assign someone to drive deadlines and check details — otherwise, a brilliant Plant-heavy team will generate ideas but never deliver. If the team is heavy on Teamworkers but light on Shapers, the manager may need to lead more directively at the start of each task. The norming-stage agreement on 'how we work' becomes more realistic when grounded in role data.

Both models have limitations. Tuckman's stages are not always strictly linear — established teams can be thrown back into storming by the arrival of a new member or a major change in scope. Belbin's nine roles emerged from observation, not controlled experiment, and the self-perception inventory is open to social-desirability bias. Even so, used together, the two frameworks give a procurement manager a powerful pair of lenses: one for diagnosing where the team is in its development, the other for understanding who is in it. Used honestly, they accelerate the journey from forming to performing.

📋 LO: 3.0 — Understand and apply approaches to planning and managing work groups or teams
📐 AC: 3.2 — Analyse theory and practice of developing effective work groups
📑 Indicative content: 3.2.2 — Theories relating to the stages of group/team development; 3.2.3 — Individual strengths and team roles

Sample Answer (~800 words):

Trust between procurement and its internal stakeholders is the foundation of an effective supply function. Without it, procurement is reduced to a downstream order-processor — invited late, briefed poorly, and blamed when supplier outcomes disappoint. With it, procurement is treated as a strategic partner whose insight into markets, suppliers, and total cost shapes the organisation's decisions. The CIPS framework on stakeholder trust draws on a body of organisational-trust research — including Mayer, Davis & Schoorman's well-known three components of trust (ability, benevolence, integrity, 1995) — and emphasises that trust must be deliberately built rather than assumed. For Adam, inheriting a transactional, low-trust relationship at JKL Ltd, the following four actions will move the dial.

Action 1 — Engage early through cross-functional involvement at the requirement-definition stage. Adam should establish a routine where procurement is brought into stakeholder conversations before a specification is finalised. Concretely, this means a standing seat at Operations' capital-planning meetings, an early-warning channel from Engineering on new product introductions, and a quarterly review with Finance on category spend trajectories. The mechanism is straightforward: engaging early gives procurement the chance to add value (market intelligence, alternative-supplier options, total-cost-of-ownership analysis) rather than simply executing what others have already decided. Repeated, visible value-adding interactions are how Mayer et al.'s 'ability' component of trust is built. Stakeholders begin to see procurement as a source of insight rather than a process bottleneck.

Action 2 — Co-create category strategies with stakeholder input. Rather than producing category strategies in isolation and then asking Operations or Engineering to comply, Adam should run joint workshops where stakeholders contribute to the strategic-sourcing approach for the categories that affect them most. For example, the Engineering team should help shape the strategy for technical components; Operations should help shape the strategy for MRO supplies and indirect services; Finance should help frame the savings-tracking methodology. Co-creation matters because people support what they help build — a strategy that bears stakeholder fingerprints is far more likely to be honoured. It also signals 'benevolence' in the trust framework: that procurement is genuinely interested in stakeholders' interests, not pursuing its own agenda. Over time, this transforms procurement from a perceived constraint into a recognised collaborator.

Action 3 — Establish transparent reporting and shared KPIs. Adam should agree a small set of joint KPIs with each stakeholder function — perhaps on-time delivery and quality with Operations, working-capital impact with Finance, and innovation pipeline with Engineering — and report against them in a way both parties can see. Open-book reporting on supplier performance, savings achieved, and contract risks builds the 'integrity' component of trust: stakeholders can verify that procurement's claims match the underlying data, and discrepancies are surfaced quickly and honestly. The CIPS Cost Transparency principle, often associated with open-book costing in supplier relationships, applies equally to internal stakeholder relationships. Shared reporting forces the conversation away from anecdote ('procurement is slow') and onto evidence ('the average sourcing cycle for indirect categories is 47 days; here's where the time goes').

Action 4 — Invest in personal relationships through structured stakeholder engagement. Trust is ultimately interpersonal as well as institutional. Adam should ensure that each senior stakeholder has a named relationship-owner within procurement — a category manager who attends their meetings, understands their priorities, and is on first-name terms. He should also model this behaviour himself by holding monthly one-to-ones with the Heads of Operations, Finance, and Engineering, treating them as customers whose feedback shapes procurement's service. Belbin's framework on team roles is helpful here: assigning a Teamworker-strong category manager to a frustrated stakeholder builds bridges faster than assigning a Shaper. Mayo's Hawthorn observation that productivity rises when people feel attended to applies to stakeholder relationships every bit as much as to direct reports.

These four actions reinforce one another. Early engagement creates the opportunities to demonstrate ability; co-creation builds perceived benevolence; transparent reporting establishes integrity; and personal investment makes the institutional trust durable. None of them is a quick fix — research on organisational trust consistently shows that trust is built slowly through repeated small interactions and lost quickly through a single breach. Adam should set realistic expectations: visible improvement in stakeholder satisfaction is achievable within six months, but cultural change is a multi-year programme.

It is worth acknowledging the limits of any single intervention. Trust-building can be undermined by structural factors outside Adam's control — for example, if JKL Ltd's incentive structures reward functional silos, no amount of relationship work within procurement will fully compensate. Adam may need to escalate such structural issues to the executive team alongside his own initiatives. With that caveat, the four actions above represent a realistic, evidence-based starting plan for moving procurement from a transactional to a trusted-partner role.

📋 LO: 4.0 — Assess the application of management concepts and principles in a procurement and supply function
📐 AC: 4.2 — Evaluate the role of the procurement and supply team and how it builds trust with stakeholders
📑 Indicative content: 4.2.3 — Building and maintaining trust with stakeholders; 4.2.4 — Collaboration for mutually beneficial stakeholder relationships