Difficult relationships do not remove the need for disciplined decisions.

Every transformation has strained relationships somewhere. A sponsor who feels burned by a prior program. A business unit that does not trust central technology. A vendor relationship that has become defensive. A team that believes architecture only arrives to slow them down. These tensions are not side issues. They shape how decisions are heard, challenged, delayed, and carried into the operating model.

The weak response is to avoid the relationship and push the work through process. The equally weak response is to protect the relationship by softening every hard question. Neither helps the enterprise.

Enterprise leaders need a better stance: respect the relationship and protect the outcome.

For an Enterprise Architect, that means separating tone from consequence. The conversation can be calm, respectful, and commercially adult while still asking direct questions. Who owns the process after go-live? Which data definition is authoritative? What control is being changed? What support burden is moving? Which customer experience will be affected? What future option are we closing by choosing speed today?

These questions can feel uncomfortable when trust is thin. But avoiding them usually makes trust worse later. People do not feel respected when hidden costs surface after commitment. They feel trapped. Good architecture makes the consequences visible early enough for honest trade-offs, which is one of the most practical ways to honour the people who will live with the decision.

This matters especially in executive settings. Leaders often inherit relationships they did not damage and constraints they did not create. The temptation is to keep meetings pleasant and move forward. But transformation requires more than pleasant agreement. It requires clarity strong enough to survive strain. It also requires a method that lets people disagree without turning every decision into a personal contest.

A useful practice is to Difficult relationships do not remove the need for disciplined decisions.

Every transformation has strained relationships somewhere. A sponsor who feels burned by a prior program. A business unit that does not trust central technology. A vendor relationship that has become defensive. A team that believes architecture only arrives to slow them down. These tensions are not side issues. They shape how decisions are heard, challenged, delayed, and carried into the operating model.

The weak response is to avoid the relationship and push the work through process. The equally weak response is to protect the relationship by softening every hard question. Neither helps the enterprise.

Enterprise leaders need a better stance: respect the relationship and protect the outcome.

For an Enterprise Architect, that means separating tone from consequence. The conversation can be calm, respectful, and commercially adult while still asking direct questions. Who owns the process after go-live? Which data definition is authoritative? What control is being changed? What support burden is moving? Which customer experience will be affected? What future option are we closing by choosing speed today?

These questions can feel uncomfortable when trust is thin. But avoiding them usually makes trust worse later. People do not feel respected when hidden costs surface after commitment. They feel trapped. Good architecture makes the consequences visible early enough for honest trade-offs, which is one of the most practical ways to honour the people who will live with the decision.

This matters especially in executive settings. Leaders often inherit relationships they did not damage and constraints they did not create. The temptation is to keep meetings pleasant and move forward. But transformation requires more than pleasant agreement. It requires clarity strong enough to survive strain. It also requires a method that lets people disagree without turning every decision into a personal contest.

A useful practice is to name the shared outcome before the hard question. “We both want the customer impact to be clean.” “We both need the operating team to succeed after go-live.” “We both want the investment to create value, not support debt.” Then ask the architecture question that protects that shared outcome.

Respect is not the absence of challenge. In transformation, respect often looks like telling the truth early, with enough structure that people can act on it.

Difficult relationships still need good governance. When enterprise architecture helps leaders ask hard questions without making the room harder, it turns strained trust into better decisions and gives the outcome a fairer chance to hold. before the hard question. “We both want the customer impact to be clean.” “We both need the operating team to succeed after go-live.” “We both want the investment to create value, not support debt.” Then ask the architecture question that protects that shared outcome.

Where is your provram avoiding the right question to preserve the relationship?

Which shared outcome could make a hard architecture conversation easier?

How do you challenge decisions without hardening the room?

Inspired by: Ephesians 6:7 (NIV) 7 Serve wholeheartedly, as if you were serving the Lord, not people,

Darin Paton is the Owner of Cornerstone Consulting Inc., an Alberta-based enterprise architecture and SAP ERP transformation advisory firm serving organizations across complex business and technology change for over 15 years.