LET'S CONNECT

Setting an Effective Strategy for Complex Utility Technology Projects

November 2025
  • Too many complex technology projects and programs start with a strategy that is overly simplistic and broad or simply doesn’t exist at all, and the initiatives that follow suffer as a result. Schedules and costs balloon, expectations are not met, and quality issues are confused with scope and functionality gaps. When a strategy does exist, it is so vague and ethereal that almost any approach or objective can be rationalized as being critical to the program.
The Red Flags
  • Have you ever been a part of a project that can’t get going? We’ve seen technology procurements that can’t complete a purchase because different stakeholders and executives can’t agree on the best vendor selection. We’ve seen executives debate the cost of programs after the budget has already been set and approved. We’ve seen programs launch projects that aren’t yet staffed because resource planning wasn’t part of the initial strategy, or due to a need to “get started” even the strategy and business value wasn’t clear.

Setting the Stage for Faster Decisions, Better Outcomes, and Long-term Success
  • What can be done? A clear, effective strategy will help a lot. It identifies the business drivers behind the effort – why it’s important, who benefits, how it supports customers, and the timelines associated with its goals. It provides clarity about what priorities are driving key decisions and operates as a sanity check for anyone associated with the effort.

  • The key is to create simplicity and alignment with a practical, results oriented strategy that will survive the length of the project. Once the project is over, the strategy that drove it feeds directly into ongoing support and maintenance and helps future teams understand the “why” behind what the project delivered, and where to best place their energy and resources.

  • Alignment of stakeholders and program participants within an organization is one of the most powerful forces in the business world. A strong and effective strategy is clear, long-lived, resonates with a broad audience, and provides guideposts that all involved can use to measure progress, turn assumptions into facts, and surface the need for adjustments.

Warning Signs of Missing Strategy
  • Stakeholders can't agree on vendor selection
  • Budget debates after approval
  • Projects launch before staffing is complete
  • "Get Started" mentality without clear business value

Setting the Foundation

Defining the Non-Negotiables
Technology strategies gain power when they define where clarity is non-optional. Shape your project strategy around these focus areas:
Value Narrative The short, testable statement connecting business outcomes to performance metrics
Operating Model Ownership of processes, data, and the “run state” after go-live
Architecture GuardrailsAgreed rules for integration, security, and reuse
Delivery TimelineKey milestones that mark tangible progress such as major releases, validated outcomes, or executive checkpoints aligned to measurable results
Change EnablementThe plan for training, communications, and stakeholder readiness
Once these non-negotiables are explicitly defined, ambiguity and the cost that goes along with it drops quickly.

Putting it Into Action

The following simplified examples illustrate how these principles can be expressed in a clear, actionable way within a project strategy.
  • Value Narrative Example

  • A company is implementing an initiative that integrates data received from the field, such as asset replacement, crews assigned, and vehicle locations into a single view and data set. A value narrative here would be:

  • “Enable faster power restoration by integrating field operations and outage data, improving service restoration times by 25% while maintaining full regulatory traceability.”
  • Operating Model Example Clarify who makes what decisions at the start of the project and include it in the strategy. One criteria might be around the financial ramifications of a decision. Create a simple matrix that describes the criteria, who makes the decision, and who reviews it.

Financial Impact
Decision Maker
Decision Reviewer
None
Team Member
Manager or Workstream Lead
<$100,000
Manager or Workstream Lead
Senior Manager
>$250,000
Senior Manager
Executive
>$1M
Executive
CEO
  • Architectural Guardrails Example

  • Direction is given to the individuals implementing the solution as to what constraints or goals they must adhere to:
  • Integrations must be APIs utilizing existing micro services whenever possible
  • The cyber security of the solution must meet enterprise standards
  • Data and process designs must be reusable across business units
  • Delivery Timeline Example

  • Establish major milestones that define measurable progress as opposed to technical completion. For example:
  • Q1 2026: Integration design and business process definitions approved by Senior Leaders
  • Q2 2026: Deliver the first end to end workflow including test data
  • Q3 2026: Solution validated with a live pilot in the Control Center
  • Q4 2026: Go live, initiate post go-live care for 90 days
  • Change Enablement Example

  • Ensure technical and business teams understand how the new capability impacts their roles and work.

  • Change Recipients Application owners, software users, and data stewards

  • Support Workshops during the design phase. Testing prior to go-live done by the applications users. Data ownership defined and documented

  • Proficiency Measures Completion of learning modules. Demonstrated ability of software users to complete tasks in the new system. Time to complete processes are the same or better than prior to go-live

  • Ongoing reinforcement Errors are delivered to and corrected by software users within 1 day of when they occurred. Community of practice meetings to share experiences and maintain consistency and alignment.

