Crisis Management In Projects

60–70% of pressure comes not from workload, but from unclear communication and misaligned expectations! Leading consulting teams through demanding projects has taught me valuable lessons about maintaining effectiveness under pressure. Here are some approaches that have worked well for me and my teams. 💙 Building Sustainable Systems 1. Clear Communication Channels: One of the most important shifts I made was creating transparency around project constraints and timelines. When teams understand the complete context - including challenges and limitations - they can contribute more meaningfully to solutions. This also helps in setting realistic expectations with stakeholders early on. 2. Iterative Delivery: I've found that delivering work in phases, with opportunities for feedback and refinement, creates better outcomes than trying to achieve perfection in one attempt. This approach allows for course corrections and ensures we're aligned with client needs throughout the project lifecycle. 3. Capacity Planning: Building buffer time into project plans has been crucial. When unexpected requests arise - as they inevitably do in consulting - having some flexibility in the schedule allows the team to respond without compromising quality or well-being. 4. Regular Check-ins: Informal conversations with team members, beyond formal status updates, have proven invaluable. These moments help identify potential roadblocks early and ensure everyone feels supported during intensive project phases. 💙 Continuous Improvement 1. Prioritization: Learning to distinguish between genuinely urgent matters and routine requests has improved our responsiveness. Not every issue requires immediate attention, and being thoughtful about prioritization helps maintain team energy for what truly matters. 2. Balanced Intensity: During particularly demanding phases, I've learned to be transparent about the intensity level and ensure that busy periods are followed by lighter ones. This rhythm helps teams sustain performance over the long term. 3. Leading by Example: Being open about challenges while demonstrating problem-solving approaches builds team confidence. Leadership doesn't mean having all the answers - it means navigating uncertainty thoughtfully alongside your team. 4. The Consulting Journey: High-pressure situations are part of consulting work. Success comes from building systems, teams, and approaches that can handle intensity while maintaining quality and team well-being. What approaches have you found effective in managing demanding projects? Always interested in learning from fellow leaders in this space. #ConsultingLife #TeamManagement #ProjectManagement #ProfessionalGrowth #Consulting

Project management teaches you how to hit deadlines. It rarely teaches you how to protect yourself while doing it. Every project manager knows the drill. Push a little harder. Absorb more tension. Stay calm so others can panic safely. We call it professionalism. But often, it’s just quiet exhaustion. I’ve lived it. Running projects that looked “successful” on paper while my mind was always in recovery mode and my team was slowly running on fumes. Here’s the uncomfortable truth I had to learn: You can’t lead clearly when you’re depleted, and your team can’t execute well when urgency never turns off. In project management, calm isn’t a personality trait. It’s an execution decision. That’s why I stopped glorifying chaos, and started leading with CALM. ✅ Create margin on purpose Not every sprint needs to be full. Margin is how projects survive reality. ✅ Ask how people are doing Not just what they delivered. Emotional data is execution data. ✅ Limit false urgency If everything is urgent, nothing is actually important. ✅ Model calm under pressure Your team follows your nervous system more than your roadmap. I've completed projects that met every milestone yet left team members feeling drained and disconnected. The projects I truly take pride in are those that delivered results while keeping the team intact. Project management isn't just about speed; it's about working effectively with a team that wants to collaborate after the release. The true outcome of a project isn't just the final product; it's the people who remain engaged and united. → Found this useful? Repost ♺ and follow Jesus Romero for grounded PM insights that protect delivery and people.

Most new PMs think handling pressure means doing everything faster. That is exactly how projects spiral out of control. When you have experience, you learn that speed without strategy burns out teams and erodes trust. → You talk to the client before sending anything new. → You re-scope instead of cramming everything in. → You fix root causes instead of pushing harder. → You renegotiate when priorities shift. → You step in to resolve conflict early. Pressure exposes the difference between managing tasks and leading people. An experienced PM knows that protecting the team is the fastest way to protect the project.

In 20 years of managing mega-projects, I’ve never seen fast-tracking projects actually save time. And I know where that pressure comes from…. → Investors want to see movement  → Teams want momentum So designs get finalized on-site instead of in the office and while it may sound agile but it's actually expensive. Let me tell you what happens when the construction starts early: 1/ A coordination issue between MEP systems caught in design review takes two weeks to resolve where the same issue discovered during construction mobilization takes two months and requires rework that halts progress on adjacent areas 2/ If specs might change, they add contingency and that 15% to 20% contingency buffer on early bids disappears when designs are locked. The savings alone often justify the delay 3/ What was planned as standard specification gets discovered as a non-standard mid-project. Each discovery becomes a formal change order, and change orders are expensive. The thing is, starting construction with incomplete design is admitting you're willing to solve problems at 10x the cost and there's no way to rationalize it as good project management. I've seen projects that waited six months to start but delivered on budget and I've seen projects that rushed to break ground and blew budgets by 15% or more. And that’s why I say that discipline in the pre-construction phase is the difference between delivering a project on budget and explaining why you need another SAR 75 million.

