Design & Failure

<Migrated from ronondesign.com> 

 I was once slated to give a presentation at CHI Camp titled “A complete Failure’s Guide to getting UX Buy-in” Even though I never gave that presentation the importance of failure and what I can learn from it stayed with me.

I have always been a strong advocate of learning from failure. It is one of the most powerful tools I know at motivating people and changing minds, attitudes and behaviors. I can say that unabashed now but it is often not easy to see the learning opportunities when sitting among the rubble of an especially large failure.

I’ve recently been reading a few books by Henry Petroski who has done extensive study about failure in design & engineering.  One book is very interesting:

Success Through Failure – The Paradox of Design

This book chronicles examples of failure and the significance those failures play within a domain.  He cites the the sinking of the Titanic or the collapse of the Tacoma Narrows suspension bridge as exceptional teaching tools in the ship building and civil engineering professions.  Each profession has learned to design against the types of failure presented in each catastrophe respectively. Failure allows for the study of known contributing factors that lead to the failure.  Hmm sounds very logical.  A sensible engineering thing to do.  But the human cost of these “learning” events is very high.

I have also recently read:

Why do People and Organizations Produce the Opposite of What they Intend? by Roger Martin, et al commissioned by the Walkerton Water Enquiry.

Flawed Advice and the Management Trap: How Managers Can Know When They’re Getting Good Advice and When They’re Not - Chris Argyris

It seems there are some very significant characteristics that are built into people and companies that make them failure averse. A bit of a paradox really.  Failure is great motivator and an exceptional teacher (if  expensive at times) – but everyone seems to do everything they can to try to avoid failure.  As Roger Martin points out in his article most often defensive personal values are re-enforced through corporate evaluation mechanisms:

  • winning
  • staying in control
  • avoiding embarrassment

Defensive behaviors drive us all toward unwanted outcomes.  Research by Chris Argyris indicates that how an organization supports or prevents defensive behaviors ultimately can decide an outcome.

Since I am primarily focused on the domain of design I thought I would provide my own observations about failure and what process, communication and cultural changes can be used to create a safe failure environment.

1) Create a safe failure culture and communication

Ensure opportunities for learning are fused into every step of a design process. Use design reviews, critique, and evaluations as learning opportunities for all individuals involved in a design. Ensure each designer is aware and comfortable with their own scope of responsibility and never do anything to diminish that responsibility since lack of trust and diminished self-esteem will trigger defensive behaviors. Never remove anyone one from a design project due to perceived failure, or lack of progress. Safe failure means there cannot be a negative consequence or embarrassment for a poor outcome – only a learning opportunity.

2) Build a  new vocabulary around failure

To know how to handle failure a new set of questions must govern communication.  Instead of ‘how did this happen’ new questions include:

  • what can we learn from this?
  • how can this outcome be used to our advantage?

3) A process to fail early

It is never too early to start reviewing and evaluating a design. Ideas are fresh and designers have not become fixated on what they feel to be the best approach (what I call designer motherhood). Early failure allows for more possibilities to be explored.  When little effort has gone into fleshing out a design a designer does not have much at stake. Failure is easier to accept.

  • with no negative consequences for failure – exploration is open and continuous

4) A process to fail often

By making failure occur earlier with few consequences except learning, designers will explore, innovate and present concepts that might have never been considered.  This will increase the rate of failure but also the opportunity for great success.

  • all avenues are explored not just the safe, known routes

While it may not be possible to eliminate defensive behaviors entirely from a design team. I believe my suggestions go a long way to reducing the embarrassment and stigma associated with failure, thereby creating opportunities for accelerated innovation.

Staying Focused on User Experience as a Nimble Start-up

For a young company there is value in being nimble.  Being nimble means you can test business ideas and adjust your business model based on early feedback. This often includes shifting the product focus, injecting new critical features, or involving members of the product team in customer-facing demos at a moment’s notice.

There is also value in delivering great user experience to your early customers.  Customers value a great experience whether a company has been around for 100 years or is new to the scene. By creating a great user experience, early customers will recognize a company’s commitment to their success and remain loyal when satisfied.

