Skip to main content

Posts

Showing posts with the label Organizational Change

Culture Hack Required!

The risk is below the water and we are headed right towards it. Organizational Transformations, Business Transformations and IT Transformations are all at their very core really CULTURE Transformations!  Ok friends, I’ve loaded this one up. For a deeper dive into some of the topics addressed in this blog, be sure to click on the embedded­­ links provided. Culture must be considered to Drive Stakeholder Value - This is POWERFUL! Think about how a culture shift  enables the following: Mapping the customer journey with all touchpoints and interactions. You can potentially map the customer journey and map the stakeholder’s roles and responsibilities brilliantly, but what about the cultural shift to enable these stakeholders? Without it we will likely fall short of our goals. If we have any hope of converting demand into value via IT-enabled services – culture is key!  Properly designing XLAs , SLAs and meaningful measurement models.  Without culture, the risk is high

The Whitehouse - Transitioning of Power to the New Administration

So the election is over and we move into the transitioning of power to the new administration. This doesn’t officially happen until January 20 th 2017. President elect Trump met with President Obama and so begins the transfer of Data, Information, Knowledge and Wisdom. So with such a short time the transfer between the transition teams and the operational teams has to happen quickly, efficiently and effectively.  This transfer of power has happened 43 times in our nation’s history with 11 happening so far in the postmodern era and the Obama to Trump administration being the twelfth. Can you say change model? The ability to have this smooth transition rests to a significant extent on the ability of those involved to be able to respond to existing circumstances, their ability to understand the situation as it currently exists along with any options that may be available, along with the known consequences and benefits.  The quality, relevance and accessibility of this knowledge

Organizational Change Management

Change is not something that you do to people, change is something that you do with people. What thoughts occur when you or your staff are notified of a significant change to a process or service?  Is it one of dread, fear or perhaps frustration?  Managing organizational change should be a required element in any or all process and service changes where significant impact for users and staff are expected.   Service providers must ensure readiness for the change and ensure that a cultural shift does indeed take place.  Organizations change for a variety of reasons that could include the need to “get better” or perhaps to “be the best”.  Sometimes organizational change management is triggered by the need to deal with a changing economy or revenue loss.  At the outset, management must be honest with workers and still able to convince them that the best way to deal with current reality is via change.  Each individual’s ability to understand and to accept change will vary.  Change is i

FAIL

We all know failure!  If a deployment for a critical service fails and negatively impacts business partners and consumers that can not be good.   One would have to consider why did this happen?  And even more critical is, why does it happen more than once? There are times when failure can be viewed as good. That of course is when we admit and then correct the reason or the cause of that failure.  Many organizations struggle with a culture that fosters hiding failure.   It is very difficult in this type of stringent culture to be effective and even more difficult to be efficient and innovative.   Not being able to admit or to discuss failure generally will lead to repeated and more disruptive failure.    What is a service provider supposed to do?  Do we fire individuals who drop the ball and fail?  If so, what size of failure would instigate such an action?  Do we restrict staff from elements or areas of the value stream so that their failure does not have the opportunity to impact u

To Collaborate or To Compromise … Which Is Best?

The people factor and your ability to absorb change could and does make all the difference for IT service providers.  Most IT practitioners will agree that “change” requires some organizational change management.  Organizational Change Management (OCM) is the process of preparing, motivating and equipping people to meet new business challenges.  Conflict can be looked upon as good!  Embrace conflict don’t ignore or avoid it because it is necessary to listen to conflicting opinions that may not have been considered.  Learning to use different conflict modes helps to move forward and increase engagement that could make your organizational change a success. The   Thomas-Kilmann Conflict Mode Instrument   is a tool for helping people understand how different conflict-handling styles affect interpersonal and group dynamics and for empowering them to choose the appropriate style for any situation.  I was studying this in preparation   for an “Organizational Change Management” workshop an

Failing Forward

In the introduction of her book The ITSM Process Design Guide, Donna Knapp writes “In today’s competitive business climate it’s not enough to do things right; Information Technology (IT) organizations have to do the right things right.”  Well what happens when we don’t? Remember New Coke?  Not every decision we make, every new design or redesign we engage in goes according to plan.  What happens when we fail?  One of the most important and most deeply entrenched reasons why established companies struggle to grow is fear of failure. In fact in a 2015 Boston Consulting Group survey, 31% of the respondents identified a risk adverse culture as a key obstacle to innovation. (1)  ITSM processes for strategy, design, transition, operation and CSI are all based on efficiency and effectiveness.  It’s about being in control of our IT environments and that we must do everything we can to prevent failures.  Now this may go against many of our strongly held beliefs but Pixar’s president, Ed Ca

Shift Happens: How?