Not every C&I solar project is viable, I learnt this the hard way. It’s easy to jump at the show of a new C&I lead. Many developers and EPCs assume that every working factory, mart, farm, or hospital is a viable solar candidate. You scan industrial rooftops, chase meetings, and finally get invited to perform site assessments and energy audits. Excitement builds. You involve the engineering team, you design diligently, you push hard through your process. But then, weeks or months in, you hit a roadblock: the economics don’t stack, the client can’t commit, or the financier isn’t convinced. C&I projects aren’t about panels and batteries. They’re about business cases. And business cases need to make sense to two groups: The Offtakers → clients who must see real savings and operational value. The Financiers → investors who must see risk-adjusted returns. If you can’t defend both sides, then what you have is not a project, it’s just a lead. So, how do you qualify early? Start with three fundamental filters: 1️⃣ Load Profile: Does the client’s consumption pattern align with solar generation? A factory running 8 am–6 pm is viable. A hotel with peak load at midnight may not be, unless they’re ready to pay for storage. 2️⃣ Tariff Environment: What benchmark are you competing against? If grid tariffs are cheap and reliable, solar won’t make economic sense. But if diesel costs are spiraling, solar PPAs suddenly become compelling. 3️⃣ Client’s Energy Spend & Financial Strength: Is power a material cost for the business (e.g., power costs 20% of OPEX in agro-processing = urgent). And beyond these, you must run feasibility studies. They’re not paperwork. They’re the due diligence backbone: Technical → can the system physically work? Financial → do the numbers hold under stress tests? Legal/regulatory → are there barriers to connect or operate? Operational → will the client maintain and honor commitments? 🚩 Red flags you must not ignore: → Night-heavy loads with no storage appetite. → Clients with poor creditworthiness. → Subsidized tariff environments where solar can’t compete. → Weak roof structures or no space for panels. → Clients treating energy as a “nice to have” rather than a strategic priority. #SolarEnergy #RenewableEnergy #CISolar #EnergyTransition #PPAs #SolarProjects #EnergyFinance #CommercialSolar #IndustrialSolar #ProjectFinance #EnergyManagement #SolarDevelopment

Boards don’t get surprised by poor results; they get surprised by assumptions they never challenged… Strategy rarely fails because of intent. It fails because of untested assumptions hiding inside business plans, budgets, forecasts, and investment proposals. Every strategy is built on beliefs about, among many others: market demand, commodity prices or input costs, exchange rates and inflation, regulatory stability, capital availability, execution timelines, human capability and productivity. Yet many boards approve plans without interrogating the assumptions architecture holding the plan together. Sometimes, when one critical assumption shifts, the entire model can collapse. Directors must move from just asking: “Is this a good plan?” to asking: “What must be true for this plan to succeed — and what if it isn’t?” Among other tools, boards should be actively stress-testing assumptions using: ✔ Scenario Analysis: Base / Downside / Severe Case — with clear management actions tied to each. ✔ Sensitivity Analysis: What happens if price drops 15%? Costs rise 10%? Project delivery slips 6 months? ✔ Driver-Based Modelling: Plans linked to operational drivers, not static spreadsheets. ✔ Pre-Mortem Reviews: Assume the strategy failed. Ask: What caused it? ✔ Independent Challenge: Audit, risk committees, or external experts validating key assumptions. ✔ Cash-Flow Stress Testing: Profit is opinion. Cash is fact. Can the organisation survive volatility? Boards do not govern by just approving documents. They govern by challenging the thinking behind the numbers. If assumptions are not examined, governance becomes ceremonial, redundant, and irrelevant. Strong boards test assumptions before reality does!

I built a tool that scores how fast your project will die in Africa. Then I tested it on a real $7M factory. It scored 50 out of 100. Not because the project was bad. The base IRR was 39%. Any investor would take that in a heartbeat. But here is what the model showed in 90 seconds that the feasibility study missed in 50 pages: Power infrastructure scored 15 out of 100. Technical dependency scored 30 out of 100. After stacking all 7 frontier stresses, the 39% IRR dropped to 8%. Before you invest in that project ask yourself one question: Has anyone ever told you it won't work? Not "it's risky." Not "proceed with caution." Has a single person in the chain ever said: this project will fail under real conditions? If the answer is no, you don't have a vetted project. You have a consensus of silence. I've been inside that silence. 50+ industrial projects across Ethiopia & parts of East Africa. The consultant is paid by the founder who needs a green light. The bank officer needs a document for the credit committee. Everyone is incentivized to produce optimism. McKinsey found that 80% of African infrastructure projects fail at the feasibility stage. The SME financing gap in sub-Saharan Africa is $331 billion. Not because capital is missing because trust is missing. Economists call this the lemons problem. When buyers can't tell good deals from bad, they price everything at the bad level. Frontier market investment is a lemons market. The missing piece is a credible signal. So, I built one. B-Box — Bankability Box. It takes your inputs, builds a 5-year DCF, then stresses it against 7 frontier realities: FX, logistics, power, inflation, working capital, maintenance, and technical dependency. Every score traces to a computed financial impact. Today it runs on 7 frontier variables across 7 East African countries. Manufacturing in Ethiopia loads different variables than agri-processing in Kenya. The library grows with the data. And the real play is the dataset nobody else is collecting. Every project that runs through B-Box and later reports what actually happened becomes a training data point. At a thousand validated projects, the model stops being rule-based and starts learning which variables predict failure by sector, by country, by deal size. The vision is a trust layer between capital and on-ground operations. Where investors get a structured signal before wiring money, and founders see what breaks first before the bank does. This isn't a finished product. It's a proof of concept to test whether this approach has legs. - If you invest in frontier markets — run a deal through it. Tell me what's missing. - If you're a founder — test your real numbers. Tell me where the output is wrong. - If you work in policy or DFI — what would make this part of the process? I need the kind of feedback that breaks something. Try it yourself: b-box.dev #FrontierMarkets #InvestmentAnalysis #BBox #Ethiopia #DevelopmentFinance #Bankability

