PMGT2822 Chap.2 Cognitive Mapping and Stakeholder Networks

Cognitive Mapping and Stakeholder Networks

Cognitive mapping turns spoken beliefs into concepts and directed relations. A concept should be specific enough to distinguish change, while an arrow should have a stated meaning such as increases, enables, delays or is required for. Ambiguous arrows create apparent agreement.

Read every connection as a claim that can be questioned, not as established causal evidence.

Individual maps preserve differences; group maps support comparison and negotiation. Combining maps is not a mechanical union. Terms may hide different meanings, and two people may disagree about direction or time scale. Retain contested links and annotate source.

A map that displays uncertainty can be more useful than a clean diagram produced through silent coercion.

Facilitation begins with the focal question and stopping rule. Elicit concepts in participants' language, ask what leads to what, probe feedback loops and validate the representation with the group. Sequence can influence salience, so allow additions and independent reflection.

Photographing the final wall is not enough; preserve definitions and decision implications.

Maps can support qualitative analysis through heads, tails, clusters, feedback loops and candidate leverage points. A highly connected concept may matter, but the count can reflect broad wording. Before intervention, test whether the relation is supported and whether changing the concept is possible.

Central-looking is not the same as causal or controllable.

Stakeholder network analysis defines nodes and relations such as advice, trust, collaboration or information exchange. Degree, betweenness and closeness answer different structural questions. Results depend on boundary and missing data.

A person central in advice may be peripheral in formal authority, and both facts can matter.

Boundary spanners connect otherwise separated groups and can translate knowledge, but they can also become overloaded bottlenecks or gatekeepers. Strengthen multiple connections, recognise invisible coordination and avoid making one person the single path for critical information.

Formal organisation charts rarely show this relational work.

Worked disagreement: sponsors map late decisions as the cause of delay; operators map incomplete field information as the cause of repeated decisions. A combined map reveals a feedback loop between data, rework and approval.

The team can test information quality and decision latency rather than debate which group is simply right.

Power and legitimacy are not network metrics. Low-power users can hold critical knowledge and bear consequences despite low centrality. High betweenness can create influence but not the right to decide.

Combine structural analysis with impact, rights, vulnerability and formal governance before designing engagement.

Use maps as living hypotheses. After an experiment or stakeholder session, mark confirmed, weakened and new links. Compare predicted and observed behaviour.

If every result is explained by redrawing arrows after the fact, the map is storytelling rather than a learning instrument.

A useful map audit samples several important arrows and writes the proposed mechanism, time lag, evidence and plausible rival explanation beside each. The team can then distinguish a relation worth testing from a convenient visual story.

Where evidence is absent, mark the link as a hypothesis instead of deleting it or presenting it as fact.

Network interventions can change the network they measure. Adding a coordination forum may reduce dependence on a broker, while publicising centrality may strengthen gatekeeping. Establish a baseline, describe the relation precisely and observe unintended redistribution of workload.

Improvement means more reliable information and fair access, not simply a denser diagram.

Missing network data are rarely random. Peripheral, overloaded or distrustful actors may be least likely to respond, making the recovered graph appear more cohesive than lived experience.

Report response patterns, seek alternative evidence and avoid converting an incomplete boundary into a confident claim about isolation or influence.

What this chapter covers

• 01

  cognitive map

• 02

  centrality

• 03

  boundary stakeholder

• 04

  map beliefs, causal claims, influence and information pathways while separating perceived relationships from verified evidence

• 05

  An arrow records a claim or relation definition, not proven causation, and a network metric does not establish legitimacy or value.

Facilitate a contested causal map

Key terms

cognitive map

A directed representation of concepts and perceived causal or influence relations used to explore how a person or group understands a situation.

centrality

A family of network measures describing structurally important positions according to a defined relation.

boundary stakeholder

A party connecting groups, domains or information communities that might otherwise remain separated.

Cognitive Mapping and Stakeholder Networks FAQ

Exam move

Retrieve the frame, map assumptions and stakeholders, generate a changed option, test one uncertainty and state the adoption boundary.

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