Why a 3 Day sprint become a half day workshop?
So we found that the 3 day workshop with a set of drawings delivered on the final day was quite an intense and amazing experience but we hit the following problems:
It burnt the team out - specifically there would be one work-horse in the team that everyone fed information to, somewhat related to item 2
Limitations in software - So there were some limitations in the Archicad software that meant that one person could effectively work at a time, which threw up challenges for the team and put pressure on one person who became the main driver so to speak
We found that the greatest value was created in the interaction with our clients and we focused and narrowed the program down to the things that we thought created the greatest value
We wanted to open the process up to all of our clients and there was no way that they were all going to commit 3 days - but a half day workshop is manageable for most people, particularly when you can convince them that:
It will save time in the long run
It will cut down on iterations at concept stage
It will create a better outcome
Introduction to the Ballast Point Archisprint Half Day Workshop
Ballast Point now kicks off every new project with a half day workshop with our clients. We use design sprint tools including user experience journey mapping to understand our client’s needs and help them set clear project objectives that we can track throughout the project.
We have found that doing this significantly reduces design time, number of revision needed as well as frustration during the subsequent phases of design. The workshop helps our team to laser-focus on our client’s key project objectives and lays a solid foundation for the journey ahead.
Origins of the workshop methodology
As a business we’ve prioritised 2 things above all else - 1. understanding customer needs and 2. improving our processes. We learnt about the Google Venture’s design sprint methodology and became curious as to whether the principles of design sprint as described in the book (https://www.thesprintbook.com/) could be adapted to architectural design - after all the word “design” is common to both.
About Design Sprint
A Design Sprint, developed by Jake Knapp at Google Ventures, is a rapid, five-day process - (later refined to 3 days) - for problem-solving and innovation. It involves understanding a problem, brainstorming solutions, selecting the best ideas, prototyping, and user testing. This method is popular in technology businesses for quickly validating new product concepts.
We initially tested a 3 day workshop that aimed to get a typical project from pre design to completion of concept design within 3 days. This method worked well, but the intense 3 day workshop was tough on our team. We decided to take the best parts and lessons learned and use them in the Pre-design stage. We then selected specific tools from the design sprint methodology to incorporate into what become a half day workshop (for more on our 3 day workshop check out www.archisprint.com )
What happens before the Workshop
In short research, research and more research. We try to bring all the key information to the workshop to brief the team.
First we commission a survey from a registered surveyor - this is something that is needed as part of a DA submission but it also enables us to build a precise 3D model of the existing building. We also research all the planning instruments (both state and council) and become familiar with how they apply to the subject property. We inspect the site to get an understanding of context and the things that are not on the survey. We bring all the info into a 3D Cad model which has a potential building envelope and key information such as allowable floor space ration (FSR) to existing FSR, site coverage, setbacks and other specific issues such as potential for overshadowing. These are the baseline parameters that give design decisions context.The workshop
The workshop is typically done in our client's house - yep we invite ourselves - and we bring coffee, snacks, white boards, timers and paper and pens.
Baseline and key questions
We start by providing a detailed briefing of what we have found to set the project baseline. We then ask a series of open-ended questions. The most important one is: Why are you doing this? What is the purpose? Other questions include: how will we know if this project has succeeded and how will we know if it has failed?We then hone in on specific needs covering everything from how many sinks in a master ensuite to thermal comfort and everything in between.
User Experience (UX) mapping
We were a bit sceptical whether this would work but the UX process is a powerful design tool. It flushes out things that we have not thought about when asking specific questions and throws up even more questions that are unique to the particular user. It also lets our clients imagine all of the other users of the property including guests, visitors, family who come to stay. It also lets us think about how a future buyer will perceive this property when they first enter.
Sketching and getting our clients to sketch.
Towards the end of the session, we ask the entire team including our clients to sketch. Every client has a different approach to this, some jump in with glee while others with trepidation. We assure them that sketching is strictly about ideas and not drawing ability. We then present the sketches and discuss them. No matter their attitude to begin with, every client has so far immersed themselves in the sketching process and it has always been a positive experience for the team.
Conclusion
By the end of the session the team has a clear sense of who our clients are and what is important to them. There is no doubt the projects run smoother and our understanding of our clients as people and their needs is deeper. We never lose sight of the fact that ultimately our clients are the decision makers on these projects and they have the final word of the workshop. If we’ve done it right our clients gain an understanding of project opportunities and limitations and are empowered to make good decisions. They gain an insight into how our team and the design process works and they become an integral member of the project team from there.
Comments