Actionable Mondays: Care More About the Downside When someone asks me about a deal, the first question is usually: “What’s the projected return?” Fair question. But I don’t start there. I start here: What would have to go wrong for this investment to struggle? Not because I’m pessimistic. But because I’m responsible. Capital represents years of discipline, sacrifice, and hard work. It deserves more than excitement. Here’s what you should stress test before looking at upside (this is what I look at): • Debt terms under pressure -- what if rates stay higher longer? • Refinance risk -- is there real breathing room at exit? • Cap rate expansion -- are we underwriting conservatively? • Expense creep -- are we being honest about operating realities? • Operator liquidity -- can the sponsor support the asset if needed? If a deal only works in a perfect environment, it’s not resilient. And resilience is where real wealth is built. I’m optimistic about opportunity. But optimism without discipline is speculation. If you’re evaluating investments right now, here’s something actionable: Take one opportunity in your portfolio and ask, “What would need to go wrong for this to struggle -- and am I prepared for it?” Run the downside scenario. Stress test your assumptions. Don’t just chase upside. Engineer durability. That balance (optimism + discipline) is what compounds over time. Let’s build wisely.

My Amazon System for Turning Chaos Into Clarity (That I Still Use Today) At Amazon, chaos wasn’t unusual. It was the operating environment. Multiple teams. Conflicting priorities. Incomplete information. Everything urgent, everything important. Early in my career, I tried to keep up by reacting faster. That didn’t work. What worked was building a simple system that helped me turn chaos into something manageable. Here’s the framework I used again and again. 1/ Write down what we actually know ↳ Facts only. ↳ No assumptions, no opinions. What changed? What hasn’t changed? What data do we have? Once the facts are visible, chaos usually shrinks. 2/ Define the real problem in one sentence ↳ Not: “The launch is complicated.” ↳ Instead: “We don’t have a clear owner for integration testing.” Precise problems lead to solvable decisions. 3/ Identify the two or three decisions that matter ↳ If everything feels urgent, nothing is prioritized. ↳ I forced the conversation into a small number of decisions. Constraint creates clarity. 4/ Draft the path forward before asking for alignment ↳ Proposed timeline ↳ Proposed owners ↳ Proposed tradeoffs People move faster when they react to something concrete. 5/ Repeat the same narrative everywhere ↳ In the doc ↳ In the meeting ↳ In the update Consistency eliminates confusion. This system didn’t eliminate complexity. But it made complex problems workable. And that’s what great program management really is. 📬 I write weekly about leadership, program management, and operating in high-pressure environments in The Weekly Sync: 👉 https://lnkd.in/e6qAwEFc What’s one technique you use to bring clarity when things feel messy?

Minimal resources, tight timelines, high expectations. We've all been there. Here’s how I deliver big projects in tough times as a VP of Engineering: ▪️ Prioritize with Purpose -When you can’t do everything, focus on the right things. Ruthlessly align efforts with goals that deliver the most value. ▪️Foster Creativity Through Constraints - Limitations can force you to think outside the box. Invite your team to find clever, simple solutions that might never have been considered with a big budget. ▪️Communicate Relentlessly - When resources are tight, the margin for error shrinks. Make sure every team member understands the plan, their role, and the "why" behind each decision. ▪️Build Team Resilience- Celebrate wins--big and small. When your team feels appreciated and focused, they’re more likely to rally together and innovate under pressure. One of my most vivid memories as a technical executive was doing exactly this- leading a high-visibility initiative where the budget felt more like a suggestion than a reality. There’s nothing quite like delivering a big project on a shoestring budget. I remember sitting in a room with my team, staring at a list of features and a budget that made us all laugh nervously. But instead of despairing, we got creative. We started by ruthlessly prioritizing: “What’s the one thing that will deliver the most value?” We questioned everything--every line of code, every resource allocation, every timeline--to ensure it was necessary and impactful. The result? A launch that exceeded expectations. We didn’t have everything we wanted, but we focused on delivering what mattered most. Looking back, I wouldn’t trade that experience for anything. It taught me that innovation isn’t about having all the resources--it’s about making the best of what you’ve got. Have you ever had to deliver something when resources were tight? How did you approach it? and what did you learn along the way? Drop your story in the comments--I’d love to hear how you thrived under pressure!