Principal Architects: All the Qualifications in the World and Not a Fucking Clue
There's a particular species of corporate employee who occupies a fascinating position in the organisational food chain.
The Principal Architect.
A title that sounds enormously impressive.
Principal.
Architect.
Two words that suggest intelligence, authority, experience and the ability to design sophisticated technical solutions.
And sometimes, that's exactly what you get.
Other times, you get a man who looks like the bug in an Edgar suit from Men in Black, possesses the personality of a lobotomised rock and communicates with the self-importance of a medieval king addressing a village of diseased peasants.
Let's call him Quentin.
Quentin is a Principal Architect.
And Quentin is a fucking dick.
The Edgar Suit
You know the bug from Men in Black?
The enormous alien cockroach attempting to operate a human body?
That's Quentin's Teams photograph.
Not literally, obviously.
But the resemblance is sufficiently alarming that every time his picture appears in a meeting, I half expect him to demand sugar water and start shedding his fucking skin.
There's something deeply unsettling about a man whose profile photograph looks like a human face being worn by something that hasn't quite understood the instructions.
And yet Quentin has chosen this photograph himself.
That's the extraordinary part.
He presumably looked through his camera roll, selected that particular image and thought:
"Yes. That's the one. That's how I'd like to present myself to the professional world."
Arnold Schwarzenegger once delivered the immortal line, "You're one ugly motherfucker."
And if Quentin ever wandered into the jungle wearing a Predator costume, I suspect Arnold would feel compelled to repeat it.
But physical appearance isn't really Quentin's problem.
Unfortunately, his personality is even fucking worse.
The Most Important Man in the Room
Quentin doesn't simply attend meetings.
Quentin graces them.
He joins a Teams call with the solemn authority of a man who believes the entire organisation has been waiting for his arrival.
He doesn't answer questions.
He delivers pronouncements.
He doesn't offer suggestions.
He establishes architectural direction.
And he doesn't disagree with people.
He identifies fundamental misalignments with the strategic technical vision.
What a fucking bellend.
Ask Quentin a simple question and he'll give you a forty-minute explanation involving seven diagrams, four architectural principles and a PowerPoint slide that looks like somebody emptied a box of spaghetti onto a fucking circuit board.
"Quentin, can we change this configuration?"
"Well, we need to consider the wider implications for our enterprise transformation architecture, particularly in relation to the evolving integration landscape and the overarching strategic objectives."
Right.
So is that a yes or a no?
"Well, it's not quite that straightforward."
Of course it fucking isn't.
Nothing is straightforward when Quentin's involved.
Because if Quentin answered a question in twelve seconds, somebody might realise that his entire contribution to the organisation could be replaced by a reasonably competent search engine.
Qualifications Galore
Now, to be fair, Quentin has qualifications.
Lots of qualifications.
He's got certifications coming out of his fucking ears.
His LinkedIn profile looks like somebody's emptied an entire training catalogue into a wheelbarrow.
Architecture certifications.
Cloud certifications.
Security certifications.
Platform certifications.
Enterprise transformation certifications.
He probably has a certificate confirming that he knows how to obtain certificates.
And I'm sure he's worked hard for them.
But here's the problem.
Quentin has qualifications galore and the common sense of a retarded chicken.
Not an ordinary chicken.
An ordinary chicken might recognise a dangerous situation and run away.
Quentin would organise an architectural review, establish a governance framework and confidently walk into the fucking fox's mouth.
Because there's a difference between knowing technical terminology and possessing practical intelligence.
There's a difference between passing an exam and understanding how things work in the real world.
And there's a very significant difference between being able to describe a process and having the common sense to fucking follow it.
Quentin can explain the theoretical architecture of a highly available enterprise integration platform.
But ask him to make a straightforward operational decision and suddenly you're watching a man attempt to solve a Rubik's Cube with his fucking forehead.
The Email From Mount Olympus
Quentin also loves an email.
Not a normal email.
Not a useful email.
A Quentin email.
A sprawling, self-important technical manifesto that begins with an apparently simple subject and rapidly descends into an incomprehensible swamp of architectural jargon.
"Following our recent strategic alignment discussions, I believe it is imperative that we establish a cohesive transformation framework to facilitate the evolution of our target-state operating architecture."
What?
What the fuck are you talking about?
We've asked whether the integration is ready for testing.
We don't need the Magna Carta.
But Quentin continues.
Paragraph after paragraph.
Acronyms.
Technical terminology.
Architectural concepts.
Transformation objectives.
Strategic dependencies.
You could print the email, roll it into a cylinder and use it to beat somebody to death.
And then, buried somewhere in paragraph eleven, comes this magnificent sentence:
"Are next object is to establish the transformation roadmap."
Are.
ARE.
Quentin.
You absolute fucking bellend.
It's OUR.
O-U-R.
Not ARE.
You're a Principal Architect.
You communicate with senior stakeholders.
You write lengthy technical emails explaining the future direction of enterprise technology.
And you've somehow managed to lose a fight with a three-letter fucking word.
I'm not expecting Shakespeare.
I'm not demanding a literary masterpiece.
I'm simply suggesting that if you're going to address the entire organisation like a visiting professor of advanced computational physics, perhaps you could establish the difference between are and our before pressing Send.
Especially when Microsoft Word has been trying to help people with this sort of thing since approximately the fucking Bronze Age.
And this isn't some casual message dashed off while running between meetings.
This is Quentin's grand architectural proclamation.
His technical sermon.
His contribution to the strategic intellectual advancement of the organisation.
And it contains the grammatical sophistication of a confused fucking chicken.
"Are next object..."
Jesus Christ.
Perhaps are next object should be learning English.
The Architecture Department: A Parallel Universe
There's another fascinating characteristic of certain enterprise architects.
They appear to believe that the rules governing everybody else don't apply to them.
Developers must follow processes.
Support teams must follow processes.
Changes must be assessed, approved, documented and implemented through the appropriate controls.
Quite right too.
These processes exist for a reason.
They protect customers, systems, data and the organisation itself.
But apparently, some architects operate in a parallel universe where governance is something they design for other people.
Not something they're expected to fucking obey.
Because they're architects.
They're special.
They're important.
They understand the bigger picture.
And when you're operating at Quentin's level of strategic magnificence, apparently the mundane requirements of operational governance are beneath you.
It's rather like an architect designing a hospital and then deciding he doesn't need to wash his hands before surgery because he understands the fucking floor plan.
The Integration Incident
And now we arrive at a particularly beautiful example of corporate incompetence.
One of Quentin's fellow architects, let's call him Oliver, implements an integration.
Nothing unusual about that.
Integrations are part of the job.
Except Oliver doesn't follow the correct change process.
No proper change approval.
No appropriate governance.
Just an integration implemented without following the controls everybody else is expected to observe.
Now, in a properly functioning organisation, this should be relatively straightforward.
Somebody identifies the failure.
The relevant people investigate what happened.
The responsible individual explains their decision.
Any risk is assessed.
And the organisation takes appropriate action to prevent it happening again.
Simple.
But we're dealing with enterprise architecture.
So naturally, things become fucking ridiculous.
Enter Stuart, Head of Missing the Point
The incident reaches Stuart, the head of department.
Stuart is one of those senior managers who can transform a straightforward operational failure into an existential crisis about the entire organisation.
He receives the information.
He considers the situation.
And then he sends an email to customer stakeholders.
Because nothing says competent internal management quite like broadcasting your department's inability to follow its own procedures.
And then comes Stuart's magnificent contribution.
He doesn't necessarily disagree with the decision that was made.
But he's concerned.
Concerned about what?
The integration?
The missing approval?
The fact that an architect apparently considers change governance an optional lifestyle choice?
No.
Stuart is concerned that if this has happened, perhaps everybody else is doing things incorrectly as well.
WHAT?
Stuart.
You magnificent fucking turnip.
One architect has failed to follow the correct change process.
One.
And your immediate conclusion is that perhaps the entire department is operating incorrectly?
What sort of fucking reasoning is that?
If a chef in a restaurant forgets to wash his hands, do you immediately assume every chef in the country is rubbing raw chicken into their fucking armpits?
If a pilot forgets a pre-flight check, do you conclude that aviation as an industry has abandoned safety procedures?
If Quentin writes "are" instead of "our", do you assume the entire English-speaking population has forgotten how to spell?
No.
You identify the person responsible.
You establish what went wrong.
And you address the fucking problem.
The People Following the Rules Are Now Under Suspicion
This is what makes Stuart's response so spectacularly irritating.
The people following the correct change process are suddenly being dragged into the discussion because somebody else didn't.
Imagine being a developer.
You raise your changes.
You complete the documentation.
You obtain approval.
You follow the release process.
You do everything you're supposed to do.
And then Oliver, the architect, decides he's too important to bother with any of that.
So Oliver implements an integration without the required governance.
And Stuart's response is:
"Well, if this has happened, perhaps we need to question whether everyone else is following the process correctly."
NO, STUART.
WE ARE FOLLOWING THE FUCKING PROCESS.
THAT'S THE POINT.
WE'RE NOT THE PROBLEM.
THE PROBLEM IS THE ARCHITECT WHO DIDN'T FUCKING FOLLOW IT.
This is the corporate equivalent of catching somebody shoplifting in Tesco and immediately launching an investigation into whether every paying customer is secretly a thief.
"Well, one person has stolen a packet of biscuits, so perhaps we need to question whether the entire population understands the concept of payment."
No, Stuart.
We need to deal with the biscuit-stealing cunt.
Everybody else has already paid.
The Courage to Hold Absolutely Nobody Accountable
But there's a reason some managers behave like this.
Because identifying a specific failure requires a specific conversation.
And specific conversations can be uncomfortable.
You might have to tell somebody they've made a mistake.
You might have to challenge a senior colleague.
You might have to explain why a supposedly experienced professional has failed to follow a basic operational control.
And that takes something corporate management often appears to lack.
A fucking spine.
So instead, the issue gets diluted.
It's no longer about Oliver failing to follow the change process.
It's about our collective approach to governance.
It's about ensuring consistency across delivery functions.
It's about reviewing organisational understanding of change management principles.
Wonderful.
We've managed to transform one person's mistake into everybody else's training requirement.
Oliver ignores the process.
The rest of the department gets invited to a mandatory governance refresher.
And Quentin will probably be asked to produce the architectural guidance.
A twenty-seven-page document titled:
"Are Strategic Objectives for Change Governance Transformation."
Written by the man whose own team apparently can't follow the fucking rules.
You couldn't make this shit up.
The Special Rules for Special People
And that's the broader problem.
Certain people accumulate enough qualifications, job titles and organisational importance that nobody seems willing to question their competence.
A junior developer makes a mistake?
Formal review.
A support analyst misses a process step?
Escalation.
An engineer implements an unauthorised change?
Investigation.
An architect does it?
"Perhaps we need to reflect on our wider governance culture."
Oh, fuck off.
Why does the responsibility suddenly become collective when the person involved has the word Architect in their job title?
Are architects immune to accountability?
Does certification confer diplomatic immunity?
Can Quentin simply flash his enterprise architecture credentials and declare himself exempt from the change process?
"Sorry, I don't require approval. I'm TOGAF certified."
Congratulations.
I'm sure that'll be a tremendous comfort to the customer when the integration takes their production environment down.
The Principal Architect's Actual Job
Here's a thought.
Perhaps the role of a Principal Architect should involve more than producing elaborate diagrams, attending strategic meetings and writing emails that require a fucking translator.
Perhaps it should involve practical judgement.
Understanding risk.
Setting standards.
Applying those standards consistently.
Supporting technical teams.
And demonstrating the professional competence expected of somebody occupying such a senior position.
Revolutionary stuff.
Because the ability to describe a governance framework is not the same as the ability to operate within one.
And being able to explain a complex architecture doesn't automatically mean you possess the judgement required to make sensible decisions.
You can have twenty certifications.
Thirty years of experience.
A job title longer than your fucking arm.
And still be an incompetent prick.
Qualifications are evidence of learning.
They're not proof of wisdom.
And they're certainly not a substitute for common sense.
The Next Architectural Review
I can already imagine the follow-up meeting.
Quentin joins Teams.
His Edgar-suit photograph appears on screen.
Martin welcomes everyone.
Stuart explains that the integration incident has highlighted some important opportunities for organisational learning.
Oliver says very little.
And Quentin begins.
"Are objective today is to ensure alignment across the strategic governance landscape."
Our.
It's fucking OUR.
But nobody corrects him.
Because Quentin is important.
Quentin is senior.
Quentin has certificates.
And Quentin has prepared a PowerPoint presentation containing forty-three slides.
Slide one: Strategic Governance Transformation.
Slide two: Enterprise Architectural Alignment.
Slide three: Target-State Operating Model.
Slide four: a diagram resembling the wiring behind a condemned nightclub.
By slide seventeen, somebody asks whether the architect responsible for implementing the integration without approval has actually been spoken to.
Stuart looks uncomfortable.
"Well, I think it's important that we don't make this about individuals."
Of course not, Stuart.
That would be far too fucking sensible.
Let's make it about everybody.
Let's organise another workshop.
Let's produce another framework.
Let's establish a governance improvement initiative.
Let's create a working group.
And let's invite all the people who were already following the correct process to spend another two hours learning how to follow the correct process.
Meanwhile, Oliver can get back to implementing integrations.
And Quentin can continue writing emails about transformation.
The Real Architectural Problem
The thing is, genuinely good architects are invaluable.
They understand complex systems.
They anticipate problems.
They make difficult technical decisions.
They provide direction.
And, crucially, they understand that expertise comes with responsibility.
Not immunity.
The best technical people I've worked with don't need to constantly remind everybody how important they are.
They demonstrate their value through competence.
They explain complex ideas clearly.
They listen.
They apply common sense.
And when something goes wrong, they take responsibility rather than disappearing behind seventeen layers of corporate terminology.
It's the other sort that drives me fucking insane.
The self-important, overqualified, under-practical, jargon-producing architectural aristocrat who believes every sentence he writes is a contribution to human progress.
The man who can explain the strategic implications of an enterprise integration framework but can't spell "our".
The man who believes operational governance is essential, provided somebody else has to follow it.
The man whose technical authority is apparently inversely proportional to his ability to behave like a normal fucking human being.
And the managers who enable it are just as bad.
Because when somebody breaks a rule, you don't need to question the competence of everybody who followed it.
You need to deal with the person who fucking broke it.
Are Final Objective
So here's my proposal.
Before anybody is appointed Principal Architect, they should have to pass three additional assessments.
First, a basic common-sense test.
Nothing complicated.
Just a few practical questions designed to establish whether they can make a sensible decision without producing a diagram.
Second, a change governance test.
"Should you implement an integration without following the required approval process?"
A. Yes, because I'm important.
B. Yes, because I'm an architect.
C. Yes, because I have seventeen certifications.
D. No, you fucking idiot.
And finally, a spelling test.
One question.
Complete the sentence:
"_____ next objective is to improve operational governance."
If Quentin selects "Are", he fails.
Immediately.
No appeals.
No architectural review.
No strategic transformation roadmap.
Just a quiet conversation with somebody from primary school.
And perhaps Stuart could take the common-sense assessment as well.
Question one:
"An architect fails to follow the correct change process. What should you do?"
A. Address the specific failure.
B. Investigate the circumstances.
C. Ensure appropriate accountability.
D. Assume everybody else is also doing their jobs incorrectly and send a fucking email to the customer.
Stuart would choose D.
Then schedule a workshop to discuss why everybody else had chosen A.
And Quentin would produce a forty-page technical document explaining the strategic rationale.
"Are next object is to ensure everyone understands the importance of following the rules."
Yes, Quentin.
EVERYONE.
INCLUDING YOU AND YOUR FUCKING ARCHITECTS.
Now get back inside your Edgar suit and stop wasting everybody's time.