Lean ·
The waste software projects keep funding
Lean names for the work that feels productive and changes nothing.
Most software waste is not slow code. It is features nobody uses, handoffs that exist so a status can be copied, and waiting on a decision that was available on the floor the whole time.
Overproduction shows up as a roadmap that outruns what the team has learned. Extra processing shows up as a workflow with twelve statuses for a job that has three real states. Motion shows up as people leaving the system to finish the task in a spreadsheet.
The useful question is not 'what else could this product do.' It is 'which step, if it disappeared, would the customer notice.' Build that. Leave the rest on a list you are willing to throw away.