Introduction: The Death of Procedure
SOP stands for Standard Operating Procedure.
At least, it used to.
Today, it increasingly stands for something else:
Seat of Pants.
The modern technology industry has developed an almost pathological aversion to process, procedure, and institutional memory. Documentation is viewed as overhead. Research is viewed as delay. Verification is viewed as friction. Experience is viewed as expensive. The very practices that once separated engineering from improvisation are now frequently dismissed as obstacles to “moving fast.”
Everything that slows delivery is treated as a problem.
Everything that accelerates delivery is treated as progress.
The result is an industry that has become extraordinarily efficient at producing output while becoming remarkably indifferent to whether that output is correct, maintainable, secure, or even understood.
Artificial intelligence has not created this mindset, but it has amplified it dramatically. For organizations already inclined to prioritize speed over understanding, AI offers what appears to be the perfect solution: immediate answers, immediate code, immediate documentation, immediate decisions.
What it does not provide is wisdom.
It does not provide experience.
And it certainly does not provide understanding.
Those things still take time.
Unfortunately, time is precisely what modern organizations have convinced themselves they can no longer afford.
Why SOPs Exist
Standard Operating Procedures are often misunderstood by people who have never experienced the consequences of operating without them.
They are frequently portrayed as bureaucratic artifacts created by managers to slow things down. In reality, SOPs are something far more important. They are institutional memory made tangible.
Every deployment checklist exists because someone once broke production.
Every change management process exists because someone once made a change that should never have been made.
Every incident response procedure exists because someone once discovered that panic is a poor substitute for preparation.
Procedure is not created because organizations enjoy paperwork.
Procedure is created because organizations eventually discover that human beings are fallible.
Humans forget.
Humans get tired.
Humans become distracted.
Humans make assumptions.
The most experienced professionals understand this better than anyone. Surgeons use checklists. Pilots use checklists. Nuclear operators use checklists. Not because they lack expertise, but because they understand the limitations of expertise.
The technology industry increasingly behaves as though expertise alone is sufficient.
Increasingly, it behaves as though expertise itself is optional.
Fast Is Not the Same as Good
One of the most damaging ideas to emerge from modern technology culture is the belief that speed is inherently valuable.
Speed is useful.
Speed is often necessary.
Speed is not a substitute for correctness.
Yet much of the industry behaves as though velocity itself has become the primary objective.
Projects are evaluated based on delivery timelines rather than long-term outcomes. Teams are rewarded for shipping features rather than understanding systems. Executives celebrate reduced development time while rarely accounting for the maintenance burden that follows.
Artificial intelligence has accelerated this trend significantly.
When AI generates code in seconds, organizations naturally begin measuring the seconds saved.
What they rarely measure is everything that happens afterward.
They do not measure the hours spent debugging generated code.
They do not measure the architectural debt created by solutions nobody fully understands.
They do not measure the operational complexity introduced by systems assembled faster than they can be reasoned about.
Most importantly, they do not measure the expertise that never develops because the problem was never truly solved by the person responsible for it.
The output appears immediately.
The costs emerge later.
This has always been the defining characteristic of technical debt.
AI has merely increased the rate at which it can be accumulated.
The Replacement of Knowledge With Confidence
Historically, difficult technical problems demanded investigation.
An engineer encountered something unfamiliar. They consulted documentation. They reviewed source material. They experimented. They tested assumptions. They discussed alternatives with colleagues. Through this process, understanding emerged.
It was not always efficient.
It was often frustrating.
It was also how expertise was built.
Increasingly, that process is being replaced by generated certainty.
A question is asked.
An answer appears.
The investigation ends.
The confidence remains.
This creates one of the most dangerous illusions in modern technology: the appearance of knowledge without the existence of knowledge.
AI systems are exceptionally good at producing plausible answers. In many cases those answers are useful. In many cases they are correct. The problem is that users often possess insufficient expertise to determine which is which.
The result is a growing number of technical decisions based not on understanding, but on confidence.
The answer sounds right.
The code looks right.
The architecture diagram appears right.
Nobody asks the more important question:
Is it actually right?
Knowledge is not the ability to repeat an answer.
Knowledge is understanding when the answer is wrong.
That distinction is becoming increasingly important.
And increasingly rare.
Seat of Pants Engineering
Organizations often describe themselves as agile.
Many have simply become reactive.
Architecture decisions are deferred until they become emergencies. Documentation is postponed indefinitely. Technical debt accumulates because addressing it would interfere with delivery schedules. Operational processes are replaced by institutional folklore.
Instead of structured engineering, organizations increasingly rely on improvisation.
Systems emerge rather than being designed.
Dependencies accumulate rather than being evaluated.
Infrastructure grows rather than being understood.
The result is seat of pants engineering.
This tendency becomes particularly dangerous when combined with AI-assisted development. Teams can now generate software at a pace that far exceeds their ability to understand it. Entire services can be scaffolded in hours. Infrastructure can be deployed in minutes. Integrations can be assembled almost instantly.
What cannot be generated instantly is the understanding necessary to maintain those systems over the next five years.
Organizations often mistake functionality for engineering.
They are not the same thing.
Functionality is easy.
Engineering is understanding why the functionality works, how it fails, and what happens when conditions change.
The industry increasingly optimizes for the former while neglecting the latter.
AI and the Industrialization of Improvisation
Artificial intelligence may ultimately be remembered as the greatest accelerator of improvisation in the history of software development.
Previously, a lack of expertise acted as a limiting factor. A developer attempting something beyond their knowledge would eventually encounter obstacles. Progress would slow. Research would become necessary. Mentorship would become necessary. Learning would occur.
AI removes many of those friction points.
A developer can now generate deployment pipelines they do not understand.
Authentication systems they have never studied.
Cloud configurations they cannot explain.
Database schemas they did not design.
The work appears complete.
The learning never occurs.
This creates a dangerous inversion.
Historically, complexity and understanding tended to grow together.
Today, complexity is growing exponentially while understanding often remains stagnant.
The consequence is an industry building increasingly sophisticated systems on increasingly shallow foundations of expertise.
This is not a criticism of developers.
It is a criticism of incentives.
Organizations are actively rewarding output while deprioritizing understanding.
AI simply makes that tradeoff easier to justify.
The Abandonment of Thought
Perhaps the most concerning development is not the abandonment of procedure.
It is the abandonment of thought itself.
Research is increasingly viewed as inefficiency.
Investigation is increasingly viewed as delay.
Analysis is increasingly viewed as unnecessary.
The assumption appears to be that if a machine can provide an answer, then the thinking has already been done.
This belief fundamentally misunderstands the value of thinking.
The purpose of investigation is not merely to obtain an answer.
The purpose is to understand why that answer is correct.
The purpose is to understand when it may no longer be correct.
The purpose is to understand the assumptions embedded within it.
AI can generate conclusions.
It cannot generate experience.
It cannot generate judgment.
It cannot generate accountability.
Those responsibilities remain entirely human.
Yet many organizations increasingly behave as though they do not.
The Cost of Forgetting
Every mature profession eventually learns the same lesson.
Knowledge is fragile.
Expertise is fragile.
Institutional memory is fragile.
Once lost, rebuilding them is expensive.
Sometimes extraordinarily expensive.
The technology industry appears determined to test this principle.
Experienced engineers are often viewed as cost centers rather than repositories of institutional knowledge. Documentation is treated as secondary work. Training receives less attention than delivery metrics. Research is considered overhead rather than investment.
At the same time, organizations increasingly rely on tools that provide immediate answers while bypassing the processes through which expertise historically developed.
The long-term consequences may not be immediately visible.
For a while, everything appears to work.
Features ship.
Applications launch.
Dashboards remain green.
The missing understanding remains invisible.
Until it isn’t.
Because eventually every organization encounters a problem that cannot be solved with generated answers.
Eventually every organization encounters a failure that requires genuine expertise.
When that moment arrives, many may discover they spent years optimizing away the very capability they now desperately need.
Conclusion
Standard Operating Procedures were never about paperwork.
They were about preserving understanding.
They were about capturing hard-earned lessons so future generations would not have to learn them through failure.
They were about ensuring that knowledge survived beyond individual people, individual projects, and individual moments of institutional memory.
The modern technology industry increasingly treats those principles as outdated.
In their place it offers speed.
Improvisation.
Automation.
Confidence.
And increasingly, artificial intelligence.
The danger is not that AI will replace procedure.
The danger is that organizations will use AI as justification for abandoning procedure altogether.
History suggests that when experience becomes optional, mistakes multiply.
When knowledge becomes optional, failures become inevitable.
When thought becomes optional, catastrophe becomes merely a matter of timing.
If we are determined to automate away expertise, we might as well automate the warning label as well.