Remote Design Sprint Story

Role: Plan, prototype, assist in user testing, website development using Webflow
cover image featuring sample screens from the finished UI for iOS screens
Why redesign the website?
We craft beautiful experiences. Itโ€™s not just a slogan. Our CEO had no problem convincing potential clients of that in a recent event in October. But our website didnโ€™t exactly give the right image ๐Ÿ™ˆ

I moved to Turkey, the rest of my team was spread across 3 time zones now. So having heard of Realtimeboard and trying it out on my own, and being genuinely interested in design sprints as a service to offer, I proposed planning and carrying out a remote design sprint to redesign our website using Realtimeboard.
design sprint plan: day 1 miro board
Planning & Education
First, I educated myself on design sprints by referring to the book Sprint and many (many) youtube videos. I participated in a sprint before but Remote sprints are a little different, so I had to be prepared. Also, we had new team members who have never been in a sprint before, so I also had to provide resources for their reference.
Logistics
Internet connection, video calling solution, timetable, assigning roles.
I created a miro board that will play as our whiteboard / playground / wall during this sprint. In there I put:
- Sprint goal & questions.
- Embedded links to the YouTube playlist & important literature.
- a frame for each day containing list of activities, description, video, person leading -activity and timetable.
- frames for all activities to save time.
The Arena
remote design sprint: voting on sketches
Sprint Days
Planning and leading a remote design sprint is a fun yet difficult experience. Here's what I learned:
โ€
1. You need to remind team members of what each activity is before kicking it off, it saves so much time to have everyone aligned and on the same age when you start working.

2. use Realtimeboard's timing plugin. iIt's much easier to make people stop working that telling them to.

3. You can use the voting plugin, but my team preferred using small color coded circles to vote for winning concepts. which was super easy and fun.

4. always have two people prepared to lead a day's activities, one main and one backup. God knows what could happen.

5. On prototyping day, let the prototyper work ALONE and using the software they like. trust me; I tried to learn a new software on prototyping day and the result was not pretty.
โ€
ui style guide: components, textstyles, layer styles, color palettes

Testing Analysis

After the prototype was done I participated in testing analysis. Predictably, the prototype was hit hard UI wise ๐Ÿ˜… but all in all, we could see where we went right with our ideas and where we missed the mark. And thatโ€™s what we needed to know.

when that was done, I created a webflow account and built the real prototype putting all my front-end knowledge to use and learning some new things as well. Good times. And in the end, we subscribed to Miro ๐Ÿ˜‰
Read the Miyazaki Classic flavoured full story here