How to run productivity innovation

Productivity innovation is a job inside the company that takes less time, or creates less waste, after the change. People have to use the new way on an ordinary Friday. A new app by itself is not that.

This is why so many of these projects feel busy and change nothing. The software is bought first. The number is hunted for later. Do it the other way. Name one job. Time last week. Write the number that would make you stop. Then change the work.

We will not sell you a transformation of the whole company. Pilot is one job, live, with a number you can read in two weeks. It costs $3,500. If you do not have last week’s hours yet, Spark is $750 and the written answer is whether the job is worth building at all.

Count the job, not the meetings

It is easy to count the wrong things: ideas, workshops, tools rolled out, projects “in progress.” Those tell you the team was occupied. They do not tell you whether Tuesday got shorter. The useful numbers are on the job itself. Hours in. Hours out. How long people waited. How much was thrown away. And whether the old way is still the real way.

Busy is not the same as useful. If you cannot say how many hours last week went to the job, and how many went to the meeting about the job, you do not have a starting number. Do not pay for a build on a feeling.

Where software that acts on its own fits

It fits when someone spent last week repeating the same preparation. A draft. A sort. A first pass on a queue. It should not spend the company’s money or send the message. A named person still does that. The time you get back is the afternoon they used to spend preparing. The approval is how a mistake does not go out on Monday.

Start with last week’s hours

Pick one job and time it for five working days before anyone mentions a tool. Write the hours, where it waited, and what “done” meant. Then write the number that would make you stop. If the people who do the job cannot give you last week’s number, you are not ready to buy software.

A useful reply names that one job, a date, and a check on Friday. Or it says no. A list of platforms is not an answer.

The sequence

Do these in order. Skip a line and you are back to a workshop.

1. 01

   Pick one job

   “The company is slow” is too big. A dispatch sheet, a claims queue, or a close that takes all day is a job you can time.

2. 02

   Time last week first

   Write down the hours, the waiting, or the waste before you look at any software. Without that number, the only thing you can say later is that people felt busy.

3. 03

   Decide what “better” means

   If the hours have not moved by a date you choose, stop. A project with no stop date turns into a tool you pay for every month.

4. 04

   Change the work, then the software

   If the steps are the same and you only added a login, people are typing in a new place. The work itself has to get shorter.

5. 05

   Keep a person on money and messages

   Software can draft the refund, the email, or the booking. A named person still sends it. Faster is only useful if a mistake can still be stopped.

6. 06

   Look again on Friday

   If people went back to the spreadsheet, the change did not stick. Using the new way is the result. An announcement is not.