Tagged: innovation management

Gearing up for Informa’s Back End of Innovation (BEI) 2016


“A great idea is only the beginning. The Back End of Innovation provides a strategic road map to successful commercialization. Learn how to bring new products to market and commercialize them for maximum impact on the bottom line.  Uncover new ways to solve problems we all encounter in today’s dynamic business world.” 

Back End of Innovation #BEICONF


M2184_Back_banner_728x90_8-29-16_v1


image

I am working on the talk that I will deliver at Back End of Innovation 2016 and just came across BEI’s banner on prominent sites, such as CNN’s Innovation section (left screenshot).

The organizers have made available a discount code, which I can share if you were interested in attending. If so, feel free to send me a message on LinkedIn.

The conference’s agenda features speakers from 3M, Cisco, Coca-Cola, Fidelity, Johnson & Johnson, Keurig, Pepsi, Vodafone and Xerox among others and I will be there proudly representing Nokia.

My talk’s title is “Lean Ops Innovation: Dynamic Service Delivery,” which is scheduled on November 17 at 11:30. Here is the abstract:


M2184_Back_banner_300x250_8-29-16_v1“Network Operators in the telecommunications industry operate complex sets of technologies and environments. This sector’s future relies on furthering software defined systems supporting the next wave of pervasive digital services, which all of us come to rely on in our day-to-day lives.

Nokia’s Applications & Analytics (A&A) team has evolved and redefined Lean principles to intertwine advanced analytics, automation, programmability and human factors engineering, the four pillars of a new LeanOps’ framework. The outcome is effective service delivery enabled by highly efficient systems that remain nimble and agile at any scale and at any point in the life-cycle. 


Join Jose for this session to learn:

  • A new Lean Ops framework intertwining analytics, automation, programmability and human factors.
  • How to effectively interweave Design Thinking, Lean, DevOps and Agile to deliver breakthrough innovation.
  • Unlocking the value of Human Factors Engineering in the cloud age and, therefore, expanding the human possibilities of technology.”

imageEarlier in the year I gave a talk at IEEE Communications Quality & Reliability – CQR 2016 also on Nokia’s Lean Ops.

Back then, my focus was HCI, Human-Computer-Interaction and operational efficiencies. As an example, immersive user interfaces taking advantage of 3D data visualization coupled with autonomation and assisted automation, as well as continuous optimization lead to effective decision support systems (DSS) that mitigate human error and elevate value based tasks.

That was discussed in the context of the kind of complex operational environments experienced in the telecommunications industry by network operators. As shared above, my presentation at BEI will focus on the underlying construct instead.


This is my “75 word” bio for this event: “Jose is a Design Director at Nokia’s Applications & Analytics Group. His 15+ years of experience feature leadership responsibilities in strategy, product management, R&D, and marketing. Jose worked with Bell Labs and holds three patents. He is a Member of the Advisory Board at MIT IDSS and is the recipient of an MBA from Chicago’s DePaul University as a Honeywell Europe’s Be Brilliant Scholar. Jose holds a postgraduate degree in Human Factors Engineering from BarcelonaTech.”


This is the second time that I’m featured as part of BEI’s Speaker Faculty and I would like to take this chance to thank the team at Informa for their kind invitation.

I will be happy to meet at BEI and hope to see you there : )

Innovation Management Essentials: Situational Awareness


“Develop foresight, to sense and understand the context around the dilemmas that challenge you. The goal is not to predict what’s going to happen but to provoke your creativity and prepare you for your biggest challenges, many of which are going to come in the form of dilemmas (…) leaders are sense makers, and they help others make sense- often by asking penetrating questions.” Get There Early by Bob Johansen.


image


Situational Awareness (SA) involves sensemaking. SA deals with critical information on what’s going on with a project as well as around it. Know-how, past experiences, lessons learned and best practices are of the essence. These work well when addressing incremental innovation. Though, our perception is also shaped by motivation, expectations, filters as well as organizational behaviors (culture, workstyle, decision making, roles and responsibilities, processes) and, possibly, conflicting priorities.

