Deliver quickly, iterate fast, keep the user in the center of the process. This is what we aim when using an agile methodology as SCRUM.

  • A lot of iterations were needed in the high fidelity mockup phase even before putting the mockups in front of the users, this was mostly a consequence of the previous point;
  • The knowledge gathered in the process wasn't spreading far enough inside the team, although almost everyone participated in the discussion or at least read through it, after that, all of the iteration was closed between the members of the team directly working on the features.
  1. Diverge - in the Diverge phase we aim to find possible solutions for the problems at hand, trying to discuss as many different solutions as possible;
  2. Converge - As the name implies, the objective here is to start from the divergent solutions and finish with the single best solution;
  3. Prototype - In the prototype step, the team will make user testable prototypes of the solution we got from the converge phase;
  4. Validate - Test the solution with potential users using the prototypes made.
  • We were going to tackle a pretty big project and splitting it in 5 days design sprints would make it pass our wished release date;
  • Our target user base is really specific and has a couple of attributes that make user testing really challenging:
    - They have limited available time, this limits the number of iterations we can have with each one;
    -They are not tech savvy, making it extremely hard to test using low fidelity prototypes;
    -They are in a different continent (we are based in Portugal and our target market is the USA).
  • We removed the validation phase;
  • We crunch everything else from 4 days to 1,5 days…

Team composition

With the main objective of reaching a feasible solution while starting with a rich enough diverge phase, we decided that a 5 member team was the right size.
Enough to diverge while keeping the discussions manageable.
Having different skill-sets hopefully would also help on the diverge phase.

The 3 Phases design Sprint

Due to the nature of our target audience we decided that high fidelity prototypes were needed, so we decided to remove the user testing phase from the design sprint.

  1. Diverge- As in the previous phase we reduced the length from a full day to half a day.
    The diverge phase starts from the critical path of the understand, for each step in the path this is our activities schedule:
    - Mind mapping (10 min);
    - Crazy Eight (5 min);
    - Storyboard (20 min);
    - Silent Critique (5 min);
    - Group Critique (15 min)
  2. Converge- One more time we aimed to reduce the converge from one full day to half a day in length. This is our activity schedule:
    - Review Assumptions (30 min);
    - Review Back Burner (15 min);
    - Identify storyboard conflicts (30 min — for each critical path step)
    - Compose the final storyboard (30 min — for each critical path step)
an example storyboard at the end of the Converge phase
  • There is no need for internal iteration on the mockups before going to the user tests.
    The mockups are reviewed by the product team before being tested and before they almost everytime needed some type of corrections. This need just vanished.
  • Rotating the team members between design sprints brings an overhead for each sprint. As most of the sprints use knowledge collected in the previous ones, this knowledge needs to be passed to the new team members and that takes a big chunk of the Understand phase.

Tools helping us implement the design sprint results

  • Invision (
    Using Invison, tightly integrated with the tool of choice for our design team, Sketch, the engineering team has a near real time view of the mockups evolution while they are being worked on.
  • Lookback (
    With lookback we are able to do remote user testing sharing the invision prototypes and recording audio, screen and video of the user while testing.
    It’s still in beta but is awesome!

Indie Campers Director of Product & Tech/ Web addict

Indie Campers Director of Product & Tech/ Web addict