The Rocket Building Delusion
Many IT departments aspire to SpaceX-level engineering: multi-year roadmaps, platform teams, and custom architectures that could impress a 1,000-engineer organization. The challenge is that most organizations serve hundreds, not millions. Over-engineered processes can slow decisions, multiply meetings, and create redundancy, without significantly improving outcomes.
In contrast, a “drone-first” mindset emphasizes small, standardized, and adaptable solutions that deliver measurable value quickly. Quick wins, minimal bureaucracy, and clear follow-ups often outperform complex frameworks that require a specialist to run effectively. It’s not about cutting corners; it’s about moving faster and smarter.
This article explores how to identify organizational bloat, simplify execution, and shift focus from perfect plans to tangible results.
How We Got Here
Enterprise IT has spent years adopting practices from large tech companies—microservices architectures, platform teams, multi-year transformation roadmaps—without necessarily needing or benefiting from that level of complexity.
Many organizations also embraced heavy process frameworks, believing that methodology equates to maturity. These frameworks can be powerful under the right conditions but require expertise and significant overhead to implement correctly.
Inside the bubble, these practices make sense:
- Concepts inspired by large-scale tech companies
- Processes borrowed from consultants
- Architectures designed for planetary-scale operations
However, most organizations operate under constraints: time, budget, people, and context. What they need is not rocket engineering, but practical, situational solutions.
The Drone Mindset: What Works
High-performing teams don’t chase architectural perfection or complex process frameworks. They operate using drone logic:
1. Practical components over custom perfection
Off-the-shelf tools, standard patterns, and common integrations reduce complexity and increase speed.
2. Lean coordination over ceremonial frameworks
Simple, recurring meetings with clear agendas, explicit decision points, and actionable follow-ups outperform rigid rituals.
3. Rapid adaptation over long-term plans
Short feedback loops and real-time learning trump multi-year roadmaps. Decisions are based on what’s actually happening, not what a plan predicted six months ago.
4. Standardization over specialization
Using the same tools, patterns, and building blocks allows teams to scale efficiently and interchangeably.
5. Value delivery over internal sophistication
If a project or process doesn’t move the business forward quickly, it becomes organizational drag.
Rocket engineering optimizes for hypothetical futures. Drone engineering optimizes for immediate impact. Most IT organizations benefit more from the latter.
Delivery: Processes vs. Outcomes
There’s a misconception that digital delivery requires heavy frameworks and certified experts. In many cases, these resemble rockets:
- Impressive when executed correctly
- Effective at very large scale
- Ceremony-heavy and resource-intensive
- Dependent on specialists
While rockets have their place, most internal work requires lightweight, disciplined coordination:
- Recurring meetings with a clear agenda
- The meeting is to make group decisions
- Action items with owners and follow-up in the next meeting
- Meeting notes
No rituals. No doctrine. Just a system that works—fast, adaptive, and low-overhead.
Breaking the Bubble: A Practical Diagnostic
To move away from over-engineering, teams need clarity—not theoretical diagrams, but observable reality.
1. The Business Impact Test
For every team or initiative, ask the end users: Does this produce measurable value? If not, complexity may be getting in the way of people talking about their needs or the discussions are about solutions instead of framing requirements.
2. The Standardization Audit
How many tools do the same job?
How many bespoke integrations exist without strategic reason?
Drones succeed because they rely on standard, interchangeable parts. IT teams should too.
3. The Delivery Speed Reality Check
How long does a simple change take to ship?
If it’s measured in weeks instead of hours or days, processes may be overbuilt.
4. Meeting Load Inspection
If senior engineers spend most of their time in status meetings and process discussions, organizational coordination may be disproportionately complex.
5. Process Overhead Scan
How often do discussions revolve around process instead of decisions? Lean, decision-focused interactions outperform process-heavy ceremonies.
Strategic Subtraction: The Ultralight Principle
Progress often comes from removing weight rather than adding more systems.
- Consolidate redundant tools and platforms
- Favor commodity solutions over bespoke engineering
- Remove legacy processes that exist only due to habit
- Retire or reshape teams without a clear mission
Reducing organizational weight = faster delivery.
Adaptive Execution: Basic OODA still applies
Rockets are planned years in advance. Drones adapt in real time.
IT organizations can benefit from the same OODA loop approach:
- Observe – What’s happening right now?
- Orient – What does it mean for the business?
- Decide – What is the next right move?
- Act – Execute, learn, adjust
Short cycles beat long plans. Decisions beat ceremonies. Outcomes beat compliance.
Knowing When to Stop
Not every initiative must be rescued, and not every problem deserves a solution.
- If it hasn’t delivered value recently, pause or stop it
- If complexity is escalating, simplify or replace
- If a platform hasn’t launched, consider sunset options
- If a vendor isn’t delivering, end the relationship
Rocket thinking preserves sunk costs. Drone thinking preserves capability.
The Path Forward
- Start with truth – document reality, not aspirations.
- Deliver three meaningful improvements in 30 days – momentum breaks inertia.
- Shift from ceremonies to disciplined weekly rhythms – what shipped, what changed, what’s next?
- Measure outcomes, not activity – faster enablement, reduced costs, higher delivery frequency.
- Build a culture of simplicity – before adding anything new, decide what will be removed.
Conclusion
Your IT department doesn’t need to be send a manned rocket to Mars.
It can succeed by adopting a drone-first mindset: fast, adaptive, standardized, cost-effective, and relentlessly focused on delivering measurable business impact.
Rockets are impressive but slow and expensive.
Drones are humble, flexible, and effective.
And in most IT organizations, they win.
The choice isn’t whether to change—it’s whether to do it intentionally now or let reality enforce the shift under conditions you didn't choose.