Barefoot Running (Less is More)

I just finished a pretty incredible book by Christopher McDougall called "Born to Run," about ultramarathoners, a tribe of Mexican Indians called the Tarahumara, and the lost skill/art/practice of distance running.  The book is all about why (when humans have actually evolved to be distance runners) we are constantly getting hurt and have largely stopped enjoying what should be a healthy and liberating activity.

The short answer:  it's in the shoes.  In fact, McDougall says that "running shoes may be the most destructive force to ever hit the human foot."  As just one small piece of backup, he cites a 1989 study that proved that the greater the padding in the shoe, the greater (not less) the impact on the runner. 

In the name of profit, McDougall says, Nike, the inventor and designer of countless running shoes since the early 1970's (and the rest of the running shoe industry), promotes more and more "advanced" shoe designs that are worse and worse for your feet.

It leads me to a conflicting conclusion:  that better, or at least more "advanced" design can actually be worse for the end user.  In this case, more padding and support actually inhibits development of muscles and other structures that are protective of the foot.

So who's to blame, and how can design come to the rescue?  I think it's safe to say the blame can be spread around; this isn't about Nike.  After all, I'm responsible for my running technique and the impact it has on my body.  But from a design perspective, McDougall and others say that we already have access to the best design, which is to say no design at all, other than our foot itself.  He says that running barefoot actually promotes a correct and healthy running style. 

Check this out:



But of course, business has the ability to capture value from "barefoot" running.  Take a look at the below from Vibram, which is the latest in running shoe design:

For the last two weeks or so, I've been running barefoot and in the barefoot style (for the record, I don't own the above shoes).  And though it's still early in my experiment, it's so far been a tough design lesson I'm happy to have learned.

Design Thinking vs. Design Action

I recently read an interesting blog post by Idris Mootee, the CEO of idea couture, an innovation and design consultancy based in Toronto.  "What is design thinking?" Mootee asks in the post.  "Design thinking is not about design. It is about helping companies and individuals to think differently about strategic options and system impact." 

Mootee worries that companies won't reap the benefits of design thinking if it's viewed simply as a buzzword and is "over-theorized" (his word) and under-acted (my word).

To avoid this over-theorization of design thinking (at a time when, it can be argued, companies need it more than ever) Mootee recommends three design techniques -- observational research or ethnography, visual sense-making, and rapid prototyping -- that he says are "most powerful if you combine them with strategic context..."

These, he says are "where D-school meets B-school" -- and how we can keep our hands busy creating and our heads out of the over-theorized clouds.

Education+Business+Design = A Conversation with IDEO's Ryan Jacoby

Ryan Jacoby studied Systems Engineering at the University of Virginia, then spent four years as a Deloitte consultant before attending business school at Stanford.

Before the Stanford d.school was officially official, Ryan studied and prototyped there under the likes of IDEO founder David Kelley, among others. After graduating, he joined IDEO full-time in the Bay Area for about two years before helping open the company’s New York City office and co-founding its Business Design practice with several others.

Ryan and I chatted a while back about business and design and education and how the three are interrelated – or should be. Here’s an edited excerpt of our conversation:

ThinkingDesign: How’d you get into all this business design stuff?

RJ: When I went back to business school, I really wanted to get back into sort of how things are made. My background was about understanding systems, and I knew enough about business to be dangerous. My first design class was called “Interdisciplinary Design and Innovation,” and it hooked me.

Our team was made up of a computer science guy, a mechanical engineer, a product designer, and me – we decided to design next-generation user interfaces for teen girls. That’s a dumb idea, right? Four guys that know nothing about being a teenage girl.

