"Innovation is CREATIVITY that ships" (Steve Jobs). Not a PowerPoint slidedeck.

Pixar Pitch

Once upon a time mergers and acqusitions (M&A) in many high tech firms was stratified as a financial transaction both in Wall Street and in cherry-picked Silicon Valley zipcodes. As a result, human capital was largely ignored like Cindrella, a drudge-like creature in the Technology Policy Ball. And because of that humanity seemed to be outside the radar of the human resources department. And because of that there was a slump in productivity and a majority of the workers were dissatisfied with their sense of accomplishment at work (also confirmed in Gallup polls). The prevailing conventional wisdom at the CEO and board levels staunchly believed that an adhoc mixture of one or more luck events, charismatic leadership and targeted rightsizing is the silver bullet for post-merger integration success. And because of that the strategic agility of the firm remained inherently weak and the accruing technical debt in the financially significant systems became a critical business issue (a three headed hydra) for the firm. Project management was also regarded an overhead which created a roadblock for the PMO to get a seat at the table. Until one day a grassroots campaign in the IT community to embrace the principles of the Agile Manifesto started a global movement in the business community to bring individuals and intereactions front and center as first class citizens, reject the tired traditions of yesteryear, adopt a system view and relentlessly focus on optimizing the business. As a result of this mandate, there was a visible change in priorities in the board room. And from that day forward, self-organizing teams catapulted into action by internalizing the founder’s touch and (1) welcomed the initial state of dissonance during post-merger integration to innovate, (2) built the muscle of strategic agility at scale in the enterprise and (3) revived the passion for Managing by Wandering Around (MBWA).


What is the M&A situation?

Nokia was a platform-based acquisition with a complexity that metaphorically represented a reverse two and-a-half somersault with a half twist. The acquisition, classified as a “burning platform,” was originally intended to provide a center of gravity for Microsoft to make an entry in the mobile phone business. As a challenger, this presented an opportunity to make a radical change to navigate towards uncharted waters in terms of both the upstream and downstream parts of the value chain while retaining existing and acquiring new Nokia customers.

“Nokia, our platform is burning.”
“We are working on a path forward — a path to rebuild our market leadership. When we share the new strategy on February 11, it will be a huge effort to transform our company. But, I believe that together, we can face the challenges ahead of us. Together, we can choose to define our future.”
“The burning platform, upon which the man found himself, caused the man to shift his behavior, and take a bold and brave step into an uncertain future. He was able to tell his story. Now, we have a great opportunity to do the same.”
Dated: Feb 9, 2011

At that time, as a shareowner, I had an outside in perspective of the firm and presented a compelling, not-to-miss opportunity to create a cadre of Activist Turnaround Managers (ATM, pun intended) on Main Street. I published a blog post in February 2011.

The corporate renewal of Nokia was not successful. The bad news was communicated via the “Hello There” memo.

“Companies spend more than $2 trillion on acquisitions every year. Yet study after study puts the failure rate of mergers and acquisitions somewhere between 70% and 90%.”
Clayton Christensen, The M&A Playbook, Harvard Business Review, Jul 2015

Precision Question

How do we turnaround the context from a public narrative of a high-visibility face-plant to write-off a failed acquisition as a distressed asset in the balance sheet to one that is more solution focused (SF), hands on, which also strikes a chord with both the financial and human propositions to achieve post-merger integration success?

Learning from Jack Welch

At an April 1986 board meeting in Kansas City, I had argued for it – and unanimously swung the board my way. It was a classic case of hubris. Flush from the success of our acquisition of RCA in 1985 and Employers Reinsurance in 1984, I was on a roll. Frankly I was just full of myself. While internally I was still searching for the right “feel” for the company, on the acquisitions front I thought I could make anything work. There’s only a razor’s edge between self-confidence and hubris. This time hubris had won and taught me a lesson I’d never forget. The Kidder experience never left me. Culture does count, big time.
(Jack Welch, Straight from the Gut, 2001)

“Even so, as lessons go, $7.5 billion is pretty steep tuition.

Hindsight is always 20/20. Rather than fall into the conventional trap of casting the blame on an individual for a bad deal (“tire that had a flat”), in a solutions focused (SF) approach we avoid spending an inordinate amount of time to find out why it is flat (root cause analysis) and focus instead on getting a new tire to try to make sure it stays inflated (i.e., make a good deal better and avoid a bad deal — sage advice that I learned at Ernst & Young). Jack Welch’s insights also emphasizes the importance of human capital during post-merger integration. However, the venture integration group in most firms often fall into the trap of viewing a potential acquisition only through a financial lens and worry less about the heavy lifting required during post-merger integration.

