Little Talks – TEDx Talk

November is National Blog Post Month (NaBloPoMo). This post is part of my post-a-day challenge. I have picked a theme for the challenge: song titles. These songs have been featured on live albums from KEXP (an awesome alternative radio station in Seattle), so at a minimum you will hear some great music.

I am excited to be able to share my little talk (Empathy for Geeks) given at a recent TEDx event in Toronto.

As I described in my director’s commentary, preparing for this talk was a lot of work. I’m very pleased with how it turned out.

I recognize that I can only step out and take risks like this because of my support network. I am grateful to those that provided commentary and encouraging words.

I hope you enjoy the talk.

I almost forgot, here is the song that inspired the title

The only way to do it

BL4YQU3CMAAWySz.jpg-large

After my spouse and I were pronounced man and wife, the minister made a small verbal misstep. He had undoubtedly officiated hundreds of weddings and knew what to say.

We all know what to say…”You may now kiss the bride.”

Despite all that experience, something happened. The minister looked my square in the eye and said “Lance…now you can do it.”

The congregation laughed uncomfortably, I kissed my bride, and we have been happily married for over ten years.

Now knowing how my wedding ended, it should not be a surprise that seeing the sign shown above makes me think of the minister’s charge. This sign hangs prominently at Stanford’s d.school and I took this picture the last time I was there.

I’ve been thinking a lot about “doing” lately. For most of us, it is much easier to sit on the couch, stay at your desk, or to not speak up in the meeting. Non-action seems to have less risk – key word being “seems”.

Non-action and not doing is every bit as risking as doing. It happens over time, almost so slow that you don’t notice it – non-action allows your skills to weaken to the point at which your contribution isn’t valued and you become a non-factor.

The best strategy for mitigating this risk is to act. To take a risk. To move from the couch. To leave your desk – Go talk to the guy in accounting that no one will talk to. Go talk to a customer. Go ask you friends what you are doing that is short of your potential. Go ask your neighbor what you can do to help them. Go do something that scares you a little and that might fail.

I want to be know as a doer. That’s how we learn. By taking risks and making mistakes. I build to think. Building is all about doing. Sure, you make start by sketching out a plan, but you build as soon as you can. You test your plan and then refine and build again.

Join me in doing.

A simple storytelling framework

What exactly goes into telling a good story? You need a hero, a villain, some conflict and a little resolution right? Something like that…

Let’s back up a little…why is storytelling important? It’s important because we connect with stories. We share our lives with stories. Personally, I have shared some of my happiest moments with new friends through stories: the story of how I met my wife, the story of the birth of first child, etc. I also have stories that describe times where I felt like a part of me has died with loved ones that I’ve lost. Our lives are a series of stories.

Another important property of a story is it’s ability to channel the complete opposite emotion of what you experienced at the time. Think of powerful stories you may have heard about a person who was without hope and didn’t see a way out. And then someone provides for them in a way they couldn’t have imagined. Or think of a story where someone was extremely embarrassed or frustrated. Years later you’ll be in a group and everyone will now laugh as you the story is told. Here’s a summary:

You were hopeless — your story —> provides hope

You were embarrassed/frustrated — your story —> provides laughter

Storytelling at work…

It’s clear to me that storytelling is important. Those best at communicating their ideas use stories to do it. Here’s an example…you are in a meeting. You propose to a coworker IT that your group needs TPS reports twice a day (and don’t forget the cover sheets) rather than just once a day. For five minutes they describe why this won’t work using generalities. You stop them and ask for a specific example.

At this point your coworker hasn’t been storytelling. Think about the best stories – they are full of details. A picture is painted for you and you are able to experience the story. Why can’t your coworker do the same thing? Here’s a sample response…

“Jane, I’d love to be able to provide your group with TPS reports twice a day. We ended up landing on daily production due to the needs of the marketing group. Let me walk your quickly through our production schedule….once we’re done, I’d love your thoughts on how we can move some of the pieces around to get your group reports twice a day. We start at 5:45am with….”

The framework

onceuponatime

Design thinking is centered around gaining empathy for your end user and having them experience a solution. Storytelling is an integral part of this process. In the picture above, the amazingly talented storyteller Scott Doorley was teaching the group this framework. Since the picture is tough to read, here it is:

Once upon a time…

And everyday until…

Until one day…

Because of that…

Until finally…

And ever since that day…

And the moral of the story is…

Here’s a simple example:

Once upon a time there were two tadpole sisters who were the best of friends. And everyday they played together, until the oldest sister turned into a frog. And because of that the youngest sister was lonely and sad. She played everyday by herself. Until finally, she turned into a frog! And ever since that day, her she and her sister have been inseparable. And the moral of the story is sadness and depression can be transformed like the tadpole into happiness and joy.

Practice, practice, practice…

So how do you improve as a storyteller? The first thing I have done is to practice. I play the “storytelling game” almost every night with my daughters. We alternate who takes each part of the framework. It is great fun for her and I’m continuing to hone my craft. You can also use the framework as a group exercise. If you’re in a meeting with 4-5 coworkers take turns constructing a story together.

