Skip to content
Thinking in Diagrams

Diagnosing Tangled Situations

System archetypesPart V · Pattern and Judgment · Chapter 11 of 12 · the second of two chapters on system archetypes

What if more than one story is true at once? Four more archetypes: two sides answering each other, growth short of capacity, a target that slips, partners who get in each other’s way. One loop structure can be read as two of these stories, and one situation can hold two archetypes, coupled through the variables their loops share.

Print this chapter, with a sheet for each exercise and the answers at the back, from its PDF.

In one school class, each family holds a birthday party for its child and sets a limit on how many children it invites. Each family measures its party against the others’: a party that looks small grows at the next birthday, and one that looks large makes the next family invite more. Guests over the limit are cut from the next party’s list, a birthday later, or the family raises its limit toward the party it held.

System archetype: escalation; eroding goals Variables: our party's size; other families' parties; how ours compares; our limit on guests; guests over our limit. Effects: our party's size to how ours compares (+, same direction); how ours compares to our party's size (−, opposite direction); other families' parties to how ours compares (−, opposite direction); how ours compares to other families' parties (+, same direction); our limit on guests to guests over our limit (−, opposite direction); guests over our limit to our party's size (−, opposite direction, with a delay); our party's size to guests over our limit (+, same direction); guests over our limit to our limit on guests (+, same direction). Loop B1 ours grows, balancing: our party's size, how ours compares, and back to our party's size. Loop B2 theirs grow, balancing: other families' parties, how ours compares, and back to other families' parties. Loop B3 cut back, balancing: our party's size, guests over our limit, and back to our party's size. Loop B4 limit up, balancing: guests over our limit, our limit on guests, and back to guests over our limit. Declared: escalation, which the structure matches. Declared: eroding goals, which the structure matches, with its delay. + − − + − − + + our party's size other families' parties how ours compares our limit on guests guests over our limit B1ours grows B2theirs grow B3cut back B4limit up Archetype: escalation Archetype: eroding goals

B1 and B2 run through how ours compares, one family’s party against the others’: escalation. B3 and B4 run through guests over our limit, the party’s size less the limit: eroding goals, with its delay on the cut. Both archetypes are declared, and the loops match both.

Escalation is two sides acting on one comparison, relative position: A’s activity raises it and B’s lowers it. When it falls, A does more (B1); when it rises, B does (B2). Both loops are balancing, and together they trace a figure-8 that reinforces: each side’s response is the other’s reason to respond. The figure-8 passes relative position twice, so it is no loop of its own and carries no label. Kim notes that it takes two sides to escalate and one to stop, and asks whether the relative measure between them can change.

System archetype: growth and underinvestment Variables: growth effort; demand; performance; perceived need to invest; capacity. Effects: growth effort to demand (+, same direction); demand to growth effort (+, same direction); demand to performance (−, opposite direction); performance to demand (+, same direction); performance to perceived need to invest (−, opposite direction); perceived need to invest to capacity (+, same direction, with a delay); capacity to performance (+, same direction). Loop R1 growth loop, reinforcing: growth effort, demand, and back to growth effort. Loop B1 limit loop, balancing: demand, performance, and back to demand. Loop B2 capacity loop, balancing: performance, perceived need to invest, capacity, and back to performance. Declared: growth and underinvestment, which the structure matches, with its delay. + + − + − + + growth effort demand performance perceived need to invest capacity R1growth loop B1limit loop B2capacity loop Archetype: growth and underinvestment

Growth and underinvestment is limits to growth with a third loop. Growth effort and demand raise each other (reinforcing loop R1, the growth loop) until demand lowers performance (balancing loop B1, the limit loop). Performance below the performance standard raises the perceived need to invest, which adds capacity after a delay and restores performance (B2, the capacity loop). Where the standard is lowered as performance falls, the need to invest falls too, and performance with it (Kim). Kim puts the leverage in judging capacity against demand before performance falls. The performance standard acts from outside the loops, so the template leaves it out.

In eroding goals, a gap between a target and actual performance closes two ways: corrective action raises actual performance, after a delay (B1), and pressure to lower the target brings the target down (B2). Kim calls eroding goals drifting goals. Lowering the target closes the gap at once and corrective action takes time, so B2 acts first: loop dominance. Unlike chapter 8’s target, here the target moves: the gap lowers it. Kim finds that targets set from outside the situation drift less.

In the parties, the gap is guests over our limit, the party’s size less the limit: named as its opposite, so B3’s and B4’s effects carry the opposite polarities and both loops stay balancing.

System archetype: accidental adversaries Variables: A's success; B's success; fixes to improve A's success; fixes to improve B's success. Effects: A's success to B's success (+, same direction); B's success to A's success (+, same direction); A's success to fixes to improve A's success (−, opposite direction); fixes to improve A's success to A's success (+, same direction); B's success to fixes to improve B's success (−, opposite direction); fixes to improve B's success to B's success (+, same direction); fixes to improve A's success to B's success (−, opposite direction); fixes to improve B's success to A's success (−, opposite direction). Loop R1 partnership, reinforcing: A's success, B's success, and back to A's success. Loop B2 A's fixes, balancing: A's success, fixes to improve A's success, and back to A's success. Loop B3 B's fixes, balancing: B's success, fixes to improve B's success, and back to B's success. Loop R4 adversaries, reinforcing: A's success, fixes to improve A's success, B's success, fixes to improve B's success, and back to A's success. Declared: accidental adversaries, which the structure matches. + + − + − + − − A's success B's success fixes to improve A's success fixes to improve B's success R1partnership B2A's fixes B3B's fixes R4adversaries Archetype: accidental adversaries

In accidental adversaries, two partners each raise the other’s success (R1, partnership). When either is dissatisfied with its own results, it takes corrective measures alone (B2, B3) that, unseen, lower its partner’s success; together the two sets of fixes close R4, the adversaries’ loop. Kemeny’s case, where the archetype was first recognized, is Procter & Gamble’s price promotions and Walmart’s stocking up on promoted goods; she puts the leverage in each partner understanding what the other needs. Each side’s fixes, with the partner’s success on the way back, also match fixes that fail, within accidental adversaries.

System archetype: escalation Variables: activity of A; activity of B; relative position. Effects: activity of A to relative position (+, same direction); relative position to activity of A (−, opposite direction); activity of B to relative position (−, opposite direction); relative position to activity of B (+, same direction). Loop B1 A's response, balancing: relative position, activity of A, and back to relative position. Loop B2 B's response, balancing: relative position, activity of B, and back to relative position. Declared: escalation, which the structure matches. + − − + activity of A activity of B relative position B1A's response B2B's response Archetype: escalation
System archetype: eroding goals Variables: target; actual performance; gap. Effects: target to gap (+, same direction); gap to actual performance (+, same direction, with a delay); actual performance to gap (−, opposite direction); gap to target (−, opposite direction). Loop B1 corrective action, balancing: gap, actual performance, and back to gap. Loop B2 pressure to lower the target, balancing: gap, target, and back to gap. Declared: eroding goals, which the structure matches, with its delay. + + − − target actual performance gap B1corrective action B2pressure to lower the target Archetype: eroding goals

