BGLP0001 Chap.1 Prosperity as an Assemblage
Prosperity as an Assemblage
Prosperity as an Assemblage treats living well as an emergent outcome of connected social, political, economic and ecological conditions. Income and livelihoods matter, but so do belonging, identity, care, voice, environment and the ability to pursue valued futures.
The analytical task is to identify a bounded challenge, trace the relationships through which it persists and test those links with evidence at the correct scale. Place is not a decorative setting: history, culture, infrastructure and institutions shape which resources can be combined and who can reach them.
Assemblage thinking therefore replaces a list of factors with an auditable mechanism and a recommendation aimed at a specific relationship.
What this chapter covers
- 01
Emergent prosperity
- 02
Relational diagnosis
- 03
Place and history
- 04
Multiscalar evidence
- 05
System leverage points
- 06
Mechanism and counter-case
Worked example · free
Map housing pressure as a relational challenge
- 1Bound the case around household security and housing pressure.
- 2Trace the proposed links among stability, travel time, care and participation.
- 1Name evidence for each arrow and a plausible rival explanation.
- 1Recommend a response that targets the diagnosed relationship and names an implementation risk.
Key terms
- Assemblage
- A configuration of heterogeneous elements and relations that changes through time.
- Emergence
- An outcome produced through interaction rather than one isolated cause.
- Leverage point
- A relationship where a targeted change can alter wider system behaviour.
Prosperity as an Assemblage FAQ
Why is prosperity more than income?
Income provides important resources, but the course also examines security, care, belonging, voice, environmental conditions and self-realisation. An assemblage account asks how those elements interact in a place rather than assuming that one monetary measure represents the whole outcome.
Does complexity mean anything can cause anything?
No. Complexity increases the need for a precise mechanism. Name the actors, resources and institutions, state what changes through each relationship and identify evidence that would weaken the claim. An unexplained list of domains is not assemblage analysis.
How can I use this concept in coursework?
Choose one challenge and draw only the relationships necessary to explain it. Use a case to test the mechanism, compare a rival account and finish with a response aimed at the relation you diagnosed. Keep the scale of the conclusion aligned with the evidence.
Assessment move
Start each revision session by drawing a four-domain map from memory, then replace the domain labels with the actual actors and resources in a case. Write one sentence for each arrow: what changes, through which mechanism, for whom and at what scale. Next remove any arrow that lacks evidence. This turns a visually impressive map into a disciplined explanation.
Practise comparing two places where one relation differs, such as transport access or housing stability, and use the contrast to refine rather than universalise the claim. For assessment writing, build paragraphs in the order bounded challenge, relationship, evidence, rival interpretation and implication. Keep aggregate statistics separate from local experiences unless you can explain the bridge.
Review the chapter by diagnosing a new public claim without using the words social, political, economic or ecological; this forces you to name concrete institutions and processes. Finish with a pathway sentence naming the actor, leverage point and risk. The strongest answers use complexity to sharpen inquiry, not to avoid judgement.
Repeat the map with a transport case and a food-security case so that the same vocabulary does not conceal different mechanisms. In each version, mark one relation as necessary, one as uncertain and one as outside the scope of the available evidence. Then write a counter-case in which comparable income produces a different outcome because tenure, mobility or public authority changes.
This exercise separates a relational explanation from an all-purpose list. Build an evidence ledger with columns for claim, actor, scale, period, source and limitation. Interviews can establish experience and interpretation, administrative records can show reach or timing, and aggregate statistics can locate a broader pattern; none should silently answer the questions assigned to another source.
Draft a blog outline in five moves: bounded challenge, assemblage relation, concrete case, credible rival and targeted pathway. For an essay, expand the rival account into a full section and return to the same mechanism in the conclusion. Test every recommendation by asking which arrow it changes, who controls that intervention and what displaced burden could weaken another relation.
A useful peer drill is to exchange maps and ask the reader to narrate the causal sequence without extra explanation. If the reader can only name domains, replace labels with actors and active verbs. If the sequence sounds inevitable, add a condition or interruption point.
Finish by compressing the case into a three-sentence judgement that states the valid evidence, the mechanism supported and the boundary beyond which the conclusion should not travel. A final timed drill gives three minutes to draw the map, four minutes to attach evidence and three minutes to write a qualified judgement. Afterwards, mark any arrow that lacks an actor or active verb.
Repeating this routine with unfamiliar cases trains transfer without turning assemblage into a memorised template. Keep the map beside the draft and verify that each body paragraph develops one of its tested relations.