Our design team has a great impact on shaping our product. We’re autonomous and passionate about solving complex problems. Rather than accept short-cuts or try to circumvent complexity, we face complexity head-on with principled Systems Thinking. Working collaboratively with different functional teams and knowing communication is the key to building the product.
Design Systems, Not Features: always designs in a way that globally optimizes the entire system (never locally optimising a specific feature). Including optimising today’s work with long-term product plans, working backwards from our ideals (link).
Design from Principles: works backwards from first principles (link) of the problem to be solved, rather than copying/solving-pain-points-in existing tools.
Tesler’s Law: always chooses to make things easier for the user, even when that means making things harder (sometimes, much harder) on our team.
Comprehensive: doesn’t give up until a problem is fully, completely solved. No matter how much effort that takes. Never say “impossible” when the correct word is “hard”. Spends as much time figuring out why a design won’t work, as they’ve spent thinking about why it could. Finds and fixes all the small edge cases.
We're a very small design team, re-imagining a complex product from scratch. Every designer in our team has a great impact on shaping our product, but it's a tough challenge. Rather than accept short-cuts or try to circumvent complexity, we face complexity head-on with
principled Systems Thinking that acknowledges Tesler's Law:
“Complexity can be tamed, but it requires considerable effort to do it well. Decreasing the number of buttons and displays is not the solution. The solution is to understand the total system, to design it in a way that allows all the pieces fit nicely together, so that initial learning as well as usage are both optimal.
Years ago, Larry Tesler, then a vice president of Apple, argued that the total complexity of a system is a constant: as you make the person's interaction simpler, the hidden complexity behind the scenes increases. Make one part of the system simpler, said Tesler, and the rest of the system gets more complex. This principle is known today as "Tesler's law of the conservation of complexity." Tesler described it as a tradeoff: making things easier for the user means making it more difficult for the designer or engineer.” — Donald A. Norman, Living with Complexity
When facing this complexity, we don't give up quickly (or ever, really...). In practice this means we invest ourselves in many more iterations than other design teams. We spend more time 'breaking' designs than we spend 'making' them. We spend more time finding problems, than we spend fixing them. We are re-designers, more than we are designers, re-working our ideas over and over until we've truly cracked the complexity. Often throwing out weeks (or even months) of work in the process.
"With productive thinking, one generates as many alternative approaches as one can. You consider the least obvious as well as the most likely approaches. It is the willingness to explore all approaches that is important, even after one has found a promising one.
Einstein was once asked what the difference was between him and the average person. He said that if you asked the average person to find a needle in the haystack, the person would stop when he or she found a needle. He, on the other hand, would tear through the entire haystack looking for all the possible needles." — Michael Michalko
Depending on your personality unforgivingly attacking this deep complexity could be either (a) the most meaningful and fulfilling work you've ever done or (b) the most frustrating and impatient work you've ever done. We've met designers on both ends of that spectrum. If you feel you're the type of designer who would feel inspired (rather than overwhelmed) by complex systems, we'd love to talk with you.