Escalation and eroding goals have one shape: two balancing loops sharing one variable. Matching reads loops and their kinds, so every match of one is a match of the other, and the lab lists one with Also reads as the other. The stories differ in what the shared variable is: one side’s position relative to another’s, in escalation, or a gap between a target and actual performance, in eroding goals. Matching can’t read that, so the loops alone don’t settle which story holds; the declaration records the drawer’s reading.

Check your understandingTwo street musicians, Ines and Kofi, play on one corner, and each plays louder when the other drowns them out. A diagram shows Ines's volume → Ines against Kofi +, Ines against Kofi → Ines's volume −, Kofi's volume → Ines against Kofi −, and Ines against Kofi → Kofi's volume +. Its loops match escalation and eroding goals. Which story is it, and why?

Yes. Both archetypes are two balancing loops sharing one variable, so the loops match both. Ines against Kofi compares one side's position with the other's, as escalation's relative position does. A gap would be a target less actual performance: the volume Ines wants less Ines's volume.

Not quite. Kofi's volume moves with the shared variable, as eroding goals' target moves with the gap, so the loops fit. But nobody chose it as a value to stay near: it is the other side's position, and that makes the story escalation.

Not quite. The loops match both because matching reads loops and their kinds, not what a variable is. The stories differ in what the shared variable is: here it compares the two musicians, so the declaration is escalation.

Coupled archetypes are two matches sharing a variable: coupled loops, read as archetypes, so a change in one archetype’s loops changes the other’s. In the parties, escalation (B1, B2) and eroding goals (B3, B4) share our party’s size: a party grown to keep up opens a gap over the limit, and a party cut back to the limit looks small again. The lab reports them coupled through our party’s size and how ours compares, pairing escalation with the eroding goals that B1 and B3, two balancing loops sharing our party’s size, also match. An external driver acting on both archetypes’ loops doesn’t couple them: it stands in for no variable of any match.

Where several leverage points are proposed, which to try first is a ranking, written beside the diagram, in words, each leverage point with its reason. No mark ranks: every leverage point is the same box. For the parties:

  1. how ours compares: both escalation loops pass through it, and Kim asks of escalation whether the comparison between the sides can change. A class that agrees one number of guests for every party leaves nothing to compare.
  2. our limit on guests: held where the family set it, B4 stops, and B3 cuts each party back to it, a birthday late.

A reason resting on a dashed effect, a hypothesis in evidence coding, is a hypothesis too.

Check your understandingA pottery studio's evening classes fill by word of mouth, and its waiting list grows. A diagram of the studio shows two leverage points: the wheels in the studio, and the waiting list the owner treats as normal. Its author judges the waiting list the better place to act. How does the diagram show that?

Yes. No mark ranks leverage points: each is the same box with its question marks. The order and the reasons go beside the diagram in words, where a reader can test each reason against the loops.

Not quite. Every mark is drawn in pencil in one weight, so a heavier box carries nothing a reader can read. A leverage point's box marks a hypothesis about where to act, not its rank.

Not quite. That drops the second proposal, and the comparison with it. Both boxes stay, and the ranking, with its reasons, goes beside the diagram.

What’s wrong with this diagram of the birthday parties?

System archetype: escalation Variables: our party's size; other families' parties; how ours compares; our limit on guests; guests over our limit. Effects: our party's size to how ours compares (+, same direction); how ours compares to our party's size (−, opposite direction); other families' parties to how ours compares (−, opposite direction); how ours compares to other families' parties (+, same direction); our limit on guests to guests over our limit (−, opposite direction); guests over our limit to our party's size (−, opposite direction, with a delay). Loop B1 ours grows, balancing: our party's size, how ours compares, and back to our party's size. Loop B2 theirs grow, balancing: other families' parties, how ours compares, and back to other families' parties. Declared: escalation, which the structure matches. + − − + − − our party's size other families' parties how ours compares our limit on guests guests over our limit B1ours grows B2theirs grow Archetype: escalation

It shows the comparison alone, declared escalation. Our limit on guests and guests over our limit hold the party’s size down but close no loop: the party’s size never reaches guests over our limit, and the guests over it never move the limit. The lab’s check for two coupled archetypes reports:

1 declared archetype. Brief: at least 2, coupled through a shared variable.

The party’s size raises guests over our limit, closing B3, the cut, and the guests over the limit raise the limit, closing B4. Eroding goals is declared beside escalation.

Bad diagram
System archetype: escalation Variables: our party's size; other families' parties; how ours compares; our limit on guests; guests over our limit. Effects: our party's size to how ours compares (+, same direction); how ours compares to our party's size (−, opposite direction); other families' parties to how ours compares (−, opposite direction); how ours compares to other families' parties (+, same direction); our limit on guests to guests over our limit (−, opposite direction); guests over our limit to our party's size (−, opposite direction, with a delay). Loop B1 ours grows, balancing: our party's size, how ours compares, and back to our party's size. Loop B2 theirs grow, balancing: other families' parties, how ours compares, and back to other families' parties. Declared: escalation, which the structure matches. + − − + − − our party's size other families' parties how ours compares our limit on guests guests over our limit B1ours grows B2theirs grow Archetype: escalation
Corrected diagram
System archetype: escalation; eroding goals Variables: our party's size; other families' parties; how ours compares; our limit on guests; guests over our limit. Effects: our party's size to how ours compares (+, same direction); how ours compares to our party's size (−, opposite direction); other families' parties to how ours compares (−, opposite direction); how ours compares to other families' parties (+, same direction); our limit on guests to guests over our limit (−, opposite direction); guests over our limit to our party's size (−, opposite direction, with a delay); our party's size to guests over our limit (+, same direction); guests over our limit to our limit on guests (+, same direction). Loop B1 ours grows, balancing: our party's size, how ours compares, and back to our party's size. Loop B2 theirs grow, balancing: other families' parties, how ours compares, and back to other families' parties. Loop B3 cut back, balancing: our party's size, guests over our limit, and back to our party's size. Loop B4 limit up, balancing: guests over our limit, our limit on guests, and back to guests over our limit. Declared: escalation, which the structure matches. Declared: eroding goals, which the structure matches, with its delay. + − − + − − + + our party's size other families' parties how ours compares our limit on guests guests over our limit B1ours grows B2theirs grow B3cut back B4limit up Archetype: escalation Archetype: eroding goals

Labels unchanged. Declared archetypes: eroding goals added. Effects: 2 added. Loops: 2 added. Now matched with its delay: eroding goals.

