Onshore Consortium

16/09/2026

"What CEOs should stop doing immediately."
After years delivering infrastructure, building, construction and other cross-cutting projects, I've sat in enough steering committees and executive reviews to say this plainly:
Some CEO habits are quietly killing your projects.
Not because CEOs are incompetent. Because the behaviours that make someone a successful CEO - decisiveness, urgency, vision - can become destructive when applied to project delivery without discipline.
Here's what CEOs should stop doing immediately:
🛑 Stop changing priorities every quarter.
Strategy pivots are sometimes necessary. But when the "top priority" changes every 90 days, project teams stop believing in any of them. You don't get agility. You get paralysis, rework, and abandoned momentum.
🛑 Stop demanding green dashboards.
If your project teams feel pressured to report "green" to avoid your reaction, you have not eliminated risk. You have hidden it. A CEO who punishes bad news gets lied to - politely, professionally, and expensively.
🛑 Stop confusing activity with progress.
More meetings. More reports. More reviews. None of it delivers the project. If your PMs spend 40% of their week preparing for your reviews, you are slowing down the very work you're trying to accelerate.
🛑 Stop skipping governance when it's inconvenient.
When executives bypass change control, procurement rules, or quality gates because "this one is urgent," you teach the entire organization that systems don't matter. And then you wonder why governance fails elsewhere.
🛑 Stop treating project management as admin.
PMs are not schedulers. Program Managers are not report writers. They are the people translating your strategy into physical reality. If you view them as overhead, you will get overhead-level results.
🛑 Stop rewarding heroics over systems.
If the PM who firefights a failing project gets promoted - while the PM who quietly prevents failure gets ignored - you have built a culture that celebrates chaos. Fix the system, not just the fire.
🛑 Stop setting deadlines without asking what it takes.
A date chosen for shareholder convenience is not a plan. It is a wish. Ask your delivery teams what the date requires - then decide whether you're willing to fund it.
💡 What CEOs should start doing instead:
✅ Ask "What's worrying you?" - and mean it.
✅ Reward early warnings as much as early wins.
✅ Protect governance, even under pressure.
✅ Invest in systems, not just heroics.
✅ Treat PMs and Program Managers as strategic partners - because they are.
The takeaway:
CEOs don't fail projects.
But CEO behaviours - when undisciplined - create the conditions for failure.
The best executives I've worked with didn't manage projects. They created the environment where projects could succeed.
What's one CEO behaviour you wish would disappear from project delivery? Let's discuss.

31/07/2026

Your legal team is not your project's shield. They are your last line of defence - and if you are leaning on them first, you have already lost.
Most project managers treat contracts like insurance policies. Something to pull out of the drawer when things go wrong.
Big mistake.
After years of delivering complex programs, I have learned a hard truth: Contracts are not legal tools. They are management tools.
If you are not using your contract as a strategic lever from Day 1, you are not managing your project - you are just reacting to it.
Here is how the best Program Leaders use contracts to drive success, not just defend against failure:
________________________________________
1. The contract is your "Truth Serum."
Ambiguity kills projects. But ambiguity is also comfortable - until it isn't.
A well-drafted contract forces clarity. It demands answers to questions like:
• What does "done" actually look like?
• Who owns what risk?
• What happens when the client changes their mind?
When you use the contract as a discovery tool early, you uncover misaligned expectations before they become multi-million dollar lawsuits. The contract isn't a trap; it is a mirror.
________________________________________
2. It is your most powerful communication tool.
Here is a secret: The contract is not for the lawyers. It is for the project team.
When scope creeps, when deadlines slip, when stakeholders argue about what was promised - the contract is the single source of truth. It removes emotion from the conversation. It replaces "I thought you said..." with "Here is what we agreed."
A contract that sits in a filing cabinet is useless. A contract that lives in your weekly steerco meetings? That is a management superpower.
________________________________________
3. It transforms "Scope Creep" into "Scope Trade."
The biggest myth in project management is that you cannot say "No" to the client.
You can. You just need the right language.
The contract gives you the framework to say: "Yes, we can do that. Here is the cost. Here is the timeline impact. Here is what we take off the table."
It turns every change request from a confrontation into a commercial conversation. Suddenly, you are not the "difficult PM." You are the pragmatic partner.
________________________________________
4. It is your early warning system.
When a client starts pushing back on contractual milestones, it isn't a legal issue - it is a relationship issue.
They are signalling a loss of confidence. A shift in priorities. A budget squeeze.
If you wait for the lawyers to interpret that signal, it is too late. Great Program Managers read the contract behaviours as leading indicators of project health.
________________________________________
5. It protects your team, not just your margin.
When you have clear contracts, your team knows the boundaries. They know what is in scope and what is out. They don't waste energy fighting battles they shouldn't fight.
A good contract gives your team permission to focus on delivery, not defence.
________________________________________
The Bottom Line:
If you treat the contract as a "legal document," you will call your lawyer when the project is already on fire.
If you treat it as a "management tool," you will use it to prevent the fire in the first place.
The best Program Managers are not just delivery experts. They are commercial leaders.
Agree or disagree?
How do you use contracts on your projects - as a shield or as a roadmap?
Drop your perspective below. Let's learn from each other. 👇
________________________________________

