Time Management In Crisis

"War-Life Balance , Week 3" I wrote about this last week. I didn't think I'd need to write it again. Three weeks now. Sirens at 2am. Running to shelters mid-meeting. Endless nights watching the news instead of sleeping. Watching my team do it night after night. War-life balance isn't a concept from a leadership book. It's what happens when your calendar has a board call at 9am and a rocket alert at 9:03. And yet — deadlines don't know there's a war. Clients don't pause. The business keeps moving. So how do you actually keep a team together when the world outside feels like it's falling apart? Here's what I've learned (the hard way): 1. Empathy first. Everything else second. Not as a tactic. As a starting point. Before any agenda, before any update — ask how they are. Really ask. Then actually listen. 2. Ruthless focus on what truly matters. In chaos, everything feels urgent. Almost nothing is. Strip the to-do list to the core. Give your team clarity when the world isn't giving them any. 3. Flexibility isn't a perk right now. It's survival. Don't count hours. Count outcomes. If someone needs to disappear at noon because their kid needs them - that's the right call. 4. Patience. More than feels natural. Cognitive load during crisis is real. People are slower, more distracted, less creative. That's not weakness. That's human. Adjust your expectations - and say that out loud. 5. Words matter. Actions matter more. We've been sending food deliveries. Surprise packages to the door. Supporting team members who needed to get their families out of the country for a few days. Small gestures that say: we see you, and you're not alone in this. War-life balance isn't about finding perfect equilibrium. It's about leading with enough humanity that your people can keep going - even when you're all running on empty. Week 3. Still standing. Still building.

Surprise missed deadlines are a major headache.  They disrupt workflows, create unnecessary stress, and leave everyone scrambling to catch up. But what if there was a better way? When you miss a deadline, it hurts your reputation and credibility. You can avoid this through 𝐩𝐫𝐨𝐚𝐜𝐭𝐢𝐯𝐞 𝐜𝐨𝐦𝐦𝐮𝐧𝐢𝐜𝐚𝐭𝐢𝐨𝐧. By letting your manager know about potential roadblocks as soon as you know about them, you become a problem-solver, not a problem creator. This not only reduces stress for everyone involved, but also builds trust and strengthens your professional presence. As the former Head of Editorial at Prezi, here are three strategies my team members used that I appreciated so much: ✅ Flag potential delays early. It benefited the whole team when I got alerted about a roadblock ahead of time. This gave everyone time to adjust, discuss solutions, and minimize the negative impact. ✅ Be specific and be clear. Be upfront about the situation and the impact it might have on the deadline.  ✅ Offer solutions and not just excuses. Coming to your manager with a plan demonstrates responsibility and initiative.  This could involve suggesting an extension, proposing a revised deliverable, or outlining how you plan to catch up. You can save this script for future use: "𝘏𝘪 [𝘔𝘢𝘯𝘢𝘨𝘦𝘳 𝘕𝘢𝘮𝘦], 𝘐'𝘮 𝘳𝘦𝘢𝘤𝘩𝘪𝘯𝘨 𝘰𝘶𝘵 𝘣𝘦𝘤𝘢𝘶𝘴𝘦 𝘐'𝘮 𝘦𝘯𝘤𝘰𝘶𝘯𝘵𝘦𝘳𝘪𝘯𝘨/foresee 𝘢 𝘥𝘦𝘭𝘢𝘺 𝘸𝘪𝘵𝘩 𝘗𝘳𝘰𝘫𝘦𝘤𝘵 𝘈.  𝘋𝘶𝘦 𝘵𝘰 𝘙𝘦𝘢𝘴𝘰𝘯 𝘟, 𝘐 𝘮𝘪𝘨𝘩𝘵 𝘯𝘰𝘵 𝘮𝘦𝘦𝘵 𝘵𝘩𝘦 𝘰𝘳𝘪𝘨𝘪𝘯𝘢𝘭 𝘥𝘦𝘢𝘥𝘭𝘪𝘯𝘦 𝘰𝘧 [𝘋𝘢𝘵𝘦]. 𝘐'𝘷𝘦 𝘦𝘹𝘱𝘭𝘰𝘳𝘦𝘥 𝘢𝘭𝘵𝘦𝘳𝘯𝘢𝘵𝘪𝘷𝘦 𝘴𝘰𝘭𝘶𝘵𝘪𝘰𝘯𝘴, 𝘢𝘯𝘥 𝘐 𝘱𝘳𝘰𝘱𝘰𝘴𝘦 𝘚𝘰𝘭𝘶𝘵𝘪𝘰𝘯 𝘠.  𝘗𝘭𝘦𝘢𝘴𝘦 𝘭𝘦𝘵 𝘮𝘦 𝘬𝘯𝘰𝘸 𝘺𝘰𝘶𝘳 𝘵𝘩𝘰𝘶𝘨𝘩𝘵𝘴." Proactive communication is a win-win. Managers appreciate the heads-up and can adjust accordingly. You avoid the last-minute scramble and maintain trust with your team. Remember that all these tips don’t just apply to big projects! The same principles apply to smaller tasks as well. Building this communication habit will put you ahead of the game — and impact your presence in terms of how your colleagues see you. 💬 How do you communicate missed deadlines in advance? Let’s exchange tactics in the comments! #ExecutivePresence #Communication #ProfessionalPresence #WorkplaceTips