Notation moveWhenWhat it showsExample
Declare two archetypes on one diagramTwo stories run through one situationCoupled archetypes, where their matches share a variableArchetype: escalation and Archetype: eroding goals
System archetype: escalation; eroding goals Variables: our party's size; other families' parties; how ours compares; our limit on guests; guests over our limit. Effects: our party's size to how ours compares (+, same direction); how ours compares to our party's size (−, opposite direction); other families' parties to how ours compares (−, opposite direction); how ours compares to other families' parties (+, same direction); our limit on guests to guests over our limit (−, opposite direction); guests over our limit to our party's size (−, opposite direction, with a delay); our party's size to guests over our limit (+, same direction); guests over our limit to our limit on guests (+, same direction). Loop B1 ours grows, balancing: our party's size, how ours compares, and back to our party's size. Loop B2 theirs grow, balancing: other families' parties, how ours compares, and back to other families' parties. Loop B3 cut back, balancing: our party's size, guests over our limit, and back to our party's size. Loop B4 limit up, balancing: guests over our limit, our limit on guests, and back to guests over our limit. Declared: escalation, which the structure matches. Declared: eroding goals, which the structure matches, with its delay. + − − + − − + + our party's size other families' parties how ours compares our limit on guests guests over our limit B1ours grows B2theirs grow B3cut back B4limit up Archetype: escalation Archetype: eroding goals
Declare escalation on two balancing loops sharing a variableThe shared variable compares two sidesThe story the loops alone don’t settlehow ours compares
System archetype: escalation Variables: other families' parties; how ours compares; our party's size. Effects: our party's size to how ours compares (+, same direction); how ours compares to our party's size (−, opposite direction); other families' parties to how ours compares (−, opposite direction); how ours compares to other families' parties (+, same direction). Loop B1 ours grows, balancing: our party's size, how ours compares, and back to our party's size. Loop B2 theirs grow, balancing: other families' parties, how ours compares, and back to other families' parties. Declared: escalation, which the structure matches. + − − + other families' parties how ours compares our party's size B1ours grows B2theirs grow Archetype: escalation
Draw the gap as a variable between the target and actual performanceThe target moves with the gapEroding goals’ second loopguests over our limit
System archetype Variables: our party's size; guests over our limit; our limit on guests. Effects: our party's size to guests over our limit (+, same direction); guests over our limit to our limit on guests (+, same direction); our limit on guests to guests over our limit (−, opposite direction). Loop B4 limit up, balancing: guests over our limit, our limit on guests, and back to guests over our limit. + + − our party's size guests over our limit our limit on guests B4limit up
Mark the delay on corrective action’s effectCorrection arrives later than a lowered targetWhich loop acts firstguests over our limit → our party’s size
System archetype Variables: guests over our limit; our party's size. Effects: guests over our limit to our party's size (−, opposite direction, with a delay). − guests over our limit our party's size
Mark the delay into capacityCapacity takes time to buildCapacity arriving lateneed for more trains → trains in service, in AR 07
System archetype Variables: need for more trains; trains in service. Effects: need for more trains to trains in service (+, same direction, with a delay). + need for more trains trains in service
Propose several leverage pointsThere is more than one place to actHypotheses about where to act, ranked in words beside the diagramhow ours compares, then our limit on guests
System archetype Variables: how ours compares (leverage point); our limit on guests (leverage point). ????how ours compares ????our limit on guests

Read one way, a match is a diagnosis: the loops are there, so the situation is that archetype. In the parties, B1 and B2 also match eroding goals, how ours compares as the gap and either family’s party as the target, and B3 and B4 also match escalation. The loops are the same either way; the stories differ in what the variables are. How ours compares sets one family’s party against the others’, so B1 and B2 are escalation; guests over our limit is a party’s size less a number the family chose, so B3 and B4 are eroding goals.

Archetypes fit any story told loosely enough, so naming one explains nothing. Lane (1998) divides generic structure in system dynamics into three kinds, of which the third, archetypes, involves “merely metaphorical thinking”.

The names are loose: escalation and eroding goals share one shape, and which one a drawing holds is the drawer’s reading, recorded in the declaration, not settled by the loops. The structure isn’t loose. A loop closes or doesn’t, its kind follows the parity rule, a delay sits on one effect and not another, and each is checked on the drawing and can be wrong: the bad diagram’s limit closes no loop, and the lab counts one declared archetype where two coupled ones were asked for.

Check your understandingSam and Jo share a flat and take turns cooking dinner for both, which leaves each of them free evenings. Short of time in the week, each starts cooking a week's lunches on Sunday afternoon. Sam's cooking takes the oven and every pan when Jo comes to cook, and Jo's leaves a sink of washing-up that Sam clears before starting. Which archetype's story is this?

Yes. Their turns at cooking free each other's evenings: the partnership loop. Each Sunday's cooking eases its cook's own week, a balancing loop for each, and gets in the other's way; the two together close the adversaries' loop. Kemeny puts the leverage in each partner learning what the other needs.

Not quite. Escalation's two sides act on one comparison, each against the other's lead. Neither flatmate measures their week against the other's: each Sunday's cooking is for its cook's own week, and it gets in the other's way as it goes.

Not quite. A drawing of the flat does match fixes that fail, one flatmate's Sunday cooking as the symptomatic solution and its side effect running through the other's week. But each such match lies within accidental adversaries, and read alone it leaves out the partnership loop that ties the two weeks together.

System archetype: eroding goals Variables: downsizing of rural services; staffing goal; veterans sent to community care; staffing need; provider retention; provider recruitment; provider burnout; patients per provider; rurality of the facility (external driver). Effects: staffing goal to staffing need (+, same direction); staffing need to veterans sent to community care (+, same direction); veterans sent to community care to staffing goal (−, opposite direction); veterans sent to community care to downsizing of rural services (+, same direction); downsizing of rural services to staffing goal (−, opposite direction); staffing need to provider recruitment (+, same direction); provider recruitment to provider retention (+, same direction); provider retention to staffing need (−, opposite direction); staffing need to patients per provider (+, same direction); patients per provider to provider burnout (+, same direction); provider burnout to provider retention (−, opposite direction); rurality of the facility to provider retention (−, opposite direction); rurality of the facility to patients per provider (+, same direction). Loop R1 burnout spiral, reinforcing: staffing need, patients per provider, provider burnout, provider retention, and back to staffing need. Loop B9 hiring to the goal, balancing: staffing need, provider recruitment, provider retention, and back to staffing need. Loop B10 hiring pressure relieved, balancing: staffing need, veterans sent to community care, staffing goal, and back to staffing need. Loop B11 services downsized, balancing: staffing need, veterans sent to community care, downsizing of rural services, staffing goal, and back to staffing need. Declared: eroding goals, which the structure matches, without its delay. + + − + − + + − + + − − + downsizing of rural services staffing goal veterans sent to community care staffing need provider retention provider recruitment provider burnout patients per provider ‹rurality of the facility› R1burnout spiral B9hiring to the goal B10hiring pressure relieved B11services downsized Archetype: eroding goals

Redrawn from Erin S. Kenzie, Mary Patzel, Erik Nelson, Travis Lovejoy, Sarah Ono and Melinda M. Davis, “Long drives and red tape: mapping rural veteran access to primary care using causal-loop diagramming”, BMC Health Services Research 22, 1075 (2022), Fig. 5. CC BY 4.0.

