How we think about improving a business

Before recommending anything, look at how the work really moves today, not how it's supposed to move on paper. Most businesses already know something feels off. Far fewer have actually watched the workflow closely enough to say why.

Not every problem deserves equal attention. A business usually has one thing quietly limiting the rest, more than it has ten equally-important problems. The job is finding that one thing, not producing a long list of everything that could theoretically be better.

A symptom rarely lives in isolation. Look at the system it sits inside, the capabilities involved, the workflow that actually carries the work, and what's currently implementing it - a person, a spreadsheet, a piece of software. Fixing the wrong layer wastes effort even when the fix itself is well executed.

Manual work is not inherently bad. Owner involvement is not inherently bad. If something is quietly doing its job - even if it looks unsophisticated - removing it in the name of modernizing is a real cost, not a free upgrade. Don't optimize away a human activity that's creating value nobody asked to lose.

Automation is not inherently good, and neither is any other technology. The right implementation is the one that reliably supports what the business actually needs - nothing more. Often that's a clarified owner, a checklist, or a small process change, not a new system. Sometimes the correct answer is to leave something alone.

A change that isn't checked is just a guess with extra steps. Use evidence and feedback from how the business is actually running, not an assumption that the change must have worked because it shipped.