The Nokia acquisition was probably originally intended to be an enhancement deal since it was designed to bring the acquirer capabilities that it didn’t yet have but would allow it to intensify its own capabilities system. However, studies have shown that unlike leverage deals, both enhancement deals and limited-fit deals don’t produce the best returns.

M&A deals continue unabated

The 15 Biggest M&A Deals Of 2015 (so far) consist of the following:

  • Private equity firm Thoma Bravo and the Ontario Teachers’ Pension Plan completed the acquisition of Riverbed Technology for approximately $3.5 billion.
  • Sopos acquired SMB email security and archiving company Reflexion Networks for an undisclosed account.
  • DLT Solutions was was acquired by private equity firm Millstein & Co. for an undisclosed amount.
  • HP bought Aruba Networks for $3 billion.
  • Bain Capital acquired security firm Blue Coat Systems for $2.4 billion.
  • PCM acquired solution provider and systems integrator En Pointe Technologies for $15 million. (En Pointe is one of Microsoft’s largest licensing solution providers in the country.)
  • Nokia acquired French rival Alcatel-Lucent for $16.6 billion.
  • Fortinet acquired Meru Networks in a deal valued at approximately $44 million.
  • Cisco acquired OpenStack specialist Piston Cloud Computing to accelerate its Intercloud strategy. (undisclosed amount)
  • EMC acquired cloud computing company Virtustream for $1.2 billion.
  • Accuvant and FishNet have completed their merger and will launch as Optiv Security.
  • SofwareOne acquired the software licensing business of $2.2 billion solution provider CompuCom.
  • Intel acquired semiconductor manufacturer Altera for $16.7 billion to bolster its Internet of Things business.
  • Avago is buying rival Broadcom in a $37 billion deal.
  • Charter Communications is purchasing of Time Warner Cable for $56 billion as well as buying Bright House Networks for $10.4 billion.

Post-merger integration success is not guaranteed for all the above deals. While there is no universal recipe, I feel that it is a valuable exercise to explore some options to “make a good deal better and avoid a bad deal.”

Higher Intent

One level up

The following Post It notes represent a subset of undesirable effects (UDEs) during an unsuccessful post-merger integration.

The higher intent “one level up” (my boss) is to reverse the UDEs and achieve a large subset of the following outcomes during the post-merger integration of a firm.


Two levels up

Taking an ounce of Tom Peters’ sage advice, the leadership (two levels up) has a recognized that a culture of execution-accountability is a pre-requisite for achieving corporate renewal (inclusive of situations during post-merger integration). Aside from the size of the deal, at a tactical level, execution excellence requires leaders to re-learn the behavior of Managing by Wandering Around (MBWA), which was the rhythm of the business during a bygone era at Hewlett-Packard (now in distant memory).

My Intent as a Shareowner

What are we trying to achieve and why?
  • Reframe past M&A failures as fallure so that organizational leaders can learn to adopt a growth mindset in a turbulent environment
  • Use the M&A (both pre- and post-merger) as a springboard to develop the generative process for strategic agility of the firm. (click on the link to view the dialogue map)
  • Develop the capability to notice an opportunity and make a rapid yet precise move using extraordinary accelerating power
  • Develop the capacity of making knowledgeable, nimble, rapid strategic moves with a high level of precision
In order to
  • Improve sensemaking, decision making and resource deployment during the selection, acquisition and integration phases of a merger
  • Increase Return on Luck (ROL) during post-merger integration and build a relevant @ResponsiveOrg

Return on Luck


A longitudinal panel of over 400 observations across multiple firms and industries has revealed that post-merger success hinges on achieving the dual goal of simultaneously improving customer satisfaction and operational efficiency. This in turn enables the merger to achieve a significant increase in long-term financial performance.

A lack of systems thinking during post merger integration can cause corporate myopia. We urge that one has to think outside the box, understand the causality among the undesirable effects (identified earlier) and target what to change, where to change and how to change.

Digital business strategy extends the scope beyond firm boundaries and supply chains to dynamic ecosystems that cross traditional industry boundaries. A digital firm’s design capital is the cumulative stock of designs owned or controlled by a firm. Design capital is a fundamental construct to the emerging logic of digital business transformation. The salient dimensions of design capital are option value and technical debt. In order to be strongly positioned for innovation and platform leadership, high-quality design capital is characterized by high option value and low technical debt. A study by the UK Design Council in 2005 revealed that companies with a sustained track record in design outperformed their peers in the FTSE 100 over a 10-year period by a startling 231 percent.

Akin to fiscal debt, technical debt is a common occurrence during systems development where time pressures or resource constraints cause developers to take shortcuts. Left unmonitored, accumulating technical debt obligations causes the cost of quality to increase over time which in turn impacts customer satisfaction and revenue generation.

Technical Debt

