Writing
Do Hard Things Before You Automate Them
May 8, 2026
AI and automation are most useful after you understand the work well enough to know what should disappear.
The spreadsheet is ugly, which is often why it is honest. Somebody has a column called “check this manually.” Somebody highlights rows in yellow because the system cannot explain the difference between urgent and merely loud. Somebody keeps a second tab because the official report lies just enough to be dangerous.
The first instinct is to automate it. Clean it up, build the workflow, add AI, and make the humans stop touching the messy thing.
Sometimes that is right. Often it is how a team turns confusion into infrastructure.
The hard part of a workflow is rarely the clicking. It is the judgment hiding inside the clicking. Why does support check that field before replying? Why does ops distrust the report? Why does the founder still keep a spreadsheet next to the product they paid to build?
If you automate before you understand those decisions, you preserve the mess and make it harder to see. AI raises the stakes because automation now feels available everywhere. Summarize this. Classify that. Draft the response. Generate the report. Route the ticket. Those can be useful tools, but they can also become bad excuses.
The better order is less glamorous. Do the work by hand. Watch someone else do it. Write down the exceptions. Notice where people pause. Find the moment where the rule stops working and taste begins. Then automate.
That is where AI gets powerful. It can remove repetitive surface area while keeping the human judgment that creates value. It can make an expert faster without pretending expertise is just a better prompt.
For founders, this is a discipline problem. Nobody wants to tell investors the next smart move is a better spreadsheet, a concierge flow, or a boring review queue. But manual work is often the shortest path to a real system. It teaches the product what the business actually does. It exposes the hidden requirements. It stops the team from spending months polishing an abstraction over a process they never understood.
The goal is not to avoid automation. The goal is to deserve it.