A task is a unit of work with an end.
Write the page. Send the quote. Ship the feature. Close the ticket.
Tasks are how people stay sane. You need them. I use them.
A business that only thinks in tasks will still feel like it is starting from zero every Monday — because the learning did not survive the tick.
A loop is a task plus what it does to the next one.
Same people. Different design of the work.
Heroes are a system smell
I have been the person who “just handles it.”
It feels like care. It is also how a company trains itself to need you.
When the same fire is put out by the same person for the third month, you do not have a people problem. You have a loop that only closes in one head.
The move is not to stop caring. It is to turn the save into an improvement: a default reply, a clearer offer, a step the next person can run without asking you.
People still matter. Taste still matters. Judgment still matters. Loops are how those things scale without turning everyone into a bottleneck.
Interactive · Same work, two designs
Done means checked off. The knowledge stays with whoever did it. Next week, a similar request starts from scratch. The company paid for the work once and threw away the learning.
Done means checked off and the next similar case is easier: a note went back to the page, the script, the product, or the playbook. The people are the same. The system got a little smarter.
Diagram · What you are actually buying
Task thinking
Hours, tickets, campaigns, deliverables. Progress looks like volume.
Loop thinking
Each output is an input to the next activity. Progress looks like less heroism next time.
Volume can go up while the business stays just as hard to run. Loops are how effort turns into leverage.
Ownership changes when the unit changes
If you own a task, you own a moment.
If you own a loop, you own a cycle: you are responsible for the quality of what comes back, and for what we change because of it.
That is a harder job description. It is also the only one that compounds.
A content person who owns a loop does not only publish. They watch what the publish did to search, to sales questions, to support. Then the next piece is aimed.
A salesperson who owns a loop does not only close. They return the pattern of objections to the offer and the page.
An engineer who owns a loop does not only ship. They watch whether the ship reduced a queue or created a new one.
None of this requires a new title. It requires a different question in the room: after this is done, what should be easier?
From here, a name
Once you see work as loops, you need a single logic you can repeat — or every function will invent its own language again.
Input. Process. Output. Feedback. Improvement.
That repeating logic is what the next chapter names: the Digital Loop.
Not a stack of tools. A way of designing the business so people and tasks sit inside a system that can learn.