Three Guiding Principles for Effective Strategy

1. Lead with Measurable Results, Not Purchases

Many projects begin with the wrong question: “What should we buy?” The better question is: “What measurable outcomes will this investment deliver?” Utilities that align technology work with business results from the start typically see up to 40% faster delivery cycles and 35% higher first-pass quality compared to scope-first programs (Capstera, “Architecting Utility Excellence: Value Stream Mastery”). Tools naturally align to purpose when success is defined in terms of reliability, customer impact, and compliance. A clear strategy translates those outcomes into decision criteria. For a utility improving their market operations, the measurable might be:
  • “Reduce manual settlement effort by 60% while improving audit confidence”
A utility installing a modern Outage Management System may have a measurable goal:
  • “Improve outage response coordination by shortening data synchronization from hours to minutes” and

  • “Increase transparency for regulators through consistent reporting standards”
Objective success criteria turn the project into a clear set of outcomes that can be observed by anyone. By defining what “winning” means, everyone involved can leverage their expertise and experience to contribute to the win. The experts already know their area and value. What they need to know is how to use it.

2. Name the Shifts

Too often, strategies describe what will be done, not what is changing. Call those shifts out early and explicitly. Common ones include:
  • Moving from batch-based processing to near-real-time data flow
  • Evolving from rigid rules to explainable automation
  • Shifting from point solutions to shared, platform-based capabilities
For example, a given company may be initiating an AI initiative to improve customer service or eliminate repetitive or low-value tasks. From the perspective of a customer advisor, that sentence can feel scary and put me at odds with the effort. By naming the shifts, we can help put a bound on what is changing and help the person see where their work fits in. The shift in this example is to reduce the manual work involved with assisting customers.

3. Build a Strategy that Learns as it Goes

The best strategies evolve with evidence. A mechanism to adjust the strategy when appropriate increases its efficacy. Importantly, it also increases the credibility of leaders for those executing the strategy. Set specific approaches for gathering feedback and be clear about when the input is gathered. For example, every design review, stakeholder meeting, or vendor demo can provide an opportunity to test assumptions. A simple way to do this is to log three quick reflections after a review or demo:
  • What surprised us? This question highlights emerging risks
  • What bothered us? This exposes friction worth resolving
  • What do we like? This question validates which parts of the strategy are working or should be emphasized
The feedback received needs to be made visible. For example, a recent large technology transformation project used a simple weekly decision log to create traceability and confidence in the decisions being made. Whenever possible, decisions were tied back to how it supported the overall strategy. When executives asked why a decision was made, the rationale was already documented, rather than being reconstructed from memory.

The Payoff of Strategic Clarity

Utilities that embed this kind of technology strategy experience more than successful go-lives. They see cultural and operational benefits that compound:
  • Faster, safer decision-making with less rework
  • Earlier delivery of measurable outcomes, reducing project fatigue
  • Greater audit and regulatory confidence through clear traceability
  • Teams that learn faster than the problem evolves
Complexity doesn’t have to mean chaos. The right strategy makes it navigable.

Putting it Into Action

If you have an existing strategy that needs improvement, or want to get started on a new strategy, use our suggestions as a guide and checklist:
  • Start with decisions that are non-negotiable
  • Set clear guardrails around value, ownership, architecture, and outcomes so everyone knows what is mandatory
  • Lead with measurable results, not purchases
  • Define success in terms of outcomes before choosing tools or vendors. Communicate those goals so everyone knows what winning looks like. Avoid beginning with product decisions or technical features until results are clearly established.
  • Name the shifts
  • Define what’s changing—whether it’s roles, processes, or technology—and communicate those shifts in simple, direct language so everyone understands how the work will be different.
  • Build a strategy that learns as it goes
  • Define how feedback will be gathered and used to test assumptions. Communicate what you learn along the way, so the strategy adapts based on evidence. Avoid rigid plans that resist course correction or treat changes as failure.

We can help!

If your team is preparing for a large technology investment or struggling to connect daily work to business outcomes, Sage can help. Our consultants bring structured methods and real-world experience to design strategies that create alignment, enable faster delivery, and sustain long-term value. We focus on helping utilities and grid participants build strategies that link every technology decision to measurable business results — improving delivery confidence, regulatory transparency, and customer impact. Contact us to start building a technology strategy that turns clarity into results and ambition into delivery.