The system design loop

A six-stage method for moving from a messy operating problem to a system that learns from use.

By GT · guide

Maintained · Updated Aug 2026

  • Method
  • GTM systems
  • Automation

Why I use it

It keeps teams from jumping directly from a frustrating task to an automation tool before the decision, data and ownership are clear.

Boundaries

It is a framing method, not a substitute for domain expertise or implementation testing.

Understand

Find what people are trying to achieve, how work moves today and where it actually breaks.

Design

Clarify decisions, ownership, handoffs and feedback before choosing the mechanism.

Structure

Create the data, state and context the system needs to behave reliably.

Automate

Remove repetitive movement, reconciliation and follow-up where rules are stable.

Augment

Use AI where interpretation, judgement or recommendations add value, with evidence and boundaries.

Improve

Observe outcomes and failures, capture corrections and refine the system continuously.