LIFT Interview

LIFT Interview

This week’s blog post is an interview with Dan Ward, talking about his new book Lift – Innovation Lessons From Flying Machines That ALMOST Worked and The People Who NEARLY Flew Them. As a special bonus, we’ve got a 14-minute audio version of the interview, which is (mostly) transcribed below

Dan, Lift is your third book. Your first book was titled, FIRE – How Fast, Inexpensive, Restrained, and Elegant Methods Ignite Innovation which explores how excessive investment of time, money, or complexity actually reduces innovation and that the secret to innovation is to be fast, inexpensive, simple, and restrained. Your second book digs deeper into those concepts – specifically the term Elegance. Titled, The Simplicity Cycle – A Field Guide to Making Things Better Without Making Them Worse, you show us that unnecessary complexity adds complications, then provide a number of techniques for identifying the problem and striking the proper balance. What made you want to write this book? 
I came across these stories of 19th century flying machines several years ago, and they completely blew my mind. I kinda fell in love with the topic. I couldn’t stop thinking about them, and the more research I did into flying machines from the 1800’s, the more I learned, the more I wanted to share these stories with other people.

In large part that’s because most of us know so little about this era of aviation history. Even among aeronautical engineers, pilots, and Air Force personnel, there’s this weird historical blind spot. People seem to think Orville and Wilbur were the first to try to build an airplane, as if they were starting with a blank sheet of paper. Of course that’s not true. There were hundreds of people doing similar work, particularly in the late 1800’s. Their stories are amazing on their own, but the best part is they are also hugely relevant to the challenges we face today.

In your intro, you talk about the five stars of your book. In a sentence or less, how would you summarize each individual?
Ooh, that’s tough, but here goes! Chapter one is about Octave Chanute, a connector who built a community for aviation experimenters in the late 1800’s at a time when lots of people were experimenting and nobody was succeeding.

Chapter two introduces Otto Lilienthal, who bravely strapped on home-made wings and jumped off cliffs thousands of times, trying to figure out how to make an airplane stable.

Alberto Santos=Dumont is the core of Chapter three, and his persistence and iterative approach to design was a huge inspiration. Also, I want to build my own version of his airship Number 9 someday.

Chapter four is about James Means, who beautifully blended pragmatic realism with a counter-intuitive perspective on gravity, and took an inclusive and invitational posture in his work.

Finally, Octave Chanute wrote a perfect summary of Chapter five’s subject, so I’ll just quote him: “If there be one man, more than another, who deserves to succeed in flying through the air, that man is Mr. Laurence Hargrave…” That pretty much says it all.

Do you have a favorite story that you came across in your research for the book – that really resonated or inspired you?
There’s a story I adore but that didn’t include because I couldn’t quite make it fit into the book, so I’ll share it here. It’s about a guy named Moulillard who strapped on some homemade wings, jumped over a drainage ditch, and was absolutely terrified when he found himself gliding along a foot off the ground, unable to steer or land. He estimated his speed was between 8 and 11 miles per hour, which put him somewhere between the top speed of a house mouse and an alligator (yes, I looked that up).

Mouillard’s flight was scary because he was out in the back forty of his farm, and he knew that if he crashed and got injured, it would be a long time before anyone found him. Fortunately he came back to earth safely – again, he was literally one foot off the ground, traveling at the speed of a mouse – and the coolest part is that after he landed he immediately measured the distance he’d flown. What an engineer!

Incidentally, he flew 138 feet that day. That’s 18 feet further than the Wright Brother’s first flight.

I love that he was so scared (the phrase he used was “oh, the horror!”), and I love that the first thing he did after landing was measure the distance he’d covered. I hope I would do the same thing in that situation. But what’s really important about the story is that before jumping, he clearly had not anticipated what to do if his wings worked. His design was focused on producing lift, with absolutely zero mechanism for control. There’s probably a lesson in there too.