Its blue lines marked + and red lines marked − drawn alike, each polarity kept; its faded variable, provider turnover, and its line left out; VA dropped from every name; sending veterans to community care renamed as an amount, veterans sent to community care, and three other names reworded; rurality of the facility marked as an external driver; its loops’ labels kept, B9 to B11 numbered as in the authors’ whole model, and their names reworded by what each loop does; eroding goals, which its authors name drifting goals, declared.

Question 1 of 3Which variable is eroding goals’ target, and what brings it down?

Not quite. Staffing need is the gap: the staffing goal raises it and provider retention lowers it. Community care reaches the need only by lowering the staffing goal, around B10 and B11.

Yes. A higher staffing need sends more veterans to community care, and each − effect into the staffing goal brings the goal down, closing the gap from the target’s side. Here the target moves, and recruitment and retention, B9, are left less to close.

Not quite. Provider retention is actual performance, the side recruitment raises through B9. Burnout lowers it around R1, but no variable sets it as a target is set.

Question 2 of 3Its authors count R1, the burnout spiral, in their drifting goals (eroding goals). With B9, R1 matches another archetype, coupled with eroding goals. Which?

Not quite. Community care relieves the staffing need only by lowering the staffing goal, eroding goals’ second loop, and R1 doesn’t pass through it. No shifting the burden matches here.

Not quite. Escalation is two balancing loops sharing one variable, and R1 is reinforcing. The escalation that matches here is eroding goals’ own shape: B9 with B10 or B11.

Yes. With provider retention named as its opposite, provider loss, as the problem symptom, B9 is the fix and R1 the side effect’s loop, its delay not drawn. B9 is eroding goals’ corrective action too, so the two matches share the staffing need, recruitment and retention: coupled archetypes.

Question 3 of 3Ranked by what Kim finds of eroding goals, which leverage point comes first?

Not quite. Recruitment corrects through B9, after a delay, while a lowered staffing goal closes the gap at once; and R1’s burnout drives out the providers recruited. While the goal can fall, a recruitment push closes the gap no sooner.

Not quite. Community care reaches veterans who would otherwise drive far for care, and it lowers the target only through its effect on the staffing goal. Holding the goal itself stops B10 and B11 with no veteran sent back to the road.

Yes. Kim finds that targets set from outside the situation drift less. Held, the staffing goal no longer falls with the community care sent, so B10 and B11 stop, and the gap stays open until B9 closes it.

Passing the checks means meeting the brief, not being right.

AR 06An arms race between two neighboring countries

Each side's safety read against the other's

  • Reasoning3 of 5
  • Polish4 of 5

Two neighboring countries, called here North and South, each judge their safety by how their armed forces compare with the other's. North buys arms until its forces are well ahead of South's: the more arms North buys, the larger North's lead in forces, and the larger that lead, the fewer arms North buys. South buys arms while North is ahead: the more arms South buys, the smaller North's lead, and the larger North's lead, the more arms South buys. Each country pays for its arms from the budget that also pays for its schools and hospitals: the more arms either country buys, the less the two countries spend on schools and hospitals.

The brief

  1. Draw each country's arms purchases closing a balancing loop through one variable that compares the two countries' forces. checked by the lab
  2. The two loops match escalation. checked by the lab
  3. Draw the spending on schools and hospitals, reached from both countries' purchases. checked by the lab
  4. One variable compares the two countries' forces, and both loops pass through it. you check this
  5. The spending on schools and hospitals returns to neither loop. you check this
  6. The declared archetype is escalation, not eroding goals, though the same loops match both. you check this

Your palette

  • Causal-loop diagram Variables: customers. customers
    variable
  • Causal-loop diagram Variables: price; sales. Effects: price to sales (polarity not yet set). price sales
    effect
  • Causal-loop diagram Variables: price; sales; revenue. Effects: price to sales (−, opposite direction); sales to revenue (+, same direction). − + price sales revenue
    polarity
  • Causal-loop diagram Variables: orders; deliveries. Effects: orders to deliveries (+, same direction, with a delay). + orders deliveries
    delay
  • Causal-loop diagram: R1 practice habit Variables: practice; skill; enjoyment. Effects: practice to skill (+, same direction); skill to enjoyment (+, same direction); enjoyment to practice (+, same direction). Loop R1 practice habit, reinforcing: practice, skill, enjoyment, and back to practice. + + + practice skill enjoyment R1practice habit
    loop
  • Causal-loop diagram: B1 warming up Variables: room heat; heating. Effects: room heat to heating (−, opposite direction); heating to room heat (+, same direction). Loop B1 warming up, balancing: room heat, heating, and back to room heat. − + room heat heating B1warming up
    balancing loop
  • System archetype: fixes that fail Variables: . Declared: fixes that fail, which the structure doesn't match. Archetype: fixes that fail
    archetype

To draw in the lab, use a tablet or a larger screen. Everything else reads normally here.

Press an empty spot to add a variable and type its name. Drag a variable to move it. Select a variable, an effect or a loop label to change it. Double-click or double-tap a variable or a loop's label or name to edit its words in place, or select it and use Rename or the fields under the canvas.

System archetype Variables: .

Nothing selected. Select a variable, an effect, a loop label or a declared archetype on the canvas, and what you can change shows here.

The tools

Variables V
add a variable (press an empty spot), move one (drag it), rename one (double-click it, or Rename under the canvas), or select anything.
Effects E
draw an effect by dragging from one variable to another.
Loop L
declare a loop by selecting its effects in order, then label and name it.
Archetype K
declare an archetype: press an empty spot, then choose which of the nine.

Keys

  • R reverse the selected effect
  • +− the selected effect's polarity
  • Delete delete what's selected
  • Ctrl+Z undo
  • Ctrl+Shift+Z redo
  • Esc clear the selection
  • Enter finish the words you're writing
  • Esc cancel them

Keys act on the lab you last used, or on the open lab view, and never while you type.

Archetypes the structure matches

Read from the loops and their kinds as drawn, after each change. Nothing here is saved.

No archetype matches yet.

0 of 8 checks passed; 8 pending.

  1. Draw each country's arms purchases closing a balancing loop through one variable that compares the two countries' forces. (Not started)No loop declared yet. Brief: exactly 2 balancing loops.
  2. The two loops match escalation. (Not started)No effect has a polarity yet. Brief: escalation.
  3. Draw the spending on schools and hospitals, reached from both countries' purchases. (Not started)No variables yet. Brief: at least 4.

Always checked

  • Each loop's kind matches its − effects (Not started)No loop declared yet.
  • Loop labels are unique and match their kind (Not started)No loop declared yet.
  • Every effect has a polarity (Not started)No effects yet.
  • The structure matches each declared archetype (Not started)No archetype declared yet.
  • No variable's name breaks the more test's three rules (Not started)No variable drawn yet.
Written feedback
Export

One defensible answer

It opens here once you've drawn at least one variable in the lab above. Your attempt saves as you draw.

One defensible answer

AR 07A country's railways

Growth held back by trains never ordered

  • Reasoning4 of 5
  • Polish4 of 5

