Saturday, January 30, 2010

Tackling LEAN change week 1

Well I have finished my first week on a two month initiative to help a very large conservative organization starts it's journey to becoming a solution factory base on lean principles.

First of all I want to thank the folks on the agile lean yahoo group for some great advice and feedback.

I have had a chance to talk to the CIO and get a sense of what he means by a solution factory.
-clear visibility around how things are being done and progress (ie the catwalk over the factory floor)
-flexible assembly lines where parts of the
supply chain can be interconnected in diffrerent ways to provide value
-an environment where workers can be proud of the work they do, and actually want to be more productive.

I also had an opportunity to discuss lean with the architecture group. This was a great conversation. The group had a keen awareness of how command and control and throwing things over the wall were not working, we had a great discussion on lean IT governance ( ala Scott Ambler and Perr Kroll. The architects really got it, and were generally enthusiastic to try to break down the wall between architecture and delivery.

I asked the architects to give their opinions on how we should proceed building a vision and roadmap by asking them to ask wether they leaned to the left or right on the following

visionary <*----> pragmatic
educational <*-----> self learning
e2e value stream <---*-> IT perspective
planning <-*---> doing

I was quite surprised about the almost unanimous desire for creating an ideal state. I think the ideal state is important, it motivates and energizes people to push beyond the possible and truly excel.

I percieved the really strong desire for education over self teaching as a general apprehension over what lean would mean to the organization, it's clear to me that people here are looking for answers, I agree that education from the outside is crucial, but I hope I can hammer home the concept that people need to get into a self learning mode. (baby steps)

I'm fairly concerned around the IT focus versus end to end value. The rational given is that the IT group already knows the problems of the business and that the IT group would like to get it's house in order before approaching the business with their desire to go in a lean direction. My major concern is that the idea that "IT already knows" is a root causes of IT-business mis-alignmnent. I'm also concerned that some leadership is emphasizing efficiency over effectiveness.

That being said I think the evidence I've collected so far signifies a genuine desire to provide better value to there cumstomers, a hunger for better collaboration, and a real understanding that it will be the people on the shop floor that will make this successful.

That's it until next week.

Location:Brock Ave,Toronto,Canada

Sunday, January 24, 2010

Tackling Agile Organizational Change

I'm just about to start a new project where I will have the chance to assist a client in setting up a "software solution factory" based on Lean principles.

The client has had some serious challenges relating to software delivery in the past, and is supporting systems with a significant backlog of defects which don't seem to be getting any smaller any time soon. The client is also in the initial stages of some very ambition systems replacement initiatives, and would like to get things right this time.

Using a mixture of lean and agile principles clearly can offer alot of value to the client. But historically the organization has many elements that could make lean change challenging, a tendencancy to rely on buraucracy and collective bargaining are a few examples.

The client wants help in the typical things that are part of any transformation effort,
ie: establishing a vision, communicationg the urgency of the problem, listing challenges, developing a target, and developing a plan.

I see a number of potential ways to tackle this problem, and would really appreciate other people submitting thoughts and ideas. The more fresh eyes I can get on this problem the better.

It should be noted that these ideas are not mutually exclusive to each other. But there is a limit to what can be accomplished during this engagement, so I've tried to bucket options in a sensible way.

OPTION 1: Realist and Careful

-In this approach the initial effort would be focused on carefully cataloging the current state.

-Structure, work habits, technology, HR, would all be reviewed and assessed.

-These inputs would be used to identify the biggest issues and realistic roadmap would be created that would show target states over time (1 year, 3 years, etc)

This approach has the benefits of being easy to scope, and allows the client some time to prepare the message in a way that minimally disrupts the way things currently work.

However this is my exact issue with the approach, if things are broken what exactly is wrong with disrupting them if a better outcome is the result. A conservative approach has the most chance of becoming shelfware. Disruption is a critical part of any change, we need to test the organization's resolve at some point, and in my mind the sooner the better.

OPTION 2: Idealist and Disruptive

In this approach I would

- spend much less time collecting empirical evidence, but do the minimum necessary to give me contex.

- create an idealized vision of the way the organization should work. Every article I read on organizational change and lean seems to indicate that the idealized vision motivates people to stretch themselves toward excellence. This intuitvely makes sense to me.

- quickly identify groups that could benefit from agile lean rught now, and coach them to some degree of success.

- set up a "supply chain" of analysis, education, and adoption. The idea is to get a repeatable process instantiated that would allow my client to increase internal capability as quickly as possible.

- instrument adoption on as many parts of the organization as possible. Then learn from the experience, then optimize the education supply chain. Plan, Do, Check, Act

I really like this aproach as it has the opportunity to offer real value, and it is inherently lean. (use lean to bootstrap lean) However this client is conservative, and may not be able to move this quickly. This approach is also really hard to scope, so much depends on the client stepping up to the table.

OPTION 3:Educate and Participate
- get context, focusing on skills and ethics gaps
- create an online education forum where practices, principles, and other educational material can be posted and improved in a structured and collaborative fashion.
- create a repeatable practice around self serve education, slowly releasing the training reins to the client
- hold a organize wide conference with the dual purpose of education and collaboratively developing a transition roadmap

This approach has the benefit of involving or attempting to involve a large portion of the organization. It also can help spread the message far and wide accross the organization. My main issue with this approach is that education becomes quickly stale if it's not used. Also education alone is not sufficient for adoption, hands on mentoring is essential as well.

Again insight from the community would sincerely be appreciated. I promise to post updates on my progress in the hopes that this will help others who are on the same journey. I am also hopeful that this level of public discourse will help my client get the most they can out if going in a lean direction.