Demand is increasing.  Dynamic or changing business requirements are a norm.  Business and customers must have quality services provisioned fast.  Ok … we get that.  Now let’s think about the service provider and what their condition or state is.  Some service providers are stuck in an organizational structure and management style that propagates an isolated us vs. them type of culture.  Others have legacy overburdened outdated systems.  Disparate and replicated tools between networking, storage and other functional teams including service desks generally create more havoc than business value.  Many efforts including data center transformation, new sourcing models, cloud computing and more have helped to some extent.  Even after these very costly initiatives many service providers experience a resistance to change and find they are working within a very rigid environment. Rigid structures, rigid process or rigid anything will not enable a service provider for success.  Some organi

Your Comfort Zone is NOT Comfortable

We have all heard mantras and messages like “If it’s not broke, don’t fix it”. Some might still cling to values like “We have always done it that way” but great leaders in contrast will see a different vision and say “There is a better way to do this”. IT service providers in today’s industry need to get uncomfortable. This is especially true for executive management. Some of the best leaders in the world make it their business to experiment, get creative and challenge the status quo. Whether your needs and interests correspond with the early stages of innovation, like education and professional enhancement, or at a later stage like funding and business development, Innovation is key and cannot be propagated by cynics whose horizons are limited by the obvious realities. So how do we manage the naysayers? Successful DevOps, Agile, ITIL and ITSM all require cultural change. One thing we can all agree on: Change is Hard. However, with the right knowledge your team can be

The Great Divide

Historically there has been a divide between the Systems Administration (Operation folks) and Software development (Application folks). This divide often results in services being released that only partially meet customer/business requirements and leaves the organization with the perception that operations is often inefficient and ineffective. This riff is not of our own making. In the past it has been caused by a combination of conflicting goals, objectives, processes, and tooling.  Development-centric people tend to believe that change is good. As a matter of fact it’s the thing that they are paid to realize. The business depends on them to be agile to the changing business environment. Because of this correlation, they are often rewarded to create as much change as they can and do it as quickly as possible. Operational people on the other hand, have institutionalized the belief that change is the nemesis of who they are. The business depends on them to keep the lights

WTF? Why the Failure?

Through the implementation of best practices, one of ITSM's critical success factors is to enhance the business' perception of the IT organization.   By creating a service strategy which helps to define good design, encourage effective transition processes and deliver valuable services through efficient and effective operational management, we work hard at making this goal a reality. Unfortunately, IT is often perceived to be ineffective and inefficient.  Recently, the government’s inability to deliver a working website for the affordable care act was splashed all over   news with many of my non-IT friends and family asking, how could this happen?   How come IT people never get it right? I want to respond with “BUT WE DO” and list many of the successes that I have been part of during my career.    But I look at them sheepishly and respond with” I don’t really know”.   As I think about this, I begin to get angry and not just because I’m an American tax payer, but because a

Collaboration

As I sit and listen to some classical music, the idea of collaboration comes to mind. To make the music,  the symphony needs to work together, yet play as individual musicians. I cannot play your part, nor can you play mine. By playing each of our parts together as part of the bigger whole, we can create something bigger than either of us. We call this the “primacy of the whole”-the sum is greater than the individual parts. This is the basis of collaboration. Pulling together a group of people into a team and instructing them to use “teamwork” or to “work as a team” does not equate to collaboration. A recent presentation made sense of this. Wikipedia© would not have come together as we know it if all the contributors had been put in the same space and given the instruction to create the site. The online encyclopedia exists precisely because the contributors did not know each other and did not work together in forced cooperation. The contributors created the information because t

Best Practice as a Meme

When looking at ITSM best practices we need to look at the culture of our organizations and understand how we would transform our organizations into value-laden delivery mechanisms. A culture is just the "known environment in which we live and work." Cultures are organic constructs--they are grown and guided, not imposed or dictated. Every person, group and organization has its own culture. The culture of an organization is really the aggregation of the individual or group cultures found within the organization. As a result if the culture of an individual, group or organization is not an environment focused on delivering value to customers, then transformation should occur. So how do we go about transforming our cultures? We can look to some of the liberal arts for assistance in this. From the study of sociology we find the concept of "memes".   meme--an idea, behavior, or style that spreads from person to person within a culture . Many of you might

“Meeting” is not a four letter word

At one time or another we have all opened our email, only to find a meeting invite and think (fill in bad word of your choice) Different organizations communicate and collaborate in different ways, depending on the message, decision or topic at hand.   Under certain circumstances, a virtual or physical meeting may be the best vehicle for making a decision or collaborating on a common objective.    While most meetings strive to be well controlled, brief and focused on facilitating a set of actions, this does not always happen. Here are some simple and effective ways to ensure that a meeting is a success: ·         Establish and communicate a clear agenda in advance.   This will allow people to prepare properly and will help the facilitator in preventing his or her meeting from being hijacked by one of the attendees. ·        Most organizations have a governing set of rules for participation in a meeting. No biting, scratching, spitting or name calling is encouraged.   R

The Future of Communication