The next bit of advice I would offer would be to view every presentation, every meeting, every project, etc as an opportunity to tell a story. Think about the opening, the conflict, the resolution and what you learned.

If you’re in the audience, what would you rather listen to? A well crafted story that allows you to experience what has happened on a project, or a deck of endless slides that just give updates on what has happened. I vote for storytelling.

Lastly, spend time talking with great storytellers…maybe even some professionals. How cool would it be to invite a professional storyteller to your office to teach your group how to tell a great story? I’m in the process of trying to set this for my team.

Storytellers are not born, they are made…keep practicing and please share your stories.

DTBC Day 2: Just beyond crazy is fabulous

Day 2 is extremely fun at the d.school (actually all the days are fun!) because we spend a lot of day 2 ideating and prototyping.

We have this phrase we like to use, “just beyond crazy is fabulous.” Today was so much fun because we pushed our team to this place. We came up with solutions that were completely beyond the realm of what is possible and legal and then we took it a step further and continued to build off of those ideas.

I love the moment in an ideation session where everyone in the group is almost crying they are laughing so hard. The gold is in those ideas because they tend to invite such rich user feedback. And since design thinking is always about getting back to user empathy, wild ideas are really just a means get higher quality empathy.

Tomorrow (Day 3) will be our last day, and I am sad to see it pass so quickly. My time here has been a blast and I’ve learned a tremendous amount from all of the wonderful coaches and participants. I now feel more comfortable with pushing pass crazy to fabulous design and solutions – and that is awesome.

Looking forward to sharing more…

Design Thinking: This Will Change Everything

Note: this blog post is a re-print of an article that I recently had published in an insurance product development journal (Product Matters!). I wrote this article in October of 2012, so when I re-read it last week I was a slightly afraid of what I would read! But after reading I decided that I should share this article with the readers of my blog. I hope you enjoy.

prod matters

Ernest Hemingway was once challenged to see if he could write a very short story that carried the emotion and power of some of his longer works. He came up with one that contained just six words. My guess is that the challenger was thinking they would at least get a few paragraphs. So what were those six words?

For sale: Baby shoes, never worn.

Read the sentence out loud and reflect upon the meaning, and you’ll feel how potent this short sentence is.

Just as Hemingway’s short sentence packs a lot of meaning into just a few words, Stanford’s Design Thinking Boot Camp is a three-day intro to Design Thinking that provides the knowledge, insight, and experience of a semester-long class. In fact, I was asked to craft my own six-word sentence about my experience at the d.School and it was this: “Life will never be the same.” I won’t try and unpack everything that sentence represents, but as you will hopefully see, Design Thinking is a game changer and I now have a new set of tools to apply to any problem. How can life be the same after you experience something like this?

One of the principles of Design Thinking is “Show…Don’t Tell.”  You learn Design Thinking by doing, not reading. So rather than writing a long article on Design Thinking, I want to introduce you to the steps of the process, and some ways that these steps can be applied to insurance product development. If you really want to “do” Design Thinking, I’d highly recommend you speak to the fine folks at the d.School.

Background and Overview

Let’s try a quick exercise. Think of someone you know that is creative…who did you come up with? My guess is that 90% of people think of someone who is a painter, musician, or writer. Design Thinking rejects the relationship of “creative” equaling “artistic.” Anyone can be creative: an actuary, an accountant, a lawyer. Children are by default creative, making a safari adventure out of a sheet and two chairs or a spaceship out of a refrigerator box. We start out imaginative, but somewhere along the way, we lose touch with our creative side. Design Thinking seeks to unleash the creative potential that lies latent inside of each of us.

Honestly, it’s only been in the last couple of years that I viewed myself as creative. Things that others may see as boring and not allowing for creativity, I see as my craft—an artistic endeavor. Design thinking will allow you to approach your work with the same mindset and look for ways to creatively solve problems.

With that said, let’s dive into the Design Thinking process. The five parts of the process are Empathy, Define, Ideate, Prototype, and Test. As I mentioned above, I’ll interject examples of how this can be applied to insurance product development.

Empathy

When most of us think about design, we think about aesthetics—making products that are appealing to the eye. While aesthetics are an important part of design, Design Thinking always starts with the human element. Therefore empathy is essential to solving a problem with Design Thinking. What are some ways to gain insight? You need to spend lots of time talking and listening to your user (the person for whom you are designing a solution). Ask lots of open-ended questions. Ask “why” often. Try to evoke stories and emotions. As you’ll see later in the process, stories are an important foundation for the other steps in the Design Thinking Process.

So how do you increase empathy among members of your team, or others in the company? You have to talk with people. Here are some ideas.

Example 1

If you were questioning, “How do we improve the customers’ experience with our company?” a great place to start would be watching what customers do when they open statements/prospectus/bills from your company (or any company for that matter). Give a customer a stack of mail and have them open it. Watch how the expression on their face changes when they open a handwritten letter, versus junk mail, versus a two-pound prospectus packet. Ask the customer to talk about companies they love interacting with—what is it about these companies that delight them? What products do they adore?