My husband sat silently during his leadership team's 3AM crisis call - our biggest client threatening to walk. "Jump in!" I urged, sliding him coffee. "You're the CEO. They need direction." He shook his head, took notes, and waited. I watched anxiety ripple across his team's faces on Zoom. The revenue loss would force layoffs. The silence was unbearable. 107 minutes in, when everyone had exhausted their ideas, he unmuted, shared his screen, and presented a framework so unexpected that his normally vocal CMO actually gasped. By 6AM, not only had the client stayed, they doubled their contract. "Why let them struggle so long?" I asked later. His response changed my approach to everything: "Strategy + patience = automatic win. The first ideas are rarely the best ones." The next week, I tried his approach when: • My feature requirements were rejected by engineering (waited 48 hours → came back with clearer user stories they approved immediately) • Our MVP launch metrics disappointed stakeholders (analyzed data for 2 weeks instead of rushing changes → identified the actual user pain point) • A competing product launched with our planned functionality (studied user feedback for a month → built a differentiated solution that's now our highest-rated feature) The most valuable move in product management might be the strategic pause everyone else is too afraid to take. What's your story of patience paying off when sprint deadlines were looming? #ProductManagement #LeadershipInsights #ProductStrategy

How to Rescue a Dying Project , Without Burning Out Your Team Let’s be real for a moment: No project is invulnerable to crisis. If you’ve been in the game long enough, you’ve seen deadlines slip, scope creep get out of control, and your team’s morale dive like it’s trying to break records. But here's the truth: You can turn things around without losing your team’s well-being. It’s not about pulling off a miracle,it’s about managing the chaos with purpose and keeping your focus on what really matters. Here’s what I’ve learned: 1️⃣  Step Back and Assess the Situation When everything is on fire, your first instinct might be to act fast. Nevertheless, sometimes the best thing you can do is to stop and think. I’ve inherited projects on the brink of collapse, and when I paused to ask, “What’s the root cause of this problem?” instead of rushing in to fix symptoms, it made all the difference. 2️⃣ Prioritize Ruthlessly No project is too far gone if you simplify. The number of tasks and deliverables often grows exponentially in a crisis. The key to recovery is deciding what truly matters and leaving the rest behind. In one project, we reduced the list of “urgent” tasks from 50 to just 5 critical items and suddenly, the team had clarity and focus again. 3️⃣ Delegate with Confidence If you’re trying to do everything, you’re setting yourself up for failure. Trust your team to own their roles. Yes, this means giving up control (and I get that it’s hard), but the truth is, your team has expertise you might not have. I found that giving people autonomy created ownership, and that’s where the magic happened. 4️⃣ Over-Communicate, Especially When It’s Hard Bad news doesn’t get easier with time, and silence is the enemy of progress. Whether it’s with your team or stakeholders, keep communication clear and consistent. When things went sideways on a project I led, I over-communicated, weekly check-ins, constant updates, and candid conversations. The trust we built made all the difference when we had to course-correct. 5️⃣ Don’t Forget the Team’s Health A healthy team is a productive team. If you’re burning the candle at both ends, so are they. Stress is contagious. Show up with empathy and model balance. Celebrate progress, no matter how small. And don’t just talk about self-care, encourage it. I’ve found that teams are resilient, but only when they feel supported. 🔥 Remember, projects don’t need a superhero to save them. They need a leader who knows how to navigate chaos, prioritize, delegate, communicate, and protect the team’s well-being. If you can do that, you’ll pull through and your team will thank you for it. Feel free to add and share any lessons learned in comments ! #Leadership #ProjectManagement Innovera Conseil

