Archive

Rightshifting

We’re All In This Together

Creating, sustaining and continually improving effective ways of New Product Development requires the efforts, commitment and active participation of everyone in the organisation. It’s not something that can be delegated, offloaded or left to just one department, function or silo.

In my previous post, I mention a number of constraints which typically prevent an organisation from having an effective product development approach. If you take a look at that post, you may begin to see how these particular constraints are organisation-wide. And how reducing or eliminating them requires the active participation of everyone, from the CEO, through function heads, to the front-line workers:

Whole Products means specialists (sales people, marketeers, finance, operations and customer service specialists, etc.) from across the organisation are needed for each and every new product development.

SBCE means changes to accounting practices, personnel recruitment, allocation and training (HR), as well as the understanding and involvement of senior executives in investment and strategy decisions for the longer term.

Flow means reorganising and smoothing the internal operations (explicit or implicit value streams, customer journeys, etc.) which run through the daily business as usual of the whole organisation.

Transitioning from a projects-based approach to New Product Development to something more effective (such as FlowChain) requires the overhaul and replacement of many policies, procedures and expectations across the organisation.

Cognitive Function asks us to learn about topics – psychology, neuroscience, sociology, anthropology – with which we may have had little experience before. And to prevent just one group (NPD) getting wildly out of step with the rest of the organisation, most people coming into contact with these new ideas and ways of relating to each other will need to at least understand what’s going on.

A clearly-articulated and jointly-created product development doctrine offers a means to encourage debate, and understanding, across the whole organisation.

Summary

Each of the above changes requires new understandings and new behaviours – including e.g. cooperation, collaboration, trust, and support – from every department in the organisation. Existing incentives, goals and rewards schemes tailored to individual performance and local (function-specific) results will directly oppose these new behaviours, so must be replaced with schemes designed to foster the new behaviours. Old assumptions and power structures, again supporting of traditional ways of doing things, must be overhauled to become more relevant to our new, more effective ways of New Product Development.

Ultimately, we will find ourselves asking the question “Is it worth it? Does an amazing uplift in our organisation’s ability to release new products and product updates with:

  • fewer delays and overruns
  • higher quality
  • lower cost
  • better product-market fit

warrant the root-and-branch changes necessary for success? Are we in business for the long-haul? And do we each want to be proud to have played our part in creating something truly awesome?

– Bob

 

Constraints On Effective Product Development

Bottlenecks

What company wouldn’t love to have its product development efforts be more effective? Be able to release new products and product updates with fewer delays and overruns, with higher quality and at lower cost? And be sure of the product-market fit, too?

Many companies spend inordinate amounts of time, effort and management attention on just this. And yet reap little in the way of benefits from that investment.

Why is this? What are the blockers (constraints) frustrating these ambitions?

I see the same patterns time after time. Patterns that stymie effective practices and lock in ineffective approaches and poor results. Here’s some of the more common ones:

Whole Products

Few companies are able to reap the benefits of a Whole Product approach to New Product Development. The constraint here is the ability of people and teams from different functional areas across the business to come together (literally and figuratively) for the duration of a product’s development. Toyota have long eliminated this constraint through their Obeya concept, and unique matrix structure.

Set-Based Concurrent Engineering

Most companies suffer unpredicted (yet predictable) overruns and delays in the development of many (most) of their products. One key constraint in play here is the lack of options when a particular component or subsystem – on the product’s critical path – proves problematic. SBCE eliminates this constraint by purposely providing options at every stage of the product’s development. At each “integration point” during a development, the most promising (and always 100% viable) option is selected. SBCE as a solution is predicated on the organisation’s ability to save its learning on and investment in the “pruned” options, for future products or upgrades.

Flow

Organising around flow offers a number of benefits, not least reduced costs and delays. Many companies attempt to organise traditionally – around skills and functional silos. The traditional approach chokes flow and reduces the effectiveness of product development.

NoProjects

The almost universal use of projects as the containers for product development work again constrains our efforts to the relatively ineffective end of the spectrum. The many drawbacks of the “projects” concept are well-known. Yet the constraint here is no so much projects themselves, but the way in which an organisation’s policies, procedures and assumptions lock in the idea of projects. Moving to a non-project approach, such as FlowChain, is a political and social challenge of the first order.

Cognitive Function