A country's railway operator draws passengers with punctual trains and cheap fares: the more passengers, the more fare offers it can pay for, and the more fare offers, the more passengers. Crowded trains wait longer at every station: the more passengers, the lower the punctuality, and the higher the punctuality, the more passengers. The operator reads its need for more trains from how far punctuality falls short of its punctuality target, once a year's figures are in: the lower the punctuality, the greater the need for more trains, after a delay, and the higher the target, the greater the need. A new train takes four years to build: the greater the need, the more trains in service, after a delay, and the more trains in service, the higher the punctuality. When the need is large, the operator lowers its target rather than order trains: the greater the need for more trains, the lower the punctuality target.

The brief

  1. Draw the passengers and the fare offers closing a reinforcing loop. checked by the lab
  2. Draw a balancing loop through the passengers and the punctuality, and one through the need for more trains and the trains in service. checked by the lab
  3. The loops match growth and underinvestment, with its delay where new trains arrive. checked by the lab
  4. Draw a delay where the operator reads its need for more trains, and one where new trains arrive. checked by the lab
  5. The punctuality target acts on the need for more trains, and the greater the need, the lower the target. you check this

Your palette

  • Causal-loop diagram Variables: customers. customers
    variable
  • Causal-loop diagram Variables: price; sales. Effects: price to sales (polarity not yet set). price sales
    effect
  • Causal-loop diagram Variables: price; sales; revenue. Effects: price to sales (−, opposite direction); sales to revenue (+, same direction). − + price sales revenue
    polarity
  • Causal-loop diagram Variables: orders; deliveries. Effects: orders to deliveries (+, same direction, with a delay). + orders deliveries
    delay
  • Causal-loop diagram: R1 practice habit Variables: practice; skill; enjoyment. Effects: practice to skill (+, same direction); skill to enjoyment (+, same direction); enjoyment to practice (+, same direction). Loop R1 practice habit, reinforcing: practice, skill, enjoyment, and back to practice. + + + practice skill enjoyment R1practice habit
    loop
  • Causal-loop diagram: R1 compounding Variables: savings; interest. Effects: savings to interest (+, same direction); interest to savings (+, same direction). Loop R1 compounding, reinforcing: savings, interest, and back to savings. + + savings interest R1compounding
    reinforcing loop
  • Causal-loop diagram: B1 warming up Variables: room heat; heating. Effects: room heat to heating (−, opposite direction); heating to room heat (+, same direction). Loop B1 warming up, balancing: room heat, heating, and back to room heat. − + room heat heating B1warming up
    balancing loop
  • Causal-loop diagram Variables: staffing gap; hiring. Effects: staffing gap to hiring (+, same direction). + staffing gap hiring
    gapdrawn as an ordinary variable
  • System archetype: fixes that fail Variables: . Declared: fixes that fail, which the structure doesn't match. Archetype: fixes that fail
    archetype

To draw in the lab, use a tablet or a larger screen. Everything else reads normally here.

Press an empty spot to add a variable and type its name. Drag a variable to move it. Select a variable, an effect or a loop label to change it. Double-click or double-tap a variable or a loop's label or name to edit its words in place, or select it and use Rename or the fields under the canvas.

System archetype Variables: .

Nothing selected. Select a variable, an effect, a loop label or a declared archetype on the canvas, and what you can change shows here.

The tools

Variables V
add a variable (press an empty spot), move one (drag it), rename one (double-click it, or Rename under the canvas), or select anything.
Effects E
draw an effect by dragging from one variable to another.
Loop L
declare a loop by selecting its effects in order, then label and name it.
Archetype K
declare an archetype: press an empty spot, then choose which of the nine.

Keys

  • R reverse the selected effect
  • +− the selected effect's polarity
  • Delete delete what's selected
  • Ctrl+Z undo
  • Ctrl+Shift+Z redo
  • Esc clear the selection
  • Enter finish the words you're writing
  • Esc cancel them

Keys act on the lab you last used, or on the open lab view, and never while you type.

Archetypes the structure matches

Read from the loops and their kinds as drawn, after each change. Nothing here is saved.

No archetype matches yet.

0 of 9 checks passed; 9 pending.

  1. Draw the passengers and the fare offers closing a reinforcing loop. (Not started)No loop declared yet. Brief: at least 1 reinforcing loop.
  2. Draw a balancing loop through the passengers and the punctuality, and one through the need for more trains and the trains in service. (Not started)No loop declared yet. Brief: at least 2 balancing loops.
  3. The loops match growth and underinvestment, with its delay where new trains arrive. (Not started)No effect has a polarity yet. Brief: growth and underinvestment, with its delay.
  4. Draw a delay where the operator reads its need for more trains, and one where new trains arrive. (Not started)No effects yet. Brief: at least 2 delays.

Always checked

  • Each loop's kind matches its − effects (Not started)No loop declared yet.
  • Loop labels are unique and match their kind (Not started)No loop declared yet.
  • Every effect has a polarity (Not started)No effects yet.
  • The structure matches each declared archetype (Not started)No archetype declared yet.
  • No variable's name breaks the more test's three rules (Not started)No variable drawn yet.
Written feedback
Export

One defensible answer

It opens here once you've drawn at least one variable in the lab above. Your attempt saves as you draw.

One defensible answer

AR 08Knee exercises after an operation

A target that moves toward what was done

  • Reasoning4 of 5
  • Polish4 of 5

After an operation on her knee, Priya sets herself a weekly target of fifteen sessions of the exercises her physiotherapist gave her. Each Sunday she counts the sessions done that week, and the gap is the target minus the sessions done: the higher the target, the larger the gap, and the more sessions done, the smaller the gap. When the gap is large she fits extra sessions into the next week, so the gap raises the sessions done a week later: the larger the gap, the more sessions done, after a delay. On busy weeks at work she falls short, and each time she does, she sets next week's target closer to what she managed: the larger the gap, the lower the weekly target.

The brief

  1. Draw two balancing loops through the gap: one through the sessions done, one through the weekly target. checked by the lab
  2. The loops match eroding goals, with its delay on the extra sessions. checked by the lab
  3. The gap is a variable of its own: the weekly target minus the sessions done. you check this
  4. The second loop is named for the lowered target, which closes the gap without a session more. you check this

Your palette

  • Causal-loop diagram Variables: customers. customers
    variable
  • Causal-loop diagram Variables: price; sales. Effects: price to sales (polarity not yet set). price sales
    effect
  • Causal-loop diagram Variables: price; sales; revenue. Effects: price to sales (−, opposite direction); sales to revenue (+, same direction). − + price sales revenue
    polarity
  • Causal-loop diagram Variables: orders; deliveries. Effects: orders to deliveries (+, same direction, with a delay). + orders deliveries
    delay
  • Causal-loop diagram: R1 practice habit Variables: practice; skill; enjoyment. Effects: practice to skill (+, same direction); skill to enjoyment (+, same direction); enjoyment to practice (+, same direction). Loop R1 practice habit, reinforcing: practice, skill, enjoyment, and back to practice. + + + practice skill enjoyment R1practice habit
    loop
  • Causal-loop diagram: B1 warming up Variables: room heat; heating. Effects: room heat to heating (−, opposite direction); heating to room heat (+, same direction). Loop B1 warming up, balancing: room heat, heating, and back to room heat. − + room heat heating B1warming up
    balancing loop
  • Causal-loop diagram Variables: staffing gap; hiring. Effects: staffing gap to hiring (+, same direction). + staffing gap hiring
    gapdrawn as an ordinary variable
  • System archetype: fixes that fail Variables: . Declared: fixes that fail, which the structure doesn't match. Archetype: fixes that fail
    archetype

