Waste starts before production.
It usually starts when a team begins work before the decision is clear.
The calendar says the project has begun. The kickoff happened. The document has a name. A designer is exploring directions. A developer is checking feasibility. Someone is drafting copy. A project manager is collecting feedback.
On paper, the team is moving.
In practice, the team may be spending money to avoid a decision.
This happens often in digital work because early activity feels productive. Screens make an idea feel real. Drafts give people something to react to. A prototype can calm a room because it looks like progress.
But production cannot solve every form of uncertainty.
If leadership has not agreed on the audience, the page will sprawl. If no one knows who owns approval, feedback will loop. If the budget is unclear, the scope will keep changing shape. If the internal argument has not been settled, the work will become a substitute for that argument.
The team will call it iteration.
Some of it may be iteration. Much of it is rework.
The common mistake is treating production as the place where alignment happens.
That is expensive. It also puts the wrong pressure on the people doing the work. Designers get asked to resolve business disagreement with layout. Developers get asked to estimate a moving target. Copywriters get asked to make unclear positioning sound finished.
Good production requires judgment, but it should not be asked to carry every unresolved decision.
The better approach is to name the decision that must happen before the work begins.
For a website, that may be the site’s job. For a campaign, it may be the audience and offer. For an AI pilot, it may be the workflow and review owner. For a publishing system, it may be who can approve content and what counts as done.
These are not administrative details. They are the conditions that make the work possible.
A team does not need perfect certainty. It needs enough agreement to protect the people doing the work from noise.
That agreement can be simple.
This is the audience. This is the problem we are solving. This is the decision owner. This is the approval path. This is what we are not doing in this phase. This is how we will know the work is good enough to ship.
Once those points are clear, production can move faster because the team has fewer hidden arguments.
The work may still change. Good work often does. But the changes should come from learning, not from discovering the basic premise halfway through.
There is a useful test for this.
Before assigning the work, ask what decision the team is trying to avoid.
If the answer is obvious, solve that first. If the answer is not obvious, the next step may be a short discovery conversation, not a production schedule.
This is where outside help can be useful, but only if it is willing to be direct. A good outside team should not accept every task as ready. Some tasks need a brief. Some need a smaller scope. Some need leadership sign-off. Some should not be done.
That is not obstruction. It is respect for the work.
Digital production is expensive enough when the plan is clear. It gets much more expensive when the plan is being invented through revision.
Before the team starts building, name the decision that makes the work real.
If no one can name it, production is early.