Lift is more than just stories about some men – and women – who built flying machines, but also practical insights about innovation. What do you want or hope readers take away from your book?
I think the main lesson is on page five: “failure is never the whole story, nor the end of the story.” Of course, I hope people will read the rest of the book too, but if you only read up to page five, you’ll at least have something useful to take away.

The other big point is the importance of diversity, inclusion, and collaboration. There’s a very clear pattern across all these experiments, and all the modern stories in the book as well, about the relationship between diversity and innovation. I lay it out in Chapter three, writing “…the people who made the most progress were the collaborators and bridge builders, the includers and inviters, the broad-minded generalists and discipline blenders. The people who had the hardest time were the isolated excluders, the narrow-minded specialists, and the arrogant purists.” If you want to read more about that, download the free excerpt from Chapter 3 at my website.

You talk about “cultivating a specific perspective on failure.” How can we get organizations and individuals to be more comfortable with failure?
I think failure is hard for so many people because it seems final. But when we understand that failure is not the whole story nor the end of the story, when we see failure as a temporary step or as an unavoidable component of progress, when we see failure as the key to learning, it’s really much more palatable. Maybe even fun.

What industries or areas do you see failure being done “well”? And which ones not so well?
When someone dies, a bridge falls down, or an airplane crashes, those communities assemble a large group of doctors, civil engineers, or pilots to investigate what went wrong and prevent it from happening again. That’s one of the instances where studying failure can make a big difference. Medicine in particular does a pretty good job of learning and adapting when things don’t work. In contrast when a software development project goes pear-shaped or a technology development project doesn’t work out, we tend to bury that and act as if it never happened.

Dan, I enjoyed the book immensely. The history of the pursuit of flight was fascinating, your writing made me laugh out loud – always a good thing – and your lessons are useful and inspiring. What’s the best review you’ve gotten on this book so far?
I love that Andy Nulman said LIFT is “ebulliently written” (even though I always mispronounce the word ebullient). I can’t say I was deliberately aiming to write with ebullience, but when I saw that description I felt seen and knew I wanted to put that on the cover.

A few people have said the book sounds like me, it matches the way I am in real life. That makes me very happy, because that’s something I very much was aiming to do. I want my writing to sound genuine, which isn’t always easy, so that’s a really good review as far as I’m concerned.

Any negative reviews?
I haven’t seen any negative reviews yet, but I’m not too worried about those. A negative review basically means that I wrote a book, I finished it, got it published, I took a chance, I sent it out into the world, and someone read it. That feel a lot like success to me – the finishing, the completion. If someone doesn’t like it, well, that person probably wasn’t my audience in the first place.

Okay, we’ve talked about the book, so I’m sure listeners are wondering where they can purchase copies of LIFT?
Not at Amazon, and that’s on purpose. My first two books are available at Amazon, but with this one I’m deliberately aiming to go more local, more of an independent, small business approach. So you can get the paperback at Lulu.com, and the eBook is available at Barnes & Noble or Kobo. The audiobook is in the works, hope to have it done by the spring!

What Is Innovation?

What Is Innovation?

Innovation is one of those words that gets used more often than it gets defined. And these days, it gets used a whole lot. In fact, it’s probably overused. But despite the popularity of the term (or maybe because of it) we run into a lot of confusion about what the word innovate even means.

Let’s clear that up today, shall we?

Team Toolkit uses a pretty simple definition of innovation. It’s just three words: “NOVELTY WITH IMPACT.” We like this definition for several reasons.

First, it’s simple, clear, and short enough to be memorable. That’s important, because a definition people can’t understand or remember isn’t very helpful, is it?

Second, “novelty with impact” is broad enough to be applicable in a wide range of situations. For example, we might talk about novel technologies or novel processes, new organizational structures or new methods of communication. We know novelty comes in a lot of different flavors, so our definition encompasses them rather than trying to list them (e.g. “Innovation is any new process, technology, solution, product, etc…”).

Incidentally, we tend to take a broad, inclusive understanding of the word novelty. The thing doesn’t have to be new to the whole world to count as novel. If it’s new to us, or new to our domain, that counts.