In a radical departure from earlier efforts, we have realized that during post-merger integration, it is vital to proactively manage the design capital of the firm (in addition to the firm’s balance sheet) by monitoring and controlling both technical debt.

Operationalizing strategic agility in an enterprise

Disciplined Agile is a process decision framework for a digital business at an enterprise level. Pioneered by Scott Ambler and Mark Lines, Disciplined Agile recognizes that an organization is a complex and adaptive system. Moreover, it is unrealistic to impose a “one-size-fits-all” agile-in-the-large model in a (global) enterprise.

Based on the cumulative real-world experiences from several hundred IT projects, Disciplined Agile is a proven framework for an enterprise to grow the muscle of strategic agility at scale in both IT and non-IT situations. Disciplined Agile has a rigorous focus on (1) the iterative delivery of consumable solutions (business value), (2) continuous learning from retrospectives, and (3) fostering an agile mindset around the enterprise. By adopting Disciplined Agile, leaders can achieve the following:

  • Pay increased attention to the (soft) human, cultural and non-functional deal aspects
  • Diminish the impacts of unknown elements (risk/value tradeoff) using an iterative incremental manner
  • Actively optimize technical debt and increase the design capital of the firm

Recognizing that there are several cross-project dependencies during any post-merger integration, there will typically be an active Project Management Office (PMO) that will be monitoring the project portfolio at an enterprise level. Disciplined Agile teams and PMO should work together and leverage suitable processes from PMBOK (Project Management Body of Knowledge) to practice project execution excellence.

The primary takeaway is that during post-merger integration, the secret sauce rests not on the framework per se but, echoing Tom Peters’ words, a culture of execution-accountability and Managing By Wandering Around (MBWA) in the trenches during post-merger integration. The Activist PMO Leader walks the Disciplined Agile talk with a learning by doing perspective and co-creates the generative process of strategic agility of the firm.


  • In order to build a resilient organization, establish self-organizing teams that practice autonomy, mastery and purpose.
  • Harness a culture of innovation so that the firm can become more intrapreneurial
  • Constraints
    • According to Barry Boehm, a system will succeed if and only if it makes winners of its success-critical stakeholders. This implies the importance of stakeholder management during post-merger integration.
    • Adopt the lean principle and minimize waste during post-merger integration.
    • Proactively identify the weakest link in the value chain during post-merger integration. This is a continuous activity (not just once at inception).


    Has the situation changed?

    The retrospectives from each of the projects in enterprise project portfolio creates a force multiplier for the firm to be in a state of continuous improvement and actively track the health of the human capital, the value of the design capital and the financial performance.


    Playing devil’s advocate, it is reasonable to critique that our proposal for post-merger integration success is either an unproven idea or old wine in new bottles. That said, the core tenet is to build the muscle of strategic agility and a passion for Managing by Wandering Around (MBWA) during the post-merger integration journey.


    • Patel, R., “Applying Project Management Approaches to Achieve Value Creation in Post -Acquisition Integration”, The ISM Journal of International Business, ISSN 2150-1076, Volume 1, Issue 4, October 2012.

A.J. Lafley constantly echoed that “We weren’t going to win if it was an ‘or,’ Everybody can do ‘or.’ That’s the way the world works. You trade things off. But you’re not going to be the best in your industry. You are not going to win if you are in a trade-off game.”
Roger Martin, The Opposable Mind: Winning Through Integrative Thinking (Boston, MA: Harvard Business School Publishing, 2009)

Results from successful transformation efforts have proven that the paradox of true leadership is to become adept at using both sides of the brain and is a balancing act between the the following in dynamic environments:

  • Providing vision yet empowering others
  • Giving up control yet architecting the choices
  • Sustaining yet disrupting the business model
  • Relying on data yet trusting your intuition
  • Being skeptical yet open-minded

strategic agility root IBIS

what is strategic agility IBIS

what are the capabilities IBIS

Evaporating Cloud

strategic agility

Refactored Assumptions

  • We will always welcome messy, complex tensions (paradoxes).
  • We will foster a deep appreciation and respect for paradoxical tensions.
  • We will value paradoxes as vital ingredient of high performance.
  • We will proactively identify and raise tensions including a code of conduct to stress tensions that spur creativity.
  • We will avoid traps of anxiety and defensiveness.
  • We will consistently communicate a both/and vision while exhibiting, in Collins’ words, “pragmatic idealism”.
  • We will separate efforts to focus on both sides of a paradox (“collective genius of the AND logic”).
  • We will constantly learn to step back and question our initial discomfort and desire for an either/or solution.
  • We believe we are doing something that has never been done before and we will take risks, innovate, and learn from our fast failures.

strategic agility_1

