6 min read · Case Study
He smiled. I smiled back. We both knew exactly what it meant without saying a word.
The Situation
Every Traffic Control Plan had two distinct parts. The traffic control application was the engineering work. The judgment calls about lane closures, pedestrian paths, signage placement, detour routing. That was the part that required a trained mind. The base map was everything underneath it. Street geometry, face of curb, back of walk, intersections, speed limits, lane striping. All of it had to be drawn before you could touch the part of the job that actually required thought.
An experienced TCP engineer could finish a complete plan in three to four hours. A new engineer could spend four to five hours on the same job. When I started tracking where the time actually went, the answer was consistent. The application itself took thirty minutes to an hour depending on the complexity of the situation. The base map consumed everything else.
I was about a year into the role when the thought first formed. It was not a strategy. It was a wish. What if somebody could just hand us the base map? What if we could pull the city’s street geometry directly from a source, cut what we needed, and drop it in? Skip the drawing entirely and go straight to engineering. I wanted my very own drafter.
The wish had no way to happen yet. But it did not go away.
· · ·
The Diagnosis
This is pretty straightforward once you can distinguish between the two parts. A skilled TCP engineer spending three-quarters of their time drawing street geometry was not an engineering problem. It was a workflow problem. The skilled work and the preparatory work were bundled into the same role, performed by the same person, billed at the same rate. Nobody had separated them because there had never been a reason to.
The pattern: Jobs often contain different kinds of work that get bundled together simply because nobody has ever separated them. Over time the bundle starts to look natural, even when one part requires skill and the other mostly requires time. Sometimes the opportunity isn’t improving the work. It’s deciding which parts of the work actually belong together.
Domestically there was never a way to fix it. You needed complete engineers, not drafters. The cost structure did not support splitting the role. So the idea stayed filed away, occasionally revisited in my mind, with no opening to act on it.
What I understood, even then, was that just because something is not ready for the moment does not mean it will not work its way back. If the idea was good enough and the right conditions eventually existed, there would be a window. The goal was to be ready when it opened.
I moved out of the TCP group and into other programs. The idea moved with me.
The Moment
The company was standing up its offshore operation. Traffic control plans were among the first work being considered for the transition. The CEO was making his rounds, asking each of us whether we saw anything in our areas that could be done better or made more efficient.
He got to me. I told him I did not have anything for my current group. But I had come from TCP, and I had been sitting on something for about five years.
I explained to him that the cumbersome part of creating a TCP was drawing the base map. The engineering application took thirty minutes to an hour. Creating the base map didn’t require much skill. It required time. It never mattered to me who did that work, only that it got done ahead of the engineering. The company was already standing up an offshore operation, and that gave the idea a path it had never had domestically. If the base map could be ready and waiting by the time our engineers sat down, they could walk straight into the application. Conservatively creating six, eight, or ten plans a day instead of one or two. Skilled labor on skilled work. A 24-hour production cycle that made full use of both teams.
He smiled.
I smiled back.
We both knew exactly what it meant without saying a word. Five years of carrying something with nowhere to put it, and in about ninety seconds it had finally landed.
The pattern: Good ideas rarely arrive at the same moment the organization is ready to use them. The value isn’t just seeing the opportunity early. It’s doing enough thinking beforehand that the answer is fully formed by the time the window opens. Some conversations take ninety seconds because the real work happened years earlier.
The Outcome
By the time it was implemented I had moved on to other programs. The TCP group still supplied permits for the work I managed, so I knew the operation was running. I heard the details secondhand. I later learned the work had been divided much the way I’d envisioned. Preparatory drafting was being completed ahead of the engineering work so the domestic team could begin with the application.
I did not see the production numbers. I was not in the room when the first plans came through the new model. What I got instead was a passing comment on a status call, someone stating, “that job is being base mapped right now.”
I had a quiet moment. I thought back to that conversation with the CEO. I smiled to myself and moved on.
That was enough.
· · ·
What This Signals
Most ideas arrive before the conditions exist to act on them. The instinct to see inefficiency is only useful if you are patient enough to wait for the right window and alert enough to catch it when it opens.
The base map idea was not complicated. Separate the preparatory work from the skilled work. Let skilled people spend their time on skilled work. Create a workflow where the skilled work is always ready to begin. The insight was not technical. It was structural, a problem of how the work was organized.
What it required was holding the idea without forcing it. Domestically it never made sense and I knew that. So it stayed filed away, not abandoned, just waiting. When the offshore model created the conditions, the idea was ready. One conversation. No presentation. No formal proposal. Just a fully formed solution that had been waiting five years for somewhere to land.
Inefficiency is waste. It costs money. It costs time. It raises stress. The base map problem was all three, quietly, every single day, for every TCP engineer who had ever spent three-quarters of a job drawing street geometry before they could do the work they were actually hired to do.
This fix was not difficult. It required someone willing to look at the work closely, see where the time was being spent, and decide that breaking up the work was the answer. The hard part was not missing the opportunity when it presented itself.
The idea wasn’t waiting for a better solution. It was waiting for the right environment.