30/07/2026

We keep hiring Project Managers. We keep losing Program Leaders.
And we wonder why 70% of complex transformations fail.
I've watched organizations pour millions into training on Agile, Scrum, and SAFe. They buy the best tools. They hire the best schedulers.
And yet, ex*****on still crumbles.
Why? Because we are confusing management with leadership - and the gap between the two is costing us billions.
Here is the leadership gap most organizations refuse to acknowledge:
1. We reward "Task Completion" over "Vision Holding."
We promote the PM who closes 100 tickets in a sprint. But we neglect the one who stands up in a room full of skeptics and says, "This is why we are doing this." When the "why" disappears, the "how" becomes chaotic. You can manage resources; you must lead purpose.
2. We teach Risk Management. We don't teach Courage.
Every PM knows how to fill out a risk register. But how many know how to walk into the VP's office and say, "We are heading for a cliff, and we need to stop - even if it makes us look bad"? Psychological safety isn't just a perk; it is a delivery metric. If your team fears speaking up, your project is already dead.
3. We invest in Tools. We ignore Trust.
We buy Jira, Asana, and MS Project. We track velocity, burn rates, and EVM. But we never measure the one metric that actually predicts success: "Does this team trust each other?" Without trust, handoffs become blame games. With trust, you move at the speed of honesty.
4. We confuse "Experience" with "Adaptability."
Just because someone has managed 50 projects doesn't mean they can manage this one. The world has changed. AI is rewriting workflows. Distributed teams are the norm. The leaders who thrive aren't the ones with the longest resumes; they are the ones with the highest learning agility.
5. We hire for Technical Skills. We fire for Emotional Intelligence.
I have never seen a project fail because someone couldn't build a Gantt chart. I have seen projects fail because a leader couldn't listen, couldn't de-escalate conflict, or couldn't inspire a tired team. The "soft skills" are the hardest skills. And we treat them like an afterthought.
The Hard Truth:
Management ensures you do things right.
Leadership ensures you do the right things.
If your organization is struggling to deliver complex programs, stop looking at your processes. Start looking at your people. The gap isn't in your playbook. It is in your culture.
Agree or disagree?
What is the ONE leadership trait you wish your organization valued more?
Drop your thoughts below. Let's start the conversation. 👇
________________________________________

28/07/2026

