Business management
Project management by people accountable for the outcome
Delivery run by someone whose job is the result rather than the status report — keeping scope, budget and expectations honest while the work is still changeable.
The situation
Green until the week before
Projects rarely fail suddenly. They fail slowly, while the reporting stays optimistic, and the truth arrives too late to act on cheaply.
- Status reports that stay green until a deadline is missed
- Scope growing without anyone deciding it should
- Nobody able to say who owns a decision
- Risks logged once and never revisited
- Suppliers managed by whoever has time
- Progress measured by work started rather than work finished
What it covers
What project management covers
Scope and change control
What is in, what is out, and a change process that makes the cost of an addition visible when it is requested.
Planning and sequencing
A plan built around dependencies and real capacity, rather than a date working backwards to a wish.
Risk management
Risks identified, owned and reviewed, with the uncomfortable ones raised early rather than managed quietly.
Stakeholder management
Keeping the people who need to decide informed enough to decide, and doing it before the decision is urgent.
Supplier management
Holding third parties to their commitments, including us.
Honest reporting
Status that reflects reality, including when reality is unwelcome. That is the whole value of the role.
How we work
How we run delivery
Establish the shape
Objective, scope, constraints, decision-makers and what success will be measured by.
Plan against reality
Sequence the work around actual dependencies and available capacity, including yours.
Run and report
Deliver in increments, report honestly, and escalate early enough that there are still options.
Close properly
Handover, documentation and a review of what actually happened, which is where the next project gets cheaper.
Outcomes
What you are left with
- A plan built on dependencies rather than a desired date
- Scope changes visible and costed at the point of request
- Risks raised while there is still time to act on them
- One person accountable for delivery rather than several partly
- Suppliers held to their commitments, ourselves included
- Status reporting you can act on rather than reassure yourself with
Common questions
Questions we are usually asked
Often you would not. Where we are usually asked to help is when a project spans several suppliers, needs technical judgement to challenge estimates, or has reached a point where an outside view is more useful than another internal one.
Whichever suits the work. Fixed regulatory scope with a hard date is genuinely better planned up front; evolving product work is not. Being dogmatic about either is a stronger predictor of failure than the choice itself.
By making the cost visible at the moment of the request rather than absorbing it quietly. Most scope creep is not unreasonable demands; it is reasonable additions whose cumulative cost nobody was tracking.
Then the first job is an honest assessment of where it actually is, which is usually different from where reporting says. That can be uncomfortable, and it is much cheaper than continuing on a plan everyone privately knows is wrong.
Less than running it yourselves, but not none. Decisions still need making, and a project manager who never needs anything from you is not managing your project.
Yes. Managing delivery from other suppliers is common, and being independent of the build sometimes makes the challenge easier to make and easier to hear.
Talk to someone who has built this
Not a salesperson working from a form. Tell us what the problem looks like and someone who has delivered this kind of work will come back to you, usually within one working day.
Book a free consultationRelated
Where this usually connects
- Business analysisMapping how the work actually runs before anything is built.
- Change managementGetting a new system actually adopted rather than merely delivered.
- Agile and DevOpsShorter release cycles and a build pipeline you can rely on.
- Application development and maintenanceBuilding it, then keeping it running and current.
- Business automationTaking the repetitive administration out of a process.
- Bespoke business applicationsSoftware shaped around how you work, when nothing off the shelf fits.