Getting the Words Right

Summary: RAG works when stable endurants map cleanly to visible perdurants, and breaks when containers and summary endurants hide the underlying dynamics. One way to make this concrete is to look at a familiar tool: the RAG (Red / Amber / Green) status. At first glance, it seems universal, just a simple way to signal whether things are on track. But the meaning of that signal depends entirely on the relationship between the endurants, what you are tracking, and the perdurants, what is actually unfolding over time. In Manufacturing Consider a production line dashboard:

•Line A: Green •Line B: Amber •Line C: Red In this setting:

•the endurants are stable and well-defined: machines, lines, batches, inventory •the perdurants are structured and repeatable: production runs, assembly steps, quality checks •the mapping between the two is tight A production line has a known process, and a batch moves through known stages. Because of this, the RAG status is not just a color. It is usually backed by telemetry that carries context.

A red status likely corresponds to something legible:

•a machine failure •a supply issue •a quality threshold breach And importantly, the system often makes it relatively clear what to do next. The signal is actionable without deep reinterpretation, because time and state are present but mostly implicit. The structure of the system does most of the work. In Knowledge Work Now consider a typical product or organizational dashboard:

•Initiative A: Green •Initiative B: Amber •Initiative C: Red At first glance, this looks similar. But underneath:

•the endurants are more abstract and fluid: initiatives, bets, opportunities, strategic themes •the perdurants are overlapping and evolving: discovery, delivery, alignment, learning, rework •the mapping between the two is loose and shifting What exactly is included in Initiative A? Has that changed? Is it still the same thing? In this context, the RAG status often carries very little embedded context. A red status might mean:

•a dependency slipped •a key assumption was invalidated •scope changed •alignment broke down •new information emerged But the color itself does not tell you:

• what changed
• when it changed
• why it changed
• what kind of response is required

The signal becomes a flag that something is off, without encoding the underlying situation. Where It Goes Off Track There are two common failure modes. The Wrong Endurant The thing being tracked is not a stable or coherent entity. Aprojector initiativemay be:

•a bundle of loosely related work •a shifting scope •a container for multiple independent efforts If the endurant is poorly defined, the RAG status becomes a flattened summary of unrelated dynamics. The underlying perdurants no longer map cleanly to it, and you are effectively asking, “What is the status of this thing?” when the thing itself is ambiguous. The Missing Perdurant Even if the endurant is reasonable, the unfolding process is not captured. There is no clear representation of:

•sequences of events •transitions •evolving states •feedback loops Without the perdurant, the RAG status becomes a snapshot without a story. Surprises become inevitable because:

•the path to the current state is invisible •emerging risks are not legible Summary Containers There is an additional layer. Executives often ask for:

• the big picture
• a high-level view
• less detail

In the later terminology of this series, this is better understood as a summary container. For example:

•portfolio status •strategic theme status •quarterly objective status These are not the underlying things. They are containers that aggregate other endurants, each with their own perdurants. This creates a compounding effect. A summary container sits on top of:

•multiple lower-level endurants •multiple overlapping perdurants The RAG status at this level compresses all of that into a single signal and often represents diffuse, distributed risk. So when a leader seesTheme X is Amber, that status may reflect:

•small issues across many areas •one critical issue hidden in the aggregate •or simply uncertainty in interpretation The risk is that the status appears precise, but the underlying reality is not. Why It Breaks Differently In manufacturing:

•endurants are physical and stable •perdurants are structured and repeatable •aggregations tend to preserve meaning, such as total output or defect rates So even at higher levels:

•summaries remain grounded in consistent structures •telemetry still carries actionable context In knowledge work:

• endurants are constructed and evolving
• perdurants are non-linear and overlapping

•aggregations often erase the very context needed to interpret them The Core Insight A RAG status works when:

•the endurant is stable and well-defined •the perdurant is structured and well-understood It breaks down when:

•the endurant is ambiguous or shifting •the perdurant is invisible or poorly represented In those cases, the RAG status becomes a signal without sufficient context to support understanding or action. At best, it is a prompt to ask better questions. On its own, it is not an explanation. Try This Now:

• Pick one status signal your organization uses regularly.

•Write down the thing that signal is supposed to describe. Does it feel like a real endurant, or is it actually a shifting bundle?

•Ask: what sequence, transition, or history would you need to see before the color would actually mean something?