It is late in the day. The shop is closed, or nearly. On the desk there is a pile of paper that did not get filed, an inbox with the same ten questions in it that were there at lunch, a lead who asked for a price this morning and has heard nothing since, and a calendar with tomorrow's appointments half arranged. Every one of those jobs is asking to go first. None of them will wait quietly. The question is not which job matters. It is which job to fix first, when you can only fix one thing at a time.
This article was drafted with AI assistance and reviewed by Abdullah Shafique, founder of Elarigent, who takes editorial responsibility for it. It is written in plain English for people who run businesses, not for people who build software, and it makes no claim about any particular product. It is the last of four short articles in a week of asking that question in public, and it reports what came back honestly, including the parts that did not go as hoped.
What we asked
For six days, from 24 to 29 October, a short post went out each morning naming one job. The fastest reply usually wins the customer, so follow-up first. Your inbox is not a to-do list, it is a queue of people waiting. Plain English first, because jargon is a tax on the owner's time. The paperwork pile is hidden payroll. It is 8pm and the same ten questions are still in the inbox. Each post asked, in its own way: which of these eats your day?
The posts went out on five platforms each morning, and an evening post went out on one more. They were read. The counts were small and ordinary for a brand-new account: a handful of views on most posts, rising to the low twenties on a few, no followers on one account, two followers on another. Reading happened. Answering, mostly, did not.
What came back
Almost nothing. That is the honest answer, and it is worth saying plainly rather than dressing it up.
When the replies were checked on the morning of 29 October, every new post from the week showed no replies at all. The older posts, from before this week began, had two replies between them: one genuine reply that had already been answered, and one piece of spam that was left alone. A handful of small signals arrived instead of answers: a like here, a follow there, one person following on a blogging platform. None of them named a job. None of them answered the question.
It would be easy to read a lesson into the silence that the silence does not support. Silence does not mean nobody has the problem. It does not mean the jobs named were the wrong ones. A new account with almost no followers is mostly talking into an empty room, and an empty room answering nothing tells you about the room, not about the problem. What the silence does tell you is simpler: asking in public, once a day, for a week, is not how you learn which job goes first. The asking was the easy part. The learning has to come from watching real days, not from waiting for replies.
What a real day shows
Watch one ordinary day instead, and the order starts to sort itself. The jobs are not equal, and they are not equal in the way people usually rank them. The biggest job is rarely the first job. The most impressive job is almost never the first job. The first job is the one with three qualities at once.
First, it repeats. It happens every day, or most days, so fixing it pays you back tomorrow and the day after, not once. The inbox is like that. The same ten support questions are like that. Chasing an unpaid invoice is like that.
Second, you can check the result in a minute. You can look at what was done and know, without a report or a meeting, whether it is right. A drafted reply you can read before it goes out. A filed document you can find again. A follow-up note with the right name and the right price in it.
Third, nothing leaves the building without you. The job can be prepared, sorted, drafted, and filed, but sending money, sending a message, or making a promise still waits for a human yes. That is not a weakness in the job. It is what makes it safe to start with.
Put those three together and an order appears. The daily queue of messages and questions usually goes first, because it repeats, it is checkable, and it can be drafted before anything is sent. The fast follow-up to a new enquiry usually goes second, because delay there costs a customer in a way delay elsewhere does not, and a drafted reply is easy to check. The paperwork pile goes third, not because it is unimportant, but because filing and finding are slower to check and easier to get wrong in a quiet way. The big, clever job, the one that would change everything if it worked, goes last. It is the job you build toward once the daily jobs are steady, not the job you bet the week on.
None of this is a claim about any tool. It is a way of choosing, and it works with a notebook and a clock just as well as it works with software. The order matters more than the method, because a good method applied to the wrong job first still leaves the inbox full at 8pm.
Four questions before you hand any job over
Before a job is handed to anyone or anything, ask four plain questions. The answers will tell you whether it is a first job or a later job.
First, how often does it happen? If the answer is once a month, it is probably not first, however painful it feels on the day it happens. Second, how will you know it was done right? If the answer needs a second person, a report, or a week of waiting, the job is harder to start with than it looks. Third, what goes out without you? If money, messages, or promises can leave before you have seen them, the job needs a human step in the middle, every time. Fourth, what can it touch? A job that only reads and drafts is a smaller risk than a job that can reach the bank account, the whole contact list, and every folder at once.
A job that repeats daily, shows its result at a glance, waits for your yes before anything is sent, and touches only what it needs is a first job. A job that fails any of those tests is not a bad job. It is a later job, once the first ones are working and you have learned what checking them actually looks like.
The short version
We asked for a week which job should go first, and almost nobody answered. That is not a failure of the question. It is a reminder that the answer was never going to arrive as a reply. It arrives by watching a real day: the job that repeats, that you can check in a minute, and that sends nothing without you goes first. The inbox queue, then the fast follow-up, then the paperwork pile, then the big job. In that order, the end of the day gets a little quieter, one job at a time, and the owner keeps the decisions.
Ready-made AI agents for small businesses, built in public.
Top comments (0)