Skip to content

A late proposal!

When I took over a project, I couldn’t make sense of the plan. Furthermore, each team member confided concerns about the timing. In particular, they did not know when they would get the data they needed from each other.

The project outcome was a multi-million-pound bid to a customer. Project recovery was the order of the day.

A late proposal!

I took three actions to recover the project.

  1. Made sure everyone knew what they had to deliver and their goals to win the business.
  2. Worked with each team member to understand what they needed from each other and when.
  3. Learnt how the company would evaluate and approve the bid.

By listening to multiple stakeholders, I could build a network diagram. This showed when each team member needed an input from another. I added in estimates of duration to build a schedule.

Cartoon schedule

Each team member came from a different business function, e.g., Purchasing, and were senior staff or managers. They followed specialist processes and didn’t need me to plan their jobs.

So, I opted out of Microsoft Project*. One of the PM specialists mocked me (gently) for making a ‘cartoon’ schedule. But I stand by my decision. Not only could everyone understand it, but we could easily share it. I don’t expect Subject Matter Experts to learn how to read a complex schedule. Just as they don’t expect a PM to do their jobs.

*MS Project is an amazing scheduling tool. But it is designed to schedule projects not communicate.

Back on track

Within a week, I presented to the leadership team and booked gate and governance reviews. We had a clear schedule, and the team needed very little ‘monitor and control’. So, I switched my focus to the internal supply chain (Supply Chain Units or SCUs) and the data crunchinging stakeholders.

Working with the supply chain

We started by improving our communications and sharing the voice of the customer. I built a brief and worked with SCU staff to agree deliverables. Our senior managers meet with their counterparts and we held seven-way reviews to learn lessons from each other.

Crunching the data

Designing the engine, supply chain and services generated costs and contributed to the financial business case.

I helped the engineering business manager simplify our resource data requirements and worked with the Finance Manager to develop robust instructions for estimating costs.

All-in-all the project was a success. Until the customer changed their minds and postponed the bid, but that is a different story.

Key skills

Focus on business outcomes – my contribution to winning the business was delivering a timely submission. To achieve that, I had to understand and manage all the dependencies.

Cross-functional/ matrix management – understanding the needs and constraints of subject matter experts. Negotiating and influencing to reduce process times.

Scheduling – managing dependencies. Developing timescales and communications.

Team leadership – supporting colleagues. Setting standards and expectations.

Governance – complying with business governance. Engaging stakeholders.

Do the issues in this case study sound familiar?

Are you struggling to satisfy your customers? No need to worry, simply schedule your free consultation today and we can discuss how to move your business forwards.

Back To Top