Mumbai’s committed contingent of 5,000 dabbawallas (dabba = tiffin, container; walla = worker) delivers over 350,000 lunches per day to office workers across the megacity with a commitment for accuracy and service excellence. I recall my childhood in Mumbai when my mother delivered a home cooked meal (ghar ka khana in Hindi) to my school through a dabbawalla.


As I consumed my bowl of Kellogg today, I mulled that while Silicon Valley and Starbucks had become part of corporate folklore, the ethos of the dabbawalla system wasn’t as well known outside the Indian subcontinent.

Following an organizational realignment, my team felt stuck and unproductive after being officially asked to stay on a “holding pattern” through a vaguely worded memo. I also felt rather jaded after seeing email signature blocks that read […] “Make a Difference“. Trapped in this status quo, I felt that I was not enhancing my contribution potential and walking the talk of “making a difference”. I heard echoes of (the infamous) “how good managers set up their employees to fail syndrome” in a corporate environment. Resisting the default urge to assign blame, I felt an itch to do something constructive and, consistent with the global tilt, I searched for outsight (outside in focus).

“The planning process spins and spins, but nothing — and nobody — moves.”
Dan Pink, To Serve is Human, 2012

As an Activist PMO Leader, I had an epiphany regarding connecting the dots between (1) the spirit of service that is the container of the dabbawalla culture and (2) the tenets of Host Leadership.

I’ve sketched a sensemaker’s view of the dabbawallas’ DNA so that I can bust the clouds in my head. The essence of the dabbawalla’s spirit is upserving, which essentially means taking the extra steps to transform a mundane experience into a memorable experience.

dabba root

host leadership root



space creator

gate keeper





org structure


make a difference

(click to enlarge)
Host Leadership

With a goal to become relevant in the conversation to mitigate strategic inertia and increase customer intimacy, I am going to learn how to help others get unstuck by being solution focused, adopt the Roles of Engagement of Host Leadership and operate like a dabbawalla in a corporate environment and co-create value. While I don’t have all the answers, this is an improvised performance of a lifetime and a growth opportunity to enhance my contribution potential.

A Leadership Team (LT) that has the courage of conviction will incorporate the dabbawalla culture in order to plant the seeds of service innovation as part of the company’s transformation journey. By incorporating key principles of the dabbawallas mindset any business can make a difference with attunement, benevolence and clarity (ABC) while serving a customer.

In 2011 the management team at NASCAR realized that the company had become dangerously irrelevant. The old way of engaging the fans, who were mostly millennials, was creating a “disjointed user experience that discouraged online exploration of the sport.”


A state of dangerous irrelevance is every CxO’s nightmare. Yet it is often too easy to miss during the daily demands of business as we fall prey to being “present-biased” and defer the need to compete for the future. Richard Thayer, University of Chicago, would probably agree that this is an example unconscious “misbehavior.” We recommend pausing periodically and taking a deep breath to process and reflect how things are unfolding and nudge the organization to take calculated risks to enhance competitive advantage.

East of Amazon.com, across Lake Union, the stay awake at night moments of Microsoft’s founders revolved around:

  • What are the things that make our organization unique?
  • Where do we focus?
  • What is unique about our people?
  • What is unique about our culture?
  • What are our core values and core competencies?
  • Are we building a company that will still be around well after Bill Gates and the founding management team are gone?

How were Gates, Grove and Jobs (The Founders’ Touch) able to steer their companies (Microsoft, Intel, Apple) through the volatile ups and downs of decades of changing technologies and mitigate dangerous irrelevance?

Founders Keys to Success

After consuming my “bowl of Kellogg today,” I had the following epiphany:

Anchoring the mental model of the Founders’ Touch is the “pre-URL” strategy for nurturing disciplined imagination and sensemaking, minimizing coordination deficit and positioning the organization to be fit for growth.

A survey by Boston Consulting Group of about 1000 senior managers around the globe reported that “lack of coordination is the single biggest barrier to innovation.” Various studies have validated Conway’s Law which states that product design mirrors the organizational and communication structure of the organization creating a product. As a result, the communication structure is a non-obvious product design constraint. Conway’s law reversed states that you won’t be able to establish an efficient organization structure that is not supported by your system design (architecture).

Mismatches between product architecture and the organizational structure is called the coordination deficit and is positively associated with quality problems. A metric of organizational misalignment (i.e., coordination deficit) can be computed by examining the number of change orders impacting the product (service). The impact of organizational complexity on failure proneness has also been empirically validated in one of the largest studies of “commercial software—in terms of code size (> 50 Million lines of code), team sizes (several thousand), and software users (several Million).”


According to American business icon Robert Half, “The search for someone to blame is always successful.” Since it is a reliable outcome, it fosters a culture for working in silos, a low appetite for taking risks and negatively impacts organizational productivity and innovation.

The success of open source software such as Linux has confirmed that a product developed by a loosely-coupled organization is significantly more modular than the product from a tightly-coupled organization.