People were betting about how bad we’d flame out. But we did amazing work by sticking with the process we learned. Because we were so outside of our element, it gave us an entirely different view.

                                       (It's not always a bad thing to be out of your element)

ThinkingDesign: how did you go about it that time?

RJ: The way the d.school teaches it. Basically hanging out at shopping malls and just trying not to get arrested or kicked out. I remember one day with my teammates going to a high school girls’ basketball game and sneaking a video camera to act like we were shooting the game but actually shooting this gaggle of teen girls, doing these amazing behaviors with their cell phones and communicating with each other at the same time. Just seeing all of this playing out in front of us and thinking about it. We talked to an expert in teenage girls, and we talked to an expert in language.

                                                 (A unique place for design research)

I remember one of the professors agreeing with one of our findings -- that information is power in these collectives [of teenage girls]. And he actually encouraged us to attempt to change that. As a team, we sat around and had to decide whether to design for the behavior, or whether to take on the mantle of trying to change teen girlhood forever.

ThinkingDesign: What’d you decide?

RJ: We totally tried to encourage the behavior. We did flash prototypes of interfaces and designed a whole system around it. We showed models of our interface designs at a table during high school lunch until security guards kicked us out. We got away with a lot by saying we were a Stanford student and doing it for class.

As an experience, it was really inspiring. I really got into it. It was a blast and a different way of thinking which I certainly appreciated, because it was a nice complement to the systems thinking and business background that I’d developed.

ThinkingDesign: How did the "Business Design: The Curriculum of 2012" idea come about?

RJ: It was one of the easiest [blog] posts I’ve ever written. I did it on a flight from New York to Florida, actually. I’d been thinking about it and started playing around with it, because I do a lot of hiring for the business design discipline at IDEO. As a student in many business programs, you have to cobble together and approximate the kind of experience we’re looking for.

                                                           (A Cobbler Cobbling)
                                            
So, it made me ask the question, “Why isn’t there something else that is preparing people to do what we do here [at IDEO]?” Business design is a craft and approach. If you believe in that craft, then where’s the educational support system to create those craftspeople? And what should it look like? I knew it would be hands-on and action-oriented and hard, but hard in the way that something that’s extremely rewarding is hard.

ThinkingDesign: Are business schools getting better at combining business and design?

RJ:  I think there are a couple of professors at each school that have picked up the mantle of design thinking. But we’re still in the very early stages. Most programs are still rooted in the traditional institutions. It’s not taught as craft, but more of a mindset. That’s a big deal in itself, but I’m still waiting for someone to close the gap with a start-up mentality.

There are a lot of prerequisites that people think you need to have before doing this stuff. You can worry about that and wait to get that experience, or you can dive in. Business schools teach people to do the right thing, but innovation and design asks you to do something different than that. It’s about being stupid as much as being smart. It’s helping people get over that scary feeling of being wrong and looking stupid.

    (A Diesel Jeans campaign that Ryan blogged about not too long ago -- so appropriate and so funny)

Imagine going into a business school and promoting my curriculum – you’d get thrown out on your ear. I was really trying to figure out how to give people experiences in this way while waiting for these institutions to change?

ThinkingDesign: You mentioned before that business design is a craft. What do you mean by that, and how do you know you’re good at it?

RJ: When you call it a craft and not a skill, you realize you can always get better at it. And you realize there are tools and methods in the world that you can acquire that can inspire you to get better.

If I were drawing it for you, I’d draw a smooth curve with a pencil and then zoom in on it. When you see it closer, you realize it’s not a smooth line but more of a jagged line. A craftsperson can see the jagged elements of it. So, one of the ways I think you know you’re really good at business design is that you can see the underlying assumptions in these business models and communicate them in ways that people can understand.

You’ve kinda got a quiver of things you want to try and a quiver of ideas that you’re constantly working on. It’s different than saying I’m really good at math, for instance. It’s saying that I can work my way through these problems and constantly staying inspired around these business issues and business models.

ThinkingDesign: Do you still do as much prototyping in business design as you do in product design?

RJ: We use discovery-driven planning a lot. You basically start with the result and work backwards. So, if you start with a scenario of a $10 million a year business situation, then what needs to be true to make that happen and what are the assumptions that underlie that outcome? What are the prototypes, pilots, and tests that we can put into place to learn into that plan? It’s like options thinking. People that can think in options in the world of business are few and far between. A lot of business design is how you can think about generating, evaluating, and learning into options – if you see what I mean.

ThinkingDesign: Okay. I’m kinda confused. How else can I think about business design?

RJ:  Another belief I have is that when you’re designing the experience, you’re designing the business and vice versa. They are intertwining activities. If you look at the web 2.0 space generally, a lot of folks are figuring out the online experience at the exact same time they’re figuring out the business model. If they are creating a great experience, then a business model can come out of that. I think there’s a lot of opportunity in that approach.

Another way to look at it – I sometimes say business design is a mix of entrepreneurship, commerce, and art – it’s a pragmatic mix of those things. It’s not business + design or design + business. It’s a craft and it’s something different.

IDEO's Ryan Jacoby Prototypes a Business Design Curriculum

Last May, IDEO's Ryan Jacoby made a posting on his blog that got a lot of people talking.  It was his vision of what a Business Design curriculum would look like.  Ryan helps run the business design practice for IDEO in NYC (and is considered the first graduate of the d.school at Stanford) so has the credibility to put this curriculum idea out there and stimulate some spirited discussion. 

When I found the posting last summer, I'd just launched Creative Design for Affordability at Cornell, and I was seeking kindred spirits and potentially more training in design thinking when I found Ryan's curriculum and a flowing discussion in the comments section at the bottom of the page. 

I wanted to do my part to continue the conversation sparked by the post, so I've included a snippet of his posting here to pique your interest (sorry it's a bit fuzzy -- please make sure to check out his whole post here).  I also had the opportunity to chat with Ryan recently -- about the posting and his work in business design.  That conversation will follow later in the week...