Example 2

If you were questioning, “How do we help people save for retirement?” you could start by conducting interviews. Go to a place where people are (obvious, yes?). I have found that it helps to get the conversation started by offering a gift card (of a small monetary value). Ask them questions about retirement. Are they ready? How are they saving? What worries them? I’ve also found it’s helpful to ask lots of “why” questions, such as, “Why is that?”

Now you may be saying, “I can get all of this data from quantitative studies that have a larger and more reliable sample size than five.” And you are right; data can give you a sense of people’s worries, problems, concerns, etc. But data cannot provide stories and a human connection. For someone like me who has spent my career focused on quantitative analysis, the qualitative focus of Design Thinking felt like California feel-good nonsense! But after having experienced it first hand and seeing how companies like IDEO have used it to deliver groundbreaking innovation, it’s hard to argue with the results.

Define

The definition portion of the process helps create a user point-of-view statement. The point-of-view statement is like a problem statement, but with feeling and emotion. This provides a great platform for ideation (brainstorming). Always start the creation of this problem statement with thinking about needs—“needs” as verbs, not nouns. Examples of needs, by this definition: To feel responsible, to show love, to enjoy time with a spouse, to provide for our kids college education. The following are not needs: security, a second home, replacement income.

After exploring needs, you craft the point-of-view statement. It’s similar to those “Mad-Libs” you played as a kid. Here’s the format: “USER” needs to “NEED STATEMENT” because “INSIGHT.” So let’s look at an example of a problem statement using this format:

An independent and energetic retiree needs to feel secure about not outliving her assets because her biggest fear is being a burden to her children later in life.

This statement is packed with emotion and compels us to want to come up with a solution. Also, we are not solution biased. At this point it may not even need to be an insurance product to solve the problem. This allows us to do what is called “ideate” without constraints (more to come on that). I’ve also selected what Design Thinkers call an “extreme user.” Identifying and empathizing extreme users allows us to come up with solutions and insights that often apply to a broader user group. Having a powerful point-of-view statement will allow us to come up with great ideas as we move to ideation.

Ideation

Ideation is what most of us usually think of as brainstorming. It’s a little embarrassing to think of what I’ve called “brainstorming” in the past. There were no empathy insights and I didn’t clearly have a user point of view. Hopefully it is starting to become clear how important these steps in the process are.

As I mentioned above, we are solution agnostic. Ask a Design Thinker for help designing a bridge to go over a canyon and her first response will be, “Are you sure it needs to be a bridge?”

At this point, some of you will think, “If I work for an insurance company, why should I brainstorm solutions that I know I can’t create?” The answer is that your “wild” solution may provide insight that leads to a product you can create or a solution you can manage. Here’s an example using the point-of-view statement above: An independent and energetic retiree needs to feel secure about not outliving her assets because her biggest fear is being a burden to her children later in life and not being able to buy birthday and Christmas gifts for her grandchildren.

One wild idea is that we create a magic jacket that always has money in the pocket if she needs it to buy gifts for her grandchildren. If she takes her grandchildren to the mall and she doesn’t have money for the gift, the magic jacket will supply a crisp $20 in the pocket.

Clearly, this solution epitomizes a wild idea, but it’s an idea into which you can delve deeper. How would it feel to wear and know that this jacket is in the closet? Can we do anything that would provide the same feeling or meet these needs?

Prototype and Test

Prototyping is the stage in the process in which you create something with which the user can interact. This goes back to the Design Thinking principal of “Show…Not Tell.” A prototype can be a skit that shows the experience, sticky notes that show an interface, or construction paper and post-its to show the layout of a call center.

The key to prototyping is that it needs to be low resolution / low fidelity (say low-res or lo-fi if you want to sound like a practitioner!). It’s important to construct a low-fi model because:

1)      You want to get feedback from your tester as quickly as possible so you improve

2)      Testers are more willing to give feedback if the model is less refined

Think about point #2 —if someone on your team brings a PowerPoint presentation he has spent months of his life working on, missed his kid’s soccer games for, and has lost a couple of years of life expectancy because of, wouldn’t it be difficult to tell your team member that his presentation was completely off the mark? Now imagine the same presentation: It has headings, but the body is a mixture of sticky notes and drawings of graphs. At this point, it’s much easier to lend feedback and make changes.

Building a low-resolution prototype is essential to being able to quickly gather honest feedback and continue working toward solution. And that’s all that testing is—having the user (or a user) interact with your prototype and receiving feedback. As with all of the steps of the process, this is another opportunity to gain empathy for your user. As the user interacts with your prototype, what problems does he have? What emotions does he feel? This empathy learning can lead to improvements as you further iterate on solutions.

Conclusion

My hope is that this brief intro into Design Thinking has given you an idea how the process can be applied in a wide variety of settings to solve problems. As mentioned above, the best way to learn Design Thinking is by experiencing it yourself, so if you are interested contact me, the d.School, or any practitioner of Design Thinking to experience it for yourself. But before starting take note: Life will never be the same!