The first realization regarding applying Conway’s law is that all connections made in an organization from a communication perspective are not equal. The second realization is that every product will have a knowledge structure that underlies the final product.

Loosely coupled organizations are more empathetic than tightly coupled organizations. Any product (or service) is an integrated version of the knowledge structure, and the associated communication /relational functions that preceded it. The types of empathy include the following: (1) subconscious empathy (mirroring behavior), (2) emotional empathy (function of both verbal and non-verbal communication enhanced by shared presence), (3) conscious empathy (process contextual information and emotional response) and (4) global empathy (larger levels of self-awareness).

The successful delivery of a software solution is not purely a technical endeavor. Since an organization is a socio-technical system, it is vital to reframe the view of solution as consisting of a social side and a technical side.

How can a manager utilize Conway’s law and shape an empathetic organization and raise its collective intelligence? While there is no silver bullet per se, managers have an opportunity to practice empathy, lead by example and create the structure of the organization, which will then drive the structure of the product (service) in order to enhance value co-creation. In an organization with a shrinking core and an expanding periphery, governed by a number of strategic alliances, there is a need for empathetic thinkers on both sides of the supply chain during the innovation process.

In a volatile environment, strategic dissonance is a “cloud in the head” as managers struggle to make sense of conflicting information in an attempt to discern the newly emerging strategic picture. The management of strategic dissonance (actions leading or lagging the strategic intent) is a messy and unstructured process. Intel’s transformation from a memory company into a microprocessor company (a disruptive innovation) was not initiated through a structured change request process. An emotional attachment on the part of top management to the business that made the company once successful can impact corporate survival.

Astute managers often ask: Are there any early warning signals that are flying at low altitude that we’ve missed while being immersed in the daily operating details of the business? In an era of information overload and reduced attention spans, there is also a business need to increase the comprehensiveness, depth and rigor of the intellectual debate among middle and top management in order to recognize and manage strategic dissonance. Leaders have the challenge of encouraging vigorous debates, devoted to exploring different issues, independent of rank with a long-term goal of building an adaptive (learning) organization at an operational level. While capitalizing on the strategic inflection points, it is imperative to bring these debates to closure so that there is also an equal emphasis in building products that are “good enough” for emerging markets and enter a new era of profitable growth.

Sensemaking is about contextual rationality and is built out of vague questions, muddy answers, and negotiated agreements that attempt to reduce confusion. In a forest fire the old playbooks no longer work. Creativity is defined as figuring out how to use what you already know in order to go beyond what you currently think. Poor sensemaking cause an organization to be strategically adrift, distracted or capacity constrained.

sensemaking - ready for growth

According to a study by Forrester: “Alignment is dead: it is time for integrated strategic thinking with end-to-end process ownership”. Strategy is the meeting point of different logics of the various stakeholders. It is not how your strategy counts but rather how those logics are reconciled that counts. The reconciliation process is demanding and requires a higher level of organizational maturity. The engagement to deal with contrasting logics is the root of the strategic execution complexity and requires sensemaking.

Computational thinking, pioneered by Jeanette Wing (Microsoft Research), is a proven enabler for understanding the value and use of modeling techniques and transfer into a context that engineers, managers, non-engineers and customers discover new knowledge and enhance collective sensemaking.

Managing strategic dissonance requires a cadre of Activist Turnaround Managers (@ATM) whose skills and abilities include the following:

  • Acting like a leader; Thinking like a leader (@) (i.e., improvising and learning by doing with an outside in perspective)
  • Perceptual acuity
  • A growth mindset to see opportunity in uncertainty
  • The ability to see a new path forward and commit to it
  • Adeptness in managing the transition to the new path
  • Skill in making the organization steerable and agile

Let’s anchor the role of an @ATM from the rowing sport. A coxswain is a person who steers the shell and is the on-the-water coach for the crew. A swing is the hard-to-define feeling when near-perfect synchronization of motion occurs in the shell, enhancing the performance and speed.

An @ATM acts as a coxswain and orchestrates the swift replacement of a traditional order with an improvised order. Akin to the Boys in the Boat, the team remains resilient with a conscious preference for the strength of the whole rather than the versatility and resourcefulness of the parts. @ATMs are creative under pressure, precisely because they routinely act in chaotic conditions and create order out of available resources or insights while striving to achieve a nearly perfect swing.

“Harmony, rhythm and balance. There you have it. That is what life is all about.”

George Pocock

“Real life can be complicated and chaotic. Rowing is beautifully simple”

Katherine Grainger

“There’s really nobody to blame but me.”

This was Pete Carroll’s sentiment after Seahawks lost in the recent SuperBowl.

