---
title: A software project can be on time and already lost
author: Giacomo Balli
published: 2026-08-17
url: https://BigBalli.com/blog/a-software-project-can-be-on-time-and-already-lost
tags: Engineering, Product, Leadership, Operations, Data
---

# A software project can be on time and already lost

*By Giacomo Balli* | *Published: August 17, 2026*

A software project can be on time and already lost. Late is the last sign, not the first. These are the ones that show up earlier.

Nobody on your side can demo it. The vendor demos it. Your people watch. If your operations lead cannot drive the current build on real data, you do not know what exists.

The scope document has stopped changing. Real projects discover things. A scope that has not moved in three months means either nobody is looking, or the discoveries are being kept off the record until they arrive as a change order.

The people who will use it have not touched it. The project is being built for the sponsor. Adoption is being scheduled for "training week," which is where adoption goes to die.

Every question gets a good answer. Healthy teams say "we don't know yet" about something. A team with an answer for everything has stopped telling you things.

The integration is still "being finalised." Integration is where projects break, so it is the first thing to prove and the last thing teams want to show. If it is not demonstrable at the halfway point, the second half is going to be about it.

None of these are technical. All of them are visible from the owner's chair, in the weekly meeting, before the schedule slips a single day.

[Discuss on LinkedIn](https://www.linkedin.com/feed/update/urn:li:activity:7504561974014369792)

---

**Tags:** Engineering, Product, Leadership, Operations, Data

---

*View the [HTML version](https://BigBalli.com/blog/a-software-project-can-be-on-time-and-already-lost) of this post.*