DESN1001 Chap.5 Systems Design and Relational Mapping

Systems Design and Relational Mapping

Set a purposeful boundary

Begin with Systems design as a historically situated design position rather than a timeless style label. Ask what problem Systems design constructs, whose experience it centres, and what media or production conditions make the position plausible.

The schedule moves from interaction to systems design, expanding the unit of analysis from an encounter to networks of actors, resources, rules and feedback.

In a Systems design reading, a visual example becomes evidence when the compositional or material choice is described first and connected to the theoretical claim without treating appearance as self-explanatory.

Trace feedback and delay

Use Interdependence to move from description to critique.

A strong Interdependence reading identifies the audience invited by the design, the behaviour or interpretation it anticipates, and the alternatives it excludes. Build a boundary around the system for a stated purpose, map flows and delays, and distinguish a symptom from the structure that reproduces it.

Compare two artefacts through the same Interdependence categories so the contrast reveals a changed design order rather than a preference for one aesthetic. A Interdependence comparison should specify what counts as authorship, participation and responsibility in each case.

Choose leverage with humility

Test the argument with Leverage point.

A prominent actor is not necessarily the strongest leverage point; small changes to information, incentives or rules can reorganise the pattern. A Leverage point counter-reading should alter a premise, not merely add a fashionable concern after the conclusion.

Follow the Leverage point consequences into the proposed transformation: show how form, production, interaction or stewardship would change if the critique were taken seriously.

Finish the Systems design reading at the scale supported by the chosen artefact and acknowledge where a wider cultural claim would need more evidence.

Use the chapter in assessment work

Use systems mapping to connect a zine transformation to consequences over time instead of presenting a single before-and-after image.

Check the limit before concluding

Every system map is selective and must disclose whose knowledge and consequences it omits.

Conclude with an intervention, expected pathway, monitoring signal and possible displacement.

Work through the chapter case

A campus reuse scheme adds bins but contamination remains high because labels, collection contracts, vendor packaging and cleaning capacity work at cross-purposes. Begin by separating the observation from the interpretation.

Then apply Systems design to fix the object or category, use Interdependence to explain the central relation, and let Leverage point test whether the conclusion survives.

For Systems design, record the additional evidence that would distinguish the preferred account from its nearest alternative.

Repair and transfer through Leverage point

Annotate every omitted actor or delayed consequence that could overturn the preferred intervention when repairing a Systems design analysis.

After the Leverage point repair, transfer the method to a different example while holding the comparison categories steady. The aim in Systems Design and Relational Mapping is to discover whether the relationship still operates when audience, setting, evidence or practical constraint changes.

Evidence checklist for Systems design

Before finishing, verify five things.

First, define Systems design at the scale of the case. Second, identify the observation that supports the interpretation. Third, explain how Interdependence connects evidence to the claim. Fourth, use Leverage point to test an alternative or changed condition. Fifth, state the conclusion with the boundary that limits it. For practice, Map why additional bins do not resolve contamination.

The worked direction is: Connect packaging, labels, disposal decisions, cleaning and contractor sorting; locate the reinforcing confusion loop for the Systems design case in a Systems design analysis. This Systems design sequence makes the reasoning visible and gives revision a precise starting point.

Final Interdependence self-check

Read the response once for evidence and once for scope.

Circle the sentence that carries the Systems design conclusion, underline the observation that supports it, and mark the relation expressed through Interdependence. If that observation cannot support the conclusion without an unstated assumption, narrow the claim or add the missing Leverage point comparison before submitting.

What this chapter covers

• 01

  Systems design

• 02

  Interdependence

• 03

  Leverage point

• 04

  Apply Systems design in a changed case

• 05

  Test the limit through Leverage point

Select a leverage point

Key terms

Systems design

Systems design is the chapter's starting category for identifying the relevant object, practice or process. It fixes the scale of the claim before interpretation begins.

Interdependence

Interdependence describes the relationship that connects the chapter evidence to an explanation. It must be shown through a specific observation rather than asserted as a label.

Leverage point

Leverage point is the checking concept used to qualify, compare or revise the first conclusion. Its value lies in changing the answer when the evidence changes.

Systems Design and Relational Mapping FAQ

Assessment move

Redraw the map after removing one actor or delay; if the explanation does not change, decide whether that element was evidence or decoration.

Working through Systems Design and Relational Mapping in DESN1001? Sia is AskSia’s AI Arts and Humanities tutor — ask any DESN1001 Systems Design and Relational Mapping question and get a clear, step-by-step explanation grounded in how DESN1001 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.