Loading
Because it competes with billable work for the same people, and only one of the two has a client asking about it. Internal projects are planned as though the time exists, and it does not.
So they run for months, everyone feels they are behind, and nobody can point to the week the plan stopped being true.
Internal projects are projects: phases, tasks, owners and dependencies, planned against the same capacity as client delivery.
Because availability comes from Nest with leave already in it, an internal plan that assumes people who are not free is visible before it is committed to.
It will not create capacity, and it will not decide what matters more. It makes the competition visible, which is where the decision should be made anyway.
And it does not track cost against a budget line — that lives in Books, reading the same records.
The trade-off becomes explicit. Choosing to do an internal project means choosing what it displaces, and both sides of that are on one screen.
Delivery risk is derived the same way, so an internal project quietly stalling is visible rather than assumed to be progressing.
If it has phases and competes for people, yes. Otherwise it loses invisibly.
Yes — one availability picture per person.
Yes, in Books against the same records.
We will run it end to end on your own numbers in half an hour, and tell you honestly which parts Treepie does not improve.