# Values in the process

> Sometimes the process of creating an outcome holds greater value than the outcome itself. We need to take care, because over-automation and the like can inadvertently destroy that value.

Sometimes the process of creating an outcome holds greater value than the outcome itself. We need to take care, because [over-automation](https://wiki.g15e.com/en/pages/Over-automation.txt) and the like can inadvertently destroy that value.

## Examples

- **Adding links in a [wiki](https://wiki.g15e.com/en/pages/WikiWikiWeb.txt)**: The process of linking documents while organizing them is valuable. Actively recalling and retrieving existing documents related to what you are writing strengthens memory, and rereading an existing document in a different context sometimes yields new insights. This value comes from linking manually.
- **[Test-driven development](https://wiki.g15e.com/en/pages/Test-driven%20development.txt)**: Automated <unit tests> are a by-product; the greater value actually lies in repeating the [TDD cycle](https://wiki.g15e.com/en/pages/TDD%20cycle.txt). We keep that by-product alongside the code rather than deleting it simply because it is useful enough.[^1]
- **[ShadowBox training](https://wiki.g15e.com/pages/ShadowBox%20training.txt)**: A decision-making training method developed by <Gary Klein> and others. Trainees face challenging scenarios resembling real situations, make decisions, and compare how and why their decisions differ from experts'. This can spark a desire or competitive urge to agree with the experts, but that is merely a way of making it engaging. What matters is the process of comparing your opinion with the expert's and reflecting on the differences.
- **<Affinity diagrams>**: As you build the diagram, holding and moving sticky notes, discussing with colleagues, and trying different arrangements, you gain many insights. This process holds far more value than the finished diagram. Using [AI](https://wiki.g15e.com/en/pages/Artificial%20intelligence.txt) to produce a "quick result" may have benefits, but also risks reducing the insights gained through the process.
- **[Puzzle Dependency Graphs](https://wiki.g15e.com/pages/Puzzle%20dependency%20charts.txt)**: The final result resembles a flowchart, but the process of drawing it is substantially different.
- **Games**: Almost all of a game's value lies in playing it. Cheating to reach the ending takes away much of the fun.

## See also

- [Knowledge in the process](https://wiki.g15e.com/en/pages/Knowledge%20in%20the%20process.txt)

## Footnotes

[^1]: "The tests that are a natural by-product of TDD are certainly useful enough to keep running as long as the system is running.", Chapter 17, [Test-driven development: by example](https://wiki.g15e.com/en/pages/Test-driven%20development%20-%20By%20example.txt)