Strategy and Tactics – Two Sides of the Same Coin

Mike correctly pointed out in his comment to my last post, Strategy By Any Other Name, that I didn’t address the difference between strategy and tactics. Well let’s take a look now. First, I think there are really two questions here. One is “What is the difference between strategy and tactics.” and the other is […]

Back to the Future with The Theory of Constraints

In so many situations today I find business people are much more savvy with IT than they used to be only 10 years ago. And while this is a fantastic advance, the result is they are MUCH more likely to dictate the solution right from the outset. I marvel at how very senior business executives are now so conversant with the specifics of application architecture, particular packages they wish to use and Cloud deployment architecture. But of course this level of direction frequently facilitates rapid action, but without full and thorough understanding of the business issues.

We know that business people should be focused on the inherent business architecture, surfacing the opportunities for common concepts and business services, business platforms, product lines and channels; identifying where standardization and differentiation is appropriate, and where partitions are relevant, all in context with the business and market  model. Get this level of architecture right and you have the chance of delivering an agile business. Get it wrong and you are in instant legacy territory!

With this interesting problem in mind I browsed my bookshelves and came across Eli Goldratt and the Theory of Constraints (ToC). There was an AH HA moment! I first came across Goldratt nearly 30 years ago; I went to one of his lectures in London and have read many of his books, but I haven’t used the ideas for a good while.

The starting point is to develop a Current Reality Tree, initially a list and then a dependency hierarchy of Undesirable Effects (UDEs) (see redacted example below). This is used to determine the root problem and then to develop a Future Reality Tree with Desired Effects (DEs). And the techniques naturally guide the user to focus on the HOW, and separate out the WHAT. In the process I insert an Ishikawa (Fishbone) diagram between the CRT and the FRT. It’s really useful in separating Domain based issues into (people, process, technology . . . ) clusters and also teasing out the root problem.

I would be interested to hear from others whether they are using ToC, or indeed if there are other techniques that do a similar job.

.  

The Open Group Certified Architect (Open CA) Program Transformed My Career

By Bala Prasad Peddigari, Tata Consultancy Services Limited Learning has been a continuous journey for me throughout my career, but certification in TOGAF® truly benchmarked my knowledge and Open CA qualified my capability as a practitioner. Open CA not only tested my skills as a practitioner, but also gave me valuable recognition and respect as … … Continue reading

