Tech
Reporting What Shipped Instead of What the System Became
The picture shows what got done, not what the software is becoming underneath. A status report tells him the feature shipped but hides three things the CEO actually needs: whether the system is getting easier or harder to change, whether the next feature will take a week or a month, and whether the team is shipping fast because the code is healthy or because they are working weekends to keep the brittle mess from falling apart.
The report describes architecture cost, not a list of what shipped.
The Cost of Not Understanding the Technology You're Building On