What the Field Taught Me That No Business Book Did
Every founder I know has a shelf full of business book classics — from Good to Great to Zero to One. I’ve read most of them. They’re valuable. But the most important lessons I’ve ever learned about building companies didn’t come from any business book. They came from the field — from real customers, real failures, and the kind of high-stakes decisions that no case study can fully simulate.
Lesson 1: Customers Lie (Not Maliciously)
Every business book will tell you to listen to your customers. What they don’t tell you is that customers often say what they think you want to hear — or what sounds good in theory — rather than what they’ll actually do. In building Muvr, we ran early surveys where people said price was their top priority. Then we launched and discovered that speed and trust mattered far more. The field revealed what no business book predicted: revealed preferences are different from stated preferences. Watch what customers do, not just what they say.
Lesson 2: Momentum Is a Real Asset
Business books talk about strategy and execution. Few of them adequately capture the role of momentum — the felt sense of a team that believes things are working. Momentum is contagious and fragile. When a team is winning, small things that would normally cause friction get absorbed. When momentum breaks, small things become big problems. Managing the emotional energy of a team is one of the most important operational skills a founder can develop, and I’ve never read a business book that covers it well enough.
Lesson 3: Relationships Are the Actual Infrastructure
No business book adequately prepares you for how much of business runs on trust between specific people. The deal that gets done because of a phone call. The investor who passes but makes an introduction that changes everything. The vendor who goes above and beyond because they actually like you. Relationship capital compounds over time in ways that don’t show up on any cap table, but it’s often the deciding factor between outcomes that look similar on paper.
Lesson 4: The Org Chart Doesn’t Reflect Reality
In any real organization, the actual decision-making structure looks nothing like the org chart. There are informal influencers, trusted advisors, and people whose buy-in matters enormously even if their titles don’t reflect it. Learning to read and navigate these informal power structures is a field skill that no business book teaches — because every organization’s informal map is unique. For more leadership thinking from Rico Suarez, visit the topics page.
Read every business book you can get your hands on. Build mental models, study case studies, absorb frameworks. But remember: the field is the real teacher. Books are just the pre-work. For curated recommendations on the most impactful business reads, Farnam Street’s reading list is one of the best resources available.
I have read the books.
The frameworks. The case studies. The playbooks about scaling, about product-market fit, about building teams and culture and operational leverage.
Some of it is useful. Most of it is incomplete. All of it is missing something the field has that no book can replicate: the weight of consequence.
When you read about a problem, the stakes are zero. When you are standing in the middle of one, the stakes are everything. And that difference — the gap between reading about pressure and being under it — changes what you learn and how deeply you learn it.
What the field taught me about customers
Books will tell you that customers want a good product at a fair price.
The field taught me something more specific: customers want to feel like someone is handling it.
Not perfect execution. Not a flawless outcome. They want to feel that the person they trusted with their belongings, their time, their day — is actually in their corner. That if something goes wrong, it will not go silent. That they are not alone in this.
That insight changes everything about how you design service. You stop optimizing for the ideal scenario and start designing for the moment when things get complicated. You build communication first, not as an afterthought. You make accountability visible, not invisible.
Because what customers remember is not that everything went perfectly. What they remember is how they felt when something went wrong and how fast someone made it right.
What the field taught me about workers
Books will tell you to hire people who fit your culture and give them the tools to succeed.
The field taught me that most platforms in this industry have never genuinely tried either of those things.
The workers doing physical service — moving furniture, carrying appliances up stairs, loading trucks in heat and cold — are some of the most underestimated people in the labor market. The best ones are exceptional. They have physical intelligence, situational awareness, and a customer-facing presence that most white-collar workers could not replicate under the same conditions.
And the industry treats them like a commodity.
Unstable pay. Unclear expectations. No support when jobs go sideways. No recognition when jobs go well. No investment in their development or their dignity.
That is not just wrong. It is strategically stupid. Because if the worker loses, the platform loses. Every time. There are no exceptions to this rule.
Building Muvr means building a platform where the worker’s success is structurally connected to the platform’s success — not just in theory, but in the actual design of how jobs are assigned, how standards are set, how quality is measured, and how people are treated when things get hard.
What the field taught me about operations
Books will tell you that operational excellence is about process documentation and continuous improvement.
The field taught me that it is actually about information flow.
Most operational failures in service businesses are not caused by people who do not care. They are caused by people who do not know. The crew did not know the building had a loading dock restriction. The customer did not know the crew was running late. Dispatch did not know that the job description was wrong and the crew would need different equipment.
Information gaps are where chaos lives.
The operational work that matters is not building a great manual. It is designing a system where the right information reaches the right person at the right time — before the problem becomes a crisis.
That is a technology problem. It is a UX problem. It is a data problem. And it is something I only understood clearly after watching it fail in the field, repeatedly, in ways that were always preventable in hindsight.
Why the sequence matters: field before product
I started in the field before I started building the product.
That sequence was not a coincidence. It was a choice, and it was the right one.
When you build from the field, you carry specific knowledge that changes every product decision. You know which problems are real and which ones are theoretical. You know which solutions will work under pressure and which will fall apart the moment a real human is under stress. You know where the system needs to be forgiving and where it needs to be rigorous.
You build differently when the problem is in your bones, not just in your notes.
That is what the field gave me.
No book comes close.