The First Storm I Inherited
On my first day as an Assistant Project Manager, I reported to a construction site already halfway through delivery. I was young, energized, convinced I could make a positive impact.
Reality corrected me quickly.
The project was behind programme. Meetings were sharp. Decisions had been made long before I arrived—and not all of them were clean.
Only near completion did I discover that several team members had placed bets on how long the new APM would last. Many before me had left midway.
I lasted. Not because I was exceptional. Because I stayed.
When the project neared completion, a consultant laughed and told me about the bet. I had unknowingly made him lose.
We laughed.
But privately, I understood something important. The betting wasn’t cynicism. It was pattern recognition. Halfway projects are the hardest to inherit. Complexity is already embedded. Time is compressed. Cost is tightening. Goodwill has often been partially spent.
That experience didn’t make me dramatic. It made me quieter. It taught me that survival in project management is rarely about brilliance. It is about endurance.
2021: Three Projects, Mid-Pandemic
In 2021, when I joined SHG, I stepped into three residential projects already under construction—in the middle of a pandemic. Manpower instability. Supply disruptions. Cashflow stress. And inherited decisions made under pressure long before I arrived.
A senior colleague once told me early in my career: “Once you take over the ship, you own the storm.”
At the time, I thought he meant authority. It took years to understand he meant composure.
Half-Working Projects Are Fragile
Most project managers enter a takeover with the instinct to correct. Identify what went wrong. Establish authority. Start fixing.
That instinct is understandable—especially when projects are visibly failing. But most projects that change hands are not failing. They are half-working.
And half-working projects are fragile.
They carry invisible friction: technical compromises made under earlier time or cost pressure; relational fatigue between consultants and contractors; decisions that were reasonable in context, even if uncomfortable in hindsight.
The assumption that a new PM must immediately redesign anything imperfect is one of the fastest ways to destabilize what is quietly holding together.
In construction, momentum is rarely visible until it is lost.
The Three Debts of Every Ongoing Project
Over time, I’ve come to see takeover projects as carrying three forms of inherited debt.
Technical Debt—compliant but suboptimal details, value-engineered substitutions, scope adjustments made under pressure.
Relational Debt—fatigue between teams, consultants who feel unheard, contractors who stopped escalating issues because escalation once led nowhere.
Decision Debt—the gradual narrowing of future options until only certain paths remain viable.
None of these debts were mine to create. All of them were mine to manage.
Ownership does not mean rewriting history. It means taking responsibility for trajectory.
On one takeover, the first significant issue I identified was a design detail that was technically compliant but operationally fragile—a likely path to defects. Changing it would cost time and money. Not changing it meant consciously accepting the risk.
Neither option was comfortable. But the difficulty wasn’t technical. The architect had defended that solution for months. The contractor had priced around it. Management had approved the baseline. Reopening it meant disturbing settled ground.
Earlier in my career, I once asked in a review meeting: “Why was this done this way?”
The room didn’t close. But it stiffened. People who had fought hard for those decisions heard judgment.
I learned to ask differently: “What constraints made this the best decision at that time?”
That shift assumes good faith. It surfaces risk history faster than audits. And it builds trust with teams who have no reason to extend it to someone new.
A Fourth Debt: Regulatory Inheritance
There is a fourth debt I have learned to check for immediately—one that doesn’t show up in the programme or the cost report.
Regulatory debt.
Not every takeover project arrives with a clean compliance position. On more than one occasion, I have stepped into projects carrying unresolved BCA submissions, outstanding conditions on structural plans, or Temporary Occupation Permit prerequisites that were not properly tracked across team transitions.
These gaps are nobody’s fault in a straightforward sense. Submissions move slowly. Teams change. Approval conditions get logged and then quietly deprioritised under delivery pressure. But once you are the named developer representative, the authority doesn’t ask who was responsible before you arrived. They ask when you will resolve it.
The first thing I do on any takeover now is map the approval trail—not just what has been approved, but what has been approved with conditions, what was submitted and not yet responded to, and what was assumed to have been resolved but has no written confirmation. That exercise almost always surfaces something.
Regulatory debt compounds quietly. Left unmanaged, it becomes a late-stage constraint with no good options.
The Biggest Risk Remains Human
The greatest takeover risk is rarely technical or regulatory. It is human.
Team anxiety. Consultant defensiveness. Contractor resistance that doesn’t appear in formal meetings but surfaces as slower information flow, or RFIs that arrive just late enough to create downstream impact.
If trust was weak before you arrived, you rebuild slowly. If trust was strong, you earn your place without disrupting it. Both require restraint.
Listening first is not passive leadership. It is the fastest way to understand where the project truly stands—not where the programme says it should be.
Momentum does not return because a new PM declares it. It returns when people feel stability. And calm is contagious—in both directions.
Navigating, Not Redesigning
Most project managers will inherit a project they did not start. We step into drawings we did not conceive, contracts we did not negotiate, working relationships we did not build.
Projects do not remember who initiated decisions. They remember who delivered the ending.
Sometimes growth does not come from redesigning the ship. It comes from steering it steadily through waters you did not choose—and arriving somewhere you can stand behind, technically, commercially, and ethically.
I am still navigating active projects. Still inheriting complexity. Still learning.
But one lesson stays constant:
Once you take over the ship, you own the storm.
Originally published on LinkedIn on 10 March 2026. This version is slightly amended from an essay first published on Medium on 22 February 2026.