A Story from the Field Guide
The Faster Aeroplane
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.
- 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.
- 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.
- 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?
- 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?
- 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?