Recently I heard a guest speaker in one of my classes talk about a bridge he helped build early in his career.

How the approach road washed out in the monsoons and the contractor disappeared. The decision he made to reroute materials by bullock cart. The engineer who said it couldn't be done. And the morning it opened.

He'd told this story a dozen times but every time differently, depending on who was in the room.

With his team, it was about not waiting for permission. With new hires, it was about what happens when the plan falls apart. With me, sitting across the dinner table, it was something else entirely: this is how you figure things out when no one is watching.

Most people answer this question the way a typical engineer could have answered it: the name of the bridge, the budget, the timeline, the delivery date.

It's accurate. It's also forgettable. What the interviewer is actually assembling, sentence by sentence, is a picture of you.

These aren't follow-up questions. They're the question. "Walk me through your most impactful project" is just the polite version.

The most useful frame for this answer is one that mirrors how good stories actually move: Situation → Complication → Resolution.

Situation sets the scene. Brief. What was the project, who was involved, what were you trying to do.

Complication is where most people rush past. But that’s where the interviewer actually leans in. What went wrong, got harder, or turned out to be different than expected. This is where your judgment shows up.

Resolution is not just the outcome. It's what you did, why, and what you'd carry forward.

Here's what this sounds like when it's not working:

"I led a supply chain redesign that reduced delivery times by 40%. We restructured vendor relationships, built a new tracking system, and delivered ahead of schedule."

Clean. Impressive on paper. But the interviewer has learned almost nothing about you.

Now the same project, using SCR:

Situation: "We were losing mid-tier accounts — not to price, but to delivery unpredictability. My brief was to fix the supply chain. Six months, cross-functional team, real urgency."

Complication: "About six weeks in, we realized the problem wasn't the vendors. It was internal — our own demand forecasting was feeding bad data upstream. The whole diagnosis had been wrong. We had to restart the analysis, reframe the brief to leadership, and rebuild trust with a vendor partner we'd already accused of being the problem."

Resolution: "We fixed the forecasting model, rebuilt the vendor relationship, and hit the delivery target — three weeks late, but with a much sounder foundation. The bigger lesson: I now ask 'What are we assuming?' before we ask 'What are we fixing?'"

Same project. Same outcome. A completely different picture of the person.

Pick one project — not necessarily your biggest, but one where something genuinely went sideways. Write it out in three parts.

Situation: One or two sentences. What were you trying to do, and with whom?

Complication: This is the part worth spending time on. What actually made it hard? Not the difficulty of the task — the unexpected turn, the wrong assumption, the moment when the original plan stopped working.

Resolution: What did you do, and what would you carry forward?

Say it out loud. Aim for ninety seconds. If you're past two minutes, the complication is probably too long or the situation is too detailed.

Then ask yourself: Does this answer tell someone how I think?
If the answer is yes, you're close.