Innovation Engineering Book

Here you can find the table of contents as a reference for reading assignments

Table of Contents

FOREWORD …………………………………………………………………………………………….. 7

TABLE OF CONTENTS ……………………………………………………………………………….. 9

ACKNOWLEDGMENTS ……………………………………………………………………………. 15

CHAPTER 1: SUMMARIZING THE PROBLEM AND INTRODUCING THE SOLUTION ……………………………………………………………………………………………… 18

The CXO Perspective…………………………………………………………………………………………. 18

Innovator Perspective………………………………………………………………………………………. 19

A MAJOR MISCONCEPTION FOR INNOVATIVE PROJECTS: ……………………………………20

WHY INNOVATION PROJECTS ARE DIFFERENT: …………………………………………………21

CHARACTERISTICS OF SUCCESSFUL PROJECTS: ………………………………………………….23

INNOVATION ENGINEERING…………………………………………………………………………………27 BOOK ORGANIZATION ……………………………………………………………………………………..28

HOW TO USE THE BOOK ……………………………………………………………………………………..30

SOME RELEVANT BACKGROUND…………………………………………………………………………..33

CASE STUDY: RICHARD DIN AND CAVIAR……………………………………………….. 36

CAVIARS STARTUP JOURNEY ……………………………………………………………………………….36

THE INITIAL CONDITIONS…………………………………………………………………………………….36

STORY ……………………………………………………………………………………………………………..37

CAVIAR’S USE OF ‘EXECUTION WHILE LEARNING’ …………………………………………………..39

LEADERSHIP AND INNOVATION BEHAVIORS ……………………………………………………………40

CHAPTER2: THE SOLUTION……………………………………………………………………43

THE BACK STORY……………………………………………………………………………………………….44

UNDERSTANDING THE SOLUTION: ……………………………………………………………………46

Inductive Learning: …………………………………………………………………………………………. 47

THE INNOVATION ENGINEERING PROCESS……………………………………………………………..52

PhaseI: InitialConditions……………………………………………………………………………….53

PhaseII: StoryDevelopment………………………………………………………………………….53

Phase III: “Execution while Learning”…………………………………………………………… 55

PhaseIV: ReadytoScale…………………………………………………………………………………56

CHAPTER 3: A STEP-BY-STEP GUIDE TO INNOVATION PROJECTS……………..58

STEP 1: ARTICULATE THE INITIAL CONDITIONS ………………………………………………………59

STEP 2: DEVELOPING THE STORY…………………………………………………………………….61

9

INNOVATION ENGINEERING

Scope the Concept……………………………………………………………………………………………..61

Further Develop the Story ………………………………………………………………………………64

What is a Story ……………………………………………………………………………………………………64

  1. Contextual story…………………………………………………………………………………………….65
  2. B) Technical Story……………………………………………………………………………………………….68
  3. Plan for Partners and Stakeholders within the Story……………………………..70
  4. Getting Started Requires a Context Leader and a Technical Leader….71
  5. Defining Success ………………………………………………………………………………………………..72

STEP 3: EXECUTION WHILE LEARNING ………………………………………………………………… 73

Learning Journey ………………………………………………………………………………………………..74

Navigating the Learning Journey……………………………………………………………………78

Agile Implementation for Technical Delivery:……………………………………………..79

STEP 4: SCALE OR HANDOFF ……………………………………………………………………………… 80

SUMMARY ……………………………………………………………………………………………………….82

CASE STUDY: ORACLE CHANGES ENTERPRISE PROCUREMENT ……………….. 83

INITIAL CONDITIONS ………………………………………………………………………………………….84

STORY …………………………………………………………………………………………………………….. 85

EXECUTION WHILE LEARNING……………………………………………………………………………..86

BEHAVIORS ……………………………………………………………………………………………………… 87 SUMMARY ……………………………………………………………………………………………………….88

CHAPTER 4: DEVELOPING A BETTER STORY…………………………………………….89

STORY DEVELOPMENT ……………………………………………………………………………………….89

High Concept Pitch …………………………………………………………………………………………….90