To draw in the lab, use a tablet or a larger screen. Everything else reads normally here.

Press an empty spot to add a variable and type its name. Drag a variable to move it. Select a variable, an effect or a loop label to change it. Double-click or double-tap a variable or a loop's label or name to edit its words in place, or select it and use Rename or the fields under the canvas.

System archetype Variables: .

Nothing selected. Select a variable, an effect, a loop label or a declared archetype on the canvas, and what you can change shows here.

The tools

Variables V
add a variable (press an empty spot), move one (drag it), rename one (double-click it, or Rename under the canvas), or select anything.
Effects E
draw an effect by dragging from one variable to another.
Loop L
declare a loop by selecting its effects in order, then label and name it.
Archetype K
declare an archetype: press an empty spot, then choose which of the nine.

Keys

  • R reverse the selected effect
  • +− the selected effect's polarity
  • Delete delete what's selected
  • Ctrl+Z undo
  • Ctrl+Shift+Z redo
  • Esc clear the selection
  • Enter finish the words you're writing
  • Esc cancel them

Keys act on the lab you last used, or on the open lab view, and never while you type.

Archetypes the structure matches

Read from the loops and their kinds as drawn, after each change. Nothing here is saved.

No archetype matches yet.

0 of 7 checks passed; 7 pending.

  1. Draw two balancing loops through the gap: one through the sessions done, one through the weekly target. (Not started)No loop declared yet. Brief: exactly 2 balancing loops.
  2. The loops match eroding goals, with its delay on the extra sessions. (Not started)No effect has a polarity yet. Brief: eroding goals, with its delay.

Always checked

  • Each loop's kind matches its − effects (Not started)No loop declared yet.
  • Loop labels are unique and match their kind (Not started)No loop declared yet.
  • Every effect has a polarity (Not started)No effects yet.
  • The structure matches each declared archetype (Not started)No archetype declared yet.
  • No variable's name breaks the more test's three rules (Not started)No variable drawn yet.
Written feedback
Export

One defensible answer

It opens here once you've drawn at least one variable in the lab above. Your attempt saves as you draw.

One defensible answer

AR 09Two parents sharing care after a separation

Partners whose own fixes hold each other back

  • Reasoning5 of 5
  • Polish5 of 5

Maya and Tom separated last year and share the care of their two children, a week each. Each helps the other's weeks go well, with lifts to football and the same homework rules in both homes: the better Maya's weeks go, the better Tom's go, and the better Tom's weeks go, the better Maya's go. When a week goes badly, each makes changes alone to ease their own weeks, such as a new bedtime or a swapped weekend: the worse Maya's weeks go, the more changes she makes alone, and the more changes she makes alone, the better her weeks go; the same holds for Tom. Each one's changes reach the other's home a week or two later, with the children: the more changes Maya makes alone, the worse Tom's weeks go, after a delay, and the more changes Tom makes alone, the worse Maya's weeks go, after a delay. Both parents see how settled the children are, which rises the better either parent's weeks go.

The brief

  1. The loops match accidental adversaries. checked by the lab
  2. Draw a delay on each parent's changes' effect on the other's weeks. checked by the lab
  3. Mark one leverage point. checked by the lab
  4. The two delays sit where each parent's changes reach the other's weeks, not on the help each gives the other. you check this
  5. The leverage point is a measure both parents can see. you check this

Your palette

  • Causal-loop diagram Variables: customers. customers
    variable
  • Causal-loop diagram Variables: price; sales. Effects: price to sales (polarity not yet set). price sales
    effect
  • Causal-loop diagram Variables: price; sales; revenue. Effects: price to sales (−, opposite direction); sales to revenue (+, same direction). − + price sales revenue
    polarity
  • Causal-loop diagram Variables: orders; deliveries. Effects: orders to deliveries (+, same direction, with a delay). + orders deliveries
    delay
  • Causal-loop diagram: R1 practice habit Variables: practice; skill; enjoyment. Effects: practice to skill (+, same direction); skill to enjoyment (+, same direction); enjoyment to practice (+, same direction). Loop R1 practice habit, reinforcing: practice, skill, enjoyment, and back to practice. + + + practice skill enjoyment R1practice habit
    loop
  • Causal-loop diagram: R1 compounding Variables: savings; interest. Effects: savings to interest (+, same direction); interest to savings (+, same direction). Loop R1 compounding, reinforcing: savings, interest, and back to savings. + + savings interest R1compounding
    reinforcing loop
  • Causal-loop diagram: B1 warming up Variables: room heat; heating. Effects: room heat to heating (−, opposite direction); heating to room heat (+, same direction). Loop B1 warming up, balancing: room heat, heating, and back to room heat. − + room heat heating B1warming up
    balancing loop
  • Causal-loop diagram Variables: reorder point (leverage point). ????reorder point
    leverage point
  • System archetype: fixes that fail Variables: . Declared: fixes that fail, which the structure doesn't match. Archetype: fixes that fail
    archetype

To draw in the lab, use a tablet or a larger screen. Everything else reads normally here.

Press an empty spot to add a variable and type its name. Drag a variable to move it. Select a variable, an effect or a loop label to change it. Double-click or double-tap a variable or a loop's label or name to edit its words in place, or select it and use Rename or the fields under the canvas.

System archetype Variables: .

Nothing selected. Select a variable, an effect, a loop label or a declared archetype on the canvas, and what you can change shows here.

The tools

Variables V
add a variable (press an empty spot), move one (drag it), rename one (double-click it, or Rename under the canvas), or select anything.
Effects E
draw an effect by dragging from one variable to another.
Loop L
declare a loop by selecting its effects in order, then label and name it.
Archetype K
declare an archetype: press an empty spot, then choose which of the nine.

Keys

  • R reverse the selected effect
  • +− the selected effect's polarity
  • Delete delete what's selected
  • Ctrl+Z undo
  • Ctrl+Shift+Z redo
  • Esc clear the selection
  • Enter finish the words you're writing
  • Esc cancel them

Keys act on the lab you last used, or on the open lab view, and never while you type.

Archetypes the structure matches

Read from the loops and their kinds as drawn, after each change. Nothing here is saved.

No archetype matches yet.

0 of 8 checks passed; 8 pending.

  1. The loops match accidental adversaries. (Not started)No effect has a polarity yet. Brief: accidental adversaries.
  2. Draw a delay on each parent's changes' effect on the other's weeks. (Not started)No effects yet. Brief: at least 2 delays.
  3. Mark one leverage point. (Not started)No variables yet. Brief: exactly 1 leverage point.

