Tim C. had co-founded a startup that built stock-market surveillance software. In the early 2000s, the WTF Exchange, or WTFX, was a major customer. His company handled one part of a broad project to overhaul the exchange's trading engine and IT systems.

WTFX placed unusual weight on procedure. The exchange required a waterfall design, a fixed project plan, and a large Gantt chart. It also treated predictability as a key requirement and regarded the process itself as a deliverable. Tim says this culture collided with his company's more agile working style.

One report was especially important to the surveillance department. Users needed it to react immediately when filtering rules changed, with cell colors determined by specific conditions. Tim concluded that report-definition files and the company's general reporting module could not meet those requirements.

He built a dedicated module in his hotel room over the following weekend. The implementation was largely complete when he presented it on Monday. The response was alarm rather than praise. The module had a new name, no place in the Gantt chart, and no prior mention in the specifications.

WTFX now faced urgent meetings, priority changes, specification updates, and revisions to the project schedule. Tim's unscheduled solution had become a process crisis. The story continues in Part 2.