Research
Why an AI project can create work before it saves work
Separate reusable setup from repeated friction when an early pilot feels slower than expected.
Zocri · 2 min read · Sources checked
A useful explanation with a dangerous misuse
The Productivity J-Curve research models how complementary intangible investment can affect measured productivity around general-purpose technologies. It offers an economic explanation for setup work that is easy to overlook. It does not guarantee that a disappointing AI project will eventually succeed if the business simply waits longer.
That distinction matters when an owner is paying both the supplier and employees preparing the process. Early effort can create a reusable asset, such as an approved reference or a clear workflow. It can also be repeated repair work that never reduces the next day's burden.
Name the asset being created
For each setup activity, write down what will remain useful afterward. Cleaning customer categories can improve reporting. Documenting an approval rule can help new staff. Repeatedly correcting the same unsupported answer may create nothing durable unless the process is changed so the correction carries forward.
Ask who will use and maintain the asset. A carefully organized document that nobody can find or update should not automatically be counted as an investment merely because it took time to prepare.
Watch the shape of the workload
Keep separate logs for setup and ordinary operation. Setup should produce observable milestones: a verified reference, a working transfer or staff able to complete a task independently. Operational effort should become understandable at a realistic volume.
If the project requires the same manual repair every week, examine that recurring cost directly. Do not hide it inside an indefinitely extended implementation phase. A limited pilot is useful precisely because it reveals whether the proposed operating process is economical.
Set a checkpoint before enthusiasm grows
Choose a date when the team must demonstrate one complete journey using current information. Specify the remaining uncertainties and the evidence needed to resolve them. A checkpoint should permit narrowing or stopping the project, not merely trigger the next purchase.
Keep the lesson even if the tool changes
Reusable preparation can retain value after a supplier is replaced. Keep business rules and source records in a form the team can understand and retrieve. This makes the setup less dependent on one interface and gives future decisions a better starting point.
Our recommendation is to judge early effort by the capability it leaves behind. The J-curve framework explains why visible output can initially lag investment, while explicit checkpoints prevent that explanation from becoming an excuse to continue paying for work that never becomes easier.