Getting 1% Better: Small Progress and Protecting Your Baseline
I try to get 1% better every single day. But when additional progress isn't realistic, my starting point is simpler: protect the essentials. For a service business owner, that means knowing which commitments need attention before adding another improvement project. On the days that feel really, really tough, at least maintain.
By Eric Yim. Published by Protocol Text.
What the 1% compounding story actually shows
In the interview, I used a dollar growing by 1% every day to explain how small improvements can build on each other. The arithmetic in my spoken illustration needed correcting. Here's the mathematical clarification.
Compounding means each increase applies to the new total, including earlier increases. Start with $1, multiply it by 1.01 every day, and after 365 days the calculation is 1.01^365, approximately 37.78. That dollar becomes $37.78.
If that exact daily rate continued, using 365 days per year, the end-of-year amounts would be:
- Year one: $37.78.
- Year two: $1,427.59.
- Year three: $53,939.17.
- Year four: $2,038,007.24.
- Year five: $77,002,912.75.
- Year six: $2,909,434,497.35.
- Year eight: about $4,153,473,513,320.
Those enormous later numbers expose the limits of the assumption. This is a mathematical illustration, not an investment forecast or a promise about business growth. A fixed daily percentage doesn't describe how a person learns, how a team improves, or when marketing produces results.
The useful part is that earlier work can support later work. A clearer process can make the next task easier. But some changes don't help, some need revising, and some days don't produce an improvement you can identify. As I acknowledged in the interview, getting 1% better every day probably isn't possible.
Why losing ground takes extra work to recover
My spoken explanation of recovering from a 1% loss also needed a correction: the required gain is approximately 1.0101%, not 2%.
The difference is easier to see with a larger loss. Start with $100 and lose 50%. You have $50 left. Getting back to $100 requires gaining $50, which is a 100% gain on the remaining balance.
The ending $100 is twice the remaining $50, or 200% of that balance. That doesn't make it a 200% gain. A 200% gain on $50 would add $100 and leave you with $150.
The percentages change because the starting amount changes. That's the loss-recovery asymmetry: a loss and an equal percentage gain don't cancel each other out.
I wouldn't assign those percentages to a difficult workday. Missing a task doesn't mean you've become 1% worse. The practical reason to protect essential work is that repairing an avoidable problem can take time away from whatever you wanted to improve next.
Separate the big vision from today's work
I think useful solutions come from balancing “thinking in the macro and thinking in the micro.” The macro is the big vision. The micro is the day-to-day detail, the nitty gritty stuff that needs to get done. That balance helps you decide when to move fast and when to slow down.
For a hypothetical service business, the vision might be handling inquiries more reliably. An improvement task could be drafting a clearer reply template. Maintenance could be answering an existing inquiry when a response is due.
If there's only time for one of those tasks today, I'd prioritize the existing commitment over the new template. The template may help later, but it doesn't answer the person waiting now.
This distinction also keeps a big goal from becoming an impossible daily assignment. You can keep the vision while choosing a much smaller piece of work for today.
Define what maintaining actually requires
“At least maintain” needs a concrete meaning. Otherwise, it's easy to stay busy without protecting anything important. I'd suggest writing down what must remain true, who owns that responsibility, and what a completed minimum looks like.
Using the hypothetical inquiry example, the commitment might be that someone awaiting a promised response gets an accurate update. Assign one person to handle it. The minimum could be a reply that answers what can be answered now and states a realistic next step.
Opening the inbox wouldn't complete that minimum. Neither would drafting a reply that never gets sent. Define completion by the commitment being handled, rather than by the amount of activity around it.
Keep the baseline small enough to guide a hard day. If it contains every improvement you hope to make, it won't help you choose. Start with commitments that would create a real problem if neglected.
“At least show up” is the phrase I come back to. Days have different capacity. Showing up may mean doing the essential work, asking someone to cover it, or communicating that a commitment needs to change. It doesn't require pretending you have a full day's energy.
FAQ
Can I use this idea if improvement is irregular rather than daily?
Yes. I'd use it as a reminder to build on useful work, without assigning yourself a daily percentage. Some improvements take several attempts before they help. Look for what you can carry forward into the next task, and don't treat an uneven pace as proof that the effort failed.
What if an essential task is larger than the time I have today?
Identify the immediate commitment and communicate a realistic next step to anyone depending on it. Then choose the smallest meaningful part you can complete. Be clear about what remains unfinished. A short update may protect a commitment, but a token action doesn't make the whole task complete.
Should every small improvement become a public post?
No. Many useful improvements belong in operations, where they help the work get done. I'd publish only when there's something accurate and useful for the audience to learn. You don't need to turn every internal adjustment into content or make a small change sound like a major result.
Can maintaining the old routine ever be the wrong goal?
Yes. If evidence shows a routine is causing problems or no longer serves its purpose, repeating it can preserve the problem. Keep the underlying commitment in view and reconsider the method. Maintaining reliable communication, for example, doesn't require keeping a process that repeatedly leaves inquiries unanswered.