Before starting a company, I spent time reading about business. In the original February 2024 version of this article, I described a year of reading 100 books. The number made a good headline. It did not tell the reader what the reading was useful for.
A long reading list can leave you with a vocabulary for entrepreneurship and no clearer idea of what to do on Monday. You can talk about differentiation, persuasion and scale while a customer still cannot work out what your offer includes.
Here is the more useful way to revisit that reading: take a few ideas, turn them into questions, and show what answering those questions could change. The examples below are applications of the ideas, not claims that a book produced a measured result for Sparrow.
Start with a decision you actually need to make
Suppose you run a small service business and are considering a new website. You could read widely about branding, sales and customer experience. First write down the decision: “Do we need a different website, or does the existing one need a clearer service page and a working contact path?”
That question gives the reading somewhere to land. It also gives you a way to reject an attractive idea that does not help with the problem in front of you.
| An idea worth exploring | A practical question | Something you could inspect |
|---|---|---|
| Test an assumption | What are we expecting the new page to change? | The current page and the unanswered customer question |
| Support a claim | What would let a reader judge our work? | A project, document or accurately attributed customer account |
| Understand the work | Where does a request wait or lose its owner? | The handoff from an inquiry to a named next action |
This is a reading method, not a reading challenge. One well-applied idea can be more useful than another finished shelf.
The Lean Startup: give an assumption a fair test
Eric Ries's Lean Startup methodology emphasizes learning through tests of business assumptions. My application is modest: before building more, name the uncertainty you are trying to resolve.
For example, a business might assume that a new service needs its own page because customers keep asking about it. A useful first step is to examine those questions. Are people asking whether the service is available, how it works, or whether the business covers their location?
Each answer suggests a different page. Putting up a generic service description and counting visits would leave much of the original uncertainty unresolved.
The book does not prove which page your business needs. It offers a reason to make the assumption explicit enough to investigate.
Influence: make the evidence easier to judge
Robert Cialdini's Influence includes social proof among its principles of persuasion. For a business website, the practical question is what a reader can actually verify.
“Customers love our work” is difficult to inspect. A permitted customer quotation with an accurate attribution is more concrete. So is a project page that shows the work and explains what was built.
The details must stay honest. A demonstration belongs under a demonstration label. An implemented feature establishes that the feature exists; it does not establish a revenue gain. A persuasive story becomes weaker when it asks the evidence to carry more than it can support.
You can see how Sparrow presents a real implementation on the Poteet Homes project page.
High Output Management: look at the work between the tasks
Andrew S. Grove's High Output Management examines management through the work an organization produces. A small business can take a useful question from that perspective without copying the structure of a large company: what needs to happen between receiving a request and completing it?
Imagine a website inquiry arrives in a shared mailbox. Someone reads it, assumes another person will reply, and leaves it there. Adding a new tool may help, but the missing decision is ownership. Who takes the next action, and how does everyone else know?
That is the kind of issue explored in the article on website inquiries and CRM handoffs. The example illustrates a question to ask; it is not an account of a Sparrow customer failure.
Keep a decision note, not just a book summary
After reading, write a short note with four parts:
- The question: the decision you need to make.
- The idea: what the author suggests looking at.
- The application: one change or investigation the idea supports.
- The limit: what you still do not know, and what would change your view.
If the note only says the book was inspiring, the next action is still missing. If it claims the idea will transform the business, it is probably running ahead of the evidence.
I would keep the curiosity from that early reading effort and put less weight on the count. Read something that helps you see the work more clearly. Then return to the customer question, page or agreement that needs your attention.



