Fail and Iterate
There’s often a focus on how architects can utilise their skills in doing other work or careers. At unmeasured I believe that architects can utilise and leverage those skills better to practice architecture better.
This is the first in a series of articles where I’ll look at the skills intrinsic to architectural practice. Unpacking how architects might use their architectural skills to not just do the work of an architect but to do better in their practice of architecture.
Continuing on with the most prominent skill, design. Design is the principal skill that the majority associate with architects, architect as designer. I wrote about it in my first article, Designing Possibility, might be worth reading before this one.
I don’t consider design as a singular skill, instead it consists of a number of different skills. For this first article I’m going to focus on design as a process of letting go of failure. Design is an iterative process. We do some design, reviewing then to identify if it meets requirements and we consider how we might make it better. Fail and iterate.
It’s fair to suggest a final design always comes from a series of failed solutions until a satisfactory one is arrived at. Architects never use just one piece of butter paper. They’ll work to come up first with as many ideas as reasonably possible as discussed in Designing Possibility. Identifying those the ideas that look likely and then iterating. Massaging and working all requirements into the design, as appropriate at the various stages. At the end there will be a stack of paper on the reject pile — all failures to one degree or another. One(ish) piece of paper will remain off that pile. The chosen solution. Fail and iterate.
Implicit in this design process is the acceptance that in order to have a single good idea, it might be necessary to have many many bad ones. There’s a willingness to fail and then improve upon the solution, involved in this process.
Let’s dig into this a little more.
After each iteration, a series of questions might be asked: Does it work — does it meet all requirements? Am I/we happy with this outcome? Can it be better? Is there another way? If there’s a need to keep going, we might identify it as a fail, and we would also just call it another step on the way to success.
What if we were to apply this to our work outside of design. Things that we might otherwise identify as failures. Perhaps they too are simply steps on the way to success. Some useful questions to ask might be: What did I learn? What worked? What didn’t work? What do I see now, that wasn’t apparent before? What can I do better?
This might be how we work with a client, or do a fee proposal, an approach we took with a Council, a conversation we’ve had with a staff member. There are many things we might apply this iterative design practice to in order to improve our architectural practice.
This iterative design process might be in response to the work we’re already doing. It might also be a deliberate design process in order to do or make things better. Being proactive and identifying opportunities to improve your practice.
Let’s also just take a moment to appreciate our pile of butter paper. We have a pile because we started. Starting is not to be underestimated. Nothing happens until we start. As Christina Rossetti said
“Can anything be sadder than work left unfinished? Yes, work never begun.”
The fear of the blank page is tangible, powerful. Many fail to start because they focus on the outcome. Wanting some level of reassurance that the outcome will not be a failure. This can never be assured. We cannot know that the outcome will meet our expectation. We can be assured that there’ll be no outcome if we don’t start. If we take a more generous posture with our work instead, we can see our failures as steps towards success.
It might be helpful to consider change to your practice as an experiment. It is as we might experiment on a piece of butter paper.
Let’s finish on another question. A challenge to apply your iterative design skills to more than service of your design projects.
What aspects of your practice might you now bring some iterative design to. Something that you might be able to do to assist you to practice better?
I have the same note as last time for those in employment. This applies to you too. How might you show leadership and bring this level of consideration to the office you’re working in? How might you apply this to yourself?
If you think you might need to apply a little Design Process Thinking to more than servicing your projects, but don’t know where to start, please feel free to drop me a line. I’m here to support you in building a better practice, forging better human and professional skills, and developing architectural leadership.
Michael is the founder of unmeasured, where this post was first published. He supports architects in their practice through coaching, workshops and community. Helping architects find their desire lines in practice.