Your First $1B Project: 10 Things That Change

1.You gain specialists, and more responsibility for joining their work

On a smaller job, you may know every decision because so much passes through your hands. On a major project, cost, schedule, design, procurement and construction need people with the time and expertise to do them properly. The manager's job increasingly becomes connecting those contributions and resolving the gaps between them. Delegating the analysis does not make the delivery outcome somebody else's problem.

Try this: Follow one change from the field to approval. Name who develops the technical answer, assesses cost and schedule, recommends a decision and has authority to make it. Resolve gaps and duplicate approvals before adding another box to the organisation chart.

2.Controls become an operating capability you have to resource

A larger reporting specification does not create the capacity to fulfil it. Contractor reviews, progress checks, forecasts and risk analysis all need preparation and follow-through. Decide what information the project needs, how frequently it needs it and who can produce and challenge it. Otherwise the team can spend the entire cycle assembling a report and have little time left to act on what it says.

Try this: Put the controls calendar beside the staffing plan. For each recurring output, identify the data provider, reviewer, decision it supports and effort required. Close the biggest capacity gap by adding capability, simplifying the process or changing a low-value requirement.

3.The spaces between packages become part of your job

Every contractor can be making progress while the overall project is losing time. A package may finish its design without delivering the information another package needs. A plant may be ready before its power connection. Make the handoff itself visible: what has to be delivered, to whom, by when and in what condition. A list of package completion dates does not answer those questions.

Try this: Select an upcoming handoff between two organisations. Put the provider and receiver together and agree the deliverable, acceptance evidence, required date and escalation owner. Track unresolved interfaces alongside the work packages they affect.

4.Your project can outgrow the market willing to deliver it

A preferred contracting strategy still needs willing and capable participants. As scope and exposure grow, an owner may find that the intended package is too large, or the proposed allocation of risk too unattractive, for a useful competition. Packaging and phasing are delivery decisions as well as commercial ones: splitting work can improve market access while creating more interfaces for the owner to manage.

Try this: Test the proposed packages against credible contractor capacity before committing to the delivery strategy. Ask what capability, capacity and risk assumptions must hold. If the answer is weak, compare changes to scope, phasing or packaging, and name who will manage the interfaces each option creates.

5.Several company names have to become one working team

Joint ventures and large delivery teams bring different employers, incentives and ways of working onto the same project. A common logo on a slide does not settle competing priorities. AJ's same-hat story asks a practical question: do people behave as members of the project team when the interests of their employers pull in different directions?

Try this: Take a real disagreement between delivery partners. Agree the project outcome both sides are protecting, who can decide and how the decision will be communicated. Establish shared routines for raising problems and resolving them; preserve the role and safety identification the site needs.

6.Material risk needs a new frame of reference

The dollar amount that dominated your last project may be a smaller part of this one, while an unfamiliar interface or external dependency may threaten the whole delivery strategy. Revisit the consequence scales and escalation triggers rather than carrying them across unchanged. Keep safety, environmental and stakeholder consequences visible alongside cost and schedule.

Try this: Take three live risks through the proposed consequence scales with the project leadership team. Check whether the ranking leads to sensible attention and action. If it hides an important dependency or pushes routine issues to the director, revise the criteria and agree the escalation route.

7.The director needs choices with consequences

When a decision commits substantial capital or changes the route to operation, the director needs more than a status update. Explain the available choices, what each changes, when the decision is needed and what remains uncertain. Keep routine progress records, but build a separate decision paper when a choice cannot be understood from the monthly pack.

Try this: Rewrite one escalation as a decision request. State the decision, options, recommendation, cost and schedule consequences, assumptions and latest useful decision date. Confirm the decision sits with the recipient; a larger title does not automatically mean authority over every commitment.

8.The same project must make sense to very different audiences

Site leadership, the owner, lenders, headquarters, a program team and public stakeholders can need different explanations of the same position. Establish common definitions and reporting dates, then tailor the detail and the decision request. Independently assembled versions of the truth are hard to reconcile when somebody asks why two reports disagree.

Try this: Make an audience map for the next reporting cycle. For each recipient, write down the question they need answered, action they can take and detail they need to trust the conclusion. Produce those views from an agreed underlying position and explain differences in period, scope or forecast basis.

9.The asset may need its own supporting world

Power, access, accommodation, logistics and connections to existing infrastructure can become substantial delivery scopes. Their dates determine when the main works can start, how people reach the site and whether the finished asset can operate. Start by asking what must already exist for the headline project to succeed.

Try this: Trace the route from supplier to site and from the completed asset to its intended users. Identify the infrastructure, access and support needed along the way. Give each dependency an owner, a required date and a place in the integrated schedule, including dependencies delivered outside your own contract.

10.Success reaches beyond your project boundary

The project can change how a community moves, works or accesses services. That wider purpose shapes expectations long before construction finishes. Learn what the investment is meant to achieve and which commitments the project has made, then connect your package decisions to those outcomes. Finishing a scope item is easier to judge when you understand why it exists.

Try this: Ask the sponsor and stakeholder team to explain the intended outcomes and the commitments that matter locally. Trace one of those commitments into a delivery decision, an accountable owner and evidence of fulfilment. Make the connection visible in the work plan instead of leaving it in an introductory presentation.

• I can identify the person who decides and the specialists who support my next significant decision.
• I know which interfaces and external dependencies can stop my work, and who owns each one.
• My reporting explains the same underlying position to different audiences.
• I can explain how my package supports the project's intended outcome.