Delivery under pressurePrioritizationAutonomyEnterprise customerIntentional tradeoffs
S — Situation
An enterprise customer had a hard deadline and needed a dashboard copy feature — letting users duplicate dashboards to edit freely without touching the original. Normally a 3+ week effort including design reviews and full testing cycles.
T — Task
Ship it in one week. The challenge wasn't just speed — it was making fast decisions responsibly so nothing broke and future cleanup was manageable.
A — Action
Deprioritized everything else. Made design calls myself using existing components for consistency — documented every decision for the designer to review after. Scoped testing to critical paths only, explicitly deferring edge cases with a written log of what was cut and why.
R — Result
Shipped in one week. Customer hit their deadline. In the next sprint, reviewed deferred decisions with the designer — minor polish in v2. Core takeaway: moving fast is possible without cutting corners if you defer intentionally and document everything.
1 week vs 3+ weeksenterprise deadline metclean v2 follow-up
90-second version — ready to say out loud
"One of our enterprise customers had a hard deadline and needed a dashboard copy feature — the ability to duplicate a dashboard and make edits without touching the original. Normally something like that would take three or more weeks given our design review process, testing cycles, and back-and-forth. We had one week.
I deprioritized everything else I had going and focused entirely on this. The key decisions I had to make fast were around design and testing. Rather than going through the normal review cycle, I made the design calls myself — using our existing component library to stay consistent — and kept detailed notes on every decision so the designer could review them after the fact. On testing, I scoped to critical paths only and explicitly logged what I was deferring and why, so it wouldn't get lost.
We shipped in one week. The customer hit their deadline and was happy. In the next sprint I sat down with the designer, they had some minor feedback, and we polished it in v2.
The takeaway I carry from that: moving fast doesn't mean cutting corners — it means being intentional about what you defer and making sure it's documented and followed up on."
"Delivered under time pressure"
Lead with: 1 week vs 3-week normal timeline
Primary question — use the script above directly
"Prioritization / what do you cut?"
Lead with: the framework — defer intentionally, document it
The decision logic is the answer, not just the outcome
"Working autonomously"
Lead with: made design calls independently, documented for review
Shows you can unblock yourself without creating tech debt
"Balancing speed and quality"
Lead with: fast ≠ reckless if you track your tradeoffs
The deferred-but-documented approach is the key insight
Key phrase to land clearly: "I didn't cut corners — I deferred intentionally and documented everything." Make sure it doesn't sound like you just went fast and got lucky.