Elevator Pitch………………………………………………………………………………………………………91

The NABC Model…………………………………………………………………………………………………92

The Customer Story……………………………………………………………………………………………92

The Future Press Release………………………………………………………………………………….93

The 6 Page Plan by Amazon…………………………………………………………………………….93

The Venture Pitch and Its Variations……………………………………………………………..95

Which Story Type Should You Use………………………………………………………………….96

Revenue Generating vs. Non-Revenue Generating Projects ……………………97

Perfecting the Story……………………………………………………………………………………………98

CHAPTER 5: COMMON STRATEGIC ERRORS AND STORY NARRATIVE MISTAKES …………………………………………………………………………………………… 101

WHAT COULD POSSIBLY GO WRONG? ……………………………………………………………….. 101

ALL LOGIC, NO EMOTION ……………………………………………………………………………….. 102

SOLVING THE WRONG PROBLEM ……………………………………………………………………… 103

10

INNOVATION ENGINEERING

UNQUANTIFIABLE VALUE PROPOSITION …………………………………………………………….. 105

 MARKET SIZE NONSENSE ………………………………………………………………………………… 108 

FINANCIAL MODEL ERRORS………………………………………………………………………………111

CORE COMPETENCY ERRORS ……………………………………………………………………………. 113

A FINAL NOTE ON GETTING NEW PROJECTS STARTED WITHIN ANY EXISTING ORGANIZATION ……………………………………………………………………………………………… 114

CASE STUDY: NETSCAPE AND E-COMMERCE ……………………………………….. 116

INITIAL CONDITIONS………………………………………………………………………………………..117

STORY ………………………………………………………………………………………………………….. 118

EXECUTION WHILE LEARNING ………………………………………………………………………….. 119

BEHAVIORS ……………………………………………………………………………………………………121

SUMMARY…………………………………………………………………………………………………….. 122

CHAPTER 6: THE MISSING PUZZLE PIECE……………………………………………… 124

WE HAVE OBSERVED MANY BENEFITS USING INNOVATION ENGINEERING …………….. 125

CHAPTER 4: MAKING IT PRACTICAL WITH THE INNOVATION NAVIGATOR…………………127

SETTING UP THE INNOVATION NAVIGATOR ………………………………………………………… 129

USING THE INNOVATION NAVIGATOR ……………………………………………………………….. 130

INNOVATION ENGINEERING: WHAT IS REALLY GOING ON? AND WHY IT WORKS …… 131

SUMMARY…………………………………………………………………………………………………….. 135

CASE STUDY: VMWARE SCALING INNOVATION IN MOBILE ………….. 136

INITIAL CONDITIONS:……………………………………………………………………………………139 STORY:………………………………………………………………………………………………………… 140 EXECUTION WHILE LEARNING:…………………………………………………………………….. 141

BEHAVIORS: ………………………………………………………………………………………………… 141

CHAPTER 7: INNOVATION LEADERSHIP……………………………………………….. 145

BUILDING THE TEAM ………………………………………………………………………………………. 145

Step 1: The initial team must build and sustain trust…………………………… 146

Step 2: Consider the balance of team expertise vs innovation culture147

LEADING AN INNOVATIVE TEAM ……………………………………………………………………….. 151

Leadership with Trust vs Insecurity ……………………………………………………………. 151

Planning, Urgency, and Agility ……………………………………………………………………. 152

TheNextChallenge: AfterGrowthComesAlignment…………………………..154

The Innovation Leader’s Role………………………………………………………………………. 155

Coaching the Team to Learn Inductively…………………………………………………… 156

SELF-DEVELOPMENT AND TEAM DEVELOPMENT…………………………………………………. 159

THE INNOVATIVE LEADER’S BROADEST FUNCTIONS……………………………………………… 162

SUMMARY…………………………………………………………………………………………………….. 163

11

INNOVATION ENGINEERING

CASE STUDY: MIXBOOK NAVIGATING INNOVATION……………………………. 165

INITIAL CONDITIONS ………………………………………………………………………………………. 166

STORY ………………………………………………………………………………………………………….. 167

