Thread regarding Enbridge Inc. layoffs

Open Letter to CIO

Hi folks,I’m thinking about sending this open letter to the CIO and or CFO. Please share you thoughts with me here about how it can be improved.

Dear CIO,

Your recent reorganization announcement identifies many things TIS desperately needs: clearer accountabilities, better collaboration, stronger business enablement, and more efficient delivery.

Those are the right priorities. But for many of us, the announcement was deeply frustrating.

We've been waiting years for these improvements.

The previous transformation initiative was supposed to address longstanding problems with governance, decision rights, processes, and collaboration. It delivered little meaningful change because the executive leadership team couldn't align on what needed to be done.

Then we gave you another year to learn the organization and establish your direction.

You've been with the company for approximately 15 years. You're an SVP with significant authority, a substantial budget, and the ability to bring in whatever expertise was needed. You didn't need to wait for a reorganization to start fixing these problems. That work should have been happening in parallel.

You inherited the dysfunction. But after a year in the role, you own the lack of progress in fixing it.

We've reorganized. What have we fixed?

Your announcement changes reporting lines and leadership responsibilities while acknowledging that significant work remains to determine how the organization will function.

That's difficult to accept.

The same executive team that has struggled for years to resolve cross-functional problems now has substantial new portfolios, teams to integrate, and businesses to support.

Expecting those same leaders to somehow find the time, alignment, and motivation to transform TIS is not a credible plan.

Running TIS and fixing how TIS works are both essential. But the latter cannot remain a side responsibility for the people who have repeatedly failed to deliver it.

Put trusted leaders in charge of transformation

Establish a TIS Transformation Council comprising a small group of directors and managers selected for their credibility with TIS employees, delivery performance, and the trust they've earned across the organization.

You don't need to guess who those people are.

Employee engagement survey results provide evidence of which leaders have built strong teams, earned employees' confidence, and created environments where people feel respected and supported. Combine those results with delivery performance and cross-functional credibility.

Let the council choose its chair. Give it dedicated capacity, a budget for external expertise, direct access to you, and the authority to challenge existing practices.

Task it with fixing the processes, governance, decision rights, and accountabilities that connect TIS. Require practical recommendations, implementation plans, measurable outcomes, and deadlines.

The executive leadership team must remain accountable for implementing the changes, but it cannot be allowed to stall them through competing priorities or an inability to reach consensus.

And listen to the people doing the work. Many have been identifying these problems for years.

Change is about human behaviour. If you want employees to embrace it, put leaders they already trust in charge of making it happen.

Reconsider who you're trusting and rewarding

One of the biggest criticisms of the previous CIO was the perception that loyalty mattered more than independent judgement and that challenging leadership carried personal risk.

Your appointment was supposed to change that.

Yet employees have seen a highly respected, trusted, and effective director leave after demonstrating the courage to challenge senior leadership and stand up for what they believed was right for the company. Not only did you fail to stop it, you've told us you enabled it.

Whatever the circumstances of that departure, its effect was chilling.

Meanwhile, leaders facing longstanding concerns about their performance, people leadership, and ability to deliver meaningful improvements remain in senior positions. Some have even been promoted.

The message employees take from this is troubling: challenging leadership may cost you your career, while failing to deliver results carries little consequence if you retain the confidence of those above you.

Whether or not that's the message you intend, it's the one your leadership decisions risk reinforcing.

Are you rewarding the people who make TIS better, or those who are best at managing their relationship with you?

When employees believe speaking up carries greater risk than underperforming, they stop telling leadership what it needs to hear.

You need to challenge your executives, confront poor leadership, and reward integrity, competence, and results rather than loyalty or personal relationships.

Accountability requires capability

There's another lesson from the previous leadership regime that appears to have been missed.

The former CTO wasn't necessarily the underlying problem. The bigger failure was assigning that position an unrealistic breadth of authority without adequate checks and balances or consideration of the capabilities required.

That was a leadership decision.

And we risk repeating it.

The new structure assigns executives responsibility for broad and sometimes very different technology disciplines. But have we adequately assessed whether they possess the experience and judgement to lead them?

We wouldn't assume a civil engineer was qualified to lead pipeline integrity simply because they held an engineering degree. We'd expect relevant expertise.

Why should technology be different?

Cybersecurity, cloud infrastructure, software development, enterprise architecture, operations, AI, and technology strategy are distinct disciplines. Experience in one doesn't automatically qualify someone to lead another.

Technology expertise deserves the same respect for specialization that we give engineering.

Executives don't need to be experts in everything they oversee. But they must recognize their limitations, understand the expertise required, and empower capable people to exercise genuine authority.