The relentless quest for Disruptive Innovations and Authentic Leadership (DIAL) is a journey. This is not the traditional electronic dialtone from yesteryear but is discovered mindfully from within (for brevity, DIALtone) and in action in a social media and mobile world.

DIALtone leaders scale for excellence and build resilient championship organizations. Mind you, this is neither a typographical or (re)branding exercise since that is below tablestakes for individuals or organizations who prefer to be “great by choice”.

What can I learn from Pete Carroll’s authenticity in order to re-calibrate my DIALtone?






I enter the office building and walk the halls of this large Fortune 50 company. Every day I see the poster with the signage “Did you had your bowl of Kellogg today?” The casual reader’s initial food for thought would regard this as an invitation to taste a brand name cereal for breakfast, which is pretty straightforward! Several reflective pauses over a span of a few months reminded me about the managerial struggle between the twin viewpoints (while also enjoying the breakfast option):

  • Does culture eat strategy for breakfast? or
  • Does strategy eat culture for breakfast?

This debate is largely unresolved when the frame of reference of an organization is hierarchical and static with a fixed mindset from the industrial revolution era with heads in the cloud. When complacency sets in, it is easy to morph into an organization where the leadership is in a state of Brownian motion and everyone agrees but nothing changes or there is a struggle to implement agreed-upon plans or become too steeped in bureaucracy or politics — ultimately losing sight of the customer. An undesirable effect is a situation called the Abilene paradox where some employees suffer action anxiety, fear of separation and existential risks.

Satya Nadella, when he was a candidate for the CEO position at Microsoft, shared the following perspective:

“What drives me every morning and what keeps me up every night is one thing: this business is not about longevity, it’s about relevance.”

Clark, D., Langley, M. and Ovide, S. Microsoft’s CEO Pick: From India To Insider, The Wall Street Journal, February 1, 2014: A 1.

    • The incorrect answer is “culture eats strategy for breakfast” or vice-versa, which causes a disconnected view of strategy and culture.
    • As Robert Burgelman of Stanford University accurately points out: “strategy without culture is powerless; but culture without strategy is aimless.” Managing the dynamic interplay of strategy and culture is an important ingredient for business relevance and leadership capability.



An organization’s relentless quest for relevance to its stakeholders is a dynamic and autonomous process as well as developing the company’s capacity to evolve and achieve corporate longevity.

growth oriented IBIS_1


The @ResponsiveOrg movement has clearly identified that “the future is impossible to predict.” The relentless pursuit of relevance is a continuous journey and requires an organization to reframe its belief system that it has to be “built to become” (not built to last) a relevant @Responsiveorg. In an omnichannel environment, employees need to become more attuned to the language of trust and inculcate a culture of customer obsession. Enterprise social networking technology such as Yammer, Jive and others are being leveraged by several organizations.

EC - ResponsiveOrg

As Is Assumptions in Traditional Organizations

      • The environment is predictable
      • The organization is a hierarchical pyramid, rigid and siloed
      • The personal capacity for control is limited to a restricted number of people
      • The rate of change on the inside exceeds the rate of change on the outside
      • I can think my way into the right action
      • Compel compliance with project plans
      • The “world is flat” and the culture is homogenous
      • Push out products and services to the marketplace based on a narrow lens of the customer (“we make, you take”)
      • The solution that works today will also work tomorrow
      • We always choose to focus more on the (PowerPoint) presentation (format, content and printout) and the documented project plan as the overarching frame of reference
      • We focus on more on hierarchy and less on the people and persuasive communication
      • We group customers into segments based on the characteristics that are shared by all customers in the segment
      • We sometimes [succumb to the temptation to] place the problem “inside” a person

Sensemaking in a @ResponsiveOrg

Responsive Org - 2

Resilient Org

ResponsiveOrg - 3

“Built to Become Relevant” Assumptions in a @ResponsiveOrg

      • The environment is unpredictable and turbulent
      • The organization is viewed as a system
      • Everything in an organization is interdependent with everything else (i.e., “people are people through other people” (Xhosa proverb) and a system does not respect organizational boundaries)
      • In an interactional view of organizations, the emergent properties at higher levels are the behaviors, relationships and results that those people generate in their interactions
      • The organization is a network, flexible and the boundary of the organization is constantly evolving
      • The rate of change on the outside exceeds the rate of change on the inside
      • I can act my way into the right thinking
      • Cut across silos and connect strategy to program execution
      • The “world is spiky”; CAGE (*) distances matter (*: Cultural, Administrative, Geographic, Economic)
      • Embrace and calibrate cultural differences to act as one unit
      • We choose to examine the marketplace and then look to deliver creatively on market opportunities (serve the needs of the market)
      • Finding solutions to customer problems become the guiding principle of the corporate architecture
      • Deliver customer-centric solutions in an iterative manner
      • Use the four silo-busting levers — coordination, cooperation, clout, capabilities — to achieve systemic integration
      • We always say “Yes, and…” and follow the customer’s path as the conversation unfolds
      • We choose to engage in persuasive conversations by focusing on the people
      • We are living in the magic of the moment and embracing alertness, flexibility and spontaneity (elements of improvisation)
      • Improvisation is flexible, exciting, natural, flexible, fresh, affirmative and collaborative
      • We always tend to look for things that make individual customers unique
      • We always communicate who we are before communicating what we want to sell
      • We focus on rich, persuasive communication and the presentation is created and brought to life when I am on the stage
      • We co-create the persuasive conversation, as a shared story, with the customer, try to spot the emerging game, and adapt the conversation to this game with a focus on achieving mutual affirmation and agreement
      • What our customer feels about his relationship with us will form the foundation of how he views our product and service offerings