Many companies understand the issues of engagement and the need for innovation. Fewer understand the nature of collaborative knowledge work, its fundamentally differences from more traditional forms of work, and the need to approach it with a fundamentally different set of assumptions. Assumptions absent which, effective product development – as the archetype of collaborative knowledge work – is impossible. The traditional assumptions at the heart of traditional management of traditional organisations are the key constraint here. These assumptions prevent us realising the high levels of employee engagement, the innovation culture and the high levels of cognitive function so necessary for effective product development.

Doctrine

Few organisations have a clearly articulated and debated doctrine describing their approach to product development. This absence of clarity constrains the whole organisation, with folks constantly wondering what they should be doing, why they’re doing it, and how everyone’s efforts fit together.

Summary

The above are just a few of the key constraints condemning product development efforts in most organisations to the ghetto of high costs, poor quality and interminable delays. None of these constrains are simple or easy to tackle. But identifying them is the first step to dealing with them. What constraints are limiting your product development effectiveness?

– Bob

Further Reading

Product Development for the Lean Enterprise ~ Michael N. Kennedy
It’s Not Luck ~ Eliyahu M. Goldratt
The Principles of Product Development Flow ~ Donald G. Reinertsen

After Agile

AfterAgileBlue

In recent workshops and conferences I’ve been inviting people to explore the question of “After Agile, DevOps, what now?”

There’s a line of argument, and of exploration, that goes something like this:

Idealised Design

What does the Ideal software development organisation / business look like and work like? If our existing organisation / company / business was totally destroyed last night, what would we choose today in rebuilding it? What are the key concepts and principles that we would choose to focus on in creating our ideal organisation? Cf. Idealised Design, Russell L. Ackoff.

The Role of Mindset

We may find “culture” or “mindset” amongst our idealised key concepts. By which I mean organisational mindset (Cf. Rightshifting and the Marshall Model). If so, then we may want to discover means to “shift” our present organisational mindset towards our ideal model.

Organisational Psychotherapy

How to shift an organisation’s mindset? I propose Organisational Psychotherapy as a means for approaching that in a structured way. What are the issues involves in such a shift? What does therapy have to offer? What does therapy feel like? And what kinds of therapy might suit?

If you’d like to explore these ideas in your own organisation and context, via a workshop or similar, I’d be happy to oblige. Please get in touch.

– Bob

Rightshifting In A Nutshell

rnut1

Folks’ different perspectives can seem very alien to each other.

Whilst in Sweden and Finland last week, I twice had the occasion to present this short (around ten minutes) set of slides, both times in the context of “After Agile”, explaining the very basics of Rightshifting and the Marshall Model. My friend Magnus suggested I turn them into a blog post with some supporting narrative. So here it is.

After Agile, DevOps. What Now?

The Agile approach to software and product development has been around for something like fifteen years now. Its roots go back at least another fifteen years before that. In all that time, more and more folks have tried it out, and more and more of those folks have found it wanting in some degree. This presentation explains where Agile fits in the broader scope of organisation-wide effectiveness, and suggests what needs to change to move on from the Agile approach.

Effectiveness vs Efficiency

Rightshifting observes that most organisations are much less effective than they believe themselves to be, and much less effective than they could be. Let’s not confuse effectiveness with efficiency:

Effectiveness

Doing the right thing.
(creating & deploying value)

Efficiency

Doing the thing right.
(maximising the gain, minimising the cost)

Normal Distribution Assumed

In the chart below, we see a distribution of all the world’s knowledge-work organisations, with respect to their relative effectiveness (horizontal axis). Most folks assume that it’s a normal bell-curve distribution, with some few ineffective organisations (to the left), some few highly-effective organisations (to the right), and the bulk of organisations somewhere in the “average” effectiveness centre ground:

rnut2

What most folks assume

In actuality, though, the distribution is highly skewed and looks like this:

rnut3

In actuality

Here (above) we see that fully half of all organisations have a relative effectiveness of less than one (the median), while there’s a long thin tail of increasingly effective organisations stretching out to the right (hence, “Rightshifting”). The most effective (rightmost) organisations are something like 5 times (500%!) more effective than the average (median).

Aside: For those interested in evidence, ISBSG data and NPS data correlate well to this distribution.

Waste (Non-Value Add) And Productivity

Overlaying lines for waste (a.k.a. muda: non-value-adding activities) and productivity on the above chart illustrates the consequences of such ineffectiveness. Median organisations for example are wasting around 75-80% of their time, effort, money and resources on doing things that add zero value from the perspective of any stakeholder:

