The build rate isn't the problem
Software used to be the bottleneck. Now it's not. Lovable, Bolt, v0. You can ship an MVP in a weekend. So we made building cheaper and thinking more expensive. Someone still has to sit with real customers, absorb the mess, and hold the discomfort of not knowing yet. That human time? It's the most expensive line item on the budget now. And nobody saw that coming. AI doesn't do it. Fast tools don't do it. It's still a people investing problem.
What a MOAT actually means right now
Traditional MOATs are real. Network effects, proprietary data, switching costs. But there's a newer, harder-to-copy one that doesn't get talked about enough: depth of pain comprehension. It's the reason why founders and key innovation players get combined with an acquisition package.
The team that understands a problem better than anyone else will consistently out-build, out-position, and out-retain competitors who understand it shallowly. You can copy a feature in a week. You cannot copy two years of watching real users struggle with a real thing. Or weeks of agony building the wrong thing just to redo it again.
Pain is the MOAT
Most teams never get there. They build on the first assumption and their own pain, not the reality of customer pain. I know it, I've done it myself. That's the gap. And that gap is where your MOAT lives.
Not customer pain as a nice product principle. Pain as a strategic asset. If you have genuinely deep, embodied understanding of a specific pain — one that took time, discomfort, and iteration to earn — that knowledge is not replicable at the speed of software. It compounds. It informs decisions across product, GTM, retention, and pricing.
The team that latched onto the first idea skips this entirely. My past week's conversations with three different founders built my empathy for how hard it is to sit uncomfortably with a blurry MOAT. With great founders and innovation teams come great pains and sacrifices.
X-shaped people are built for this
Most specialists retreat to their lane when things get ambiguous. The designer waits for a clear brief. The PM waits for validated requirements. The engineer waits for a spec. Retreat is comfortable. Retreat is also how you miss the real problem.
The X-shaped person doesn't have a lane to retreat to. They have to hold the whole thing. That's uncomfortable. It asks you to carry product questions into a design conversation, bring GTM instincts into a research session, and push back on the roadmap when the data doesn't support the assumption yet. Most people can't do that for long without losing confidence in themselves.
X-shaped people are trained by necessity to stay in the fog longer, move at 70% confidence, and triangulate truth from across design, product, tech, and GTM simultaneously. They're not lost in the trees. They're the ones who can see the forest and help others get through it.
What sitting in the pain actually looks like
It's not a philosophy. It's a practice. And it's unglamorous.
It looks like running user interviews when you already think you know the answer, and being wrong. It looks like pushing back on the roadmap because the signal isn't there yet. It looks like saying "we're not ready to build this" when the team wants to ship. It looks like noticing what customers don't say as much as what they do. And it looks like ruthlessly prioritizing the two or three pains that actually matter, and letting go of the rest.
None of this shows up in a sprint review. It looks like slowness from the outside. It feels like friction from the inside. But it's the work that separates durable products from features that get deprecated six months after launch.
Suffering is the curriculum
Here's the part nobody puts in the framework deck.
Innovation work will ask you to hold uncertainty for longer than is comfortable, lose confidence regularly, make calls without full information, and occasionally be very wrong, in public. GASP*
The people who can tolerate that, who treat the discomfort as a signal to dig rather than failure, are the ones who eventually find the real problem underneath the assumed one.
That's not mysticism. That's pattern recognition earned through friction. Every no you've heard, every pivot you've had to make, every time you thought you had it and didn't — that's the curriculum. You don't get to skip it. Neither does your team. Easier said than done, but it doesn't make it less true. Do you subscribe?
The founders and builders who earn real MOATs aren't the ones who moved the fastest. They're the ones who stayed in the room with the problem long enough to actually understand it.
The MOAT is earned, not shipped
The MOAT isn't in the roadmap. It's not in the stack. It's in the team's willingness to stay uncomfortable long enough to earn real understanding. Find those people. Be the person who does the concierge manual work when everyone else rushes to ship. Get told no. Sit with that no and the self-doubt that comes with it. The build rate will follow.
This is Part 8 of an ongoing series on X-shaped people and the future of innovation teams. Read Part 1: The X-Shaped Individual: Solving for Problems in 3D and Part 2: It's Only Through Doing That You Become: How X-shaped people are made — and how teams can grow them and Part 3: Your Design System Isn't a Style Guide Anymore — It's AI Infrastructure and Part 4: How Do We Price Human Judgment When 5 Hours Turns Into 30 Minutes and Part 5: Architecting Adoption: How Design Systems Survive Like a Language and Part 6: When the Truth Isn't Absolute: Managing Variance Across Design, Code, and Docs and Part 7: We're Teaching AI to Read Context, then Forgot to Tell Each Other.
Thu Do is a hands-on product owner with 10+ years bringing products from 0-to-1 across startups, Fortune 500 consultancies (BCG, PwC), and innovation studios. She helps early-stage to early-growth companies ($1-10M ARR) and innovation teams turn big visions into competitive market-ready products and services through human-centered design, product alignment, and AI innovation. This article originally appeared on Thu's Tech Dialect. Find her on LinkedIn.
Co-created with ClaudeCo-created with Claude