Business The Speed Of Thought

Why Most Small Business Owners Misread This Book

Michael Gerber's Business The Speed Of Thought isn't a book you finish once and shelve. It's the follow-up to The E-Myth Revisited and it hits different because it deals with what happens after you've already got the operating system running. The core argument is that information speed determines competitive advantage, and in 2007 when it came out, that was more provocative than it sounds now. Today it's just background noise, but the mechanics Gerber lays out still apply if you ignore the buzzword-heavy packaging. Gerber organizes the book around five pillars: vision, knowledge, information, time, and money. He calls it the speed triangle, though honestly it's more like a hub system where information flows between each point. The idea is that your business moves at the speed of the slowest node in that network. Most owners I talk to focus on the wrong node. They pour money into CRM software and call it a speed upgrade, then wonder why their revenue doesn't change. The counter-intuitive part nobody emphasizes enough: having faster information doesn't automatically make you faster as a business. You can have real-time data flowing through dashboards and still make decisions based on whatever your most vocal customer shouted yesterday. The book's actual contribution is the distinction between information and knowledge. Information is raw data. Knowledge is information that has been processed through your operational framework. You can drown in information and starve for knowledge, which is exactly what happens at scale.

Here's what I learned the hard way running my own operation through the mid-2010s. We implemented a full-stack ERP system that gave us real-time inventory, order tracking, and financials. Cost us roughly $85,000 over two years in licensing and integration. Revenue per employee actually dropped twelve percent in the first six months. Not because the system was bad. Because our people didn't know what questions to ask the system. We had information speed but zero knowledge infrastructure. I spent about three months rewriting standard operating procedures to match the new data points the system was generating, then another two months retraining staff on how to interpret them. After that, revenue per employee climbed back up and exceeded the previous peak by around eighteen percent over the next fourteen months. The ERP wasn't the bottleneck. Our inability to convert information into decisions was. One thing Gerber handles better than most business writers is the time-money-information tradeoff. He maps it as a matrix where each corner competes for your attention. A startup typically operates in the information-poor, money-poor, time-dense zone. That's fine. A growing business hits the money-poor, information-dense, time-poor trap and that's where things go sideways. I've watched three separate companies I've consulted with get crushed there because the owner assumed more information would solve their problems when what they actually needed was to invest time in building systems that filtered and acted on that information. There's also the knowledge management angle that gets glossed over. Gerber mentions tacit versus explicit knowledge but doesn't push it far enough for practitioners. In my experience, the explicit knowledge transfer is the easy part. Documenting processes, creating checklists, building wikis. The tacit side is where most implementations fail. Tacit knowledge is the stuff your senior people know but can't articulate. The gut feeling about which suppliers to trust, the pattern recognition for when a client is about to churn, the timing instinct for hiring. You can't digitize that through a Business The Speed Of Thought exercise alone. It requires deliberate mentorship structures and observation-based training that most owners skip because it's uncomfortable and slow.

The practical application boils down to a few steps that are simpler than the book makes them sound. Map your current information flows. Not your ideal flows, your actual flows. Track where data enters your business, where it sits stagnant, where it gets lost, and where decisions are made without adequate information. Then identify your knowledge gaps. What do you know that you can't teach anyone else? What decisions keep getting made reactively because nobody has the right information at the right time? From there you prioritize interventions by impact on the speed triangle, not by how exciting the technology is. A well-maintained spreadsheet shared across your team beats a poorly configured Slack channel every time. I've seen it happen repeatedly. Owners chase the shiny tool because it feels like progress. It isn't. Progress is when a decision that used to take three days of back-and-forth emails now takes forty-five minutes because someone built a clear process around the information flow.

Where the Approach Breaks Down

Business The Speed Of Thought works well for service-based and light manufacturing businesses in the $500,000 to $20 million range. It breaks down outside that window. If you're running a capital-intensive operation with long production cycles like industrial fabrication or construction, the information speed model compresses reality too much. Your bottleneck is physical capacity, not information velocity. Throwing more CRM or ERP at a scheduling problem won't make concrete pour faster. The book also assumes a certain baseline of operational maturity. If you haven't yet documented your core processes or stabilized your revenue streams, reading this won't help much. You'll recognize the concepts but lack the infrastructure to implement them. In those cases, The E-Myth Revisited is the stronger starting point. Get your franchise prototyping right first. Then come back to the speed layer. Another limitation worth noting: Gerber's framework treats technology as neutral infrastructure. It isn't. Platform dependencies create real risks. When your information speed depends on a third-party SaaS provider and they have an outage or change their pricing model, your entire speed triangle shifts overnight. I've seen this happen to two clients. One lost access to their customer database for eleven hours during a payment processing failure on the vendor side. The other got hit with a 40 percent price increase after a funding round and had to migrate their entire data set to a cheaper platform, which took six weeks of downtime. Neither had built an exit strategy into their information architecture.

There's also the organizational resistance factor that the book barely addresses. Speed of thought initiatives require transparency that most middle managers don't volunteer for. When information flows freely, hidden inefficiencies become visible. People who benefited from information hoarding push back hard. I've watched competent operations managers torpedo speed projects simply by not responding to requests for their workflow documentation. The workarounds are usually political, not technical. You need executive sponsorship that's willing to enforce participation, not just encourage it.

A Practical Walkthrough

Here's how I run a speed assessment for a client, stripped down to the essentials. Week one is mapping. I sit with the owner and walk through every major process in the business, starting with revenue generation and working backward through fulfillment, support, and administration. For each process I note where information enters, where it moves, and where it exits as a decision or action. This usually takes about six to eight hours across three sessions. The output is a set of flow diagrams that look ugly but reveal the friction points immediately. Week two is gap analysis. I compare the mapped flows against industry benchmarks and the owner's stated goals. Where are decisions being made without sufficient data? Where is data sitting unused? How long does information typically take to travel from source to decision point? This is where the time-money-information matrix becomes useful. Most gaps cluster in one or two areas, which tells you where to focus. Week three and four are intervention. This is the implementation phase where you pick three to five high-impact fixes and execute them. Common fixes include automating data entry to eliminate manual transcription delays, creating shared dashboards for metrics that multiple departments need, establishing weekly information review meetings, and writing or updating SOPs for processes that rely on tribal knowledge. Each intervention should have a measurable before-and-after metric. If you can't measure the improvement, you haven't picked the right intervention.

The whole cycle typically takes six to eight weeks for a business with under fifty employees. Larger operations stretch to twelve to sixteen weeks. Cost varies widely depending on whether you run it internally or bring in outside help, but the internal route usually works if you're disciplined about time boxing the assessment phase. The biggest mistake I see is letting the mapping stage drag on forever. Two weeks max. If you need more time than that to understand your own business, you have a deeper problem than information speed. The downloadable resources Gerber references through his website are adequate but thin. The speed triangle worksheet is useful as a starting point. The knowledge management templates are more generic than helpful. For anything beyond the basic framework, I'd recommend building your own tools rather than relying on off-the-shelf templates. Your business has specific information flows that no generic template will capture accurately. A simple Airtable base or Notion database mapped to your actual processes will serve you better than any PDF worksheet. The long-term play here is treating information speed as a continuous improvement discipline, not a project. The businesses that benefit most from this framework are the ones that institutionalize regular speed audits. Quarterly reviews of information flow, annual reassessment of the speed triangle, and ongoing knowledge management through documented processes and mentorship programs. The owners who treat it as a one-time initiative tend to see their gains erode within eighteen to twenty-four months as the business grows and the old information patterns resurface in new forms.