Otherwise, we're setting leaders up to fail and then expecting to hold them accountable for responsibilities they may never have been equipped to fulfill.

As CIO, you're accountable not just for your executives' performance, but for whether you've put the right people in the right roles with the support and authority to succeed.

Stop leaving employees to reconcile contradictory expectations

Your direction appears to give the business greater authority over technology decisions while TIS retains responsibility for architecture, cybersecurity, standards, and risk.

That ambiguity is unfair to employees and dangerous for the company.

People are expected to follow established governance requirements while being criticized for slowing down the business when they do exactly that.

If the policies are wrong, change them. If accountability belongs elsewhere, move it. But don't expect employees to read your mind.

If you want to change the rules, change them in writing. Communicate the new expectations, align authority with accountability, and stop treating employees who follow existing policies as obstacles to business enablement.

The longstanding ambiguity between the BSS/DSS teams and TIS is another example.

You knew about these problems from your years in the business. Yet after a year as CIO, the boundaries, decision rights, and accountabilities remain unclear. Have we moved the needle even a little? It doesn't seem so.

These aren't technical problems requiring years of study. They're leadership decisions that should have been addressed long ago.

Lead the organization. Leave the technology to the experts.

You weren't appointed CIO because you had the deepest technology expertise.

Your value proposition was your business knowledge, relationships, leadership experience, and ability to improve collaboration and organizational culture.

Those are valuable strengths. But we need to see them put to work.

We already have talented professionals who have spent their careers mastering technology, delivery, governance, and risk management.

What we lack is consistent executive leadership that trusts their expertise, removes organizational barriers, resolves conflicts, and supports sound professional judgement.

We don't need you to become the smartest technologist in the room. We need you to create an organization where the smartest technologists can do their best work.

The previous CIO brought technical discipline but struggled with culture and collaboration. Your opportunity was to retain that discipline while fixing the leadership problems that held us back.

Instead, we risk weakening governance without materially improving trust, accountability, or organizational effectiveness.

That's not the change people were expecting.

It's time to raise the standard

Nobody expects you to resolve years of dysfunction overnight. But after a year in the role, we should have a credible plan, dedicated leadership, clear accountabilities, and evidence of progress.

Instead, we have another reorganization that appears to reward the EMT, and another promise that the real work is about to begin.

We need you to establish the Transformation Council or something similar, empower trusted leaders, resolve longstanding accountability problems, and hold your executive leadership team responsible for supporting meaningful change.

We need you to reconsider whose advice you rely on, whose performance you reward, and whether employees can challenge leadership without fearing the consequences.

And we need you to hold yourself and your executive team to the same standards of competence, integrity, accountability, and professional judgement that you expect from everyone else.

There are exceptional people throughout TIS who know how to deliver. They've spent years working around organizational barriers that leadership has failed to remove.

They don't need another announcement about change. They need leadership that finally delivers it.

You have the experience, authority, resources, and relationships to be that leader. But it requires focusing on the problems that only you can resolve.

Stop trying to prove you can lead the technology conversation. Start proving you can lead the technology organization.

We've been ready for change for years.

Now it's time for you to deliver it.

We in TIS deserve better. Enbridge needs better.


by
| 494 views | | 24 replies (last 8 days ago) | Reply
Post ID: @OP+1m5tkjvwd

24 replies (most recent on top)

A few more layoffs with this re-org.

How many more to go?

I can think of some good candidates.

by
| | Reply
Post ID: @1k0+1m5tkjvwd

Lol. There is zero talent left in TIS. What you see is the remnants of keep the ship afloat with outsourced everything.

by
| | Reply
Post ID: @1h3+1m5tkjvwd

It’s amazing how many IT threads get deleted.

by
| | Reply
Post ID: @19h+1m5tkjvwd

@ph
These CIO types dont have the attention span required to read something this long

by
| | Reply
Post ID: @re+1m5tkjvwd

@nx IT employees in non-technology companies often face accountability without authority, responsibility without recognition, and conflicting expectations without leadership support, to a degree few other functions experience.

Their own leaders often lack the visibility to recognize their contributions, while the business treats them as vendors rather than teammates. They’re caught between IT standards and business demands, accountable to both but supported by neither.

They can save the company millions or avert a major crisis one day. The next day, they’re blamed for a problem they had neither the authority nor the opportunity to prevent. And others often take credit for their work because they want to play with the technology themselves (DSS teams for example).

CIOs compound the problem by swinging between rigid technology control (Bhushan) unquestioning business accommodation (Scott).

The result is capable people held accountable for outcomes they can’t control, denied recognition for the value they create, and caught between leaders who don’t understand their work and clients who don’t consider them part of the team. That’s not an attitude problem. It’s a leadership and organizational design failure.