rnut4

Where Does Agile Fit?

So, how effective are those organisations that are using Agile (as intended)? Let’s look at where Agile fits on this chart:

rnut5

As we can see, organisations using the Agile approach span the range circa 1.2 through 2.0. And that’s for organisations in which Agile being done well. (There’s not much point talking about AINO – Agile in Name Only. That buys us nothing in the effectiveness stakes.) The exact position in this range of Agile’s effectiveness depends, in part, on how well the rest of the organisation is aligned to the Agile practices in e.g. the development, ops or DevOps groups within the organisation. Closer alignment = a more effective organisation as a whole.

From the above chart, we can see there’s a whole swathe of effectiveness (from circa 2.0 rightwards) not open to us through the application of the Agile approach. Organisations must find other approaches to access these higher levels of organisational effectiveness.

Explaining Effectiveness

So just what is it that accounts for any given organisation’s position on the Rightshifting Chart? What do the highly ineffective organisations to the left do differently from the average? What do the highly effective (Rightshifted) organisations do differently from the rest? What explains any and every organisation’s effectiveness? It’s very, very simple:

Effectiveness = f(Collective mindset)

That’s to say, any organisation’s effectiveness is a function of its collective, organisational mindset. A function of the assumptions and beliefs it holds in common about work, and how work should work. We can characterise the spectrum of organisation mindsets (a.k.a. memeplexes) into four basic categories: Adhoc, Analytic, Synergistic and Chaordic. This forms the essence of the Marshall Model.

The Adhoc Mindset

Least effective of all the mindsets is the Adhoc mindset. This is characterised by a near-complete absence of organisational structures and disciplines.

rnut6

Adhoc-minded organisations have no managers, no processes, no standards and no accepted ways of doing things. Every day is more or less a new day, a clean slate, as far as running the business is concerned. In these organisations, the value of discipline has not yet been discovered. I like to think of these organisations in terms of the typical Mom-and-Pop family business.

Some of these organisations, of course – if they, for example, find a profitable niche in which to do their business – can grow despite their ineffectiveness. And with that growth, sooner or later, comes the realisation of the need for some discipline. At this time these organisations will likely start appointing managers, splitting the business into departments (silos) and thereby begin transitioning into the next mindset.

The Analytic Mindset

More effective than the Adhoc-minded organisations, those organisations with an Analytic mindset are typified by the corporates, large and small, that we have come to know and love(?) over the past one hundred years or so.

rnut7

Central to the Analytic mindset is the belief that organisations are machines, and that just as with machines, if they are broken into parts, with each part performing well, then the whole will perform well. As Russell L. Ackoff (source for this sense of the term “analytic”) points out, this is a fallacy, although one very widely held in businesses everywhere.

Other common beliefs in the Analytic mindset include:

  • Theory X (Douglas McGregor) – people are idle and shiftless and have to be beaten with a stick in order to get any work out of them.
  • Extrinsic motivators such as perk and bonuses enhance performance (demonstrably false in knowledge-work).
  • Managers do the thinking and workers do the doing.
  • Check your humanity, emotions and passion at the door.

Eventually, a few organisations in pursuit of effectiveness may stumble – for it’s rarely intentional – out of the Analytic mindset and into the next mindset – Synergistic.

The Synergistic Mindset

The real uplift in effectiveness starts with an organisation’s transition into the Synergistic mindset. We’ve been hearing about some exemplars of this mindset for years (W.L. Gore, Semco) and others, more recently (Morning Star, Buurtzorg, et al.).

rnut8

At the heart (sic) of the Synergistic mindset is the belief that organisations are much more like organisms than machines. Complex adaptive social systems rather than complicated yet predictable “mechanical” systems. The term “Synergistic” comes from R. Buckminster Fuller, and his statement that the performance of synergistic (synergetic) systems can never be predicted from an examination of their parts considered separately. This is not a comfortable concept for many of those more traditional business people.

Other common beliefs in the Synergistic mindset include:

  • Theory Y (Douglas MgGregor) – people are keen to do a good job, if only they have the opportunity.
  • Intrinsic motivation enhances performance (demonstrably true in knowledge-work).
  • The people doing the work must decide how the work works.
  • Alignment – and effectiveness – is a consequence of a shared, common purpose.
  • Management  – the social technology invented around one hundred years ago – is dead.
  • Bring your humanity, emotions and passion with you into work, every day.