Always checked

  • Each loop's kind matches its − effects (Not started)No loop declared yet.
  • Loop labels are unique and match their kind (Not started)No loop declared yet.
  • Every effect has a polarity (Not started)No effects yet.
  • The structure matches each declared archetype (Not started)No archetype declared yet.
  • No variable's name breaks the more test's three rules (Not started)No variable drawn yet.
Written feedback
Export

One defensible answer

It opens here once you've drawn at least one variable in the lab above. Your attempt saves as you draw.

One defensible answer

AR 10A coastal town and its sea walls

Two archetypes sharing one variable

  • Reasoning5 of 5
  • Polish5 of 5

A coastal town of eight thousand people floods when winter storms push the sea over its seafront: the more winter storms, the more flooding of the seafront. Each flood brings calls for sea walls, and a wall stops the sea at once: the more flooding of the seafront, the more sea walls built, and the more sea walls built, the less flooding. The walls stop the waves from carrying sand along the shore, so the beach in front of them thins, and years later the sea reaches the walls with more force: the more sea walls built, the more sand lost from the beach, and the more sand lost, the more flooding, after a delay. Restoring the dunes behind the beach would protect the coast for decades, though new dunes take years to grow: the more flooding, the more dune restoration, and the more dune restoration, the less flooding, after a delay. Behind each new wall, the town allows homes and shops: the more sea walls built, the more building behind the walls. The town's engineers think the new building makes dune restoration costlier, since the land behind the beach is no longer free, but they have no figures yet: the more building behind the walls, the less dune restoration.

The brief

  1. Declare each archetype the structure holds, at least two. checked by the lab
  2. The declared archetypes are coupled: their matches share a variable. checked by the lab
  3. Mark at least two leverage points. checked by the lab
  4. Code the effect you judge less supported as a hypothesis, declared in the legend. checked by the lab
  5. Draw at least three loops. checked by the lab
  6. Beside the diagram, rank the leverage points in a list, each with its reason. you check this
  7. The winter storms sit outside a boundary named for the town's coast, and nothing inside acts on them. you check this
  8. No variable is drawn twice: the sea walls built are one variable, in both archetypes. you check this

Your palette

  • Causal-loop diagram Variables: customers. customers
    variable
  • Causal-loop diagram Variables: price; sales. Effects: price to sales (polarity not yet set). price sales
    effect
  • Causal-loop diagram Variables: price; sales; revenue. Effects: price to sales (−, opposite direction); sales to revenue (+, same direction). − + price sales revenue
    polarity
  • Causal-loop diagram Variables: orders; deliveries. Effects: orders to deliveries (+, same direction, with a delay). + orders deliveries
    delay
  • Causal-loop diagram: R1 practice habit Variables: practice; skill; enjoyment. Effects: practice to skill (+, same direction); skill to enjoyment (+, same direction); enjoyment to practice (+, same direction). Loop R1 practice habit, reinforcing: practice, skill, enjoyment, and back to practice. + + + practice skill enjoyment R1practice habit
    loop
  • Causal-loop diagram: R1 compounding Variables: savings; interest. Effects: savings to interest (+, same direction); interest to savings (+, same direction). Loop R1 compounding, reinforcing: savings, interest, and back to savings. + + savings interest R1compounding
    reinforcing loop
  • Causal-loop diagram: B1 warming up Variables: room heat; heating. Effects: room heat to heating (−, opposite direction); heating to room heat (+, same direction). Loop B1 warming up, balancing: room heat, heating, and back to room heat. − + room heat heating B1warming up
    balancing loop
  • Causal-loop diagram Variables: orders; stock. Effects: orders to stock (−, opposite direction). Boundary the shop contains: orders; stock. the shop − orders stock
    boundary
  • Causal-loop diagram Variables: weather (external driver); footfall. Effects: weather to footfall (+, same direction). Boundary the café contains: footfall. Outside every boundary: weather. the café + ‹weather› footfall
    external driver
  • Causal-loop diagram Variables: training; quality. Effects: training to quality (polarity not yet set, hypothesis). training quality
    evidence coding
  • Causal-loop diagram Variables: reorder point (leverage point). ????reorder point
    leverage point
  • Causal-loop diagram Variables: . Behavior note: oscillation. oscillation
    behavior note
  • System archetype: fixes that fail Variables: . Declared: fixes that fail, which the structure doesn't match. Archetype: fixes that fail
    archetype
  • System archetype Variables: pests; spraying (symptomatic solution). Effects: pests to spraying (+, same direction). + pests sprayingsymptomatic solution
    symptomatic solutiona role, written above its variable's name
  • System archetype Variables: pests; hedgerows planted (fundamental solution). Effects: pests to hedgerows planted (+, same direction). + pests hedgerows plantedfundamental solution
    fundamental solutiona role, written above its variable's name
  • System archetype Variables: spraying; predators lost (side effect). Effects: spraying to predators lost (+, same direction). + spraying predators lostside effect
    side effecta role, written above its variable's name

To draw in the lab, use a tablet or a larger screen. Everything else reads normally here.

Press an empty spot to add a variable and type its name. Drag a variable to move it. Select a variable, an effect or a loop label to change it. Drag a boundary by its outline or its name to move it, and by the square at its corner to resize it. Drag a behavior note to move it. Double-click or double-tap a variable, a loop's label or name, a boundary's name or a behavior note to edit its words in place, or select it and use Rename or the fields under the canvas.

System archetype Variables: .

Nothing selected. Select a variable, an effect, a loop label, a boundary, a behavior note or a declared archetype on the canvas, and what you can change shows here.

The tools

Variables V
add a variable (press an empty spot), move one (drag it), rename one (double-click it, or Rename under the canvas), or select anything.
Effects E
draw an effect by dragging from one variable to another.
Loop L
declare a loop by selecting its effects in order, then label and name it.
Boundary B
drag out a boundary around the system, and name it.
Note N
place a behavior note (press where it goes).
Archetype K
declare an archetype: press an empty spot, then choose which of the nine.

Keys

  • G legend on or off
  • R reverse the selected effect
  • P the selected variable's role, in turn: none, then each role this exercise offers
  • +− the selected effect's polarity
  • Delete delete what's selected
  • Ctrl+Z undo
  • Ctrl+Shift+Z redo
  • Esc clear the selection
  • Enter finish the words you're writing
  • Esc cancel them

Keys act on the lab you last used, or on the open lab view, and never while you type.

Archetypes the structure matches

Read from the loops and their kinds as drawn, after each change. Nothing here is saved.

No archetype matches yet.

0 of 14 checks passed; 14 pending.

  1. Declare each archetype the structure holds, at least two. (Not started)No variables yet. Brief: at least 2 declared archetypes.
  2. The declared archetypes are coupled: their matches share a variable. (Not started)No archetype declared yet. Brief: at least 2, coupled through a shared variable.
  3. Mark at least two leverage points. (Not started)No variables yet. Brief: at least 2 leverage points.
  4. Code the effect you judge less supported as a hypothesis, declared in the legend. (Not started)No effects yet.
  5. Draw at least three loops. (Not started)No loop declared yet. Brief: at least 3 loops.