by
| | Reply
Post ID: @ph+1m5tkjvwd

Its amazing how often TIS shows up on these boards

by
| | Reply
Post ID: @nx+1m5tkjvwd

A “little” long, but the original poster nailed it. Good luck getting anyone with influence to read it, nevermind act on it.

by
| | Reply
Post ID: @jw+1m5tkjvwd

Effective people leadership is not defined by one's own intellectual prowess, but rather by the ability to curate a high-caliber team, empowering their expertise while proactively shielding them from tangential demands that lack demonstrable business impact

by
| | Reply
Post ID: @jk+1m5tkjvwd

Sorry to bust your bubble but the most important qualification is been a friend or likable by your people leader. They don’t care if you have PHD in that subject

by
| | Reply
Post ID: @gs+1m5tkjvwd

@fe what are you talking about the “development opportunities for executives”?

by
| | Reply
Post ID: @ff+1m5tkjvwd

@OP - I’m not in TIS, but I think almost ALL of this letter could be included in a letter to MANY of the leaders across the enterprise!! Can you please post more of them and send them to a broader group of “Leaders”?!?!!! I didn’t know we had this level of awareness and intelligence existing within the Company to peg an organization within Enb THIS well in writing! Almost feels like this and the other “Development Opportunities for Exec leaders” post are GE’s parting gifts “to the people”. Both very enlightening and entertaining to read!

by
| | Reply
Post ID: @fe+1m5tkjvwd

@ar CORRECT! This is literally THE ENTIRE Enterprise, ALL of Enbridge!!!

by
| | Reply
Post ID: @fc+1m5tkjvwd

@d3 Some of these are barely supervisors. Not sure how they made it to Directors

by
| | Reply
Post ID: @ep+1m5tkjvwd

@d3 BLOAT

by
| | Reply
Post ID: @dm+1m5tkjvwd

@a5 some of the good ones for this committee are,

BM: Director TIS Enterprise Architecture
BB: Director TIS Cybersecurity Operations
MI: Director TIS SCADA Replacement Program Delivery
SB: Director TIS Business Applications Operations & ERP
TE: Director TIS Network Services
JP: Manager TIS Infrastructure Modernization
CH: Director TIS GDS Enablement - Operations, Engineering & Integrity Services
ES: Director TIS GDS Portfolio & Program Management
GD: Director TIS Projects Execution Office

by
| | Reply
Post ID: @d3+1m5tkjvwd

@az there’s definitely a DEI hangover at Director table. A few Directors from that era that we could stand to lose from JGs former team.

by
| | Reply
Post ID: @b7+1m5tkjvwd

@ax JP didn’t get it, what about KA? These 2 got overlooked while under performers got shuffled around and taken care of.

by
| | Reply
Post ID: @az+1m5tkjvwd

JP was a strong and deserving candidate for the Director of Infra structure, bringing the capability and leadership potential needed to succeed. It is disappointing to see his contributions overlooked while SG advances 🤨 sweet mother of poor decisions! This raises serious questions about judgment, selection criteria, and the leadership qualities being rewarded. When influence and calculated manoeuvring appear to take precedence over genuine merit and integrity, it undermines confidence in the appointment process. JP deserves far greater recognition for the value he brings and the leadership potential he has demonstrated. Leadership appointments should reflect competence, integrity, and genuine ability—not the behind the scenes hidden manipulations.

by
| | Reply
Post ID: @ax+1m5tkjvwd

“We wouldn't assume a civil engineer was qualified to lead pipeline integrity simply because they held an engineering degree. We'd expect relevant expertise“

lol, this is GDS x 1000.

Equating Degrees with intelligence is literally currently wasting hundreds of millions at least.

by
| | Reply
Post ID: @ar+1m5tkjvwd

I can’t speak to every point in the letter, but what I do recognise is depressingly accurate.

The DSS situation is a complete shambles. There’s a reason Architecture has distinct disciplines, with clearly defined responsibilities. DSS was never meant to take ownership of technology, and the CIO ought to know that given his involvement in the original arrangements. Yet years later, we’re still muddling through overlapping mandates, confused accountabilities and competing authority. It’s basic organisational design, for goodness’ sake. Why is this still not sorted?

by
| | Reply
Post ID: @ae+1m5tkjvwd

TL;DR = Do better. Here’s how.

by
| | Reply
Post ID: @ac+1m5tkjvwd

tldr

by
| | Reply
Post ID: @a8+1m5tkjvwd

Tf is gonna read all of that?

by
| | Reply
Post ID: @a6+1m5tkjvwd

Serious question. Which directors would you
put on this council? Who are the good one?

by
| | Reply
Post ID: @a5+1m5tkjvwd

Post a reply

: