Skip to content
“Proven to Optimized” is a short blog series drawn from lived experience on both sides of the implementation table. After more than two decades working within a utility, I’ve seen how early, well-intentioned market decisions tend to persist long after their original context has changed.
Now working from the vendor side with many utilities at once, I see those same patterns repeat. SPP Markets+ creates a rare pause point before designs, workflows, and integrations get locked in again.
This series explores that moment—what tends to stick, why it does, and how experience can be used before go‑live to move from what’s proven to what’s truly optimized.
In Part 2, I examine how decisions built for an earlier moment gradually become technical debt — and why understanding that history is the first step toward getting ahead of it.
The decisions that become technical debt rarely begin that way. They begin as practical responses to a very specific moment in time.
For many utilities, entering the Western Energy Imbalance Market (WEIM) was not just a market transition; it was also a shift in how systems were built and operated. Longstanding, internally developed tools were often being supplemented or replaced with commercial platforms. At the same time, familiar integration patterns — SFTP transfers, CSV processing, and scheduled batch workflows — remained dominant, while newer approaches like APIs were still relatively unfamiliar in day-to-day operations.
That combination shaped how solutions were designed.
Teams were learning the mechanics of a new market while also learning how to operate within a new technical environment. The systems producing market results were different, the interfaces into those systems were different, and the ways data moved and surfaced required a new kind of trust.
Under those conditions, the priority was to establish control and build confidence as quickly as possible.
The most effective way to do that was to anchor the new environment to something already understood. Existing workflows, reconciliation approaches, and validation steps carried forward because they provided a reliable foundation. File-based integrations kept data movement visible and auditable, while spreadsheet-driven reviews gave operators an independent way to confirm results before acting on them. Additional validation steps added a layer of reassurance when outcomes needed to be explained and defended.
These choices aligned with the reality of the work. When results were questioned, traceability mattered. When system outputs were still gaining credibility, independent verification mattered. When participation introduced real financial exposure, predictability and explainability carried more weight than elegance.
Over time, those patterns proved themselves. They supported certification, held up through early settlement cycles, and gave teams a framework for answering difficult questions when they surfaced. As systems stabilized and familiarity with market behavior grew, the workflows that enabled that transition became part of the standard operating model. They were documented, repeated, and passed on.
What began as a way to manage uncertainty gradually became the way work was done.
The surrounding environment, however, did not stand still. Market operations matured, vendor platforms evolved, and integration capabilities expanded. Systems that once required external validation began to incorporate more transparency and control within the platform itself. The technical foundation continued to improve, while the workflows built on top of it often remained consistent.
This is where the shift begins to show.
Processes that once provided clarity can begin to introduce delay. Checks that once built confidence can overlap with capabilities already handled by the system. Data movement patterns that once made information accessible can become points of friction as expectations for speed and flexibility increase. Each element still functions as designed, yet the overall shape of the workflow reflects an earlier set of conditions.
None of these outcomes reflect a poor decision. Each decision solved a real problem at the time it was made. The challenge is that those solutions tend to persist as the environment changes around them.
That’s how technical debt accumulates — approaches that worked under past constraints continue to be used, even after those constraints have changed.
From the outside, these patterns can appear uniform. Internally, they often represent layers of decisions made at different points in time — some tied to early adoption, others to operational stability, and others to incremental refinement. Understanding those layers is what allows teams to separate what remains essential from what has simply endured.
The decisions in front of us now will shape operations for years, just as earlier EIM decisions did.
That makes this the right moment to step back and review the foundations those operations are built on. Looking closely at how familiarity influenced design, how confidence was originally established, and which patterns still reflect current needs creates clarity about what should continue forward.
The next post focuses on how to approach that review in practice — where to look, how to evaluate what you find, and how to apply experience in a way that strengthens what comes next.
If you’re just joining the series, start with Part 1: Proven to Optimized, Part 1: Why Early Market Decisions Are So Hard to Undo. Then come back here; Part 2 builds directly on it.
Want to learn more about Markets+? Check out the following on the PCI blog:
- SPP Markets+ Transmission Integration: An Operational Framework for Balancing Authorities & Transmission Service Providers
- SPP Markets+ Launches Its Implementation Strike Team — What Participants Need to Know
- Why WRAP’s Next Chapter Matters for the Future of Western Markets — & Markets+
- SPP’s Move from SOAP to REST for Markets+ and What It Means for Your Utility
- SPP Markets+: Navigating the West’s Next Market Transition
