University College London · FACULTY OF MANAGEMENT

GBSH0049 Chap.2 Stakeholders and Organisational Needs

- one subject, every graph, every model, every mark
6 Chapters3-page Bible
Our own words - no uploaded lecturer files
Updated for this semester
Chapter 2 of 10 · GBSH0049

Stakeholders and Organisational Needs

Stakeholders and Organisational Needs moves from listing groups to analysing relationships. Managers ask who influences a choice, who experiences its consequences, whose knowledge is required and who controls resources or legitimacy. These dimensions can point in different directions: people with little formal authority may bear the greatest burden and hold essential experiential knowledge.

The chapter therefore combines influence with impact, legitimacy and dependency. It also treats engagement as a designed process with a decision boundary, accessible participation, feedback and accountability. Stakeholder awareness becomes management only when it changes who is consulted, what evidence is considered, which safeguard is added and how conflict is resolved.

In this chapter

What this chapter covers

  • 01

    Influence and experienced impact

  • 02

    Legitimacy, dependency and knowledge

  • 03

    Stakeholder relationships and resource exchange

  • 04

    Consultation, participation and decision rights

  • 05

    Power differences and missing voices

  • 06

    Accountability and feedback after engagement

Worked example · free

Plan engagement for remote monitoring

Q [6 marks]. A service considers remote monitoring. Design engagement for patients, clinicians, a supplier and governance actors. This weighting is not an official university assessment scheme.
The stakeholder field separates formal influence from experienced impact, preventing powerful actors from becoming the only voices in the analysis.The stakeholder field separates formal influence from experienced impact, preventing powerful actors from becoming the only voices in the analysis.more influencegreater impactRegulatorStaffPatientsPartners
The stakeholder field separates formal influence from experienced impact, preventing powerful actors from becoming the only voices in the analysis.
  • 2Map each group's impact, influence, knowledge and dependency.
  • 2Match the method to the issue: co-design, workflow simulation, contract specification and governance review.
  • 1State which decisions remain open and how feedback will change the design.
  • 1Retain an alternative route for people unable to use the technology.
Use different engagement methods for different dependencies rather than one general meeting. Show how patient and staff evidence enters design, how supplier duties become enforceable, and how governance controls the decision.
Sia tip — Name what each stakeholder contributes to the decision, not only what each wants.
Glossary

Key terms

Stakeholder
A party that affects, is affected by or contributes knowledge to a decision.
Legitimacy
The recognised validity of a stakeholder claim within the decision.
Participation
A process through which contributions can influence an outcome.
FAQ

Stakeholders and Organisational Needs FAQ

Is an influence-interest grid enough?

It is a useful starting point but can hide people who experience high impact with low formal power. Add legitimacy, dependency, knowledge and relationships, then explain how the map changes engagement or the decision.

How do I avoid token consultation?

State what remains open, provide accessible ways to contribute, explain how evidence will be weighed and report what changed. Consultation is weak when the central choice is fixed or participants never hear what happened to their input.

How should conflicting stakeholder claims be handled?

Clarify the interests and consequences, collect evidence about likely effects, and apply a transparent decision rule grounded in purpose and responsibility. Do not turn disagreement into stereotypes about resistant or demanding groups.

When should the stakeholder map be updated?

Update it as the decision moves from problem definition to design, implementation and review. The knowledge, influence and dependency that matter can change at each stage. A community partner may be essential for problem definition, frontline staff for workflow design, a supplier for technical correction and governance actors for safe scale-up. Date the map, record why salience changed and connect the update to engagement.

This prevents categories from appearing permanent and makes consultation more than a single meeting. It also helps managers identify a newly affected group before an implementation burden becomes established.

Study strategy

Assessment move

Choose one management decision and build a stakeholder field using influence, impact, legitimacy and dependency. Add arrows for information, resources and accountability. Identify one missing voice and explain how its absence could bias the result. Then design engagement by specifying the issue, method, timing, owner and decision influence.

Practise difficult cases where preferences conflict, such as sensitivity versus staff workload. Reframe the conflict as a threshold, workflow or resource question that can be tested. For report preparation, connect stakeholder analysis to functions, implementation and safeguards. Avoid assigning fixed motives to categories. Use evidence to describe variation and uncertainty.

Finish each practice response with accountability: who gathers input, who decides, who reports back and what condition pauses or changes implementation. Improve the map by changing the decision stage.

Before design, experiential knowledge and problem definition may be central; during implementation, workflow ownership and capability may become more salient; after launch, affected users and governance actors may reveal unintended consequences. Write how engagement changes across these stages rather than treating consultation as one event. For each group, distinguish a preference from a requirement or constraint.

Privacy, safety and lawful accountability may set boundaries, while service features permit negotiation. This prevents the vague instruction to balance everyone equally. Create an evidence ledger with the claim, source, likely bias and management consequence. Compare what powerful stakeholders say with the experience of those who bear the outcome.

Where participation is unequal, propose accessible formats, resource contribution and explain the decision boundary. Practise writing feedback to a stakeholder whose preferred option was not chosen. The response should acknowledge the evidence, explain how it affected the analysis, state the decision rule and identify what future result could trigger review.

Add a relationship audit by asking who depends on whom for information, legitimacy, delivery or remedy. A powerful actor may still rely on frontline knowledge, and a low-power group may be essential to implementation. Finish with a dated engagement plan because salience changes as the decision moves from design to delivery.

This routine builds the accountability that token consultation lacks and helps the report connect stakeholder reasoning to implementation rather than isolate it in a descriptive section.

Working through Stakeholders and Organisational Needs in GBSH0049? Sia is AskSia’s AI Management tutor — ask any GBSH0049 Stakeholders and Organisational Needs question and get a clear, step-by-step explanation grounded in how GBSH0049 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.

A+Everything unlocked
Unlocks this Bible + all 32 of your subjects at University College London, plus 1,000+ more Bibles across the AskSia library.
Sia - your GBSH0049 tutor, unlimited, worked the way the exam marks it
The full 3-page Bible + practice bank with worked solutions
Chrome extension - sync your LMS so Sia knows your deadlines
Bilingual EN / Chinese on every Bible and every Sia answer
$0.99 Trial
30-day money-back · cancel in one tap · how it works