Taking things to new levels, disruptive innovation gets us immersed in what turn out to be game changing environments. In this specific context, creative destruction takes place and so do errors in judgment. Dealing with uncertainty, ambiguity and rapidly superseding cascading events can quickly render one’s viewpoint out of focus and even out of place.

Those just sticking to what they know because relying on one’s “assumptions and belief system” has consistently served they well, might now suffer from complacency, myopia and tunnel vision instead… experiencing blindsiding denial in the process. Clayton’s “The Innovator’s Dilemma” and Taleb’s “The Black Swan” and “Antifragile” are worth understanding. 


Early awareness takes continuous listening and monitoring. Lets first think of project sensors gathering data and probes strategically placed to explore and discover clues which might not yet be visible. Leading indicators form a set of metrics that change in advance to a given event taking hold and can be used to raise alerts. Lagging indicators signal conditions in place for changes to take hold and become the new pattern.

Defining a narrow set of key performance indicators (KPI) improves visibility, saving us from clutter and information overload. KPIs can correlate and synthesize need-to-see data and can work with high level abstractions. These are usually delivered as “dashboards” that we can easily work with. Here is a “6 R” framework on KPI quality to mitigate distortions:


Relevancy: validity and utility level in context.   Resolution: meaningful detail and abstractions.
Range: scope (fields) and scale dimensions.   Recency: lifecycle – growth, decay and refresh velocity, ephemeral vs. durable.
Robustness: complete or sufficient to support the analysis, portrays what’s being measured.   Reliability: data integrity and error free, factors signal to noise rate, accounts for outliers.

The above is based on a “5 R” version I first learned on an MIT course about big data and social analytics.

I would also like to share that perfect data might be elusive and different quality levels can be applied. Hence, we talk in terms of things being “directionally correct” or “good enough” to keep things moving. In some other cases, over-engineering data by going beyond what’s really needed (data overload) can shortchange focus, efforts and budgets, which would be better allocated to other priority and/or pressing tasks. We can also face crunch time situations when we need to operate without benefiting from more data since delays would trigger higher risks.


Nonetheless, acknowledging that we need to make those kind of judgment calls does not excuse giving up on perfecting how to work with data. But, data alone will not deliver SA: this involves intertwining analysis and synthesis cycles as well as fine tuning sensemaking, which is an iterative and continuous improvement process.

Keeping cognitive biases at bay is a challenge. Subjective statements supporting adversarial stances such as “been there done that, it just doesn’t work” (even if that experience happened in a different context and a distant past) or the “not-invented here” (NIH) “not-one-of-us” syndromes can be easy to spot. But, there is a wide range of logical fallacies and “devil’s advocate” plays which can be perceived as reasonable even though the underlying logic is flawed.  


I designed the above chart drawing from the all familiar Strengths-Weaknesses-Opportunities-Threats (SWAT) model. As far as Frequently Asked Questions (FAQ) is concerned, the one I get the most is about the difference between “clash” and “shift”. Basically, the clash’s bucket is there to outline ongoing mismatches and adversarial confrontations. Those having reached critical mass can be plotted in the “clash x critical” quadrant.

The “shift” column captures game changing items that are still evolving, where a succession of disruptive believes and assumptions reshape the context and prompt new environments that can render a project obsolete… shouldn’t we gear up in advance or course correct as needed. Looking into impact levels, correlations, outliers and then sorting things accordingly is part of the thought process.

The next FAQ relates to how to best address “core” vs. “beyond comfort zone”. A core competence is an existing skill and capability. This refers to traits worth leveraging and further developing provided that they continue to make a difference. Though, asking any person, organization or system to just focus on what they already know and do well might not necessarily be the best approach in today’s rapidly changing and commonplace uncertain environments. Therefore, the need for assessing what and how to continuously grow beyond a given comfort zone, and at what point that new capability can be rolled up as a core competency.

One other thought, let’s keep in mind that being aware and alert are good things. Taking no action or seating tight while waiting for the dust to settle happen to be options available to us, though paralysis by analysis or paralyzing fear are not.

