# Agile Beyond IT

Carry agile principles into a new domain while tailoring practices to its real work, constraints, and cadence.

Duration: 14 min

Agile practices did not begin and end in software. Pull systems, visual work, limits on work in progress, and structured reflection have roots in manufacturing and operations. The useful transfer rule is simple: principles travel, while practices must be adapted.

In this lesson, use examples from marketing, healthcare, recruiting, and education to separate a transferable principle from its local expression. Then build a starter kit for one non-software setting. Famous transformation stories are evidence to question, not organization charts to copy.

## fmap-m5-l1-v1

The approved narration and animated design draft remain under review. This pending provider record is intentionally excluded from public delivery. Watching the video does not complete the lesson; the readable digest is an equivalent learning path.

## fmap-m5-l1-digest

### What transfers, what adapts

Visual boards, pull systems, WIP limits, and continuous improvement have roots outside software. Their history helps correct a persistent misconception: adaptive work is not a software metaphor being stretched across unrelated industries.

The transfer rule is **principles travel; practices adapt**. Small slices, evidence, limited WIP, psychological safety, and inspect-and-adapt are not tied to a particular job. Meetings, board columns, cadence, and role labels are local expressions. Copying those expressions without examining the work produces costume agile. Carrying the principle and redesigning the practice is the actual skill.

Four settings show the rule:

- A marketing team can use short goal-led cycles, story-form campaign items, and reviews of real drafts. Its vocabulary and cadence should fit campaign work.
- A clinic can make patient flow and waiting visible, limit partially processed cases, and make it safer to surface errors. Patient safety constrains every experiment.
- A recruiting team can define its actual stages, expose an interview bottleneck, and run one owned improvement experiment.
- A teacher can pilot a unit with one class, gather evidence, and refine it before wider use. Minimum scope must still be viable in quality.

Named transformation cases require a warning label. They can show that principles moved into a new setting, but they are not neutral blueprints. Read each case for the move from principle to tailored practice, the investment and constraints that made it possible, and the limits of its evidence. Do not copy an organization chart.

The practical test is: **which principle are we carrying, and what must its expression become here?**

## fmap-m5-l1-r1

### Dated case cards — evidence, not blueprints

These cards are quarantined from the evergreen lesson because organizations, reported results, and available source editions can change. If the review date passes, use the lesson digest instead.

**ING — banking, Netherlands.** Primary leadership interviews describe a large head-office reorganization into small, cross-functional squads grouped into tribes and organized around customer missions. Published accounts report a substantially faster release cadence qualitatively; this card makes no unsupported percentage claim. **Caveat:** this was a heavily supported restructuring in a regulated bank. Study the move toward mission ownership, not the chart.

**John Deere — agricultural equipment, United States.** A 2022 case study produced with the consultancy involved in the transformation reports agile work beyond software, including marketing and embedded product programmes, and reports increased output, faster time to market, and positive return on investment. **Caveat:** treat consultancy-reported figures as situated evidence, not a forecast for another organization. The useful pattern is adaptation inside a long-established manufacturer.

**Spotify — the model that warns against copying it.** The widely circulated squads, tribes, chapters, and guilds picture described one evolving organization at one time. Later accounts from people inside Spotify stressed that it was not a universal operating model and continued changing. **Caveat:** its most transferable lesson is to invent practices from principles rather than reproduce its labels.

Card set version: 2026-07. Sources and wording are reviewed every six months.

## fmap-m5-l1-i1

Complete any one four-part kit, then compare another domain. The principles remain recognizable; the practices should not be identical.