How to Uncover “Shadow Projects” That Are Secretly Draining Your Company’s Budget

Leadership had one pipeline. The company had several tributaries.

A shadow project is sustained change work consuming shared capacity without entering portfolio demand.

Follow capacity and money

Review small vendor contracts, contractor invoices, overtime, recurring “working sessions,” new software subscriptions, and requests to shared analysts or developers. Ask department heads what initiatives their staff support that do not appear in the portfolio.

Start with how to stop stakeholders from bypassing project requests when the unofficial work is visible. Use this audit when leadership does not yet know which departments, invoices, and recurring meetings are carrying it.

Do not begin with accusation. Shadow work often exists because official intake is too slow or too large for the request.

Separate projects from operations

Recurring service belongs in operational capacity. Time-bound work changing a process, system, policy, or customer experience belongs in demand. Put the latter into software project intake.

One review uncovered a six-month “reporting task” that used three departments every Friday. Nobody had called it a project, so nobody had approved its cost.

Repair the door that was bypassed

Create a lighter track for small work, then require every track to reach capacity planning. Use the free Project Intake Evaluation Worksheet to map the channels where budget currently disappears.