From Business Design to Business Change (#3) – The Learning Circle

<p><span class=”s1″>Let us suppose you are to consult in the redesign of the ‘Incident Management’ process in a business-IT environment. This is not necessarily rocket science. But what do you do when the managers of the six different teams involved in the process have overlapping views on the roles of their teams? How do you avoid the pitfall of endless discussions on roles and responsibilities between teams and business units? And how do you take advantage of the involvement of the employees to arrive at a workable and acceptable solution?</span></p><p><span class=”s1″>The case I write about in this blog is situated in a governmental service organization, 15k+ employees, where a restructuring of the organization required this cross-business unit redesign. This case represents a nice example of how I recently encountered the <a href=”http://www.bizzdesign.com/blog/from-business-design-to-business-change-1-the-content-paradox/” target=”_self”>content paradox</a>.</span></p><p><span style=”font-size: 11px; line-height: 19px;”><img alt=”” class=”right” longdesc=”Improvisation on television” src=”http://www.bizzdesign.com/assets/BlogDocuments-2/20130515_From-Business-Design-to-Business-Change-3/Business-design-business-change-improvisation_large.jpg” style=”width: 180px; height: 124px; float: right;” title=”Improvisation. Dutch TV show the Lama’s”/>A traditional design approach would start out by trying to define a design scope and process requirements by interviewing stakeholders. We assumed this approach would be a one-way ticket to views a world apart. We looked at other options and our good experiences with </span><a href=”http://www.bizzdesign.com/blog/business-games-1-of-4-why-and-when-of-gaming/” style=”font-size: 11px; line-height: 19px;” target=”_self”>serious gaming</a><span style=”font-size: 11px; line-height: 19px;”> </span><span style=”font-size: 11px; line-height: 19px;”>came to mind. What I personally like about it is that participants are caught in the moment and have to improvise. Sensible decisions and behaviour just arise. We used this effect to kick-start our design process. We organised what we called a Learning Circle with participants from each team.</span></p><p> </p><h2>The Learning Circle</h2><p><span class=”s1″>We planned a full day for the Learning Circle workshop. We had one of the team managers as the sponsor for our approach. He asked all other team managers to send two or three employees to participate, in total about fifteen people. The participants had no idea what to expect and came without preparation. The workshop had three parts:</span></p><ul><li class=”li1″><span class=”s2″>The first part of the session was the <b>gaming</b>-part. We started from scratch with a simulation, as if the future process was already there. The idea was to just see what would happen, to experiment and to harvest the issues that would naturally arise.</span></li> <li class=”li1″><span class=”s2″>T</span><span class=”s2″>he second part of the session was the <b>dialogue</b>-part. For every issue teams were asked to share their view with the other teams. No discussion, just sharing of truths.</span></li> <li class=”li1″>T<span class=”s2″>he third part of the session was the <b>solution</b>-part. The participants were split into two groups with all teams represented in both groups. The groups were asked to come up with a draft proposal addressing as much issues as possible. Issues could also be put in the ‘for management to decide’ box.</span></li></ul><h2 class=”li1″><span class=”s2″>​The gaming part</span></h2><p><span class=”s1″><img alt=”” class=”right” longdesc=”Learning Circle” src=”http://www.bizzdesign.com/assets/BlogDocuments-2/20130515_From-Business-Design-to-Business-Change-3/Learning-Circle-workshop-set-up_large.png” style=”width: 171px; height: 180px; float: right;” title=”Learning Circle workshop set-up”/>The participants were seated into a half circle, grouped in teams, facing a number of flip over sheets put on the wall. We asked the participants to imagine as if the process to-be was already in place and they were performing their future roles already – whatever that might be. In case of doubt we asked them to act the way they would find most logical or sensible for the organisation as a whole and its (internal) customers.</span></p><p><span class=”s1″>We triggered the incident process by presenting typical incident calls and handing over a marker pen to the team that first indicated they would receive it. The rules of the game were simple:</span></p><ol><li><span class=”s1″>​</span><span class=”s1″>The team with the marker pen decides how they act themselves and which team they trigger next by handing over the marker pen.</span></li> <li><span class=”s1″>The team with the marker pen is allowed to discuss among themselves what to do. The other teams are to remain silent</span></li> <li><span class=”s1″>The team with the marker pen writes down on the flip over sheet which activities they perform (if any!) and what result or information they pass on to which team</span></li> <li><span class=”s1″>All other participants are allowed at any time to come forward, in utter silence, with a sticky note with their initials. They can place it on the flip over sheet on the spot where they want to raise an issue (or question).</span></li></ol><p><span class=”s1″>​<img alt=”” class=”left” longdesc=”The power of silence” src=”http://www.bizzdesign.com/assets/BlogDocuments-2/20130515_From-Business-Design-to-Business-Change-3/Learning-circle-the-silence-rule_medium.gif” style=”float: left; width: 120px; height: 113px;” title=”The best and most fun part was the silence rule”/>The harvest of the gaming part was rich. A process developed spontaneously and at the same time the astonishing number of 28 issues were already raised during the handling of the first incident alone – but no panic at all. The best and most fun part was the silence rule. With some small interventions from our side and some grinning of team members even the most control-freaky participants were able to zip it, just let it happen and use their – silent – sticky notes.</span></p><p> </p><h2><span class=”s1″>The dialogue and solution part</span></h2><p class=”p1″><span class=”s1″>After the game we saw curious and smiling faces going for the coffee break. With the notion that each participant would get their turn on expressing their views the atmosphere had become open and calm. After the break issue per issue was addressed. Participants were amazingly patient with each other and interruptions were rare. The result was interesting: without making agreements it was clear that most issues could be resolved. The role of one team appeared to be almost completely omitted in the simulation of the process. Yet the dialogue part gave this team a great platform to position with their tasks themselves in a way that was logical and sensible for the other teams. </span>After sharing six separate truths in a dialogue, the two groups had a good go at resolving the issues and their first ideas were presented. </p><h2 class=”p1″>Follow-up of the Learning Circle</h2><p class=”p1″><span class=”s1″>With just a few issues to be resolved, the overall result was a great kick-start. It brought about a good energy among participants who brought this feeling across to their respective team managers. Next we, as independent consultants, formulated a number of recommendations on the redesign for management. We based this on the results of the Learning Circle. We organised a management meeting to have them decide on these recommendations. We asked the participants to prepare this meeting with their team manager.  The managers were happy that a lot of issues were already tackled by their employees. The open energy was also present on this table. It took management two meetings to resolve all redesign issues and start the implementation. </span></p><p class=”p1″><img alt=”” class=”left” longdesc=”How to bring these different truths together” src=”http://www.bizzdesign.com/assets/BlogDocuments-2/20130515_From-Business-Design-to-Business-Change-3/How-to-bring-different-truths-together_700x184.png” style=”width: 700px; height: 184px; float: left;” title=”All in all it was not about “which team is right?”, but more about “how to bring these different truths together?””/></p><h2 class=”p1″>In conclusion</h2><p class=”p1″><span class=”s1″>In a traditional design approach it is good practice to test a business process design when it is finished in a simulation workshop with employees. In the case above we turned it around! We used the Learning Circle as an open experiment to speed up the design process with a lot of parties involved. Each participant brought along their own mix of ideas, stakes, insecurity on the outcome, personal preferences and historical context. Still, we noticed everyone was in his or her own way committed to deliver a good service in the end. All in all it was not about “which team is right?”, but more about “how to bring these different truths together?”.</span></p>

Categories Uncategorized

Dinner and a Little Disruption

I attended Forrester’s Annual Forum For CIO, EA, Infrastructure & Ops, Security & Risk, and Sourcing Professionals in Washington DC a few weeks ago and had the opportunity to have dinner with Forrester CEO, George Colony. Colony emphasized his message about Digital Disruption and the speed at which we must adapt to change.

During his keynote address he showed the two pictures you see here to

How to build a Roadmap – Define End State

This post will provide a little more exposition and insight into one method I have found useful in practice for quickly defining desired end states. Done well, it can provide an honest and objective look to successfully understand where we truly want to be as an organization and face the uncomfortable truth in some cases where we need to improve.

The Open Group Sydney – My Conference Highlights

By Mac Lemon, MD Australia at Enterprise Architects Well the dust has settled now with the conclusion of The Open Group ‘Enterprise Transformation’ Conference held in Sydney, Australia for the first time on April 15-20. Enterprise Architects is proud to have been recognised at the event by The Open Group as being pivotal in the success of … … Continue reading