Eventually, a few organisations in pursuit of effectiveness may stumble – for, again, it’s rarely intentional – out of the Synergistic mindset and into the fourth and most effective organisational mindset – Chaordic.

The Chaordic Mindset

Most effective of all are those very few organisations embracing the Chaordic mindset.

rnut9

Key to the Chaordic mindset is the continual, active, systematic searching for new business opportunities. The term “Chaordic” comes from Dee Hock – the originator of the Visa organisation back in the 1960’s.

The Chaordic mindset inherits from the Synergistic, with some additional common beliefs, including:

  • Dynamic market sweet spots – tracking and exploiting the ever-changing high-margin sweet spots in the market.
  • Instability – always teetering on the cusp between stability (order) and chaos (disorder).
  • Inevitable collapse – occasionally, the organisation will collapse into (temporary) chaos and disorder.

Transitions

Even more interesting than the four mindsets, though, are the three transitions (shown in orange, below). Each transition is an enormous wrench for most organisations.

rnut10

The Adhoc to Analytic transition is relatively easy, going with the flow, as it were, in that wider society and most people in work mostly believe organisations should be run along the lines suggested by the Analytic mindset. Much more challenging are the other two transitions, being very counter-intuitive for most people.

Where Does Agile Fit In Terms Of Mindsets?

So, where does Agile fit amongst these four mindsets?

rnut11

Here we can see how Agile straddles the Analytic-Synergistic transition. This explains just why sustainable Agile adoption is so difficult for most organisations. If part of the organisation makes the transition and the remaining parts do not, then Organisational Cognitive Dissonance ensues, and its eventual, inevitable resolution rarely results in the whole organisation shifting its mindset. Much more likely is either a) the now-synergistic part is dragged back, kicking and screaming, into the (old) Analytic ways of doing things or b) the (newly) synergistic folks find they cannot or will not go back, and thus quickly quit for pastures new.

From the above chart we can also see what is to come After Agile: More Synergistic thinking, more of an approach embracing the beliefs of the Synergistic mindset, and for some brave few, Chaordism.

– Bob

 

Collaborative Change

“The only thing of real importance that people in business do is to create and manage culture.”

~ Edgar Schein (adapted)

If we believe in the Myth of Leadership, we may leave it up to “the leaders” to lead change. In collaborative organisations, where leadership is more distributed and diffuse, this can be a recipe for frustration, inaction and diffusion of effort.

For some clues on how to procede with collaborative change, how about we take a look at Schein’s culture change actions though the lens of fellowship:

Primary Actions

Attention

To what issues, and topics do we wish to pay our (limited) attention? What do we believe is most important? The present or the future? The business or the people? Revenues or growth? The exclusive needs of customers, shareholders, executives or employers, or some balance? The way the work works, or getting work done? Joy or wages? And etc. A collaborative organisation that does not pay attention to where it’s focussing its attention will find itself uselessly spinning its wheels.

Further, what are the limits to our seeing? How can we expand our horizons such that we begin to see things hitherto invisible and unknown to us?

“We do not think and talk about what we see; we see what we are able to think and talk about.”

~ Schein

Reactions To Crises

In times of crisis, how do we react? Do we hunker down and each look after ourselves, or do we rally round and look after each other? What do our reactions tell us about who we are? Is that who we aspire to be?

Role Modelling

People listen to others, and more significantly, carefully watch what they do. In any mismatch between someone’s words and their deeds, the actions generally say more than the words. “Actions speak louder…”.

People also tend to assume that the behaviours they commonly see in others are the accepted way to behave, and thus tend to conform to those behaviours. Are those the kinds of behaviours helpful? Will they lead towards the future we seek?

Allocation Of Rewards

When we’re trying to encourage collaboration, rewarding individuals might seem… discongruent?

Inclusion And Exclusion

Inclusion and exclusion – of people into or from working groups, teams, tasks, etc. – is critical for choosing who does what, and also often seen as a form of reward or punishment. Collaborative groups who lose sight of the kinds of changes they’re jointly trying to effect, and of the kinds of behaviours they’re jointly wanting to strengthen, often forget about the far-reaching implications of inclusion and exclusion decisions.

Secondary Actions

Design Of Organisational Structure

Conway’s Law (as applied to organisational systems) echoes the more familiar ‘function follows form’, and ‘first we create our organisations and then they create us’. The “shape” of our organization will have a subtle effect on how we operate. Organisations seeking to become more collaborative benefit from structure(s) which encourage and enable that collaboration.