Relational Coordination in a @ResponsiveOrg

As Is - Relational Coordination

Relational Coordination

@Responsiveorg Design

Achieving the @ResponsiveOrg Swing

ResponsiveOrg - 4

The individual has intelligent emotions, or sechel (a Hebrew word), when (s)he is able to see and live the interconnections of intuition, understanding and knowledge in a rigorous and consistent way.

      • What to change?
      • What to change to?
      • How to change?

The secret sauce is to make sure that enterprise social network (ESN) technology (e.g., Yammer) remains the enabler and servant of the business model and not its master.

Viewing an organization as a system and leveraging the collective insights of the Yammer discussion thread, the leadership team should (1) define the throughput operating strategy and (2) create a cadre of @Activist PMO Leaders who have an appetite for jugaad innovation and being the first mate on a sinking ship.






Growth Oriented Leadership

5 Focusing Steps

Built to Become a @ResponsiveOrg

Built to Become - Part 1

In 2013, Gartner estimated that “through 2015, 80% of enterprise social networks” (e.g, Yammer, etc) “would not achieve the intended benefits due to inadequate leadership and an overemphasis on the technology.”

It is our viewpoint that merely relying on analysts’ predictions that the adoption of enterprise social networks (ESN) will be successful is insufficient. A laisez faire attitude towards technology adoption is inadequate and does not create either a lift or transformative organizational changes. Creating “infinite” virtual hallways for conversations and stories about successful usage of Yammer (for example) that create buzz together with sustained executive sponsorship, ownership and community management play a pivotal role in shaping an responsive organization.

In this paper, Yammer is used to illustrate how enterprise social network (ESN) technology can cross the chasm and shape the culture of a @ResponsiveOrg that is built to become relevant. Ultimately business success lies at the intersection of an organization’s completeness of vision and its ability to execute that vision.

Proposition: The fusion between Yammer and sechel is a driver for an organization to become relevant and responsive


“We’ve created this perfect platform of evil,” with increasing reliance on the Internet that ties together mobile computers, social networks, cloud and websites, said David Dewalt, chief executive officer of FireEye Inc., a security software company in Milpitas, Calif. “You throw all that in a petri dish with no governance model, complete anonymity and a lot of intellectual property one click away. That creates a very interesting model for attackers to use to get into systems that we now completely rely on – our critical infrastructure, our smart grid, our transportation industry, our financial systems, our military.”

“A 2014 study by the Ponemon Institute that evaluated security-breach costs in the retail sector indicated that the cost is $105 per stolen record.”


