Fix the job your team types twice first: the one that happens every day, starts the same way each time, and moves details from one app into another by hand. It is rarely the most interesting job in the business. That is why it makes the best first fix, because you can count it before and count it again after.
If you have not yet looked at where your team's week goes, start with the one-week list of work no customer sees. This post is the next step: picking the first job off that list.
What makes a job worth fixing first?
Four things at once. It happens daily, so a small saving repeats every day. It has a clear start, such as an enquiry landing or a bill arriving, so everyone can see where it begins. It carries details that already exist somewhere else, so the retyping can go. And it can be counted, so you will know whether the fix worked.
A job with all four is usually dull. Good. Dull jobs are predictable, and predictable jobs are the safest place to start.
Which three questions find it?
Take each job on your list and ask:
- Does it start the same way most days? A new enquiry, a booked job, a supplier bill. If nobody can name the moment it begins, it is not ready to fix.
- Is someone typing a detail that already exists? A customer's name and number copied from an email into the job app, then again into the accounts. Every copy is another chance for a typo.
- Can you count it this week? How many times it happens, and roughly how long each one takes. If you cannot count it before, nobody can show the change worked after. Count one thing covers which number to pick.
The job with three yeses goes first. When two jobs tie, pick the one nearer the customer. Retyping that sits between an enquiry and a quote slows the reply as well as the team, and the reply is where the next job is won.
What does the retyping cost?
Minutes first, then mistakes. A few minutes each time is easy to ignore, until it happens many times a day, every day, across several people.
The mistakes cost more. One wrong digit in a phone number means a customer who never hears back. An old email address means a quote nobody reads. Neither shows up anywhere until the customer goes quiet.
There is an Australian price on one version of it. The ATO says paper and PDF invoices generally cost $27 to $30 each to process, that eInvoicing can bring this to less than $10 an invoice, and that a business receiving eInvoices does not need to scan and manually enter them into its software (ATO, benefits of eInvoicing). The page does not say where its figures come from. Read them as a guide.
Who knows where the retyping is?
The person doing it, and usually within a sentence. We learned this building an enquiry desk for an air conditioning installer in Melbourne.
He read how the desk would work and stopped on one line. He quotes every job from his job app. As we had it, a new customer only reached that app once the job was won. Until then, he would be typing each customer's name, number, email and address into it himself, for every enquiry he wanted to quote.
He asked for those details to land in the job app the moment an enquiry arrives, without waiting for the customer to reply to anything. We had put the fix at the end of the job. He wanted it at the start, where the job begins and every later step can read from it. He was right, and we changed the design.
Two things came out of that. Ask the person who does the typing before anyone designs anything, because they already know. And fix the retyping at the point where the work starts.
Where does choosing go wrong?
In four places:
- The interesting job. The one with a clever idea behind it, or the one the loudest person complains about, picked ahead of the one that happens every day.
- The end of the job. Fixing the last copy and leaving the first, as we nearly did.
- Paying for what you already have. Check the settings and connections your apps already offer before anything is built. Supplier bills are the clearest case: if your accounting software can send and receive eInvoices, that retyping may only need switching on.
- No before number. Without one, the first fix becomes a matter of opinion, and the second fix never gets agreed.
When should you leave it alone?
When the job happens once a week and takes a few minutes. Rare jobs repay slowly, and your first fix should pay back quickly enough for the team to notice.
Leave it, too, when the person retyping is also deciding as they go: checking a price, choosing which job a note belongs to. That is judgement. It stays with a person.
One step for this week
Take the three jobs that came up most on your team's list and ask each one the three questions. For the job that scores highest, count it for five working days: how many times it happens, and how long each one takes, including the checking. Write the number where you will find it in a month.
Enquiry to quote to booking, without retyping a thing, is one of the eight things we build. See it in section 02.