Design Of Systems and Procedures

The systems, policies, processes and procedures by which an organisation is run have a wide effect on how people think. Such systems include budgeting, information systems, performance reviews and people-development activities. Deliberate design of these can ensure alignment with collaboration objectives.

Design Of Facilities

The layout of offices, meeting rooms, etc. often reflects subconsciously the values of an organization, both in terms of who sits near whom, and also in the differentiation in benefits that individuals are given. Effective collaboration does not necessarily require strict equality, but have you thought about the implications of these things?

Stories, Legends and Myths

The stories that people tell and re-tell in organisations typically reflect the values and beliefs of the culture. Hence, changing the stories will tend to change the culture. This is particularly powerful as it is spread at the individual level and hence has grass-roots support and credibility. How we choose to describe our histories and events have a profound effect on the emergence of a particular kind of culture. Creating and telling stories together, explicitly, can help us build the kind of collaborative culture we seek.

Formal statements

Formal statements by “the organisation”, although not always as credible as grass-roots whisperings, are the public face of the organisation – both internally and externally. Who gets to write and present these statements? Some individual(s) – or a group/groups?

– Bob

The Antimatter Model

spiral

For me, the power of any model lies in its predictive ability – that’s to say, in its ability to help us predict what might happen when we intervene in the domains, or systems, to which it applies.

“Essentially, all models are wrong, but some are useful.”

~ George Box

For example, the Dreyfus Model helps us predict the impact and outcomes of training initiatives and interventions; the Marshall Model helps us predict the outcomes of our organisational change efforts and interventions.

The Antimatter Principle

The Antimatter Principle is a principle, not a model.

Principle: a fundamental truth or proposition that serves as the foundation for a system of belief or behaviour or for a chain of reasoning.”

The Antimatter Principle proposes a single course of action (namely, attending to folks’ needs) is sufficient as a means to create a climate – or environment – that will lead to groups, teams and entire organisations becoming more effective at collaborative knowledge work.

The Antimatter Transformation Model

Confusingly perhaps (and my apologies for that) I wrote recently about the Antimatter Transformation Model. I’m rueing my calling it a model at all now, seeing as how it seems ill-suited to be labelled as such (having no real predictive element). Let’s set that aside and get on…

The Antimatter Model

In this post I present the Antimatter Model. This model serves to improve our understanding of how the Antimatter Principle works, to help share that understanding with others, and to allow us to predict the outcomes from applying the Antimatter Principle within e.g. collaborative knowledge work organisations.

Virtuous Spirals

The Antimatter Principle basically proposes a collection of positive feedback loops, akin to Peter Senge’s “Virtuous Spiral” systems archetype.

Virtuous Spiral 1

As people attend to others’ needs, they find joy in doing so. This is a typical human response to helping others, being part of our innate nature as social animals (cf Lieberman). This feeling of joy tends to encourage these same people to invest more effort into attending to others’ needs, increasing both the frequency and reach of such activities. And by doing it more often, they are likely to become more practiced, and thus more capable (skilful).

Virtuous Spiral 2

As those other folks see their needs attended to, they will likely feel an increased sense of wellbeing. Not least because they sense people, and the “organisation” more generally, cares for them. This is compounded by a further increase in their sensation of wellbeing as they see their needs actually met. This increased sense of wellbeing also contributes to an increased sense of community, and positive feeling about their social relationships – another key driver for us human social animals.

Virtuous Spiral 3

And as these other folks feel their wellbeing and social connections improve, our strong and innate sense of fairness raises individual cognitive dissonance levels, such that some might choose to reciprocate and attend to the needs of others, in turn. In other words, folks sense they are on the receiving end of something beneficial, and find themselves wishing to see others similarly blessed. And with the Antimatter Principle, they are automatically well-placed to act on this social imperative.

Virtuous Spiral 4

Further, the same sense of dissonance may encourage people to attend more closely, perhaps for the first time, to their own needs.

And the Bottom Line

And, finally, beyond the dynamics of the Virtuous Spirals improving the climate/environment of the workplace and organisation, actually meeting folks’ needs (customers, managers, shareholders, employees, wider society) with effective products and services is what successful business is all about.

Predicted Outcomes