I don’t wait for the missed deadline. I wait for the silence.
If you are only looking at your Gantt chart to spot trouble, you are already six weeks behind.
After years of turning around failing projects, I’ve learned that catastrophic failure never arrives without warning. It sends subtle signals. The trick is knowing where to look - and most PMs look in the wrong places.
Here are the 5 early warning signs I never ignore:
1. The Status Report is "Green" for the third month in a row.
Perfection is suspicious. If every single metric is in the green with zero risks logged, your team isn't performing - they are hiding. A healthy project has yellow flags. No yellow flags mean no one trusts you enough to tell you the truth.
2. Meeting attendance starts "slipping."
When senior stakeholders stop showing up to the weekly sync, they haven't gotten busy. They have lost confidence. They are disengaging mentally before the project actually fails. If your steering committee goes quiet, sound the alarm immediately.
3. The answer to "How are things?" is a single word.
"Fine." "Good." "On track."
Beware the one-word update. Teams that are genuinely on track want to share their progress. Teams that are struggling want to end the conversation as quickly as possible. Short replies are often a shield, not a status.
4. Rework tickets start spiking.
A few bugs are normal. A sudden surge in rework or "Change Requests" isn't a quality issue - it's a clarity issue. It means the requirements were never understood in the first place. You aren't fixing errors; you are building the wrong thing twice.
5. The "Hero" is working weekends.
When one person becomes the single point of failure - the only one who can fix the code, approve the budget, or talk to the client - you have a single point of failure. If your superstar is burning out, your project is one sick day away from collapse.
The Bottom Line:
Great project managers don't manage tasks. They manage tension. They listen for what isn't being said. They look at the data, but they trust their gut.
If you wait for the red status to take action, you aren't managing risk. You are just documenting failure.
What is YOUR non-negotiable early warning sign?
I'll go first: When my team stops asking questions in stand-ups, I know we are in trouble.
Drop your red flag in the comments. Let's build a masterclass on risk detection. 👇
________________________________________

21/07/2026

Large projects rarely fail with a bang.
They fail with a whisper.
By the time the cancellation memo is issued or the sponsor requests a "reset," the outcome was already sealed months - sometimes years - earlier.
The collapse is not sudden. It is gradual. And most of the warning signs are either ignored, dismissed, or simply not visible to those in authority.
This is what I call "silent failure."
Unlike small projects, where issues surface quickly, large-scale initiatives have layers of reporting, complex governance structures, and significant organizational inertia. Problems get absorbed, filtered, or smoothed over before they reach decision-makers.
Where large projects fail silently:
1. The status report illusion
Green status indicators. On-track milestones. Comforting RAG ratings. Yet beneath the surface, quality is eroding, stakeholder confidence is declining, and technical debt is accumulating. The reporting system becomes a shield, not a window.
2. The sunk cost trap
Once significant investment has been made, organizations become reluctant to ask hard questions. The project continues not because it is viable, but because stopping feels more difficult than continuing. Momentum masks judgment.
3. Diffused accountability
In large programs, responsibility is spread across multiple work streams, vendors, and governance bodies. When everyone is accountable, no one is truly accountable. Issues fall into the gaps between roles.
4. The "too big to fail" mentality
Scale creates a false sense of security. The assumption is that resources can solve any problem. But resources cannot fix flawed assumptions, unclear requirements, or misaligned stakeholder expectations.
5. Escalation fatigue
Early warnings are raised, but action is delayed. Over time, teams stop escalating. They adapt to dysfunction. The silence becomes normalized.
How to prevent silent failure:
✅ Demand narrative over numbers – Status reports should tell a story, not just display colours. Ask what is not being said.
✅ Conduct independent health checks – Bring in fresh perspectives to assess progress without organizational bias.
✅ Create safe escalation channels – Protect those who raise concerns. Reward candour. Silence is a symptom, not a solution.
✅ Review assumptions regularly – What was true at initiation may no longer hold. Test critical assumptions throughout the lifecycle.
✅ Monitor leading indicators – Do not wait for lagging metrics to signal trouble. Track engagement, decision velocity, and requirement stability.
The most dangerous moment in a large project is not when it fails.
It is when everyone stops talking about the problems.
If you are leading a large initiative, ask yourself this question today:
What is the one thing my team is not telling me?
Then create the space for them to answer.
What silent warning signs have you observed in your largest projects? Let's bring them into the open. 👇
________________________________________