EXECUTION WHILE LEARNING ………………………………………………………………………….. 168

BEHAVIORS AND MINDSET………………………………………………………………………………. 171

CHAPTER 8: CULTURE, MINDSET, AND BEHAVIOR……………………………….. 173

MORE BACKSTORY…………………………………………………………………………………………. 173

BEHAVIORS AND MINDSETS FOR INNOVATION ENGINEERING ……………………………….. 175

GENERAL BEHAVIORS FOR INNOVATION ……………………………………………………………. 175

Storytelling as a Leadership Model……………………………………………………………..175

Trust ……………………………………………………………………………………………………………………176 Comfort Zone ……………………………………………………………………………………………………177

Accretive Negotiation and Fairness…………………………………………………………….177

Connectors are key…………………………………………………………………………………………178

Diversity equals value……………………………………………………………………………………179

Inductive Learning …………………………………………………………………………………………..179

Emotional Quotient and Grit ………………………………………………………………………..180

SUMMARY ……………………………………………………………………………………………………. 180

CASE STUDY: NVIDIA 2005-2010 ……………………………………………………. 181

INITIAL CONDITIONS:…………………………………………………………………………………… 182

STORY: ……………………………………………………………………………………………………….. 185 EXECUTION WHILE LEARNING:…………………………………………………………………….. 186

BEHAVIORS, MINDSET AND LEADERSHIP:……………………………………………………… 188

SUMMARY: ………………………………………………………………………………………………….. 189

CHAPTER 9: TECHNICAL BEHAVIORS FOR INNOVATION ………………………. 190

User-First …………………………………………………………………………………………………………… 191

Break it down……………………………………………………………………………………………………192

Effectuation ………………………………………………………………………………………………………192

Look for Insight in the technical story…………………………………………………………193

Minimal Viable System Architecture…………………………………………………………..193

Agile Increments and Flexible Technology Strategy:………………………………193

Keep it Simple……………………………………………………………………………………………………193

Reduce the Downside……………………………………………………………………………………..194

Measurable Objectives…………………………………………………………………………………..194

Create a support ecosystem………………………………………………………………………….194

SUMMARY ……………………………………………………………………………………………………. 195

CASE STUDY: IMPRINT ENERGY AND CHRISTINE HO ……………………. 196

12

INNOVATION ENGINEERING

INITIAL CONDITIONS:……………………………………………………………………………………197 STORY:………………………………………………………………………………………………………… 198 EXECUTION WHILE LEARNING:…………………………………………………………………….. 198

BEHAVIORS LEARNED FOR DEVELOPING THE BUSINESS:………………………………… 200 SUMMARY:…………………………………………………………………………………………………… 202

CHAPTER 10: APPLICATIONS FOR INNOVATION ENGINEERING ……………. 203

LARGER FIRMS AND GOVERNMENT ORGANIZATIONS …………………………………………… 204

APPLIED RESEARCH IN UNIVERSITIES OR COMPANIES …………………………………………… 207

Innovation in Academia: ………………………………………………………………………………. 207

Innovation in Corporate Research ……………………………………………………………… 208 NEW VENTURE CREATION ……………………………………………………………………………….. 210

THE CAPSTONE PROJECT OF THE FUTURE …………………………………………………………… 212 SUMMARY…………………………………………………………………………………………………….. 213

APPENDIX OF ADDITIONAL CASE STUDIES……………………………………………. 215

CASE STUDY: STARTING AN AGILE IMPLEMENTATION FOR TECHNICAL

DELIVERY…………………………………………………………………………………………….. 216

CASE STUDY: DATA-X, A PRECURSOR TO INNOVATION ENGINEERING…. 218

DATA-X CASE EXAMPLE A: MAIA: AI FOR MUSIC CREATION ………………………………… 222

DATA-X CASE EXAMPLE B: STAYFE ………………………………………………………………….. 224

DATA-X CASE EXAMPLE C: PRISM FOR TRACKING INFLUENCERS IN SOCIAL MEDIA ….. 226

EPILOGUE……………………………………………………………………………………………. 229

INDEX OF TERM…………………………………………………………………………………… 231