Being nimble and delivering great user experience shouldn’t be at odds; It is possible to deliver both speed and great experiences if you keep these tips in mind:

Make someone responsible for the product experience immediately.

A great product experience requires that an individual be responsible right from the beginning.  Having a dedicated role means that product experience is always being considered despite the twists and turns the business may take. It also guarantees that product experience won’t suffer when things get hectic.

A dedicated role means time is allocated for design to explore concepts and alternatives. This can seem like a luxury when deadlines are looming, however a rash decision today could affect the flexibility and sustainability of the product in the future.

Use a Design Mentor

Young companies routinely use mentors to assist them when establishing sales and engineering programs. A design mentor should be used to help in establishing a design program. A seasoned design mentor will provide perspective and direction and know which processes and techniques will work well given the team’s goals, workload and commitments. The rapid change necessary in a startup can be overwhelming for anyone.  A design mentor provides perspective that helps ensure objectives are met and done so in the most logical way for success.

Learn to be a cross-functional team.

What do we mean by a cross-functional team?  Startup employees often wear many hats and often make decisions together regarding product strategy. Being cross-functional means a team can understand enough of each functional domain (engineering, sales, design) well enough to take part in interdependent decision-making. For example, it is important to realize how decisions made about product experience can impact the rest of the business. When decisions arise, a cross-functional team can evaluate the available options and make informed choices together, since they are grounded in the fundamentals of each domain.

But what does this have to do with experience design?  Design decisions are often delegated to the “designer” on the team due to lack of knowledge and understanding, but it’s much more strategic if all decision-makers have a cursory knowledge of design and make informed choices together. 

So how do you become a cross-functional team? It requires some training.  Design education should be part of developing the leadership team.  Education isn’t about giving a one-hour talk and a bunch of slides.  The best way for a team to learn is through doing.  Education should involve teaching techniques through brief instruction followed by prolonged facilitated working sessions. This allows a team to learn something new while delivering an actionable piece of work or decision. Each working session solidifies what is being taught and can help to provoke any questions team members may have.  It isn’t necessary for each team member to become a designer, but rather that they become aware of the concerns that go into design decisions, since these decisions can have dramatic effect on the success of a business.

Use Design Techniques that Allow for Speed.

Start-ups have unique real-time pressures since they are always trying to accomplish concrete goals before each round of funding runs out.  The techniques used in design must move fast enough to enable and maintain this rapid pace.  Techniques that require a great deal of planning must give way to lighter, less formal approaches.

Interviews and discussions with potential customers provide input to defining the product.  This research coupled with the team’s own vision for the products must be captured. Fast tools for capturing ideas and input include journey maps, scenarios, and personas. An effective design mentor will be able to educate teams in fast techniques that distill ideas. A startup should avoid using heavy formal product specifications such as Product Requirements Documents (PRD) due to the work required to keep such documents accurate and up-to-date. Concepts must also be developed using quick techniques like sketching and rapid wire-framing.  The benefit of speed in capturing inputs and concepts is volume; more ideas and concepts can be evaluated in a short span of time. Formal evaluation techniques (usability testing) give way to quick concept evaluations and walkthroughs with potential customers.  Design is about considering the possibilities. The more possibilities considered always leads to a better design.

Deliver!

The final and most crucial item for any start-up is delivery.  Getting a product out the door is one measure of a team’s success. The product delivery schedule must not sacrifice the necessary planning and review.  This is why it is important to implement checkpoints or milestones that force the team to stop and review what has been implemented so far and plan what work remains. Checkpoints ensure that product remains true to the established vision and achieves the level of consistency and quality required.

Each startup’s situation is a little different, but the need for speed and flexibility remains constant.  Rigid processes interfere with both of these goals. By combining skilled people (a designer, design mentor), some training (to become a cross-functional team), light-weight design techniques (scenarios, personas, wireframes) and built in checkpoints; not only will you remain nimble and flexible but product experience will become an integral part of your product delivery process.