Finance doesn’t run on vibes; it runs on deadlines. Meet Jide, a junior accountant handling the month-end close. He thought he had enough time and decided to work through tasks in no particular order. Instead of prioritizing, he bounced between emails, reconciliations, and chatting with colleagues. By the time the head of finance requested a schedule, he hadn’t even finished payroll and inventory adjustments. The pressure got to him. He stayed late, skipped lunch, and still he missed the deadline. The head of finance wasn’t happy, and his credibility took a hit. The painful lesson? Hard work without time management leads to stress, errors, and excuses. Now meet Chioma, a finance associate with the same workload and the same deadline. She approached things differently. On day one, she listed out all tasks and used a priority matrix: urgent tasks first, important ones scheduled, and non-essentials left for later. She blocked 2-hour windows each morning to handle reconciliations without interruptions, leaving her afternoons for emails and meetings. Whenever small requests came in, she used the two-minute rule to clear them quickly, then refocus. When the head of finance asked for schedules, Chioma was ready. Her numbers were accurate, she finished on time, and her manager trusted her more than ever. The difference? Not luck! It's just smart time management. Deadlines don’t care about your excuses. They only reward those who plan, prioritize, and execute with discipline. ⏹️ 3 Habits & Tools That Save the Day for me: ✔️ The Priority Matrix (Urgent vs. Important) Not everything on your desk deserves your attention right now. I use a simple 4-box matrix: ▪️ Urgent & important tasks get my first energy ▪️ Important but not urgent tasks get scheduled, while the rest can wait or be delegated. ✔️ Time Blocking Multitasking feels productive, but often isn’t. I block out specific hours for specific tasks. For instance, mornings are for reconciliations when my brain is freshest, while afternoons are for meetings and reviews. This way, I don’t spread myself too thin, and I hit my deadlines with fewer errors. ✔️The Two-Minute Rule If a task takes less than two minutes, I do it immediately, replying to a quick email, signing off on a document, or forwarding a schedule. Small tasks left undone pile up and eat into the time you could use for big tasks. Clearing them fast creates mental space for the heavy stuff. ⏹️ Why This Matters ✔️ Deadlines are non-negotiable in finance. ✔️ Missing them can mean penalties, loss of trust, or worse. Remember that time management is not just about being “organized”; it’s about protecting your credibility and sanity in a high-stakes role. What’s your go-to productivity hack when deadlines pile up? Do you rely on coffee, sticky notes, time blocking, or something else? Kindly share in the comment section. I’d love to learn from your strategies too!

My first month at Bain & Co. after IIT Bombay... I dreaded having to tell my manager that a project deadline was due and slipping, with only little progress done. At IIT, if you were running late on an assignment, there were usually only two options: Work harder, or pull an all-nighter. You handled the stress yourself. But on a client project, hiding a delay is one of the fastest ways to destroy trust. I remember working on a financial model where the client data was a mess. Cleaning it would take an extra day, which meant our internal review deck would be delayed. I spent more time worrying about how to tell my manager than fixing the actual problem. When I finally walked into his room, expecting a difficult conversation, he said something I've never forgotten: "I don't mind bad news. I mind bad news delivered too late, and without a solution." Looking back, that one conversation changed how I think about ownership at work. Three lessons stayed with me: 1. No surprises. Never wait until a deadline has already passed to say you're behind. The moment you realize a roadblock will delay your work, flag it. A manager can easily help pivot client expectations if they have a few hours' notice. But they can't help you if you tell them at 5:59 PM for a 6:00 PM meeting. 2. Never bring a problem without a proposal. When you flag an issue, your sentence shouldn't end with: "What should I do?" It should end with: "Here are two ways we can solve it. I recommend option A." For example: "The client data is corrupted, which delays the model by a day. We can either manually patch the key segments tonight or wait for a clean extract tomorrow. I recommend the patch." Now you're not escalating a problem. You're facilitating a decision. 3. Move the conversation from panic to control. Senior leaders don't panic because something went wrong. They panic when they don't know what's happening. The fastest way to build trust is to provide visibility, options, and a recommendation. The moment people feel they have control over the situation, a crisis becomes a decision. One of the biggest adjustments from IIT to consulting wasn't learning strategy or finance. It was learning that ownership doesn't mean carrying every problem alone. Sometimes ownership means raising your hand earlier. What's a professional lesson you learned at work that nobody taught you in college? #learning #consultingcareers #communication #professionalgrowth #productivity #bain #iitb

