Examples Who's supposed to be running this project?
Who's supposed to be running this project?
There's a technical project underway, and no one inside your organization has the time, context or mandate to actually keep it moving.
The technology here is usually fine. What's missing is someone whose job includes noticing that the project stalled and doing something about it, rather than everyone assuming it's someone else's turn.
If the work turns out to have a clear beginning and end, that's a sign it's actually a Solve for U project wearing a capacity problem's clothes. Otherwise, this is exactly the kind of ongoing, unglamorous ownership Add Capacity+ exists for.
- Vendors are waiting on a decision that's stuck between two departments
- The last update was "we're still looking into that," several weeks ago
- Whoever's closest to it is doing it on top of an already full job
- Nobody could currently explain the full state of the project if asked today
- Get a clear, current picture of where the project actually stands
- Take ownership of the vendors, deadlines and open decisions
- Push the stuck decisions to the people who can actually make them
- Keep the work moving between the monthly check-ins, not just during them
- Document the state of things as it goes, so the project never depends on one person's memory
Add Capacity+ Reserved monthly capacity
For ongoing technical work that doesn't justify another full-time position. A reserved block of time each month, used however the month requires.
Technical help, without the usual boundaries.
Tell me what's going on. “No” is in my vocabulary. If it isn't something I should take on, I'll say so.