What about “organic” vs. “inorganic”? The former entails opportunities that can be approached with existing competencies and, possibly, scaling by growing resources. The latter talks to efforts that involve collaborating (collaborating with customers and partners, coopetition with competitors) and even acquiring other ecosystem players in the value chain, mergers being another example.


Last but not least, perspective is of the essence and the journey is comprised by experiences (where we come from) situational awareness (where we are) and foresight (where we are headed). Antonio Machado (Spanish poet, 1875-1939) stated that we make our path as we walk, which anyone working on innovation projects can relate to. Delineating and providing a sense involves the following “journey points”, which I will discuss on another post on agile project planning:

  • kick-off / start point
  • takeoff limits
  • checkpoints
  • milestones
  • crossing chasms
  • touch points
  • breakeven point
  • tipping point
  • chain reaction
  • inflection point
  • turbulences
  • crossroads
  • decision points
  • pivoting
  • point of no return
  • breaking point
  • moving targets
  • valley of death
  • dead ends
  • aftermath

Hope this remains of interest. As usual, I will welcome your comments and emails to continue our discussion.

Link to my latest post.

Innovation Management Essentials: Impactful Demos


“The Mother of All Demos is a name given retrospectively to Douglas Englbart’s December 9, 1968 […] The live demonstration featured the introduction of a complete computer hardware and software system called the oN-Line System or more commonly, NLS. The 90-minute presentation essentially demonstrated almost all the fundamental elements of modern personal computing: windows, hypertext, graphics, efficient navigation and command input, video conferencing, the computer mouse, word processing, dynamic file linking, revisions control, and a collaborative real-time editor (collaborative work). Engelbart’s presentation was the first to publicly demonstrate all these elements in a single system. The demonstration was highly influential and spawned similar projects at Xerox PARC in the early 1970s. The underlying technologies influenced both the Apple Macintosh and Microsoft Windows graphical user interface operating systems in the 1980s and 1990s.”The Mother of All Demos, Wikipedia.


image


Compelling demonstrations can make all the difference when introducing emerging technologies. There is no slideware or paper substitute for the kind of revelations, quality insights, and lasting emotions that we all get when experiencing things live and first hand. On the research side, interactive demonstrations have become invaluable tools that expose and test concepts. Moreover, they prompt invaluable feedback by questioning, validating, unveiling unsuspected items as well as winning hearts and minds to further advance a cause.

Those are some of the reasons why I prioritize demo development and my research process involves activities such as field trips and ethnographic insights captured in environments like the Museum of Science and Industry (MSI) in Chicago and open-door showcases at renowned institutions like Fermilab. Successful science exhibits make complex topics approachable and engaging. They are carefully designed with craftsmanship pride to be perceived as astute, immersive and to appeal to our brain’s intuition and intellect.


The above graphic features quotes from Albert Einstein and Nicholas Negroponte on the left, coupled with Salvador Dalí and Arthur C. Clarke on the right.  I created that poster’s first version a few years ago and became my reference framework for prototyping and demonstration since. The photographs are courtesy of Wikipedia. Here are further insights on what these quotes mean to me:


1.- DEMO OR DIE – The introduction of inventions and diffusion of innovations relies on effectively conveying clear and concise value. Interacting with engaging demonstrations can be best supported by well thought out whiteboarding sessions. This communication strategy works best when allowing dynamic conversations instead of long agendas packed with presentation monologues. Most people can talk about the many times when they were either overwhelmed, underwhelmed or just bored to death by slideware… and became suspicious of hype. Note that we all deal with an unfavorable Signal-to-Noise (S/N) ratio in today’s information rich environment and, therefore, compete for customers and/or users’ undivided attention. Once again, memorable hands-on demonstrations can make all the difference.


2.- GROW TO LOOK LIKE THE PORTRAIT – High tech is a fast paced industry. One can be left wondering if the technology, toolset, application and/or overall system being discussed will grow and scale as needed beyond day one. There can also be concerns around maturity levels, roadmapping options and future proofing when working with emerging technologies. Demos can be used to convey a tangible vision based on attainable end-goals. They can also be used for what-if-analysis, sunny and rainy day scenarios (which can include full lifecycle and stress tests) and plot plausible journeys to go from A to B and any steps in between. Helping everyone come to terms with what lays ahead is key to defining product strategies and planning decisions “to grow to look like the portrait.”