“At the end of 2010, the Office of Management and Budget (http://whitehouse.gov/omb) established the “Cloud First” policy as part of an IT reform plan unveiled by the federal government CIO Vivek Kundra. The plan was to modernize federal IT systems on a number of fronts, including reducing the number of data centers and fixing or eliminating unsuccessful IT projects. As with the use of cloud technology in the private sector, the goal of transitioning to the cloud was to reduce costs and increase efficiency, agility and innovation.”
[…] “Other milestones, including the June 5, 2014, deadline for agencies to certify that their cloud systems with the Federal Risk and Authorization Management Program (FedRAMP) also provided difficult to meet.”


The crossing of the chasm towards “FedRAMPing” with the “Cloud First” policy is work in progress. The good news is that there is growing awareness of the emerging cybersecurity threats and vulnerabilities while acknowledging that in many instances, in both the private and public sectors, the cyber attackers are one or a few steps ahead, as evidenced by the security breaches in Target.

Higher Intent

The pursuit of better software quality is, more or less, a team sport. Achieving the desired level of quality for customer satisfaction is still work in progress. The prevailing record of security breaches among a large number of critical software- based systems demonstrates that there is a need for fresh thinking about refining the craft of software development. While Understanding the Cybersecurity Challenge is a first step, the VUCA governance model of the [cybersecurity] “petri dish” drives home the point that taming cybersecurity is a “ground war” and not simply an “air war” campaign.

The word “art” in the “Art of Computer Programming” has been used to drive home the notion that software development cannot easily be automated (i.e., requires human creativity and human assistance).

According to Brad Becker of IBM, “the whole focus of this [cognitive computing] is that technology should work for people, and not the other way around.”

We recognize that human beings are by no means perfect. Psychologists use an assortment of evidence-based treatments to help people improve themselves. Borrowing a page from “The Future of Computerized Therapy,” there are some initial promising experiments underway using Watson, IBM’s cognitive computing innovation, that is attempt to focus on who is going to be launching cyberattacks on the technology infrastructure, what their malicious intentions are, how cyberattackers work, what’s the ethnography and the cognitive psychology of the cyberattackers.

software psychology

The Programming Language F#

F# is a designed as a hybrid/functional object-oriented programming language. F# has a powerful type inference system which enables a programmer to write fewer lines of code and catch non-trivial errors at compile time. Functions are first class objects which can be combined to create new functions.

F# facilitates a paradigm for responsible programming by providing an environment fashioned for continuous validation of a set of assertions as the program is developed. F# has continued to improve its ranking in the Tiobe index.


Technical Debt

Disciplined Agile Delivery (DAD) is an IT process decision framework for delivering sophisticated agile solutions in the enterprise. Originally pioneered by Scott Ambler, “DAD fills in the gaps left by mainstream methods by providing guidance on how to effectively plan and kickstart complex projects as well as how to apply a full lifecycle approach, with lightweight milestones, effective metrics, and agile governance.”

Technical debt captures the cost that software systems endure due to poor design choices and insufficient levels of modularity. The unconscious cultural acceptance of technical debt breeds vulnerabilities and curtails the advancement of software assurance maturity. According to Martin Fowler:

“Like a financial debt, the technical debt incurs interest payments, which come in the form of the extra effort that we have to do in future development because of the quick and dirty design choice.”

Technical Debt

Software Assurance Ecosystem

“Trustworthiness requires a commitment to rigor in both software production and its verification. No soft skill, rigor has a hard edge.”


Software Assurance Ecosystem

Software Supply Chain

The non-governance of the “cybersecurity petri-dish” is a partial Glimpse of the Blindingly Obvious (GBO). We have to work together and launch a grassroots campaign with swiftness and strength to shift the odds and improve software assurance maturity in the industry. Thinking out loudly, I see a three dimensional view of this campaign strategy:

  • Accelerated adoption of a programming language such as F# (or Swift, OCaml, etc.)
  • Increasing awareness to reduce technical debt (T)
  • Building a self-organizing network for software assurance program management (Ecosystem)

Cementing F#TE and software assurance is an “all hands on deck” initiative to rapidly fortify the systems in both the public and private sectors. That said, F#TE is not meant to be silver bullet.

Code Psychotherapy

At a software testing conference, I remember reading Dr Bjorn-Freeman Benson’s use the term “code psychotherapy” to increase the attention span for the software developer to “listen to code screams.” A code scream is a behavioral indication of a deeper problem in the system. The minority opinion is that the craft of programming should include code psychotherapy. We need to mindfully reflect about the software developer and team collaboration more broadly and deeply (*), besides analyzing the technical details of the bug triage. (* : a mile long and a mile deep)

I will readily agree that code psychotherapy might be somewhat tangential to this discussion. In the spirit of thinking out loudly, perhaps there is an outside chance that we can leverage the ability for Watson to get rapidly trained in a (non-algorithmic) domain such as therapy and discover hidden, non-obvious patterns that will serve as heuristics for preventing sophisticated cyberattacks. Furthermore let’s consider the following questions:

  • What can developers learn from psychotherapy and incorporate the insights in the software engineering process?
  • We need to build a growing cadre of software developers who can play a variety of roles — the “good guy”, the “bad guy”, the “naive user”, etc to improve the dialogue between team members and engineer software that is trustworthy and robust (which may seem lofty goals today). This means going beyond the (passive) man-machine interface, walk in the other person’s shoes and co-create beautiful code that is verifiable.
  • With the growing attachment toward devices, perhaps there is room for psychotherapy body of knowlege to break new ground, forge collaboration with software developers, and contribute towards the interpretation of “code psychotherapy.”

Software Assurance Program Management

Below is a sketch of the mental model for software assurance program management
Cyber PgM_1

Cyber PgM_2

Cyber PgM_3

Cyber PgM_4

Cyber PgM_5

Cyber PgM_6

My hunch is that the F#TE is an art of turning software engineering activity into thoughtful, purposive action. In military parlance, this is a strategy of directed opportunism. In this context, the twin goals are to make software more humane while also improving the software assurance maturity.

(This is a living blog that is work in progress)