Similarly, the word impact might refer to saving time or saving money, increasing effectiveness or improving efficiency. It might refer to solving a problem, making an improvement, changing the marketplace or revolutionizing the battlespace. Rather than trying to pack our definition with a comprehensive list of all that stuff, we just refer to all forms of positive difference making as “impact.”

Third, “novelty with impact” helps distinguish innovative things from non-innovative alternatives. How can we tell the difference between an innovative product and a standard offering? The innovative product is novel. And what’s the difference between an innovative product and something that is merely creative? The innovative product has an impact.

But the best thing about this definition is that it points to two very important questions: What novelty are you trying to introduce? What impact are you trying to have?

Answering those two questions is a great way to get clarity about the sort of innovation we’re trying to introduce to the world.

For example, this blog post is offering a new definition of innovation (Novelty!), to help people better understand what innovation is and to build their innovation strategies (Impact!).

Which brings us to you. What sort of novelty are you trying to introduce in your arena? What sort of impact are you trying to have? Answer those questions and you’re well on your way to doing it.

Customizing Tools

Customizing Tools

Our previous blog post looked at the Rose, Bud, Thorn canvas, one of the most popular tools in the kit. This week’s post continues on that theme, but with a bit of a twist.

Photo by Ben Weber on Unsplash

A few months back one of our ITK facilitators received an interesting request from a potential toolkit user. They said they were open to the idea of using the Rose, Bud, Thorn with their team, but only if we could create a militarized, hypermasculine version. They said the floral imagery inherent in this tool made them uncomfortable, and they suggested perhaps something like “Gun, Knife, Bomb” might work better.

Um, that’s a big nope. We’re not doing that.

As a general rule, Team Toolkit aims to meet people where they are. We customize tools all the time, to make sure they fit well with the specific language, preferences, and inclinations of the people we are trying to help. We think it’s good to modify our vocabulary and make sure our language choice is as clear as possible. If a word has different meanings in different domains, we make every effort to ensure we’re using the right one for the environment.

For example, with some folks we might talk about mission and purpose rather than objectives and goals. Similarly, when working with military organizations we tend to not use terms like “profit” or “sales,” because those terms aren’t generally relevant within DoD organizations.

However, changing a tool’s name to accommodate narrow biases and insecurities does not do anyone any favors. And to be quite clear, this team was not asking to rename RBT because they come from a post-agrarian society and can’t relate to botanical metaphors. No, they asked for the change because they explicitly felt flowers aren’t manly enough.

Here’s the thing – if you can’t handle a flower-based metaphor because it seems too girly, you’re going to have a really hard time doing anything innovative. I promise, accommodating this team’s request would have limited their ability to be innovative, not enhanced it.

Team Toolkit’s mission is to “democratize innovation.” We are here to help people understand what innovation is and how to do it. This necessarily involves expanding people’s horizons, introducing new metaphors, building new connections, and taking teams beyond business-as-usual methods and symbols. Allowing teams to stay in their narrow comfort zone is the very definition of non-innovation.

So yes, we love to customize our tools, but not if those changes make the tools less effective. Not if the changes narrow people’s mental aperture rather than expanding their horizons. And definitely not if the change reinforces lame stereotypes.

And for those of you who ARE open to a flower-based innovation tool, can I suggest also checking out the Lotus Blossom?

Rose Bud Thorn

Rose Bud Thorn

The Rose, Bud, Thorn tool is consistently the most downloaded tool in the kit. I have to admit that particular statistic from our website’s analytics always puzzled me a bit. I mean, RBT is a fine little method but it never struck me as particularly special. In fact, I always thought it looked pretty basic (that’s the term the kids use these days, right?). All you’re doing is listing the positive (rose), potential (bud), and negative (thorn) aspects of a project. No big deal, right?

Apparently my meh opinion was based on the fact that I’d never really used it before. When I finally did give it a try with a workshop last week, it pretty much blew me away.

