Metkagram · Pattern Routes · diagnose-a-system-before-optimising

Diagnose a system before optimising it

Follow effects beyond the first visible result, locate moving bottlenecks, separate symptoms from drivers and avoid local optimisation traps.

After this pack: Explain why a local improvement may fail at system level and identify the structural condition that keeps reproducing the outcome.

For: B2 · C1 · professional English · systems thinking · AI tutor

Route

  1. 01 · Pattern

    The immediate effect may be [X], while the second-order effect could be [Y].

    Start by separating the immediate effect from the second-order effect it may trigger.

    Open canonical object
  2. 02 · Pattern

    This removes the bottleneck at [X], but may move it to [Y].

    Check whether removing one bottleneck merely moves the constraint somewhere else.

    Open canonical object
  3. 03 · Pattern

    Optimising [X] locally can make [Y] worse overall.

    Challenge local metrics by asking what the optimisation does to the whole system.

    Open canonical object
  4. 04 · Pattern

    This treats the symptom [X] without changing the underlying driver [Y].

    Separate the visible symptom from the driver that keeps recreating it.

    Open canonical object
  5. 05 · Pattern

    The system will keep producing [X] as long as [Y] remains unchanged.

    Finish by naming the unchanged structural condition that will keep reproducing the result.

    Open canonical object

Teacher & Tutor Exports

Need to reuse this pack outside Metkagram?

Download a portable bundle with the same stable IDs and canonical links instead of copying cards by hand.

Continue learning

Choose the next useful route.