Designing in a Pandemic: Integrating Speed and Rigor

Key Insights

• •

  Prioritizing what customers need most during a crisis helps guide which features and fixes to focus on for faster delivery.

• •

  Breaking work into parallel streams allows teams to work concurrently, speeding up overall progress without sacrificing quality.

• •

  Using low-fidelity, untested mockups can be sufficient to start technical development early, enabling faster iteration cycles.

• •

  Vertical slices focus on specific parts of the experience, while horizontal slices provide a general outline before deep dives; combining both can optimize workflows.

• •

  Launching a minimally viable but usable product during urgent situations can better serve customers than waiting for perfect.

• •

  Developers only need a general outline, not pixel-perfect designs, to begin feasibility assessments and coding.

• •

  Organizations can repurpose staff (e.g., office colleagues volunteering for order picking) to meet unexpected demand spikes.

• •

  Competitive pressure (like a rival launching delivery) can force teams to reshuffle and prioritize work for speed gains.

• •

  Managing technical debt during rapid development can be done by breaking fixes into smaller incremental improvements tied to business goals.

• •

  Digital products’ inherent flexibility allows continuous post-launch improvements, making speed-first approaches less risky.

Notable Quotes