A Cathedral That Floats
When Solutions become the Problem
A client approaches with what seems like a clear request, and immediately your mind races toward the grandest possible solution. You envision building something magnificent—a cathedral of code, strategy, or systems. Something that will stand for centuries, inspiring awe in all who encounter it.
So you begin. Foundations are laid, blueprints drawn, teams assembled. Months pass. The structure takes shape, impressive and complex. You’re proud of the emerging masterpiece.
Then comes the call.
“This looks amazing,” the client says, “but there’s just one small thing we forgot to mention... it has to float.”
Your heart sinks. A floating cathedral? The foundations you’ve poured, the load-bearing walls you’ve erected, the very permanence that makes it magnificent—all of it now works against you. Retrofit is nearly impossible. Starting over feels devastating.
But here’s what you missed: if you had listened more carefully to the original need, you would have discovered that all the client really wanted was a sacred space for reflection—somewhere they could connect with something larger than themselves, with complete flexibility about when and where.
They didn’t need a cathedral. They needed a prayer mat.
And a prayer mat? Yes, we could make that float. It requires no foundations, adapts to any terrain, travels anywhere, and serves the core need perfectly. You could have delivered exactly what they needed in a fraction of the time, with elegance instead of engineering heroics.
The client would have been delighted by a solution they hadn’t even imagined—something that met their need not just completely, but in ways that exceeded their expectations.
🧑💼 The Business Reality
This cathedral versus prayer rug dynamic, even though it sounds silly, comical and absurd, reveals one of the most expensive mistakes in business: the tendency to engineer complexity when simplicity would better serve the underlying need.
The Builder’s Paradox
The builder’s instinct: When presented with a problem, talented people naturally gravitate toward comprehensive, sophisticated solutions. We want to build something impressive, something that demonstrates our capabilities and anticipates every possible future requirement.
The user’s reality: Most needs are simpler and more fundamental than they first appear. Users want outcomes, not architectures. They want their problems solved, not monuments to our cleverness.
The irony is that our expertise often becomes our liability. The more capable we are of building cathedrals, the more likely we are to miss opportunities to deliver prayer mats. We solve the problem we’re excited about rather than the problem that actually needs solving.
The Prayer Mat Advantage
Organizations that master “prayer mat thinking” gain several crucial advantages:
Speed to Value Prayer mats can be deployed immediately. Cathedrals require extensive planning and construction. In fast-moving markets, speed often trumps sophistication.
Adaptability When requirements change (and they always do), prayer mats can be easily modified or replaced. Cathedrals require extensive renovation or complete reconstruction.
Resource Efficiency Prayer mats require minimal investment, leaving resources available for other priorities. Cathedrals consume enormous resources that might be needed elsewhere.
Learning Velocity Prayer mats allow rapid experimentation and learning. You can test assumptions quickly and adjust. Cathedrals lock in assumptions that might prove wrong months later.
User Adoption Simple solutions that solve specific problems clearly tend to see higher adoption rates than complex solutions that solve many problems adequately.
Common “Cathedral vs. Prayer Mat” Scenarios
The Software Development Trap
Cathedral approach: Building a comprehensive platform with every conceivable feature, perfect scalability, and elegant architecture. Months of development, extensive documentation, robust error handling.
Prayer mat reality: The client needed to automate one repetitive task that was taking their team 3 hours every Friday. A simple script that runs in 10 minutes would have solved their actual problem.
The “float” moment: “Oh, by the way, we need this to work on mobile devices too.” Now your desktop-optimized comprehensive platform needs a complete rethink.
The Strategy Consultant’s Dilemma
Cathedral approach: Developing a 200-page strategic transformation roadmap with detailed change management protocols, comprehensive stakeholder analysis, and phased implementation over 18 months.
Prayer mat reality: The CEO needed clarity on whether to pursue one specific partnership opportunity that was time-sensitive.
The “float” moment: “Actually, we need to make this decision by next week because the opportunity expires.” Your elaborate strategy framework can’t adapt to the real timeline.
The Marketing Campaign Monument
Cathedral approach: Creating an integrated multi-channel campaign with custom creative, extensive A/B testing protocols, sophisticated attribution modeling, and cross-platform consistency.
Prayer rug reality: The startup needed to validate whether anyone would pay for their product before running out of cash.
The “float” moment: “We just realized our budget is actually 10% of what we initially discussed.” Your comprehensive campaign strategy can’t scale down gracefully.
The Organizational Restructuring Cathedral
Cathedral approach: Designing new org charts, updating job descriptions, creating new performance management systems, establishing cross-functional committees, and implementing change management training.
Prayer rug reality: Two key departments weren’t communicating effectively, causing project delays.
The “float” moment: “The CEO wants to see immediate improvement—we need results this quarter, not next year.” Your systematic reorganization can’t deliver fast wins.
The Product Feature Cathedral
Cathedral approach: Building a comprehensive feature that handles every edge case, integrates seamlessly with existing systems, includes detailed analytics, and anticipates future expansion.
Prayer rug reality: Users were struggling with one specific workflow that forced them to switch between three different tools.
The “float” moment: “We need this to work for our enterprise clients too, who have completely different security requirements.” Your elegant consumer solution can’t adapt to enterprise constraints.
🧑🔬 The Science Behind Over-Engineering
Research in cognitive psychology and behavioral economics reveals several well-documented biases that drive us toward complex solutions when simpler ones would be more effective:
The Complexity Bias Studies by Silverman et al. (2012) demonstrate that people systematically prefer complex solutions over simple ones, even when the simple solution performs better. This bias appears across domains from medical diagnosis to investment decisions. We unconsciously associate complexity with competence and thoroughness, making simple solutions feel inadequate even when they’re optimal.
The Planning Fallacy Kahneman and Tversky’s research shows we consistently underestimate the time, cost, and effort required for complex projects by 20-50% on average. This optimism bias, documented across thousands of projects, leads us to believe we can anticipate all requirements (like the “float” constraint) if we just plan carefully enough.
Escalation of Commitment (Sunk Cost Fallacy) Research by Barry Staw and others demonstrates that once we’ve invested significant resources in an approach, we become psychologically committed to it even when evidence suggests a different path would be better. The more we’ve invested in a cathedral approach, the harder it becomes to pivot to a prayer mat solution.
The Curse of Knowledge Studies by Heath and Heath show that experts consistently overestimate others’ ability to understand complex solutions. The more we know about our domain, the more we assume sophisticated approaches are obviously necessary, losing touch with how simple the core need might actually be.
Status Quo Bias and Loss Aversion Kahneman’s prospect theory explains why users often resist even superior solutions: they focus more on what they might lose (familiar processes) than what they might gain (better outcomes). Complex solutions that change many things simultaneously trigger stronger resistance than simple solutions that change just one thing.
🧑🎨 The Art of Listening for Prayer Mats
The key to avoiding cathedral thinking lies in developing what we might call “need archaeology”—the ability to dig beneath stated requirements to uncover fundamental needs.
Listen for the Job to Be Done When someone asks for a cathedral, they’re usually trying to hire something to do a job. Ask: “If this solution worked perfectly, what would be different about your day?” Often, the answer reveals that a prayer rug could do that job just as well.
Look for the Constraint That Isn’t Mentioned The “float” requirement is rarely the first thing clients mention because they assume it’s obvious or they’re embarrassed they forgot it. Ask explicitly: “What constraints haven’t we discussed yet?” and “What would make this solution completely unusable?”
Test the Minimum Viable Cathedral Instead of building the full cathedral, create the smallest possible version that delivers the core benefit. This “proof of concept” approach reveals whether you’re solving the right problem before you invest in the wrong architecture.
Pay Attention to What They Don’t Ask For Cathedral builders get excited about features the client didn’t request. Prayer rug makers focus obsessively on the features they did request. If they don’t ask for scalability, beautiful architecture, or comprehensive reporting, maybe they don’t need those things.
Watch How They React to Simplicity When you propose a simple solution, notice their response. If they seem disappointed that it’s “too easy,” they might be suffering from complexity bias. If they seem relieved, you’ve probably found their prayer mat.
💡The Key Insight
Don’t start with the solution—understand the problem in depth first. The cathedral versus prayer mat story teaches us that:
The most elegant solution is often the one that does less, not more.
True mastery lies not in building impressive monuments to our capabilities, but in delivering exactly what’s needed with the minimum viable complexity.
When you feel the urge to build a cathedral, pause and ask: “What if they just need a prayer mat?” The answer might surprise you—and delight your client in ways they never expected.
The next time someone asks for something that seems to require foundational architecture, remember that the most beautiful solution might be the one that floats effortlessly, adapts to any situation, and serves the core need with elegant simplicity.