14/07/2026

A mistake I have seen too often in program and project management:
Confusing activity with progress.
We generate status reports. We hold recurring steering committees. We update dashboards and track RAID logs. These are necessary disciplines - but they are not, in themselves, indicators of delivery.
The mistake I have observed repeatedly is this: teams become so consumed with managing the mechanics of the project that they lose sight of whether they are actually advancing the business outcome.
This manifests in several ways:
1. Reporting outputs rather than outcomes – Milestones are met, deliverables are produced, yet the intended business value remains unrealized. The project is "on track" by the metrics, but off course where it matters.
2. Confusing motion with momentum – Frequent meetings, extensive documentation, and rigorous process adherence can create a false sense of security. Activity is visible; progress is not always visible - and they are not synonymous.
3. Delaying difficult conversations – Issues are logged but not escalated. Risks are identified but not mitigated. Assumptions are documented but not validated. The project moves forward, but the underlying vulnerabilities remain unaddressed.
4. Overlooking stakeholder adoption – We focus on technical delivery and assume that if we build it, they will use it. In my experience, the greatest ex*****on risk is not technical - it is human. If stakeholders are not prepared, engaged, and enabled, the investment yields little return.
What I have learned to do differently:
• Anchor every milestone to a measurable business outcome. If we cannot articulate why a deliverable matter, we should question whether we should be delivering it at all.
• Distinguish between governance and progress. Governance provides oversight; progress requires tangible movement toward value. Both are necessary, but they serve different purposes.
• Escalate early and explicitly. The cost of delay in communication far exceeds the cost of early intervention.
• Invest as much in change management as in delivery management. Adoption is not an afterthought; it is a core delivery discipline.
The most effective project and program managers I have worked with share one quality: they are relentless about distinguishing what looks like progress from what is progress. They measure success not by tasks completed, but by value delivered.
I would be interested to hear from others in this network: What mistakes have you observed that consistently undermine project success?
________________________________________

26/06/2026

What causes most disputes in projects?
It's rarely the technical complexity.
It's rarely the budget.
It's rarely the schedule.
It's misalignment on expectations.
Let me explain.
I've seen it happen more times than I can count:
🔹 The sponsor thought "done" meant something different than the team did.
🔹 The contractor assumed the client would approve the change, and proceeded anyway.
🔹 The project manager delivered exactly what was in the scope document - but the stakeholder wanted something else entirely.
And then comes the claim. The variation order. The escalation. The arbitration.
Not because anyone was dishonest. Not because anyone was incompetent.
Because nobody stopped to ask: "Are we on the same page?"
Here's what I've learned after decades on large programs:
Most disputes don't start in the contract. They start in the conversation.
They start when:
❌ Assumptions go unspoken.
❌ Risks are not discussed openly.
❌ Changes are implemented without formal agreement.
❌ Progress reports say "green" while problems are quietly brewing.
❌ Stakeholders interpret the same clause differently.
And by the time the dispute is formalized?
The relationship is already damaged. The trust is already eroded. The project is already off track.
The best dispute resolution is prevention.
And prevention starts with:
✅ Clarity – Define scope, roles, and expectations in plain language, not just legal text.
✅ Communication – Create safe spaces for stakeholders to raise concerns early, before they become claims.
✅ Documentation – Record decisions, assumptions, and changes as they happen. If it's not written, it didn't happen.
✅ Relationship management – Treat your counterpart as a partner, not an adversary. Disputes are harder when trust exists.
✅ Project controls – Use early warning indicators to spot misalignment before it escalates.
✅ Governance – Ensure the right people are engaged at the right time to resolve issues before they become disputes.
The contract is the last line of defence, not the first.
If you're relying on the contract to resolve a dispute, you've already lost something. Time. Money. Reputation. Trust.
Great project and program managers don't just manage scope, cost, and time.
They manage alignment.
They make sure everyone is reading from the same page - before the page becomes a legal document.
They ask the uncomfortable questions early, so they don't have to answer the painful ones later.
So here's my question to every project professional:
When was the last time you asked your stakeholders: "What does success look like to you?"
And when was the last time you actually listened?
Tag a project or program leader who understands this 👇
Repost ♻️ if you believe prevention is better than resolution.