Always checked

  • Each loop's kind matches its − effects (Not started)No loop declared yet.
  • Loop labels are unique and match their kind (Not started)No loop declared yet.
  • No effect runs into an external driver (Not started)No variable is marked as an external driver yet.
  • External drivers sit outside every boundary (Not started)No variable is marked as an external driver yet.
  • The legend is on when effects are coded or tagged (Not started)No effect is coded as a hypothesis or tagged with a viewpoint yet, so the legend has nothing to declare.
  • Every effect has a polarity (Not started)No effects yet.
  • The structure matches each declared archetype (Not started)No archetype declared yet.
  • Each role is the place its variable stands in a match (Not started)No variable has a role yet.
  • No variable's name breaks the more test's three rules (Not started)No variable drawn yet.
Written feedback
Export

One defensible answer

It opens here once you've drawn at least one variable in the lab above. Your attempt saves as you draw.

One defensible answer

CS 11Kelsham Primary School: the town school's pull and its rising class size

Two archetypes coupled through one share

  • Reasoning5 of 5
  • Polish5 of 5

Brayford Primary School teaches each year in classes of its own, and Kelsham's families know it. The larger Brayford's share of the villages' starters, the more Kelsham children at Brayford, and the more Kelsham children at Brayford, the larger the share, as brothers, sisters and friends follow them there. The larger Brayford's share, the fewer pupils on roll at Kelsham; the fewer pupils on roll, the more mixed-age classes at Kelsham; and the more mixed-age classes, the larger Brayford's share. Helen Marsh, Brayford's head teacher, aimed for classes of 26. The more Kelsham children at Brayford, the larger its average class size, and the larger the average class size, the more pupils a class above Brayford's aim. Above its aim, Brayford offers fewer places to children from outside the town the next September: the more pupils a class above the aim, the smaller Brayford's share, a year later. Yet each year its classes run above the aim, Brayford's governors raise it, toward the most they allow, 30: the more pupils a class above the aim, the higher the class size Brayford aims for, and the higher the class size Brayford aims for, the fewer pupils a class above it.

The brief

  1. Draw Brayford's share of the villages' starters on two reinforcing loops that match success to the successful. checked by the lab
  2. Draw the gap between Brayford's class size and its aim on two balancing loops that match eroding goals, with its delay on the places held back. checked by the lab
  3. Declare both archetypes. checked by the lab
  4. The declared archetypes are coupled: their matches share a variable. checked by the lab
  5. Mark one delay: the September before places held back change the share. checked by the lab
  6. Brayford's share of the villages' starters is drawn once, on both archetypes' loops. you check this
  7. Beside the diagram, one sentence says what each rise in Brayford's aim does to the pupils on roll at Kelsham. you check this

Your palette

  • Causal-loop diagram Variables: customers. customers
    variable
  • Causal-loop diagram Variables: price; sales. Effects: price to sales (polarity not yet set). price sales
    effect
  • Causal-loop diagram Variables: price; sales; revenue. Effects: price to sales (−, opposite direction); sales to revenue (+, same direction). − + price sales revenue
    polarity
  • Causal-loop diagram Variables: orders; deliveries. Effects: orders to deliveries (+, same direction, with a delay). + orders deliveries
    delay
  • Causal-loop diagram: R1 practice habit Variables: practice; skill; enjoyment. Effects: practice to skill (+, same direction); skill to enjoyment (+, same direction); enjoyment to practice (+, same direction). Loop R1 practice habit, reinforcing: practice, skill, enjoyment, and back to practice. + + + practice skill enjoyment R1practice habit
    loop
  • Causal-loop diagram: R1 compounding Variables: savings; interest. Effects: savings to interest (+, same direction); interest to savings (+, same direction). Loop R1 compounding, reinforcing: savings, interest, and back to savings. + + savings interest R1compounding
    reinforcing loop
  • Causal-loop diagram: B1 warming up Variables: room heat; heating. Effects: room heat to heating (−, opposite direction); heating to room heat (+, same direction). Loop B1 warming up, balancing: room heat, heating, and back to room heat. − + room heat heating B1warming up
    balancing loop
  • Causal-loop diagram Variables: staffing gap; hiring. Effects: staffing gap to hiring (+, same direction). + staffing gap hiring
    gapdrawn as an ordinary variable
  • System archetype: fixes that fail Variables: . Declared: fixes that fail, which the structure doesn't match. Archetype: fixes that fail
    archetype

To draw in the lab, use a tablet or a larger screen. Everything else reads normally here.

Press an empty spot to add a variable and type its name. Drag a variable to move it. Select a variable, an effect or a loop label to change it. Double-click or double-tap a variable or a loop's label or name to edit its words in place, or select it and use Rename or the fields under the canvas.

System archetype Variables: .

Nothing selected. Select a variable, an effect, a loop label or a declared archetype on the canvas, and what you can change shows here.

The tools

Variables V
add a variable (press an empty spot), move one (drag it), rename one (double-click it, or Rename under the canvas), or select anything.
Effects E
draw an effect by dragging from one variable to another.
Loop L
declare a loop by selecting its effects in order, then label and name it.
Archetype K
declare an archetype: press an empty spot, then choose which of the nine.

Keys

  • R reverse the selected effect
  • +− the selected effect's polarity
  • Delete delete what's selected
  • Ctrl+Z undo
  • Ctrl+Shift+Z redo
  • Esc clear the selection
  • Enter finish the words you're writing
  • Esc cancel them

Keys act on the lab you last used, or on the open lab view, and never while you type.

Archetypes the structure matches

Read from the loops and their kinds as drawn, after each change. Nothing here is saved.

No archetype matches yet.

0 of 10 checks passed; 10 pending.

  1. Draw Brayford's share of the villages' starters on two reinforcing loops that match success to the successful. (Not started)No effect has a polarity yet. Brief: success to the successful.
  2. Draw the gap between Brayford's class size and its aim on two balancing loops that match eroding goals, with its delay on the places held back. (Not started)No effect has a polarity yet. Brief: eroding goals, with its delay.
  3. Declare both archetypes. (Not started)No variables yet. Brief: exactly 2 declared archetypes.
  4. The declared archetypes are coupled: their matches share a variable. (Not started)No archetype declared yet. Brief: at least 2, coupled through a shared variable.
  5. Mark one delay: the September before places held back change the share. (Not started)No effects yet. Brief: exactly 1 delay.

Always checked

  • Each loop's kind matches its − effects (Not started)No loop declared yet.
  • Loop labels are unique and match their kind (Not started)No loop declared yet.
  • Every effect has a polarity (Not started)No effects yet.
  • The structure matches each declared archetype (Not started)No archetype declared yet.
  • No variable's name breaks the more test's three rules (Not started)No variable drawn yet.
Written feedback
Export

One defensible answer

It opens here once you've drawn at least one variable in the lab above. Your attempt saves as you draw.

One defensible answer