3.- EXPLAIN IT SIMPLY – Apparently unavoidable jargon and well intended technical kumbaya can become easily entangled. Complex explanations suffer from information overload. Convoluted narratives pleasing the presenter’s ego can make unclear what specific problem or pain point he/she solving, and what the sought after benefits and priorities are. When “less is more” it definitely pays to define a vantage point, zoom out, distill fundamentals and synthesize the essence. Knowing your audience and getting the job done in the clearest and most effective terms possible means striking a balance and staying away from oversimplifying or complicating matters. This is an iterative exercise that often demands more time, effort and reviews than the usual information dump. We also need to be able to step-zoom to deliver the next level of detail and to conduct deep dives… without incurring information overload. Humanizing technology, storytelling techniques and ease of information visualization are key to developing a coherent narrative.


“The meaning of a communication is defined by the Change and Affect it creates for the audience. Stories are concerned with transformation. In stories something Changes to create an emotion […] The Change has to resonate with the Audience to generate an Affect; a feeling, a reaction or an insight […] We shall consider these two defining characteristics of narrative to clarify the purpose of any communication […] Change and Affect create meaning. – “Crackle and Fizz. Essential Communication and Pitching Skills for Scientists.” – Caroline van den Brul. Imperial College Press.


image


4..- IT’S MAGIC – This is all about the so called X-FACTOR: an unsuspected quality making something be different and special in unequivocal terms. To be more precise, the X-FACTOR’s experience can be broken down as follows:


  • SURPRISE FACTOR – this relies on managing perceptions and the discovery process, the tipping point being delivered by a timely and unsuspected clever twist and a defining punch line – the “aha” moment.
  • WOW FACTOR – high impact, impressive, awe-inspiring outcome, benefits and results that can be easily understood and embraced – the “I didn’t know we could do that” and “I want to know more” moment.
  • COOL FACTOR – elegant sophistication and grace, clear object of desire – the “I want that” moment, this being most demos’ ultimate Call-To-Action (CTA.)

The art and science behind the above is known as “affective design.” Techniques such as perceptual learning and emotional intelligence in design (emotional design in short) are applied in Human-Computer-Interaction (HCI) to foster pleasant ease of use, drive further engagement and productive usage in the process. Widespread digitalization and the advent of wearables make HCI commonplace, which is influencing product design.


image


The above is a demo’s “full disclosure” chart, which breaks down what’s real and what’s not. This is needed because vaporware can be an issue of concern.

1.- PRIOR ART – In the above example, a given percentage of the demonstration system involved known technologies, some from third party partners.

2.- STATE OF THE ART – The greatest and latest features, cutting edge delivered by technologies that are available today.

3.- FUTURE ART – A sneak preview of new features and capabilities that are planned, undergoing development and/or committed, but not yet available.

4.- ART OF THE POSSIBLE – Proof of Concept illustrating experimentation results and potential, bleeding edge capabilities that are not yet committed.

By the way, vaporware is the result of positioning 3 and 4 as part of 2. Avoiding unpleasant misunderstands prompts the need for disclosing these four different maturity levels. Note that one graphic applies to a comprehensive demonstration system encompassing those four aspects and their relative weight.


One other thought, there is a difference between incremental and disruptive innovation. The first delivers improved qualities such as better performance in A/B comparison testing as an example, “A” being prior art and “B” state of the art. Most would agree on defining disruptive innovations as game changers which deliver unique capabilities that clearly supersede legacy and conventional systems. That alone renders “A” obsolete. A/B comparison testing leads to discussions on the difference between Present Mode of Operations (PMO) and Future Mode of Operations (FMO.)


“Humanists must be educated with a deep appreciation of modern science. Scientists and engineers must be steeped in humanistic learning. And all learning must be linked with a broad concern for the complex effects of technology on our evolving culture.” – Jerome B. Wiesner.