I recently had the chance to encounter a very telling situation about the modern world. A presenter was talking about how the college age generation (the future employees of IT and business) was moving away from what he called “old style web pages”. That is full web sites and pages overloaded with content and information that requires someone to commit time to actually “reading”. The preferred communication approach for the upcoming generations is rather the “text” or “tweet”—140 or so characters of information or knowledge spun into the universe as snippets of data, information, knowledge and wisdom. Older generations are capable of producing such ‘text bites” of knowledge, but generally see them as links or parts of a much bigger activity called a conversation. For the future those “texts” and “tweets” will be the whole conversation or story: beginning, middle and end in 140 characters or less. It brought to mind the importance of coupling existing knowledge management with new or

How Do You See ITIL?

As with most things, ITIL® can be viewed from multiple perspectives. I have found that many people seem to take a polarized view of the set of best practices. They either see ITIL® from a very literal, functional and operational focus or they see ITIL® from a more figurative, conceptual and strategic perspective. The interesting thing about ITIL® is that it is both of those things and everything in between all at the same time! After spending many years reading, thinking, teaching and using ITIL® I have found that one of its greatest benefits is its flexibility. The set of best practices can be seen from strategic, tactical and operational perspectives. In addition it is my firm belief that to be a true expert in the best practices one must be able to think at all three of those levels at the same! Because ITIL® takes a lifecycle approach (cradle to grave for the life of a service) it operates very strategically. Because ITIL® provides a set of processes for achieving value fo

Keeping People Engaged

One of the most important questions we can ask in ITSM is “How do we keep people engaged and excited about ITSM?” This question is fraught with danger. If too little energy is put into keeping people engaged then ITSM has a chance of withering and dying. If too much energy is put into the people aspect then other important efforts gets sacrificed. So how do we find the right balance? How do we know what is the right level of energy to employ in an effort to keep ITSM on a steady path for your organization? The answer lies in the concept of engagement. The term means to hold the attention or efforts of a person. To keep people engaged we must therefore keep everyone involved, active and attentive to ITSM in our organizations. How do we keep people engaged? By giving them new opportunities to learn, demonstrate capabilities and new challenges to overcome. We can provide new areas for exploration and engagement by using process and maturity assessments to identify current levels of

Single to Double Loop Learning

C hris Argyris is one of the most important and influential thinkers in the last 100 years. Yet, few people are aware of his efforts in organizational development and human behavior. Argyris wrote about a number of different areas of organizational change management. Perhaps one of his most important contributions has been in the area of Single-loop and Double-loop learning for individuals and organizations. Single-loop learning is when an individual or group undertakes an action and the result is not what they expect or believe be the result should be. So they go about “correcting” their approach on the assumption that they must have done something “wrong” the first time. As a result of the “correction” they expect a different result. Some of you may recognize this as the classic definition of “insanity”. Others have called these “self-fulfilling” prophecies. Doing the same kinds of things over and over and expecting different results. Single-loop Learning results from creating what

Conducting Productive Meetings

When we think about ITIL® we think about being able to manage the delivery of value-laden IT services to customers. But are there other, less obvious ways we can use and gain from the best practices and ideas contained within ITIL®? One of the areas that ITIL® and ITSM can help us with is by making conversations and meetings more effective and efficient. One of the ways that ITIL can help us with meetings is by using the concepts embedded in RACI. Traditionally the ideas of being responsible, accountable, consulted and informed have been for use with process activities and levels of authority and accountability. However, once we identify those levels and assign them to roles we can use them to help us establish the proper attendance at a meeting. When sending out a meeting announcement or invite we can indicate that the meeting is for those roles holding particular levels within the RACI models. In this way we have the appropriate roles and individuals at the meeting. Another wa

Building a Community of Practice (Part 2)

Part 1 of this series introduced the idea that a community of practice (CoP) is group of people who are bound together by similar interests and expertise . CoPs are an extension of the blended learning strategy being adopted by many organizations that combines formal, informal and social approaches to learning. Like service management, communities have lifecycles – they emerge, they grow, and over time they become institutionalized. Also like service management, the plan-do-check-act cycle can be applied to each of these stages. Plan involves identifying the audience for the CoP and defining its purpose. It is also critical to ensure the needs and goals of its members are understood and that its purpose and goals are tied to the vision, mission and values of the greater organization. For example, you could have a service management CoP that brings together all of the practitioners in your organization, or you could have CoPs that focus on individual lifecycle stages but occasi

Linking Employee and Customer Satisfaction

Techniques used to measure employee satisfaction include informal one-on-one discussions, focus groups and periodic surveys. As with customer satisfaction surveys, for accurate and reliable results, employee satisfaction surveys should be created with care by people who understand how to develop questions that produce unbiased information. In other words, ask your HR folks for help! So what questions should you ask? "How satisfied are you with your job?" is a good place to start. A question such as: "Compared with a year ago, how would you describe your overall job satisfaction?" can provide additional insight.  You can also ask employees to rate their satisfaction with areas such as: Reward and recognition programs Career development and advancement opportunities Education and training  Supervision, coaching and feedback Teamwork Availability of resources needed to do the job Ability to contribute to organizational goals  And in the spirit of co