Describe a project where you handled a critical issue or crisis

 

The Day the Deadline Didn't Matter (And How We Saved the Project)

​Every Project Manager remembers "The One." That specific moment when the dashboard turns bright red, the client is on the phone, and the technical team is staring at a problem that looks unsolvable.

​Earlier this year, I was managing the launch of a high-traffic fintech platform. We were 48 hours from the "Go-Live" when a critical security vulnerability was discovered in our third-party payment gateway. If we launched, we risked data breaches. If we delayed, we lost a $2M marketing window.

​Here is how we navigated the storm:

​1. Stopping the Bleed (Immediate Action)

​The first instinct in a crisis is to panic-work. I did the opposite: I called a "Stop-Work" for 30 minutes. We gathered the lead architects and stakeholders to assess the impact vs. effort. We identified that the issue wasn't our code, but the integration layer.

​2. Radical Transparency

​I didn't sugarcoat it. I immediately contacted the stakeholders with a "Flash Report":

  • ​The Issue: Security vulnerability in the gateway.
  • ​The Risk: Potential data exposure.
  • ​The Plan: Evaluating a hotfix vs. a secondary provider backup.

​3. Empowering the Experts

​As a PM, I am not the one writing the patch. My job was to clear the path. I canceled all non-essential meetings for the dev team, ordered dinner for the office, and acted as the "Shield" against executive interruptions so they could focus entirely on the fix.

​4. The Result

​We found a workaround that involved a temporary "Manual Approval" flow for high-value transactions. It wasn't the "perfect" automated launch we dreamed of, but it was secure. We launched on time, and the vulnerability was fully patched 12 hours later without a single byte of data lost.

​The Lesson? A crisis isn't managed by working harder; it’s managed by communicating faster and prioritizing ruthlessly.

​Interview Answer (The "STAR" Method)

​Question: "Describe a project where you handled a critical issue or crisis."

​Situation: During the final phase of a retail ERP implementation, our primary data migration script failed, corrupting 15% of the legacy inventory records just three days before the system handover.

​Task: My goal was to recover the corrupted data and restore the project timeline without delaying the "Black Friday" freeze date set by the client.

​Action: * Isolated the Issue: I immediately pulled the technical leads into a war room to identify the root cause (a character encoding mismatch).

  • ​Managed Stakeholders: I proactively informed the Client Steering Committee, presenting a revised 72-hour recovery roadmap rather than just reporting the failure.
  • ​Resource Allocation: I re-assigned two senior devs from the "nice-to-have" UI polish team to assist the database team with manual data validation.

Comments

Post a Comment

Popular posts from this blog

Threshold Transactions Reporting (TTR) - Nepal

Image
              Threshold Transactions Reporting (TTR)   Definitions: TTR : It stands for Threshold Transactions Reporting. TTR is a report that financial institutions and Designated Non-Financial Businesses and Professions are required to file to FIU-Nepal for : Deposit, Withdrawal, Exchange of currency, Other payment or transfer; if it exceeds prescribed threshold limit Provided by FIU-Nepal.  Reporting Thresholds for Reporting Entities The regulators of REs have designated different threshold limits as stated in their AML/CFT directives. The designated thresholds for REs have been categorized into; 1) Bank and Financial Institutions – 5 Regulators 2) Other Reporting Entities. – 6 Regulators Threshold :- Bank and Financial Institutions Currently, the designated thresholds for Bank and Financial Institutions in Nepal are as follows by the regulatory NBR ( Nepal Rastra Bank): Cash deposit or ...
Read more

How do you stay curious about product details as a project manager

How do you stay curious about product details as a project manager? Interview question asked in Infosys? Staying curious about product details as a project manager isn’t just helpful — it's often the secret to bridging the gap between vision and execution. Here’s how experienced PMs keep that curiosity alive and useful: How to Stay Curious About Product Details as a PM. 1. Ask “Why” Like a Newbie — Even When You’re Not > Don’t just manage tasks — ask why that feature matters, who it’s for, and what happens if it’s removed. “Why did we pick this flow?” “Why does this feature need to launch in Phase 1?” This opens up dialogue with devs, designers, and users — and reveals assumptions you may need to challenge. 2. Join Customer Support Channels or Feedback Loops Sit in on support calls or read user feedback in tools like Zendesk, Intercom, Reddit, or app reviews. Curiosity grows when you see the product through users’ eyes. > Real users ask the best questions — and t...
Read more

Interview as a Requirements Gathering Technique: A Business Analyst's Perspective

Interview as a Requirements Gathering Technique: A Business Analyst's Perspective Requirements gathering is a crucial phase in any project, as it lays the foundation for developing solutions that meet business and user needs. One of the most effective techniques for eliciting requirements is conducting interviews with stakeholders. This technique allows Business Analysts (BAs) to obtain detailed insights, clarify ambiguities, and understand business goals directly from key individuals. Interview as a Requirements Gathering Technique An interview is a structured conversation between the Business Analyst and stakeholders to extract necessary information regarding project requirements. It can be formal or informal, depending on the project's scope and complexity. Types of Interviews Structured Interviews – These follow a predefined set of questions to ensure consistency in data collection. Unstructured Interviews – These are open-ended and flexible, allowing for free discuss...
Read more