Why I plan for things to go wrong [This is the last in the "starting the year right" series: what needs to come into your project setup and how to get it right from day one.] Well, there was a time I believed good planning meant accounting for every scenario. Experience taught me something better: 𝐒𝐭𝐫𝐨𝐧𝐠 𝐩𝐥𝐚𝐧𝐬 𝐝𝐨𝐧'𝐭 𝐚𝐬𝐬𝐮𝐦𝐞 𝐩𝐞𝐫𝐟𝐞𝐜𝐭𝐢𝐨𝐧. 𝐓𝐡𝐞𝐲 𝐚𝐬𝐬𝐮𝐦𝐞 𝐩𝐫𝐞𝐬𝐬𝐮𝐫𝐞. Experienced PMs don't build plans hoping nothing breaks. They actually build plans expecting that something will. So early on, I'm asking: ↪️Where do we have room to move if timelines slip? ↪️What can be deprioritized without breaking outcomes? ↪️What are the non-negotiables we protect at all costs? Its also important to note that Flexibility isn't about being vague but about 𝐛𝐞𝐢𝐧𝐠 𝐡𝐨𝐧𝐞𝐬𝐭 𝐚𝐛𝐨𝐮𝐭 𝐜𝐨𝐧𝐬𝐭𝐫𝐚𝐢𝐧𝐭𝐬. When the team build room to adapt early, decisions later feel deliberate and not reactive. And when pressure shows up, the project simply bends instead of breaking. Here's what this looks like in practice: 📍I identify the three most likely failure points before kickoff. The ones that would actually derail us. Then I build contingencies that don't require a miracle to execute.👌🏽😁 📍I mark decision points in the timeline & not just milestones. Week 4: Review resource allocation. Are we still on track, or do we need to shift? Week 8: Reassess priorities. What's slipping, and what matters most? Week 12: Reality check. What do we need to protect to still call this a win? These aren't crisis meetings. They're planned moments to course-correct before we're in crisis mode. 📍I get stakeholders to agree on trade-offs upfront. "If timeline slips, do we cut scope or add resources?" "If budget tightens, what drops first?" "What does 'good enough' look like if perfect isn't possible?" And I don't wait until we're underwater to ask these questions. Because by then, every answer already feels like a compromise. And that's it! 𝐀 𝐫𝐢𝐠𝐢𝐝 𝐩𝐥𝐚𝐧 𝐥𝐨𝐨𝐤𝐬 𝐜𝐨𝐧𝐟𝐢𝐝𝐞𝐧𝐭 𝐨𝐧 𝐩𝐚𝐩𝐞𝐫 𝐛𝐮𝐭 𝐟𝐥𝐞𝐱𝐢𝐛𝐥𝐞 𝐨𝐧𝐞 𝐬𝐮𝐫𝐯𝐢𝐯𝐞𝐬 𝐫𝐞𝐚𝐥𝐢𝐭𝐲. And the difference between the two is whether you planned for things to go right or planned for what to do when they don't. [This brings together everything from the past week: the templates, the stakeholder mapping, the decision frameworks, the senior-level thinking.] I hope we all have a great start to our projects, initiatives, and deliverables in 2026. Let's talk...What is/are your approach(es) to building flexibility into your projects? Follow Benjamina for practical perspectives on #projectexecution, #leadership judgment, and #delivery under real constraints.