What’s so awesome about this tool? Why do I love it now? Well, it is hugely accessible, for starters. There are no complicated steps to explain, no detailed procedures to follow, no subtle nuances to watch for. You’d think a guy who literally wrote the book on simplicity would be better at recognizing elegant simplicity when he sees it, but that’s the thing about simplicity. It often appears underwhelming at first blush. Sometimes the real value only becomes apparent when we look closer or take the thing out for a spin. I should probably go re-read my own book.

Last week’s workshop helped me see the RBT is a powerful lens groups can use to assess, analyze, and strategize. It reveals hidden assumptions and enables us to see past superficial considerations and achieve a deeper understanding of our situation. This participants spent an hour going through the RBT analysis, and it really set the stage for the rest of the two-day event.

If you’re going to use this with your team (and I highly recommend it!), I have one facilitation tip to consider: resist the urge to write the same thing in all three columns. This was a very common error in all the groups I worked with last week. Over and over again people said “We think X belongs in all three columns, because it has positive (rose), negative (thorn) and potential (bud) aspects.” Yes, the thing they’re talking about has roses, buds, and thorns. But the whole point of the tool is to distinguish between the roses, buds, and thorns. So putting the same word in all three columns isn’t terribly helpful. Once the groups began writing down the actual good, bad, and promising aspects of those things… the results were amazing.

How about an example? Consider a medical treatment that cures an illness. The cure is the ROSE. However, the treatment also has negative side effects. That’s the THORN. And let’s say that some (but not all) patients experience a secondary benefit. That would be the BUD.

Writing TREATMENT X in all three columns is not very helpful or insightful. It’s the wrong way to use the tool. Instead, I would suggest writing “Cures the disease” in the rose column. Then list the negative side effect (e.g. Causes significant fatigue) in the thorn column. Finally, describe the potential benefit (e.g. “Clears up acne for some patients”) in the bud column. We could now evaluate the relative costs and benefits of the treatment and decide how to proceed.

I hope you’ll give this tool a try – and we’d love to hear your stories of how you used it!

ITK & F-35

ITK & F-35

This week’s guest post is by Rick Dunham, from MITRE’s Air/Ground Surveillance Program, and it highlights a recent application of the Innovation Toolkit to the F-35 program.

Image of the MITRE F-35 Team Builds a Foundation for Success

Lead Human Factors Engineer Jessica Yu (standing) briefs F-35 Lightning II Enterprise Focus team members on using the Innovation Toolkit.

On Nov. 5-6, MITRE’s F-35 Lightning II Enterprise Focus team met in Dayton, Ohio, to build collaborative FY20 strategic foundations, covering shared-knowledge, sponsor-specific deliverables and outcomes. The diverse team, which includes more than 65 MITRE engineers from across the U.S., is charged with delivering F-35 Continuous Capability Development and Deployment (C2D2) to the field faster and more efficiently.

An Air Force Portfolio High-Profile Program, F-35 Enterprise team leads Portfolio Manager Jen Hebert and Project Leader Chris Jella—facilitated by the Innovation Toolkit Team—pioneered and challenged four main focus area groups: Reduce Live Fly; Implement Advance Capabilities; Integrate US, Partner, and International Efforts; and Modernize Mission Support and Infrastructures. The goal is to leverage and link cross-functional expertise in building shared mission-driven impactful products and outcomes.

This team-based approach and visionary mindset is why our F-35 Enterprise sponsors have come to rely on MITRE to organize work so that it magnifies the delivered capability to any one individual sponsor. By synthesizing MITRE’s internal, full-spectrum-funded research, labs, direct sponsor work, and related activities, the government pays once for a capability that benefits many sponsors and stakeholders.

MITRE F-35 Challenge Coin 500.jpgAdditionally, shared deliverables are a centerpiece of the MITRE F-35 Enterprise strategy. Each focus area group has both a set of sponsor-specific deliverables and a well-crafted outcome that contributes to a higher strategy while addressing local sponsor priorities.

This collaborative, get-to-know-you comradery structure will pay dividends, strengthening MITRE’s core excellence and service and ultimately, solving our sponsor’s most challenging C2D2 needs.