www.onshore.co.ke

Your One-Stop, Full-Service Consortium offering multidisciplinary expertise in Project Management, Engineering, Interior Design, and Technology Services for seamless project ex*****on from inception to completion.

18/06/2026

Good executives manage projects.
Great ones manage the system around them.
I've worked with both. And the difference is staggering.
Here's what I've learned:
Good executives ask: "Are we on time?"
Great executives ask: "Do we have the right governance to know if we're on time?"
Good executives review the status report.
Great executives challenge the assumptions behind the status report.
Good executives approve the budget.
Great executives question whether the budget reflects reality - or just last year's numbers with 10% added.
Good executives celebrate milestones.
Great executives celebrate the controls that made those milestones predictable.
Good executives react to problems.
Great executives spot the patterns that create problems - and fix those instead.
Here's the uncomfortable truth:
Good executives are busy. Great executives are effective.
Good executives manage what's in front of them. Great executives design systems so nothing surprises them.
Good executives rely on their team's memory. Great executives rely on data, trends, and early warning indicators.
Good executives hope risks don't materialize. Great executives build resilience into the plan so risks don't matter as much.
Good executives deliver projects. Great executives deliver certainty.
And certainty? That's what separates leaders who get promoted from leaders who stay busy.
So here's my question to every executive reading this:
Are you managing the project?
Or are you managing the system that delivers the project?
Because one keeps you busy.
The other makes you irreplaceable.
Tag an executive who gets this 👇
Repost ♻️ if you believe systems beat heroics every time.

www.onshore.co.ke

Your One-Stop, Full-Service Consortium offering multidisciplinary expertise in Project Management, Engineering, Interior Design, and Technology Services for seamless project ex*****on from inception to completion.

17/06/2026

Most project decisions are made in chaos.
And nobody talks about it.
We gather in a room. We debate. We compromise. We go with the loudest voice.
Then we call it "decisive leadership."
No.
That's just organized guessing.
Here's what I've learned after years of leading complex programs:
There is a hidden power in structured decision-making.
And it's not about bureaucracy. It's about survival.
Here's why:
1. Structure removes emotion from the equation.
When you have clear criteria, clear alternatives, and clear consequences, you stop fighting over opinions. You start evaluating evidence. Suddenly, the best path forward isn't about who speaks loudest - it's about what the data actually says.
2. Structure forces you to consider trade-offs.
Every decision has a cost. Time vs. quality. Scope vs. budget. Speed vs. risk.
Structured decision-making doesn't let you pretend otherwise. It forces you to be honest about what you're giving up to get what you want.
3. Structure creates auditability.
When things go wrong - and they will - structured decisions can be reviewed. Tested. Learned from. Unstructured decisions? They vanish into memory and blame.
4. Structure accelerates ex*****on.
This is the counterintuitive part.
Most people think structure slows you down.
It doesn't.
Because when you have a clear decision framework, you stop second-guessing. Stop re-debating. Stop waiting for permission.
You decide. You move. You deliver.
Here's the truth that separates good programs from great ones:
Great programs don't just make better decisions.
They make decisions consistently better.
They build systems that remove bias. They create frameworks that scale. They empower teams to decide with confidence, not anxiety.
💡 A decision made with structure isn't a box-ticking exercise.
It's a competitive advantage.
So here's my question for every program leader:
Are your teams deciding with clarity?
Or are they guessing in silence?
Tag a leader who builds decision-making systems 👇
Repost ♻️ if you believe better decisions start with better structure.

www.onshore.co.ke

Your One-Stop, Full-Service Consortium offering multidisciplinary expertise in Project Management, Engineering, Interior Design, and Technology Services for seamless project ex*****on from inception to completion.