Six months behind. Legally mandated deadline. Failure meant regulatory penalties, audits, & legal exposure. No pressure. A regulatory compliance program was supposed to start 12 months before the deadline. But when I stepped in, it hadn’t even begun. Six months had already been lost. The project was stuck in a dangerous loop: > Regulatory language was vague and open to interpretation > Teams were resisting the effort > Requirements weren’t defined > Leadership alignment didn’t exist > No one owned the path forward Meanwhile the legal deadline wasn’t moving. This wasn’t a project. It was a potential regulatory crisis. So the first step wasn’t planning. It was stabilization. The program required someone operating across multiple roles simultaneously: > Program recovery > Requirements translation > Architectural coordination, > Executive alignment under extreme time pressure. I shifted into recovery mode & rebuilt the program from the ground up. 1️⃣Rapid stakeholder mobilization We brought legal, architecture, engineering, & business leaders together to translate regulatory language into clear tech & operational requirements. Ambiguity had been the blocker. Clarity unlocked execution. 2️⃣Adaptive governance The teams involved operated in very different delivery models, & required direct executive alignment. Instead of forcing a framework, I built an adaptive governance structure that connected teams & ELT through: > Executive communication and decision checkpoints > A formal C-suite SteerCo > Clear escalation paths > Shared milestones tied to the regulatory deadline This removed fragmentation, ensuring technical execution & executive risk management stayed aligned. 3️⃣Iterative requirements refinement Regulatory language rarely translates cleanly into systems. I ran structured refinement sessions to: > Identify compliance requirements > Validate technical feasibility > Architect controls that satisfied both regulatory & operational needs This turned vague mandates into executable workstreams. 4️⃣Non-negotiable approval gates Under extreme timeline pressure, teams often skip validation. We did the opposite. Critical approvals were built into the program to ensure: > Compliance alignment > Architectural integrity > Audit defensibility Speed without rigor would have created bigger risks later. THE RESULT Despite starting six months late, the program delivered before the legal deadline. > Zero regulatory penalties > Zero audit defects > No legal exposure > No additional budget required The difference wasn’t working harder. It was turning regulatory ambiguity into executable workstreams & decisions. And the biggest risk? It wasn’t the timeline.  It was lack of ownership. Leadership isn’t about managing tasks. It’s about creating clarity fast enough for the organization to execute. And once someone owns the problem, translates the requirements & aligns leadership… Execution follows. ___  ♻️ Repost 🔔 Follow Elizabeth Dworkin

Half your team was just laid off, and somehow you're expected to do the work of ten people. Leadership sent a Slack message about "organizational efficiency," thanked everyone for their flexibility, and expected you to figure out the rest. No additional resources. No extended deadlines. Just you, staring at a roadmap that was already ambitious when you were fully staffed. Here's the truth they won't tell you: You cannot do the work of ten people. Not even close. The sooner you accept that, the sooner you can lead strategically instead of reactively. ━━━━━ 𝗙𝗼𝗿𝗰𝗲 𝘁𝗵𝗲 𝗽𝗿𝗶𝗼𝗿𝗶𝘁𝘆 𝗰𝗼𝗻𝘃𝗲𝗿𝘀𝗮𝘁𝗶𝗼𝗻 Walk into your manager's office with the list. "Here are the five things we can actually deliver with the team we have left. Everything else stops, gets delayed, or breaks. Which five matter most to you?" Make them choose. Get it in writing. 𝗦𝘁𝗼𝗽 𝗯𝗲𝗶𝗻𝗴 𝘁𝗵𝗲 𝗼𝗿𝗴𝗮𝗻𝗶𝘇𝗮𝘁𝗶𝗼𝗻𝗮𝗹 𝗯𝗮𝗻𝗱-𝗮𝗶𝗱 Your instinct is to step in and cover every gap so nothing falls apart. Don't. If you absorb all the pain, leadership never feels it, and they'll never prioritize backfilling roles. Let something break. Choose what breaks strategically. 𝗣𝗿𝗼𝘁𝗲𝗰𝘁 𝘁𝗵𝗲 𝗽𝗲𝗼𝗽𝗹𝗲 𝘄𝗵𝗼 𝘀𝘁𝗮𝘆𝗲𝗱 Your remaining team is watching how you handle this crisis. If you burn them out trying to pretend ten people didn't just disappear, they'll update their LinkedIn profiles and leave too. Redistribute work honestly, not desperately. 𝗗𝗼𝗰𝘂𝗺𝗲𝗻𝘁 𝗲𝘃𝗲𝗿𝘆𝘁𝗵𝗶𝗻𝗴 Keep a running record of delayed projects, dropped priorities, and risks you've flagged. When things inevitably slip, you need proof you saw it coming. This protects you and your team when blame starts getting assigned. ━━━━━ You didn't create this disaster. You're not responsible for compensating for leadership's choices with personal martyrdom. Your job is to navigate the chaos with clarity, protect your people, and survive with your integrity intact. Working 70-hour weeks to cover for a layoff isn't heroic. It's free labor for a company that already made you more expendable. Guard your energy like the finite resource it is. How many hours did you work last week that no one will ever thank you for? 💫 ━━━━━ If you're navigating this exact chaos right now, The Arena is for leaders who want to lead effectively inside the system without burning out or becoming a political casualty.