How it works The original Design Sprint framework or Design Sprint 1.0 is a 5-stage process that runs over the course of 5-days to solve big problems and answer critical business questions. Besides team bonding, the team will develop a shared sense of ownership which will help to carry over the results (as opposed to a prototype a designer or agency built). A design sprint is a flexible product design framework that serves to maximize the chances of making something people want. Popularized by Jake Knapp in the book “Sprint”, the design sprint framework is now being adopted by companies big and small, and from all over the world within different industries. We’re currently traveling the world and we’re excited to be working with different industries. So, after a quick introduction over lunch, Artefact One was invited to start right away and we did a kick-off that very afternoon. Before this, they had worked on separate concepts and not everyone was up to date with the latest client feedback. On Thursday, you build a realistic prototype. . Since MAPP needed a quick and effective method to align towards a common goal and involve their team in a creative session, the format of a design sprint offered a lot of benefits: First, it would allow the entire team to align and agree on one direction. We decided that the benefits trumped the downsides. On Monday, you create a map of the problem. This article is meant to shed some light on how introducing design sprints into the field of architecture and adapting them to the field, can lead to great results within a short period of time. Or alternatively, the problems we were tackling were too broad to allow a practical solution or too narrow to be worth the investment. Feel free to share your stories below or reach out to us personally if you’d like to share your thoughts about this. It is an intense effort conducted by a small team where the results will set the direction for a product or service. The sprint enabled the team to reach a common understanding of requirements, and it helped grow the team’s confidence with the project. Artefact One joined forces with landscape and hardscape architecture firm MAPP, who contacted us with a challenge: They were working on a large corporate project for a client where multiple stakeholders had different areas of influence. And finally, on Friday, you test that prototype with five target customers. On Tuesday, each individual sketches solutions. The way we adapted it to fit the architecture workflow and our client’s timeline looked something like this: In our adaptation, we skipped days 4 & 5, mainly for two reasons: Can you really have a testing day with users for an architecture design sprint? It acted as a team-building activity — all team members contributed ideas and felt that their input mattered. We are excited to answer this question together with MAPP, so we’re going to do a brainstorm and write an article about our conclusions as a follow-up…. We will use the rest of the morning, for the Solution Sketch. This field is for validation purposes and should be left unchanged. The heated discussions from Tuesday’s storyboarding session are now a thing of the past, and with a clear head, the team reviews and refines the storyboard (if needed) while at the same time assigning roles and planning prototyping work (1 hour tops). This is especially important in more hierarchical cultures. Thirdly, it would follow the design thinking approach to problem-solving — a step by step format that starts with understanding the project scope and ends with quickly testing a solution. We refined the second day of the design sprint by kicking off with ideation and ending it with a cohesive storyboard. how would that look like? Secondly, it would provide clear instructions for the team to brainstorm, all within their specific time constraints. Design Sprint distilled the 3 key qualities of Design Thinking: 1) Identify the right problem to solve. Moment of truth. The team came up with a truly shared vision and were well aligned on the delivered concept proposal. Problem Framing is a half to a full-day workshop that involves the main stakeholders, typically exec. Design Sprint made the problem-solving and learning process faster and more fun. For those of you who are not familiar with it, you can find a quick overview of the Design Sprint methodology HERE, or go ahead and take a deep dive by reading “Sprint” (thesprintbook.com). We are building Empathy with the User right from the first day of the sprint, by embedding research insights or existing data into the Understand and Define phase. With only a “minor” downside: we only had 3 days and we wouldn’t be able to do quick validation with users, an essential part of design sprints. On Monday, the Sprint Team (which most of the time is different than the one in the Framing) takes the time to understand the problem, context and all available information and insights. That is why it becomes critical to pick the right problem to solve to make this investment worthwhile. Then, on Wednesday, you decide which sketches are the strongest. Get updates on our workshops and other useful information about Design Sprints.