LazyPay Design
Published in

LazyPay Design

We tried a 3-hour remote design sprint

And this is what we learnt from it

Colourful graphics which say “Ready, set, sprint”

Sprints are well-suited for ideating on new products, or for tackling open-ended problem statements where there’s a lot of room for exploration.

A screenshot of a Google meets meeting with 8 team members smiling
All smiles before the real work began

The objective

The agenda for our sprint on FigJam

Ready, set.. sprint!

Context setting (30 mins)

Business goals, data, scope of the sprint, personas and research insights
All the things we discussed during this 30 min slot

Diverge: Individual sketching (1 hour)

People working on sketches at home
Getting down and dirty with paper wireframes

Converge: Gathering feedback (1 hour)

Screenshot of the FigJam used for the sprint
Images and screens blurred for confidentiality

Voting (15 mins)

Picture of all the team members’ voting badges on FigJam
Time to stamp your face on the idea you like most


What we learnt

📝 Set clear expectations

Going forward, we plan to ask participants to express ideas in any form they’re comfortable with, so they can think in all directions without feeling judged.

🌳 Start small, then scale up

Next time, we’ll involve people from different functions in the organisation, like product managers, developers, marketing folks, and business teams.

⭕️ Limit the scope of the problem

In future, we’ll try to narrow down the scope even further, and add more specific constraints to the problem statement.



Stories from the design team at LazyPay

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store