top of page
Your Project Is Green Until It Isn't: Lessons From the HS2 Reset

Your Project Is Green Until It Isn't: Lessons From the HS2 Reset

4 days ago
5 min read

Most project overruns don't start with a big mistake. They start with small gaps that seem manageable at the time. A budget is still being refined. A key decision owner isn't clear. The team begins work before requirements are stable. Hours are logged late, so costs look better than they really are.

That pattern is one of the clearest lessons from the HS2 reset. The program's challenges weren't caused by one bad week or one missed task. Cost pressure, scope changes, planning assumptions, and delivery complexity built over time. By the time the issues became impossible to ignore, the choices available were much more limited and much more expensive.

A small or mid-sized services firm isn't running a national rail program. But the delivery risks are surprisingly familiar. A fixed-fee implementation can go over budget. A client can request "small" additions every week. Senior consultants can spend too much time on unplanned work. A project can remain green in a status meeting while its margin quietly disappears.

For a VP of Professional Services, the key is not predicting every problem. It's building enough control into delivery that small problems become visible while the team can still act. Here are three practical ways to do that.

A project plan isn't a baseline just because it has dates and tasks. A useful baseline gives the delivery lead a clear point of comparison throughout the project. It should show what the team agreed to deliver, who will do the work, how much effort is expected, what the client will provide, and what financial outcome the project needs to achieve.

Too many teams begin work with only part of that picture. The statement of work may be signed, but the staffing plan isn't confirmed. The project budget may exist, but it isn't broken down by phase, role, or workstream. The project manager may know the target date, but not the assumptions that support it.

That creates a dangerous situation. The team is moving, but nobody can tell whether they are moving according to plan.

Before kickoff, make sure every project has these baseline elements:

  • A defined scope with clear exclusions

  • A work breakdown that connects deliverables to estimated effort

  • A budget by role, phase, or task

  • A planned schedule with key client dependencies

  • A target gross margin or fixed-fee variance threshold

  • Named decision owners for scope, staffing, and commercial changes

  • A documented change control process

This doesn't need to become heavy process. For many SMB services teams, a one-hour internal project readiness review is enough. The goal is to ask simple questions before billable work begins.

Do we know how many consultant hours this work should take? Do we have the right people available? What happens if the client delays a decision? Which work is included, and which work requires a change request?

If the answers are vague, the project isn't ready to start. It may still start because of a client deadline or revenue pressure, but the delivery lead should treat it as a known risk. That risk needs a mitigation plan, not a hopeful status color.

A strong baseline also protects the team when scope creep begins. Without one, every conversation becomes subjective. With one, the project manager can point to the agreed effort, timeline, and deliverables. That makes commercial discussions easier and gives the client a fair, clear view of the impact of requested changes.

2. Track actual effort and cost while there is still time to respond

Projects often look healthy because the team is reporting progress, not performance. A project manager might say that 60 percent of the tasks are complete. But if the team has already used 80 percent of the budgeted hours, the project isn't 60 percent complete from a financial standpoint. It is heading toward an overrun.

This is where real-time delivery tracking matters. Services leaders need to see the relationship between planned effort, actual effort, remaining work, and expected revenue. If those numbers are updated only at month-end, the project may have already lost its margin before anyone sees the warning sign.

The most useful measures are straightforward:

  • Budgeted hours versus actual hours

  • Percent complete versus percent of budget consumed

  • Estimate to complete, based on remaining work

  • Fixed-fee variance

  • Billable versus productive utilization

  • Realization rate for time-and-materials work

  • Unapproved change effort

  • Revenue backlog and expected project revenue

For example, imagine a fixed-fee project with a 500-hour budget. At the midpoint, the team has logged 300 hours but believes only 45 percent of the work is complete. That isn't a minor variance. It means the original estimate, scope, or delivery approach needs to be reviewed immediately.

The right response isn't always to push the team harder. In fact, that often makes things worse. The delivery lead may need to reduce rework, adjust staffing, defer lower-priority items, issue a change request, or reset client expectations. The important point is that the team sees the issue early enough to choose.

Timesheet discipline plays a major role here. Late or incomplete time entry hides reality. Consultants may see time tracking as admin work, but it is project data. Without accurate actuals, a services lead can't understand project health, forecast capacity, or identify revenue leakage.

Set a clear expectation: time should be logged weekly, ideally daily, and coded to the right project and task. Then review project financials on a regular rhythm. Weekly is usually right for active projects. A monthly review is too slow for work that is burning through budget every day.

3. Set decision rights and enforce scope control

The HS2 story also highlights the cost of unclear decision-making. When large choices are delayed, revisited, or made without full cost visibility, the delivery plan becomes unstable. The same issue appears in services organizations when nobody knows who can approve a scope change, add a resource, extend a deadline, or write off hours.

Projects lose money in the gray areas.

A client asks for an additional workflow. A consultant agrees to "take a quick look." A technical lead adds extra configuration to avoid a difficult conversation. A project manager delays raising the issue because the request feels small. Soon, the team has delivered several days of work that isn't in the project budget and isn't covered by a signed change request.

That is scope creep, but it is also a decision-rights problem.

Every project should have a simple approval model. The project manager can manage day-to-day delivery. The services lead approves staffing shifts or budget changes above an agreed threshold. The account owner or executive sponsor approves commercial concessions. The client has a named owner who can approve scope and timeline changes.

Make the rules visible. If a request affects effort, cost, schedule, or deliverables, it gets documented. That doesn't mean every request needs a formal legal document. A lightweight change log may be enough for small items. But the team needs to record the request, estimate the impact, and get approval before doing the work.

This discipline improves client trust. Clients don't usually object to paying for added value when the impact is explained early and clearly. They do object when unexpected invoices arrive at the end of a project.

It also protects consultants. When decision rights are unclear, delivery staff are often put in the position of absorbing client pressure. Clear escalation paths let them focus on good work instead of negotiating scope at the task level.

A green project status should mean more than "nobody has raised an alarm yet." It should mean the project is on track against an approved baseline, actual costs are understood, remaining work is realistic, and scope decisions are under control. Which one of those signals is hardest for your team to see today?

About Continuum

Continuum PSA helps services leaders prevent project overruns by connecting project plans, resource assignments, time entry, budgets, and project accounting in one system. With real-time visibility into actual effort, fixed-fee variance, project profitability, revenue backlog, and emerging delivery risks, teams can spot trouble before margin disappears. Continuum gives delivery leads the data needed to manage scope, make faster staffing decisions, and keep projects on track financially and operationally.

 
 
 

Comments


bottom of page