The Antimatter Model predicts the following beneficial outcomes

  • Folks discovering pleasure and delight in seeing others’ needs met – we often call this sensation “joy”.
  • Improved interpersonal relationships and social cohesion – we often call this “community”.
  • Improved self-knowledge and self-image.
  • Reduced distress.
  • Increased eustress.
  • A progressively more and more effective organisation, business or company.
  • Reducing levels of waste and increasing flow of value (i.e. needs being met).
  • Increasing throughput (revenues), reducing costs and improving profits (trends).

Risks

I have yet to write about the risks implicit in the Antimatter Model. These include:

  • Sentimentality
  • Indifference
  • Posturing
  • Hubris
  • Jealousy
  • Vigilantism

I will be writing about these risks – and ways to mitigate them – in a future post.

Summary

As folks start to attend to folks’ needs, social cohesion and the sense of community rises, folks find joy in attending to others’ needs – and in seeing others’ needs attended-to. Those actively and joyfully engaged want to do more, and those not (yet) actively engaged become curious and then, often, keen to participate themselves. Thus more people choose to engage, more needs get met, social relationships improve, and yet more folks may choose to participate. And so on.

And all the while, the needs of all involved – including those of the business – are getting better and better (more effectively) met, too.

– Bob

Further Reading

Social: How Our Brains Are Wired To Connect – Matthew Lieberman
The Neuroscience of Human Relationships ~ Louis Cozolino
Social Physics: How Good Ideas Spread ~ Alex Pentland

The Agile Enterprise Is A Thing But Not THE Thing

mindsets

A Thing

Many proponents of Agile in the field of software development suggest that the whole enterprise (company, firm, organisation, business) could benefit from adopting Agile – i.e. the principles set out in the Agile Manifesto – across the board. I suspect that most of these proponents have little to no clue about the realities of running a business.

For sure, the idea of a whole business – including e.g. Sales, Legal, HR, Finance, and more again – becoming “agile” sounds attractive. The fourth item of the Agile Manifesto seems most relevant here:

“[We have come to value] Responding to change over following a plan.”

In today’s business climate, who would not wish for a business that could better respond to the vicissitudes of the market, technology and people? That could better adapt its plans in the face of change? That could duck, dive and spin on a dime to keep in the “sweet spot” of maximum customer satisfaction, sales, revenues, costs, quality and profits?

Agility with a small “a” – and the agile enterprise – that’s a thing.

THE Thing

Few indeed are the Agile adoptions – even in the limited confines of the software development business unit – that succeed in a sustainable way. Jeff Sutherland, one of the originators of Scrum, suggests that less than 25% of Scrum adoptions succeed, longer term.

Aside: I use the term “succeed” here to mean “realise the benefits or beneficial outcomes that people were seeking”.

To understand why the Agile Enterprise is not THE thing, we might do well to understand the implications of adopting e.g. Agile principles.

I have written much about this here in this blog, but to sum up:

Successfully and sustainably adopting Agile ways of working means adopting Agile ways of thinking and being – ways diametrically at odds with the ways of thinking and being typically seen in most organisations.

I describe those ways of thinking and being – ways congruent with Agile – as “Synergistic”, and those ways typical of most organisations as “Analytic”.

These two ways of thinking and being CANNOT exist for long in the same organisation. Sooner or later (with a half-life of circa nine months) something has to give. Most often, it’s the Agile ways of thinking and being that have to go, not least because those who hold the whip hand (shareholders, senior management, the Core Group) cleave so firmly to the Analytic mindset.

Synergism – that’s THE thing.

Hints

Whilst Agile hints coquettishly at the Synergistic, Agile memes comprise a very small subset of the Synergistic memeplex. For example, Synergism as a memeplex (a.k.a. mindsetcontains many memes concerning people and their relationships with each other, memes barely hinted at in the Agile memes.

The Synergistic Enterprise

So when we see the advantages of Agile and wish to see those advantages conferred on our long-suffering businesses (and shared with their long-suffering people) we may leap to labelling that “the Agile Enterprise”, but in fact we’re really talking and thinking about something else – the Synergistic Enterprise.

Why does what we call it matter at all? Well, for me it matters because attempting an Agile adoption across the Enterprise, couched in those terms, is bound to fail. Whereas, if we understand what we’re actually trying to achieve – a wholesale adoption of the Synergistic mindset – we may just have a chance of pulling it off.

– Bob

Further Reading

Rightshifting Transitions (Part 2 – Analytic to Synergistic) ~ FlowchainSensei

Follow

Get every new post delivered to your Inbox.

Join 12,797 other followers

%d bloggers like this: