Lighthouse mark for Influencing the Enterprise

Influencing the Enterprise

A Field Guide for Enterprise-, Domain- and Solution Architects

"The model can be flawless. The room still has to agree."

Even in the new era of AI, Enterprise-, Domain- and Solution Architects are expected to influence some of the most consequential decisions in an organization — while often owning neither the budget, the teams nor the final decision.

Influencing the Enterprise explores the part of architecture that frameworks rarely teach: people.

The lighthouse mark, in charcoal, teal and gold
Why a lighthouse?

The lighthouse represents a steady light on changing waters. It also holds its ground through every tide.

It stays lit from the same fixed point on the shore, through fog, storm and calm, so that whoever is out on the water can see the coastline, the rocks, and their own position a little more clearly.

That's what architecture can offer an organization: making risks visible before they're hit, giving people a fixed point of reference when everything else is moving, connecting others who are each looking at a different stretch of the horizon.

Influence, like light, can travel a long way without ever touching the ship.

The Field Guide

Fifty stories, told across four themes.

A one-year writing project, one story at a time — and more relevant now that AI can do more of the analysis for us. Here are the four threads running through it.

Latest Story · Organization

The Well Everyone Loved

Every village chief applauds the plan for one great well — until they learn which of their own wells will be closed.

Beyond the Field Guide

More ways to follow along.

Get each new story by email, follow along on Instagram, or wait for the podcast — coming soon.

The Field Guide

Fifty stories, told across four themes.

Here's the question I keep sitting with: when AI can increasingly do the analysis, the modelling, the documentation — the parts of the job that used to take an architect the longest — what's actually left that's uniquely ours?

My answer, and the working thesis behind this whole project, is the ability to influence how the enterprise makes decisions. Not the model. The decision.

Which means the psychology, the politics, the messy human research behind these stories was never really a side interest attached to architecture. I think it's becoming central to the job — more so now that the analysis itself is getting cheap.

So I'm treating the next twelve months as a one-year challenge: fifty stories, written and gathered along the way, each one looking at architecture from the ground most frameworks skip over — the human side of getting something built. Some I'll write myself. Others I hope to shape together with architects who've lived through the moments they describe.

They won't arrive in order. A story about a hallway conversation might sit right next to one about a boardroom standoff, and which number it happens to be will matter far less than which of four themes it belongs to:

Each story starts the same way: the fiction first, then two questions — what's really happening beneath it, and what an architect could do differently. No new framework here, and no universal answers. Just a year spent paying attention to something I think matters more now than it used to: the space between having the right insight and actually creating impact with it.

Self · How do I show up?

The King's Mapmaker

A story from a year-long field guide · Written by Ioana Bour

The King's Mapmaker

Illustration of the mapmaker Elias drawing a map at his desk, from The King's Mapmaker

Once upon a time, in a kingdom obsessed with expansion, there lived a mapmaker named Elias. Elias had mapped every river, mountain and marsh in the realm. His maps were so accurate that generals carried them into battle and merchants framed them in their offices.

One spring, the King announced that his army would march east to conquer a neighboring valley. Elias studied the route and went pale. Between the army and the valley lay the Black Marsh, a place where horses sank, wagons vanished and even mosquitoes were rumored to have military training.

Elias rushed to the General.

"You cannot take this route."

The General examined the map.

"Very impressive."

"So you'll change the route?"

"No. The King wants us there by Tuesday."

Elias returned the next morning with a larger map. He colored the marsh bright red and added skulls.

The General thanked him for improving the visualization.

The army marched.

Three days later, half the supply wagons were stuck in mud.

Elias was furious. He produced a forty-page document entitled Principles for Responsible Eastward Movement and scheduled a Cartography Review Board.

The General did not attend.

Finally, the court jester found Elias drawing an even more detailed swamp.

"My friend," said the jester, "your maps are magnificent. But have you considered that your problem may no longer be cartography?"

For the first time, Elias stopped drawing.

He went to find out why Tuesday mattered so much to the King.

What's really happening?

Notice what Elias does the moment nobody listens: he doesn't ask why, he just does more of what he's already good at — a bigger map, a brighter red, eventually a forty-page standard nobody asked for and a review board that meets without the General anywhere in the room. It's an easy trap, and most of us have fallen into some version of it. The architecture gets ignored, so we answer with more architecture. It feels like rigor at the time. Most of the time it's really just avoidance.

Here's the part of the job nobody puts in the posting: Enterprise, Domain and Solution Architects are routinely asked to shape decisions they don't own — not the budget, not the delivery team, often not even the applications the decision is actually about. Elias assumes a better map will change the General's mind, because that's what's always worked before. But the General was never arguing about the marsh. He was standing inside a decision Elias couldn't see the shape of — a King, a deadline, maybe a promise made to someone else entirely.

Why Tuesday?

Maybe the King made a promise he can't walk back. Maybe supplies run out on Wednesday. Maybe there's a rival army closer than anyone's said out loud. Elias doesn't know yet — and that's the point. Before you can influence a decision, you have to understand the system making it, not just the merits of your own recommendation.

There's a useful distinction here from social psychology: some power is positional, the kind that comes with a title and lets you reward, punish or simply instruct. Some is personal — your expertise, the information you hold, the trust you've built over time. Most architects start the job with almost none of the first kind. Elias keeps acting as if he has it anyway, expecting the map itself to compel action the way an order would. What he actually has, and barely uses, is real information the General doesn't.

What could an architect do differently?

Stop acting like you have authority you don't have, and start building the kind of influence you actually can earn. That doesn't mean the architecture stops mattering — the map still has to be right. It means accuracy alone was never going to carry the day. What moves a decision is understanding who's making it, what they're actually optimizing for, and what constraint they're under that you simply can't see from your seat.

Elias's real mistake wasn't the marsh. It was spending three rounds improving a document when one honest conversation would have gotten him further.

A place to start: pick one recommendation of yours that's stuck. Before you touch the diagram again, find whoever's closest to the decision and ask them straight: "What would need to be true for you to be comfortable with this?" Then actually listen to the answer — there's usually a constraint in there you didn't know about.

Reflection

Think of an architectural decision you are currently struggling to influence.

Am I still drawing a better map? Or do I understand why Tuesday matters?

Organization · How do decisions really happen?

The Bridge That Was Almost Built on Time

A story from a year-long field guide · Written by Ioana Bour

The Bridge That Was Almost Built on Time

Illustration of the architect Apolodor presenting a bridge model to the King and his Lords, from The Bridge That Was Almost Built on Time

Once upon a time, a king ordered a construction of a new bridge towards a territory newly conquered. Since it was not an easy conquest, it was important that the best of the bridge builders had to be chosen and the bridge – to be a first of its kind. For such a bridge just any builder would not do. So the King's men travelled across seven seas and seven realms and found Apolodor, the most celebrated bridge architect there was.

The job was not easy. The bridge had to be majestic, bordered by two even more majestic gates upon which two marble statues of the King had to be placed. Apolodor made several plans and presented them in the King's council. The King was easy to convince – he easily picked the most majestic design.

The other Lords had several questions: the Lord of the Roads wanted to know how many horses and carriages the bridge could carry, the Lord of Troops asked how many soldiers can march over the bridge in safety, the Lord of Fish wanted to make sure that fishermen's boats would not be obstructed while the bridge was being built, the Lord of Subjects' Safety enquired about rails, wind, separate lanes and what would happen if a distressed horse would start running erratically up and down the bridge. All other Lords present (24 of them!) asked their questions. Apolodor wrote down every question, comment and promise. Then he returned to his team with many notes and a beginning of a headache.

But he also saw one empty chair at the Council and went to ask the Chancellor who is usually seated there.

"The Lord of Naval Forces"

"Oh, then I must speak to him! How do I find him?" enquired Apolodor.

"Don't worry", said the Chancellor waving a hand, "he's off salvaging what can still be salvaged after the war. We haven't seen him in a year"

"But the bridge does cross a river…"

"I wouldn't worry; he cannot be bothered with celebratory projects. I wouldn't stop any work for this, he is likely not to have any second to spare."

"Understood", replied Apolodor, thinking to himself "I anyway have enough work now and besides, 24 Lords are quite enough". Off he went turning the plans into almost reality.

Six months later all requirements were happily reconciled in the final design and – as customs required – he went again to the King's council to present a most detailed 1:1000 model of the bridge.

"Magnificent", said the King.

"Extraordinary", whispered one Lord.

"Spectacular", shouted another.

"Absolutely superb", added three others. Many did not say a word, for there was no word to describe the glory of what they were seeing.

"This cannot be built."

Silence. Apolodor turned trying to see who spoke.

It was the 25th Lord. The Lord of Naval Forces. He got up from his 25th chair and went to point at the model:

"The King's latest generation of warships will not be able to pass under this bridge. They are taller and wider than the old fleet. This bridge you are building is a wall to them and they will be trapped never to conquer other territories again."

The King was not smiling anymore.

Apolodor could not believe his ears. He enquired about the length and height of the new ships and went to measure the model. The Lord was right. After all this work. Everything (except the King's statues) had to be reconsidered – the positioning of the bridge, the exact location, the type of pillars and the width between them, the height of the bridge.

Apolodor packed away his model and returned to the drawing desk, no other time to spare now!

What's really happening?

Apolodor did many things right. He identified his stakeholders, he understood the non-negotiables (among which, the King's statues...), he treated everybody with respect and managed to accommodate their wishes with an exemplary design.

He also noticed that one of the Lords was missing and guessed it could be an important stakeholder, after all the bridge did go over a river. But he had to listen to the Chancellor. The bridge was definitely a Prio 1 on the Portfolio of celebratory projects and Lord 25 did not have time for celebratory projects.

One can judge that this is down to luck – it could have also been a Lord that truly did not care. And one can be right.

But what Apolodor did wrong is that he mistook interest for power or influence. Just because a stakeholder is not interested does not mean that they will automatically approve a design.

This is where it is important to get accustomed with the power-influence matrix used in mapping stakeholders.

  • High power & high interest = manage these stakeholders closely
  • High power & low interest = keep these stakeholders satisfied with information
  • Low power & high interest = keep these stakeholders informed
  • Low power & low interest = monitor to see if power or interest changes
Stakeholder matrix diagram showing four quadrants: manage closely, keep satisfied, keep informed, and monitor, illustrated with the King, Lords, and the Lord of Naval Forces from The Bridge That Was Almost Built on Time
Who is your 25th Lord?

This story was about a stakeholder with high power and low interest. He was not interested in the bridge, he was interested in whether the new naval fleet could pass underneath it. And once he realised it wouldn't, his interest also increased.

As important as it is to map these positions, it is equally vital to realise that they are not fixed:

  • someone not interested today may become very interested tomorrow, especially if the design affects their budget, their risk, people, autonomy
  • power is also less obvious than only an organisational chart; stakeholders can influence decisions also through expertise, relationships, control over resources

What could an architect do differently?

Drafting a stakeholder matrix is a good starting point. It is a nice step to be done with the entire design team – together you can uncover more nuances about your stakeholder field.

In my experience it is good to pay particular attention to two quadrants:

  • High power & low interest – these are precisely the stakeholders that will not volunteer their time to help you with your cause, but who have the power to block your deliverable if it goes against their own vision. It is important to keep informing them and check their thoughts. Ask open questions, wait for answers
  • Low power & high interest – these stakeholders will make time for your project or artefact. They are definitely interested in the topic – many times for their own learning or to apply their expertise – and add clear value in brainstorming sessions. The risk is to spend too much time with them to the detriment of the stakeholders with more power.

There is also a useful check to do just before approval: revisit your stakeholder map. Did anything change? Did you miss any high-power stakeholder? The organisation you have mapped in the beginning may no longer be the organisation standing behind the decision today.

Reflection

Think about an upcoming approval for a part of your recent work.

Who is sitting in the 25th chair? Who is sitting in the other 24?

People · How do I work with people who see the world differently?

The Druid's Daughter

A story from a year-long field guide · Written by Ioana Bour

The Druid's Daughter

Illustration of Masteria looking toward her village, from The Druid's Daughter

The year is 50 BC. Word has spread of a small Gaulish village, but not yet of another Gallo-Roman one, where the old druid Herbamatix now feels ready to pass his mistletoe knife to his daughter, Masteria.

Since childhood Masteria was a curious child, always interested in puzzles and always ready to lend a helping hand. Going together to see villagers in need, she would listen to her father's line of questioning and then try to diagnose herself.

"What do you think yourself, Masteria?"

The question always came. Masteria was delighted her father was asking her and her father was delighted to hear her answer. Many times her creativity brought breakthroughs and faster recovery times and Herbamatix himself was thrilled - so much talent in his own daughter.

It was now announced that Masteria is to be called for all matters and that she is equipped with all knowledge Herbamatix himself had. Villagers trusted her fully.

Five years passed and Masteria was putting all her effort into her job. She bought a Roman cart so that she could reach the villagers and the forest faster, she arranged her herbs in alphabetical order and standardised her remedies. She even started carrying clay tablets to scribble what needed to be done so that her advice could be followed to the (Latin) letter. Her pride was growing and so was her efficiency. In five years she had already surpassed her father in number of home visits per year and she also started working on a compendium of common ailments and home treatments - in the hope that people can help themselves too.

Masteria was delighted. Herbamatix less so.

"So how much time do you spend per patient now?"

"Much less!" said Masteria proudly

"Efficient", said Herbamatix with a nod to himself that doesn't usually belong with a congratulation.

The truth is that after five years Masteria has seen everything. Sometimes she could look through the doorway and already know what needed to be prescribed. She became more direct and she confidently told them what needed to be done. Soon there was no point anymore in asking questions. So she stopped asking them. Some villagers followed her advice to the letter, some didn't. And within this second category there was even a worse group, those who repeatedly made the same mistakes.

"No surprise you got a stomach upset after putting mud in your mouth! This is the third time; didn't we discuss this before?? Mud. Does. Not. Heal. Cavities!!!"

Soon villagers grew partly ashamed, partly afraid, partly offended and slowly-but-surely learned to do without Masteria's help. By the time Masteria was called, problems that were once simple became very complicated to treat.

One winter a contagious outbreak stemming from the Roman garrison could not be contained after the first family infected turned to relatives for help instead of calling Masteria. At some point, the entire village was sick. And what is worse, Masteria knew this could all have been avoided.

Feeling defeated, she went to see her father.

"Father, I have a problem."

"What happened, Masteria?" asked Herbamatix from the middle of his garden.

"People avoid me on purpose!"

Herbamatix waited.

"They call me only when everything else fails. They know I can help them. Why do they deliberately avoid the only person that can truly help them?"

"That is a good question. What do you think yourself, Masteria?"

How well she knew this question. She sighed.

"I suppose I was not very patient with them…"

Herbamatix did not say anything.

"But it is so difficult, I just want them to get better fast!"

"Must be very frustrating. What do you think they want themselves?"

Masteria's jaw opened. Then closed.

"Probably the same…"

"Interesting…" Herbamatix picked up his mistletoe knife again and turned back to his gardening.

"That's it? I came here for advice!"

Herbamatix smiled. Masteria stared at him, then started to laugh.

"I see what you are doing…"

Herbamatix continued his pruning. Masteria came and sat next to him.

"If I want people to understand, maybe I should give them a chance to understand my line of thought…

And perhaps I should ask them what they have already tried…

And maybe I should see them before something actually goes wrong…"

Herbamatix finally looked up at her:

"They all sound like great ideas."

Masteria smiled.

"Heh, it seems I came up with them all by myself."

"Must be the excellent education", smiled Herbamatix.

The next morning a farmer came to Masteria for help. She saw his swollen arm, she knew which herbs would work, she was ready to go get them, but she stopped. She grabbed two chairs.

"Tell me, what happened?"

What's really happening?

Masteria has become very good at her job. This is admirable in itself given that she had big shoes to fill. She became very efficient at it and was able to get to the core of the issue and treat more patients faster. The problem is that efficiency often has the awful side-effect of replacing curiosity.

Of course, her diagnoses are not wrong. In fact, she is right most of the time. The problem is what happens to the relationship when the expert already knows the answer before the stakeholder had the chance to explain it. The paradox is perhaps recognisable: the more certain someone becomes, the less likely they are to be involved if their confidence is read as inflexibility or as arrogance. Her expertise, though not less valuable, has become much more difficult to access.

From Masteria's perspective, she is saving people time (and people!). From the villagers' perspective, calling Masteria increasingly means that they are to be scolded. So they adapt, they go to other 'experts', much less suited to solve their problems. Sometimes these experts even come from outside the village itself! Sounds familiar?

Have you grabbed two chairs?

For an architect, grabbing two chairs can be surprisingly literal. Sitting next to someone before looking together at the diagram, asking what they have already tried, what worries them and what they are trying to achieve – before jumping to the solution. You may still end up recommending what you had in mind five minutes prior. But now they are ready to listen. And you are ready to change your recommendation to better fit their situation.

What could an architect do differently?

Expertise is partly about pattern recognition. What my team and I call 'connecting the dots'. An experienced architect will see things faster than someone encountering them for the first time. Of course, you should not pretend to know and turn all discussions into hour-long brainstorm sessions. But making sure you are attuned to the other is a must for a productive conversation.

In coaching 101, a first framework we learn to get a bit of confidence while asking open questions is GROW: Goal – Reality – Options – Way forward. It sounds like this:

  • Goal — What do you hope to accomplish? What does success look like?
  • Reality — What's actually happening? What have you already tried?
  • Options — What haven't you considered yet?
  • Way forward — What will you do differently, starting now?

You've already seen it in action. Herbamatix never tells Masteria what her problem is or what to do about it. "What happened, Masteria?" is Reality. "What do you think yourself?" and "What do you think they want themselves?" are Options, dressed up as simple curiosity. And the two chairs she grabs the next morning — nobody suggested those to her. That's her own Way forward, which is exactly why it sticks.

GROW framework diagram — Goal, Reality, Options, Way forward — illustrated with Masteria and Herbamatix at the table, from The Druid's Daughter

Last but not least, when an architect is brought in too late, it is worth asking if we are looking at more than only a governance or mandate question. Can it be that stakeholders actually don't feel like involving Architecture? Like Masteria, we should eventually ask ourselves, "What is it like to ask us for help?"

Reflection

Think of your last meeting with one of your stakeholders.

Have you created the space for the other person to tell you what is happening? How about what is really happening?

Impact · How does architecture create change and impact?

The Castle on the Border

A story from a year-long field guide · Written by Ioana Bour

The Castle on the Border

Illustration of the architect Reginald studying his castle design while the King's ministers look on, from The Castle on the Border

Once upon a time a king ordered the construction of a new castle at their kingdom's newest border. The castle had to be strong enough to deter invaders, majestic enough to impress anyone approaching the kingdom, comfortable enough for the king and the queen to spend their summers there. The view over the sea was too beautiful to only waste on soldiers. Architects from across the kingdom and beyond were invited to submit their designs. Eventually one emerged as it truly was the most majestic and beautiful of them all. The winning design belonged to Reginald, an architect whose castles on paper looked almost as impressive as they eventually did on stone.

It was now time for our architect to come to the king's ministries and bring his design closer to reality. All ministers and Reginald met during the Crown's Council, where given its importance, the castle was the only agenda point of the day.

It was first the ministers' turn to ask their questions:

"Can it be built in time for the king's birthday next year?"

"Yes."

"Can the necessary marble and timber be sourced?"

"Yes."

"Will it accommodate for its double purpose, military defense and leisure?"

"Yes."

"Without compromising on each requirement?"

"Yes."

"Was it high enough to overlook the sea?"

"Yes."

The queen leaned forward:

"From the royal bedroom?"

Reginald is looking at the drawing:

"Yes, your Majesty"

Everyone was pleased.

Reginald closed the drawings.

"I have a few questions, too. Most important one, when do we start?"

Silence.

"I mean, has the Ministry of Roads planned the road required to transport the stone? And to build the permanent road afterwards?"

The Minister of Roads became unusually interested in his papers.

"Are the materials and workers ready to be given to me for supervision?"

The Minister of Built Environment honestly did not have the answer with him.

"How about after the construction is done, are we taking measures already to make the castle part of the Ministry's catalogue to plan for regular inspections and potential repairs?"

More silence.

"Which garrison will provide the soldiers?"

The Minister of War looked at the Minister of Something Else.

"We have not decided yet"

Reginald had now more questions than answers. He looked around the table, then again at his drawings. The castle was there. Majestic as he drew it. But the road was not. And there was also no construction camp and no indication of how the castle is to be run once ready. And yet without these, there would be no castle.

What's really happening?

The first round of questions is about whether the design satisfies the desired outcome. The second round of questions is whether the design actually works.

Reginald gradually discovers that nobody else in the Council has considered the changes around making the design work, both during construction and operation time. In architecture terms, both can be true: the target-architecture is literally beautiful and the organisation needed to implement it is nowhere near ready. A target state can be perfectly designed while the path towards it remains completely undesigned. Reginald noticed this, he himself had thought of all the questions, but not even a road was drawn on his design. The castle is the target architecture, the missing road is what has to become true for the target state to become real: the impact of change and its dependencies, the enabling conditions and the transition architectures.

Did you draw the road?

If not, how will stakeholders realise a road is actually needed for executing the vision?

What could an architect do differently?

Architecture should not stop at describing the desired future state. The lesson here is to not only architect the destination, but to also make the journey visible to all relevant stakeholders.

  • What does my design mean for the business?
  • What does it mean for the CIO?
  • What dependencies do I see?
  • Who needs to do what to accommodate for the new design?
  • (and more importantly) Have I made these dependencies visible, or are they only in my head?

Reginald obviously thought of all the questions while creating the design, but he did not make the impact or the change needed to get there part of the story.

It is important to also mention here that an architect does not need to personally recruit the workers and the soldiers or prepare for maintenance, he or she is not a program manager either. However, architecture must make visible that these elements are required in the first place. Coming back to Reginald, as building the castle was dependent on having a road ready, the road itself belonged in the conversation.

Reflection

Think of your last design or architecture.

Did you make the impact on the (delivering) organisational units visible? Did you draw the road?

Self · How do I show up?

The Owl Who Was Always Right

A story from a year-long field guide · Written by Ioana Bour

The Owl Who Was Always Right

Illustration of Owl flying toward the council of animals gathered on a sandbank, from The Owl Who Was Always Right

Once upon a time, in a faraway forest all animals lived in complete harmony. Whenever something of importance had to be done or had to be built, the king of animals summoned his council: the Beaver (who knew everything there is to know about dams), the Fox (who knew everything there is to know about markets and commerce), the Bear (who knew everything about defence), the Deer (who knew every path, stream or meadow in the forest), the Rabbit (representing villages of rodents) and the Owl (who knew everything the others also knew).

Owl was not only the longest-serving in the council, but he possessed the talent of understanding what humans did and translating that to useful did-you-knows for the animal kingdom. For example, Owl knew how deep foundations for burrows needed to be laid in sandy soil, how much weight an oak tree could carry, he knew the average rainfall per month and he also knew how busy the forest would get in the different seasons. But most importantly, Owl also knew when someone was wrong.

One morning, the King called his council. A new bridge had to be built.

Beaver unrolled a drawing:

"Good thinking, your Majesty. I was waiting for this. The best place is this exact point. Here the river is narrow enough".

"Actually", said Owl, "the banks are clay in that area. The bridge will not hold".

"And it is far from civilisation!" weighed in Fox. "Let's add it next to the market".

"That road you're pointing at is not the main road to the market" answered Owl. "It would not help at all".

Deer suggested another location.

"Protected orchids", said Owl.

Bear wanted towers for soldiers.

"Not needed. We are in the middle of the forest here" was Owl's answer.

"Not even for making it look good?"

"That is inefficient."

By lunch time Owl won every argument, and the King thanked him for his wise contributions.

"What would I do without you", he said.

But the location of the bridge was nowhere near being chosen.

Over the following weeks, the Beaver brought new drawings, the Fox came with new ideas, the Rabbit even conducted a survey to see what the villagers would prefer. All in vain, the Owl shut down all ideas.

At one point, the Owl was seen marching triumphantly towards the Council meadow carrying seventeen tree barks filled with calculations. The entire meadow was empty.

"This is strange" thought Owl. "Everybody should be here, how are we going to build the bridge otherwise?"

After some time, he decided to fly and find the others. Eventually he heard voices coming from the sand bank in the middle of the river. Here they were.

Beaver was showing the others a drawing of his. Fox was nodding. Deer was calculating something in the sand. Bear was pointing something on the horizon to the Rabbit. The Owl landed among them.

"What are you doing here?" asked Owl.

Eventually the Rabbit muttered:

"Brainstorming…"

"Without ME?! But I know all the answers!"

"That is true…" said Fox. "And that is precisely the problem."

"What do you mean??"

"Unfortunately you also think for the rest of us…" dared Deer.

Then everybody was silent. Owl picked at the drawings. He saw three mistakes. Then four. But this time he did not dare to say anything.

For the first time, Owl understood something. They did not invite him because he knew too little, they stopped inviting him because when he was present, everybody seemed to know less.

"What if… you explain your plans to me? I will not interrupt."

The animals started talking, argued for a while after discovering the flaws Owl also saw but had not communicated. They came up with new ideas. Owl did not say anything. He found it incredibly difficult.

Finally Beaver looked at him:

"Well, Owl, will it work?"

"I don't know yet. Let's work it out together"

What's really happening?

Owl has fallen into a trap that is particularly tempting for experts: he has confused being right with being useful.

Every correction he has made was… correct. But something else is happening at the same time. When such an expert is in the room, people become either shy to propose their ideas or disengaged – after all, he knows it all. When questions disappear, conversations stall and relationships between stakeholders become colder and colder.

Influence rarely disappears with an announcement. Nobody tells Owl that it has become too difficult to deal with him. He is simply not invited anymore to some of the meetings. His expertise has not become less valuable, but has become harder to use.

Has your conversation moved?

Owl would have thought that the Council has become more efficient: fewer questions, fewer debates, fewer objections. Or that building the bridge is suddenly not a priority anymore. What he did not realise is that the conversation has moved elsewhere.

Architects rarely get a notification when this happens. So pay attention to the silence. Are people still bringing you new ideas to test? All your stakeholders, or only the select group of architects that already admire your expertise?

If you start to recognise the silence, the question is not always "How to position myself at the right table, I have the mandate!", but "What needs to change for my stakeholders to want to brainstorm with me again?"

What could an architect do differently?

Architects are often invited into conversations because they know things others don't. They are passionate about the 'content': about the product, the value proposition, about how things are done and integrated and they also know the history of it all sometimes better than the leading stakeholders.

The temptation is to demonstrate that knowledge. But there is no prize. Especially if it's done like the Owl does.

Of course you should not withhold expertise, only change the way you introduce it.

  • Instead of: "That won't work because X.", ask "How are you thinking about X?" or
  • "There's one constraint I think we need to bring into this. Can we test the idea against it?" or
  • "I see a problem, but before I jump in, take me through how you're thinking about this."

Instead of only asking "How quickly can I spot what is wrong with the proposal?" or "How quickly can I find the solution?", try asking "How can what I know help this group think better?". That means in practice welcoming ideas, letting someone explore something you already assume won't work, asking open questions, correcting assumptions without shutting people down.

Sometimes, the time 'at the table' is the architect's most valuable contribution. It is not about giving back a bullet-proof solution, but about making the table smaller, so everyone at it is a little closer to the middle of the conversation.

Reflection

Think about your last few architecture conversations. Who still brings you ideas before they are fully formed?

When someone proposes something flawed, what is your first instinct? Do you seek to understand their thinking or to show them what they've missed? And if some stakeholders have become unusually quiet: have they stopped thinking about the problem, or has the conversation simply moved somewhere else?

Self · How do I show up?

The Keeper of Imperial Maps

A story from a year-long field guide · Written by Ioana Bour

The Keeper of Imperial Maps

Illustration of Cassian studying the imperial map while the young Emperor Hadrian gestures beside him, from The Keeper of Imperial Maps

The year is 107 AD. We are in Rome, with Emperor Trajan victoriously returning from conquering rich Dacia. Two long wars are finally over and Rome becomes greater, richer and more admired than ever. But now the real work starts. And we are not talking only about Trajan's Column representing the great battles, but about fully connecting the Empire with the new territories. Roads had to be extended, fortifications strengthened, aqueducts, markets, ports, public buildings had to be erected.

And somewhere among all those plans sat Cassian, the most trusted Chief Planner, the Keeper of the Imperial Maps. He was entrusted with the Imperial Plan and led a literal army of engineers, surveyors and builders. When a governor wanted a new Via, Cassian considered whether it made sense and where it was to be connected. When two provinces requested competing investments in water, trade or defence, Cassian was the first to notice. His maps covered everything in the Roman Empire from West to East, from North to South. Emperor Trajan valued him greatly.

Whenever Trajan had an idea, he would summon Cassian:

"What do you think?"

Cassian would study his maps, ask questions and sometimes disagree. Trajan would usually push back:

"But how could it be done?"

Over the years, Cassian became very good at understanding his emperor. He knew Trajan believed that Rome's strength depended on connecting its growing territories fast, he knew which roads the emperor considered strategically important and which provinces he wanted developed. Soon, Cassian could anticipate Trajan's questions before he asked them. And he worked hard to make sure fewer questions were asked over time. When two alternatives were possible, Cassian knew which one Trajan would prefer.

Trajan was delighted. One afternoon, when a senator asked Trajan whether he would discuss the possibility of a new colosseum in his province, Trajan said

"Ask Cassian, he can answer better than I do, sometimes I think he can replace me while I sleep!"

The room laughed. Cassian could not have imagined a greater compliment.

10 years later there is a new emperor. Hadrian calls for Cassian, the continuous and knowledgeable Keeper of the Imperial Maps.

Cassian arrives carrying all the plans he has spent years preparing: future roads, future military infrastructure, future eastern initiatives – the logical continuation of everything Rome has been, is and, in Cassian's mind, is meant to become.

Cassian begins confidently while opening his maps:

"Emperor Trajan's plan was…"

Hadrian raises his hand to stop him.

"I know Trajan's plan. I want to know what you think."

Cassian is not sure he understands:

"My Emperor?"

"You have spent twenty years studying this Empire. You know all the roads, cities, borders and dependencies better than anyone. You know why choices were made in the past."

Hadrian points at the maps:

"So tell me: what did we get wrong? What does Rome need now?"

Cassian looks down at the Imperial Maps. For years he had become better at predicting questions and reading his emperor's mind. And yet he cannot do it now.

What's really happening?

Cassian has not suddenly become incompetent, quite the opposite: over twenty years he has developed an extraordinary understanding of his emperor's strategy. Eventually he becomes so good at translating strategic intent that Trajan does not need to explain anymore. That sounds like success, but is it? Cassian has fallen into a trap that is particularly tempting for experts: he has confused serving his most senior stakeholder with serving the thing that stakeholder is meant to serve.

Cassian initially challenges Trajan, then he understands his emperor, he learns to anticipate him – first the questions, then the answers – then he becomes his voice. That means he has moved from understanding strategy to anticipating strategy to internalising strategy. His behaviour is rewarded at every step. It is what makes him effective towards the emperor. But his reason for existing is Rome as a whole. Sometimes even the most experienced architects may fall into the same trap.

The closer we work with senior leadership, the better we become at understanding what they want to achieve. The organisational awareness is valuable, because it separates investments that are likely to receive support from the rest. But taken too far, it can turn architecture into an increasingly sophisticated implementation of assumptions that nobody is challenging anymore.

So the danger is not that Cassian understands Trajan too well, or that he will need time to understand Hadrian. The danger unfortunately is that Cassian stopped asking the difficult questions – not only towards the emperor, but to himself.

Whose maps are you carrying?

Cassian arrives to Hadrian carrying the Imperial Maps. Metaphorically however, he forgot he was also carrying twenty years of Trajan's thinking. He missed that 'Imperial' meant 'Empire,' not 'Emperor.'

So whose maps are you carrying? And if your most senior stakeholder were promoted elsewhere, which parts would you still defend in front of their successor?

What could an architect do differently?

Proximity to stakeholders is something all architects strive for. The problem is losing the distance necessary to remain independent and useful to the enterprise or the domain. Understanding the strategy is more than becoming the echo of the most senior stakeholder.

A useful discipline is to separate three questions that can easily be tangled together:

  • What has leadership decided? This is the strategic direction that architecture needs to enable
  • What assumptions does the architecture direction depend on? These are the topics architecture should continue to test as circumstances change.
  • What do I see, from my enterprise-wide (or domain-wide) perspective, that leadership may not see? This is where architectural judgement adds value.

Of course, and very importantly, this does not mean that the sole purpose of architecture is to challenge direction to demonstrate independence. Cassian does not need (and should not) argue with Trajan every morning. But he does need to preserve the distance to observe when yesterday's assumptions do not fit today's situation.

Reflection

Think about one important architecture you are currently shaping.

If your most important stakeholder left tomorrow, how much of your architecture would you still defend?

Impact · How does architecture create change and impact?

The Owl and the Alarm

A story from a year-long field guide · Written by Ioana Bour

The Owl and the Alarm

Illustration of Owl presenting a leaf reading 'If you see a wolf, sound the alarm immediately' to the forest council beside a tower of reports, from The Owl and the Alarm

Once upon a time in a faraway forest all herbivores came together to see how they could better protect themselves against predators. Soon they realised wolves were not the only dangers. Squirrels brought up falling trees, beavers made a point about the river overflowing, birds were afraid of storms.

"Leave it to me," said Owl. "I will document all possible dangers and ways to keep safe".

She then went and interviewed all involved animals and kept notes on everything that was worth mentioning in her book. Whenever an animal raised a concern, she added another section. When she was finally satisfied with what she produced, she presented her work to the forest council.

"Everything we need is in here."

"It certainly looks like everything," said Badger who tried to lift the notes from the floor but lacked sufficient strength.

It was so detailed that they asked a parrot to prepare summaries. But the entire text was so long that Parrot thought it was better to summarize it keeping the animals' strengths in mind:

Rabbit was very fast and could alert everyone, so to him Parrot summarized as "At the first sign of danger, raise the alarm".

Badger asked how they would know if it's a real danger. To him Parrot summarized: "Confirm the danger before raising the alarm".

Fish pointed out that heavy rain was hardly an emergency for fish, so to him Parrot summarized: "Each part of the woodland should respond according to its circumstances".

Everyone was satisfied, so the council approved the report.

The next morning, a branch fell beside Rabbit. As directed, Rabbit sounded the alarm and raced around the forest to alert everybody. Within minutes, the entire woodland was fleeing towards the river.

"All this for a branch?" demanded Badger.

"I followed the plan," said Rabbit.

Two nights later, Badger spotted wolves near the clearing. But this time he would do things properly. He tried to look for Owl to confirm the danger, but Owl was out hunting. He tried to find Parrot, but Parrot was fast asleep at the top of a tree. The alarm was still not sounded when wolves were already approaching the burrows. The rabbits escaped only because one of the wolves sneezed.

At the next council, Rabbit and Badger expressed worries that Owl's report was not fit for purpose.

"But who made these summaries?" asked Owl. "If you had read everything, you would have understood how rules were to be applied..."

"But who has time to read everything?" shouted the animals. "Also, sometimes you say the alarm has to be sounded immediately, sometimes to wait for confirmation. Very confusing!"

Owl opened her report.

"Those passages need to be understood in context."

"Then why wasn't the context in our summaries?" asked Rabbit.

"There was too much of it," said Parrot.

Owl reached for her quill.

"Perhaps I can add a section on..."

"Please don't," said Hedgehog. "There has to be another way."

Owl looked around the council.

"We need to decide which is worse when someone sees wolves: a false alarm, or a late one."

"A false alarm ruins my breakfast," said Badger.

"A late one makes us breakfast," said Rabbit.

Then Owl wrote on a single leaf:

"If you see a wolf, sound the alarm immediately. Everyone takes shelter. Do not wait for confirmation".

"Agree! That's it! That's your entire report!" Parrot squeaked.

Underneath, Owl added:

"Wolves can reach the burrows before a warning can be checked. We accept an occasional false alarm because waiting could cost lives. A falling branch alone does not trigger a woodland evacuation".

Owl's great report was kept safely in the council's archive. Nobody threw it away; in fact they kept coming back to it in many of the following years. But from then on, whenever the council had an important choice to make, Owl reached for a leaf rather than add a new chapter.

What's really happening?

Owl's report was very thorough; it covered every concern and gave every animal something to agree with. But perhaps the most important question was: when speed and certainty conflict, which takes priority?

The same can happen with a future-state architecture. A lengthy presentation can describe efficiency, resilience or standardisation so convincingly that everyone approves it - while keeping different target states in mind. The disagreement appears only later, when teams have to agree on what is to be built.

The approval of a document does not necessarily mean agreement on future decisions.

The purpose of a summary is that it must leave things out. Next to this, when reasoning is scattered across dozens of slides, the reader has to reconstruct the decisions. One person may remember the recommendation, another the exception that applies to them, another a principle they themselves also came up with.

"Raise the alarm immediately" sounds reckless until you know how quickly wolves can reach the burrows of the rabbits. "Wait for confirmation" sounds sensible until you understand what the delay can mean when the danger is wolves. In architecture decisions, context is what turns a decision from an instruction into something people can apply intelligently. It explains why a choice makes sense, under which circumstances — and keeps the architects sharp to recognise when the circumstances have changed.

What is on your leaf?

Meaning: after all your analysis, slides, principles and diagrams, what is the actual choice stakeholders need to remember?

What could an architect do differently?

This story is not an argument for replacing Future State Architectures with decision records. They serve different purposes: artefacts preserve knowledge, decisions create direction. We will still need the broader picture, but when a decision was made stakeholders should not have to reconstruct it from that broader picture. How? Four points here:

  1. Find the choice. For every document you are creating, or any decision you are recording, always ask yourself what is the choice we have here as an organisation? Make the choice explicit. A statement like "Improve resilience and efficiency" is something that is always right. But deciding which takes priority in a particular situation gives teams direction.
  2. Keep the decision and its reasoning together. What is the relevant context, what were the options considered, what was the choice made, and why was it chosen in that moment. Include the consequences and disadvantages being accepted. A good test is that someone who missed the meeting should still be able to understand the decision, both the What and Why it was made.
  3. Test agreement through consequences. It is always insightful to check: "What will you do differently because of this decision?" Rabbit and Badger would have discovered their conflicting interpretations before the first alarm.
  4. Circle back to the decision. At the moment a decision is recorded, add the intended result and when the decision should be reviewed. At that later point, reflect together: did it help teams act consistently? Did the expected benefit materialise? Have the circumstances changed?
Four steps illustrated with Owl and the council: find the choice, keep the decision and its reasoning together, test agreement through consequences, circle back to the decision, from The Owl and the Alarm

As AI increases the speed at which architecture can be produced and changed, maintaining lengthy architecture documents may become less sustainable. The answer cannot be to produce documentation faster. As the animals shouted, "who has time to read everything?" We need to become better at recording the decisions that matter, the reasoning behind them and the outcomes they are meant to achieve. The value of architecture becomes visible in the choices people make and what those choices achieve.

Reflection

Think of your most recently approved architecture document.

If three teams summarised it independently, would they identify the same decisions and understand why they were taken? And most importantly: would they know what to do differently because of those decisions?

Self · How do I show up?

Sir Reginald and His Horse Riding Lessons

A story from a year-long field guide · Written by Ioana Bour

Sir Reginald and His Horse Riding Lessons

Sir Reginald calling out corrections while Eleanor rides, and Princess Beatrice pointing towards the gate

Once upon a time at a Royal Academy of Horse Riding, there was an instructor named Sir Reginald. For many years, Reginald had been one of the finest riders. He was so precise in his riding that it was almost like magic to see him on the horse. So naturally when he retired from active duty and became an instructor, knights travelled from across the kingdom to learn from him. His waiting list became very long very fast.

One spring morning, a young knight called Eleanor arrived for her first riding lesson. There was one problem though. In those days, ladies have only recently been allowed to enrol and train to become knights and Eleanor was the first of her generation. The implication was that she had to learn how to ride for the first time.

Reginald was delighted. A firm believer in equal opportunities himself, he always secretly thought that women might be even more suitable for riding than men – given their naturally more petite stature – and he was determined to give his best in teaching Eleanor.

"Okay, let's begin. Climb on," demanded Reginald.

Eleanor carefully mounted the horse. As the horse began to take his steps, she instinctively leaned forward.

"Don't lean forward!" called Reginald, who was determined to correct every mistake as it happened so that Eleanor would learn first-hand how riding should be conducted.

"Not so far!" he said again as Eleanor tried to lean backwards. "And don't pull the reins!"

"Don't let the horse go that way!"

"Don't keep looking at the ground!"

"Don't grip with your knees!"

"Don't bounce the saddle..."

"Don't panic!!"

By now Eleanor did nothing but panic... An hour that seemed like an eternity later, Eleanor dismounted, both exhausted and embarrassed.

"That did not go well," said Reginald, who was now contemplating whether he needed to teach women differently than men.

"No..." agreed Eleanor. "If I may, sir..."

"Yes?"

"You have told me what not to do, but I am not sure what I should do..."

"Let's do better next time."

"Yes, sir."

When the next time came, Princess Beatrice happened to visit the Academy and see the lesson. Princess Beatrice was the King's first daughter and as such, she was allowed to learn riding from an early age. She loved horses and was an accomplished rider herself.

The lesson was progressing much as before:

"Don't rush the horse!"

"Don't loosen the reins!"

"Don't slouch!" etc.

Beatrice watched Eleanor grow increasingly tense. She approached both instructor and apprentice.

"Sir Reginald, may I try something?"

"Your Royal Highness! Of course!"

"Eleanor, first of all, sit tall as if a string is gently pulling the top of your head toward the sky."

Eleanor straightened.

"Now, keep your hands steady, but soft."

The horse relaxed visibly.

"Now look towards that wooden gate at the far end of the field. That's where you are going."

Eleanor looked ahead and like magic the horse began moving in the same direction and crossed the training ground.

"Excellent!" shouted Beatrice. "Now do exactly the same things as you come back to us."

Eleanor finished her riding lesson with much more hope for the future. As she bid her farewell, Sir Reginald approached the princess.

"Your Royal Highness, I would like to first extend my gratitude."

"Of course," smiled the princess.

"And may I just ask, what is this technique you are using for teaching women riders?"

Beatrice burst into laughter.

"Women?? Reginald, this has nothing to do with it. Your apprentice is just a first time learner. You are used to teaching experienced riders who already know how to ride, and even how to ride well. But what can she improve if she doesn't yet know anything?"

Reginald listened further, with both great interest and slight embarrassment.

"Reginald, you kept telling her what not to do," continued the princess. "I showed her what success looks like!"

What's really happening?

Sir Reginald is not a bad instructor. He is in fact very knowledgeable and knows a lot of things intuitively after so many years of his own training. He is able to recognise mistakes immediately, understand the risks and know just from a glimpse what a good rider should or should not do.

His problem is not the expertise, but the way he communicates it. Every instruction he is giving is a negation: don't do this, don't do that. These instructions identify very specific problems and try to get them corrected, but our heroine is missing the greater picture: in this case, how a rider should actually ride.

Eleanor is pushed towards a lot of mental training too, next to the physical bit: she first has to understand what is wrong, work out alternatives, choose one, translate it into action and repeat. Especially this repetition can be both tiring and frustrating if you don't know what you are after.

When the princess intervenes, her instructions are clear, concrete and immediately actionable. And what is even more beautiful, Eleanor can imagine herself performing these actions before doing them. Princess Beatrice has not changed what Eleanor needs to learn, she has only changed how Eleanor is able to act on the information she is getting.

By now, the problem is recognisable by architects. Just like Sir Reginald, architects are trained to recognise risks, identify inconsistencies, prevent unnecessary complications and provide well-intended critical arguments. As a result, their communication can also become a series of warnings and prohibitions:

  • "Don't duplicate data!"
  • "Don't build a point-to-point integration"
  • "Don't deviate from the target architecture"

These are all valid concerns, but knowing what to avoid is not the same as knowing what to do best. An architect's impact depends not only on the quality of their knowledge, but also on their ability to translate it into actions. And this is where positive framing becomes powerful in communication.

  • "Use the authoritative data source for X type of data"
  • "Use the approved integration patterns, you have 4 to choose from"
  • "Your transition architecture could try to do XYZ to move us safely towards target"
Can your knights see the wooden gate?

Sir Reginald saw every mistake Eleanor did and tried to correct these one by one. The princess pointed Eleanor towards the wooden gate and the to-be knight knew intuitively what to do to get there. The next time you give architectural guidance, ask yourself: can your knights see their gates?

What could an architect do differently?

To make it clear: this is not about making all our communication positive and rosy. Both types of sentences are important: the positive sentences describe direction, while the negative statements define boundaries. Both are useful and taken separately they might create a different experience for the listener:

  • When only positive statements are used, the extreme is that the one who communicates may gradually be perceived as a micromanager and become a bottleneck because they do not allow for any decision at the level of the implementation team
  • When only negative statements are used, the extreme is that the one who communicates may gradually be perceived as someone who only blocks, criticises or complicates work

The magic is when you combine both: explain the boundary and make the direction unmistakable. For example, a warning becomes helpful when accompanied by a clear alternative: "You cannot store sensitive customer data in this environment. Best is to use the approved secured environment and you have these 3 ways on how to do this."

Reflection

Think about your last architecture review or open your last architecture artefact.

How many times did you use phrases as "X is not allowed", "the organisation should not do Y", "this is not compliant with our standards"?

Now imagine having the same conversation / text to write, how can you rephrase in a positive framing?

Check question: instead of telling what not to do, have you told what is to be done?

Impact · How does architecture create change and impact?

The Faster Aeroplane

A story from a year-long field guide · Written by Ioana Bour

The Faster Aeroplane

Mr. Harrison, Thomas and the Director studying a process drawing laid out on a table

Once upon a time, not many years after aeroplanes had been invented, there was a small aviation company called Agile Air.

It was 1925, and aviation was still a rather adventurous business. Aeroplanes were expensive and engines not yet that reliable, so pilots were greatly admired for their courage. Especially by people who preferred to keep both feet on the ground.

Agile Air was a young company with two aeroplanes, three pilots and a rather ambitious director. They were also struggling to find their place in the market, but the Director had an idea: instead of competing on scheduled routes, they chose to specialise in urgent deliveries. There were plenty of businesses willing to pay extra to receive important goods quickly, particularly when delays could cost them considerably more than the price of a flight.

In time, Agile Air began offering a rather unusual service: transporting small, urgent consignments directly to customers, whenever the weather and flying conditions allowed. Unlike the established airlines, which operated according to fixed schedules, Agile Air could collect a package from a small airfield near a supplier and fly it directly to a landing field close to the customer. It was a promising business model, but they needed a customer large enough to prove it worked.

The largest textile manufacturer in the country, the Royal Textile Company, operated eight enormous mills across the northern valleys. Its factories employed thousands of workers, and its machines produced enough fabric to supply a considerable part of the kingdom. Unfortunately for them and fortunately for our Agile start-up, these machines also had a tendency to break down. And for a factory with hundreds of workers waiting to restart production, that was an expensive problem.

Agile Air proposed something rather bold. They would collect the most urgent replacement parts directly from the suppliers and fly them to a landing field near the textile mills. From there, the parts could be delivered to the factories by tractor or car. What previously took a day or more could now be achieved in approximately four hours. The Royal Textile Company was impressed and agreed to a six-month trial with a larger contract on the horizon.

Needless to say everyone worked extraordinarily hard at Agile Air and beyond. The pilots learned the routes through the northern valleys. Mr. Harrison, the company's Chief Engineer, improved the loading procedures. The suppliers agreed to keep urgent packages ready for collection, and the textile company arranged motorcars to meet the aircraft. After several months, the results were impressive. The four hours had been achieved.

Unfortunately, the Royal Textile Company was not entirely satisfied. While the company acknowledged the impressive delivery times, its factories were still experiencing considerable production downtime.

The trial was approaching its end and the contract extension was shaky. The Director of Agile Air immediately summoned his management team.

"Gentlemen*, we have a problem. Our largest customer is considering whether to renew our contract."

(*the year is 1925...)

Mr. Harrison looked surprised.

"But we have delivered exactly what we promised! Four hours, on average. That's considerably faster than anything the established airlines can offer."

"Apparently, it isn't fast enough," replied the Director.

Mr. Harrison thought for a moment.

"We have already improved almost everything we can with our current fleet. There is very little time left to save the contract."

"Then perhaps we need faster aeroplanes," suggested the Director.

Mr. Harrison nodded.

He had been studying a new model from a French manufacturer. It was expensive, but it could potentially reduce their delivery time by another forty minutes.

"That would give us another seventeen percent improvement," he explained.

The Director was delighted.

A week later, the management team gathered to review the proposal. There were beautiful drawings of the new aeroplanes, technical specifications and several charts demonstrating the expected improvements.

The Director was ready to approve the investment.

But Thomas, a young engineer who had recently joined the company to help plan its airfields and operations, had a question.

"May I ask what our customer would be able to do with those additional forty minutes?"

The Director looked at him.

"Excuse me? Restart their factories forty minutes earlier, of course."

"Are they able to restart so quickly? Do they restart production as soon as our spare parts arrive?"

"How is this our problem?" replied the Director.

Thomas turned to Mr. Harrison.

"I was just curious to understand what happens there after we deliver."

Mr. Harrison thought for a moment.

"That is not such a bad idea," he said, slightly blaming himself for not having thought of it earlier. "What if the delay is not about our aeroplanes at all?"

The Director considered this.

"Very well. You both go, but make it quick. We have a contract to renew."

And so Thomas and Mr. Harrison travelled to the northern district.

At the first factory, Thomas discovered that the replacement part had indeed arrived in four hours. Unfortunately, the mechanic who could install it was working at another mill and would only be available the following morning.

At the second factory, the part had arrived even faster. But the maintenance manager had ordered the wrong size, and they were now waiting for a new delivery.

At the third factory, Mr. Harrison was shown a large weaving machine that had been standing idle for almost two days.

"When did you receive the replacement part?"

"Yesterday morning," replied the factory manager. "Your pilots are doing a wonderful job."

"Then why is the machine still not working?"

"We are waiting for the engineer from the manufacturer. These machines are rather complicated, you see. We cannot repair them ourselves."

Thomas and Mr. Harrison spent another two days visiting factories and speaking with managers, mechanics and machine operators. Everyone was working hard, just as hard as at Agile Air. Yet somehow, the factories were still losing enormous amounts of production time.

They began to understand why. Each team was improving its own part of the work. But the entire sequence, from the moment a machine broke down until production resumed, had never been examined as one process.

They asked for the process plans.

"Purchasing has its procedures. Maintenance has theirs. And every factory has its own way of organising repairs," said one of the factory managers.

"But is there one view showing how everything fits together?"

"Not that I know of."

And so Thomas asked for a large piece of paper.

Together with the purchasing manager, the head of maintenance and several factory supervisors, he began drawing what actually happened when a machine broke down.

First, the operator reported the problem. Then a mechanic assessed the damage. If a replacement part was needed, someone identified it and sent a request to purchasing. Purchasing contacted the supplier, who prepared the part for collection. Agile Air transported it to the factory. Then maintenance arranged for someone to install it, test the machine and return it to production.

It was a rather long drawing. And the longer it became, the more questions appeared.

Why was the mechanic only scheduled after the part arrived?

Why did different factories use different descriptions for the same components?

Why did maintenance not always know which parts had already been ordered?

And why were some commonly needed parts being flown repeatedly from the south when they could have been stored closer to the factories?

When Thomas and Mr. Harrison returned to Agile Air, the Director was waiting for them.

"So?"

Thomas spread his large drawing across the table. He explained everything and then triumphantly proposed:

"What if we coordinated the delivery of the part with the availability of the mechanic?"

The Director was growing impatient.

"Are you suggesting that instead of buying new aeroplanes, we should organise mechanics and warehouses?!"

"Not exactly, sir," intervened Harrison. "Thomas is only suggesting that we help our customers with their core problem and, in doing so, continue to sell our services."

There was a long silence.

Then Mr. Harrison pointed to the drawing.

"Actually, we could change the way we receive orders. If we knew which machine had broken down, and not just which part was needed, we could notify the supplier and the maintenance team at the same time."

"And perhaps prioritise deliveries based on how much production is affected," added Thomas.

"Yes. At the moment, we prioritise orders by when they arrive. But a small component stopping an entire factory may be more urgent than a larger delivery to a machine that is still running."

The Director looked at the drawing, then at the beautiful illustrations of the French aeroplanes.

The following week all three travelled north and presented their findings to their customer's management team.

At first, the textile company's managers were somewhat defensive. Purchasing had its procedures. Maintenance had its schedules. Every factory had its own particular circumstances. And, more importantly, none of them had asked an aviation company to explain how to run a textile business.

But as they examined the drawing together, the conversation slowly changed. They agreed to a pilot (pun intended) and over the following months, the two companies experimented with a new way of working.

Agile Air started to live up to its name as well. After all, it was not only about the fastest deliveries. They were actually offering a service that coordinated urgent deliveries with the activities required to make those parts useful. When the trial came to an end, the contract was extended.

Mr. Harrison was particularly pleased to be solving challenges with Thomas. He found his Lead Architect. The Director was happy too. Although he still occasionally looked at the drawings of the French aeroplanes. They really were beautiful machines.

What's really happening?

Agile Air was a young company trying to compete with larger and more established airlines. It had found its niche not by having better aeroplanes, but by organising its services differently, around a specific customer need.

The Director and Mr. Harrison were not wrong in wanting faster aeroplanes. They had tried many improvements and were genuinely good at delivering spare parts quickly. Their measure of success was the delivery time.

The Royal Textile Company measured success differently: how quickly its factories could resume production.

In negotiation theory, we distinguish between positions and interests. A position is what someone says they want, while an interest is the reason behind it.

The Director's position was that the company needed faster aeroplanes. His interest was keeping the company's largest customer. The textile company's interest was reducing production downtime. Once Thomas understood those interests, many more possibilities became visible.

But there is another aspect I find particularly interesting about this case: the breakthrough came when Thomas stopped looking at the delivery service in isolation and started looking at the entire process.

Every department was improving its own activities; each had its own procedures, responsibilities and measures of success. But the customer outcome depended on all of them working together.

This is where process architecture becomes so important: it helps us understand how an organisation delivers value across departments, systems and even organisational boundaries.

Additionally, Thomas did not come back with a complete solution to impose on everyone. He made a drawing that helped the different experts understand the problem and identify improvements together. And this was precisely what was needed. Sometimes the architect's most valuable contribution is not designing a better component, but helping everyone understand how the components should work together.

Are you building faster planes?

Imagine a request to improve an application. You start discussing requirements, integrations, technology choices and target architecture.

You might even work in an agile team delivering improvements every few weeks and that's wonderful. But do you know which business process the application supports? What happens before someone starts using the application? What happens afterwards? Which other systems, employees and departments contribute to the actual outcome? And does anyone have a complete view of that process?

Over the past few years, many organisations have invested heavily in becoming more agile. We have organised teams around products and applications, introduced backlogs, shorter delivery cycles and continuous improvement. We have become much better at delivering changes quickly. But an application is only one part of a larger process, often involving many other applications, data, decisions and people.

In a small company, people might still know how everything fits together because they speak to each other every day. In a large organisation, with hundreds of applications and many departments, that becomes considerably more difficult.

If we want to improve the customer journey or the experience with our product, we need to understand what we are changing and how it fits into the bigger picture (which is considerably larger than the application landscape).

What could an architect do differently?

I think there are two lessons an architect can take from this story: listening before architecting, and understanding how an individual solution fits into the larger business process.

1. Listen before architecting

When a stakeholder brings you a requirement, resist the temptation to immediately start designing.

Instead, explore five layers of listening.

  1. Hear the request. What is the stakeholder asking for, and how did they arrive at that conclusion? What have they already tried? Don't assume they haven't done their homework.
  2. Understand the desired outcome. What would become possible if the requirement were fulfilled? Focus not only on what the application should do, but on what the business or customer should achieve.
  3. Explore the actual pain. Where is the problem experienced? What happens before and after the activity you have been asked to improve? Have you spoken with the people experiencing it?
  4. Discover the constraints and underlying interests. Why are things organised this way? Which constraints are unavoidable, and which are simply decisions or assumptions from the past?
  5. Agree on what success looks like. Will success be measured by how much faster the application performs, or by how much better the business outcome becomes?

These are not five questions to fire at a stakeholder like an interrogation. They are layers of understanding that should emerge naturally through a conversation.

And sometimes you will discover that a faster aeroplane really is exactly what is needed, but at least you will know why.

2. Look at the process, not only the application

When improving or replacing an application, understand where it fits within the larger business process.

What triggers the process? What outcome does it deliver? Which activities, decisions, people, data and applications are involved?

This does not mean every assignment requires a detailed process diagram with hundreds of boxes and arrows. We should aim for a sufficiently clear end-to-end view to understand how everything works together.

And in a large organisation, this should not depend entirely on individual project teams rediscovering the same processes.

This is where process architecture comes into the picture. We need a coherent view of the organisation's end-to-end processes, particularly those crossing departmental boundaries. We need reference processes that help identify where activities can be standardised and reused, and where variations are genuinely needed. And we need to understand how our application landscape supports those processes.

That allows us to make better decisions about where to invest, what to standardise, which applications to reuse and which dependencies to consider. Most importantly, it helps us understand whether the changes we deliver actually improve the outcomes that matter.

Reflection

Think about the last application your organisation developed, modernised or replaced.

Could you point to the end-to-end process it supports, explain how it works across departments and show how your change improves the outcome for the customer?

Are we making our aeroplanes fly faster, or are we helping the factories get back to work?

Organization · How do decisions really happen?

The Well Everyone Loved

A story from a year-long field guide · Written by Ioana Bour

The Well Everyone Loved

The royal planner presenting one great well to the King and the village chiefs

Once upon a time there was a kingdom with twelve villages, each with its own village well. Not one well resembled another: one was deep, one was shallow, one produced the purest water, one had more minerals, one more mud than anyone would care to admit and so on. Each village maintained its own well and paid for all repairs (and complained about the cost).

One day, the King announced a magnificent plan.

"We shall build one great well for the entire kingdom! Cleaner water, more reliable supply and cheaper maintenance. Why should twelve villages pay for twelve wells when one could serve us all? We will make sure that everyone benefits!"

The village chiefs applauded.

"A splendid idea!" said one village chief.

"A triumph of efficiency!" agreed another.

The royal planner was delighted. Finally, a change everyone supported.

Six months later, he returned with the final designs.

"The great well will be ready by spring," he announced proudly. "And naturally, all twelve village wells will then be closed."

The room fell silent.

"Closed?" asked one village chief. "But then our people would have to walk twice as far!"

"And who guarantees the quality of this shared water?" demanded another chief. "We will not agree to this until we have certainty that our pure water can be replicated!"

Another village chief cleared his throat. "Our village has drawn water from the same well for four generations. It is part of our identity. This cannot be the future."

Even the first village chief, who had enthusiastically supported the project, now insisted that his village's buckets were specially designed and might not fit the new well.

Within an hour, the great well had become the most controversial project in the kingdom.

The royal planner was furious.

"They are resisting change!" he complained to the King. "They all agreed to the plan!"

An old water carrier, who had spent forty years carrying water between the villages, happened to overhear.

"Of course they agreed," he said. "You asked whether they wanted a better well. You never asked what they were willing to give up for it."

"They are only winning with this new well!" protested the planner.

"The kingdom is winning," replied the water carrier. "But the villages? Did you consider convenience? Quality control? Identity?"

The planner spent the following weeks personally visiting the villages and meeting the people. He discovered that some objections could be solved, that others required compromises, and that only a few could not be reconciled at all. Those were the true price of moving to what the kingdom had decided was a better solution. A few villages still had to walk farther for water, there was no way around it. But that water would be cleaner than what they had today.

When he returned to the council, he brought a new plan. He made sure to include local collection points, shared water-quality checks and a transition period during which the old wells would remain available. The eastern village could even keep its old well as a monument. The new plan was, however, more expensive and took longer. But this time, when the chiefs agreed, they knew what they were agreeing to.

What's really happening?

In short, the royal planner confused agreement with commitment. While everyone agreed on the destination, no one was committed to taking the steps of the journey.

This, in hindsight, is a recognisable situation. In large organisations people rarely oppose ideas like standardisation, simplification, reuse, or efficiency. They all make sense! They are attractive objectives, especially when discussed at an abstract level. But along the way, 'resistance' often emerges, especially when implications become concrete.

This is partly explained by loss aversion: people tend to experience the pain of losing something more strongly than the pleasure of gaining something of comparable value. But there is more to it than psychology.

A shared solution may genuinely create benefits at enterprise level while introducing disadvantages locally. A department may lose autonomy, flexibility, influence or a capability it has invested years in developing. What looks like resistance from the centre may be a perfectly rational concern from within the domains.

Are your village chiefs resisting?

It's not always "politics". In this example everyone supported the initial idea and the principle of one shared well until someone explained that the current wells would be decommissioned. Only then did the impact become clear, and the real questions began.

Architecture discussions can become difficult not only when the envisioned target state is wrong. This also happens when the general enterprise benefit and the local consequences have not been discussed together. This is why resistance can be a good thing! An architect who feels resistance has an opportunity to ultimately improve the design.

What could an architect do differently?

This is not to say that the architect should go down a rabbit hole and try to eliminate every disadvantage of an enterprise-wide decision. However, the architect can make the consequences visible before asking for commitment.

  • Discuss what disappears, not only what improves. Which systems, processes, responsibilities, or freedoms will stakeholders lose?
  • Distinguish legitimate constraints from preferences. A critical local requirement is different from an emotional attachment to an old solution, even though both deserve to be understood.
  • Make trade-offs explicit. Who benefits, who bears the cost and who has the authority to decide?
  • Design the transition as carefully as the destination. Migration, temporary arrangements, and clear ownership may matter as much as the future-state architecture.

And perhaps most importantly, involve stakeholders before the solution is considered finished. Their concerns may reveal requirements that were invisible from the enterprise perspective.

Reflection

Enterprise Architecture in particular is full of shared wells: common platforms, standardised processes, reusable capabilities.

Before celebrating agreement on your architecture, ask yourself: whose well are you planning to close and do they understand the implications?

Stories

Every story published so far.

Out of a planned fifty. New ones arrive out of order — check the Field Guide to see which theme each belongs to.

Coming soon

Influencing the Enterprise — The Podcast

Conversations about what happens when the architecture is clear — but the organization is complicated.

"Tell me about a time you knew what the right architectural decision was, but couldn't get the organization to make it."
About

Not a framework. Not a guru. A field guide.

Architecture frameworks teach us a great deal about how to describe an enterprise. They teach us considerably less about what happens when people disagree.

Influencing the Enterprise is about the part of the job that never quite makes it onto a diagram: authority, trust, stakeholder psychology, storytelling, negotiation, politics, knowing when to push and when to fold. The stuff that quietly decides whether the good architecture actually happens.

This isn't trying to give you a new way to structure the work, and it won't hand you universal answers — anyone promising those hasn't done the job. What it is: fifty stories, written over a year, checked against real research and tested against how decisions actually get made — not the tidy version from the slide deck.

Every story follows roughly the same shape: the fiction first, then what's actually going on underneath it, then what an architect could do differently. The stories are made up. What they're pointing at, unfortunately, is not.

There's a podcast coming too, eventually — conversations with architects, executives and the other people in the room when these decisions actually get made.

"The goal isn't to become the most powerful person in the room. It's to help the room make a better decision."

Portrait of Ioana Bour
About the author

Ioana Bour

I'm Ioana Bour, an Enterprise Architecture leader, architect and coach based in the Netherlands.

I've spent much of my career working at the intersection of business and technology — first as a technical & management consultant and later in Business & Enterprise Architecture. Today I lead a team of Enterprise Architects in a large financial organization, working on questions that cut across organizational boundaries: future-state architecture, business processes, simplification, governance, operating models and the changing role of architecture in increasingly autonomous organizations.

Over the years, I became increasingly interested in something architecture frameworks don't teach particularly well: what happens after you've worked out what the architecture should be?

Architects rarely own all the teams, budgets or decisions required to make that architecture happen. We work through other people. We need to understand their priorities, challenge their assumptions, bring different perspectives together and sometimes convince people considerably more senior than ourselves. And occasionally, after doing all of that, we need to accept that the organization has chosen a different path.

My work as a trained coach made me even more curious about this side of our profession. Architecture taught me to look at systems, dependencies and structures, but coaching taught me to pay closer attention to the people inside those systems — how we listen, what we don't say, what makes us defensive, how trust develops, and why asking the right question can sometimes achieve more than presenting the right answer.

Influencing the Enterprise grew out of the intersection of those two worlds.

There's also a more current reason this feels urgent to me. I lead a team of architects inside a large financial organization, and I'm already watching AI take over more of the analysis, the modelling, the documentation — the work that used to fill most of an architect's week. It hasn't made the job smaller. If anything, it's made the part nobody's automated yet — getting an organization to actually act on good architecture — the part that matters most.

This is not a new architecture framework, and I certainly do not claim to have all the answers. Let us make it a place to explore the situations that Enterprise, Domain and Solution Architects encounter every day but that rarely appear on architecture diagrams: authority and influence, trust, stakeholder psychology, storytelling and so on.

Trust & Authority
Collaboration & People
Insight & Direction

For Enterprise-, Domain- and Solution Architects