Archive for the ‘ Corporate Culture ’ Category

What is “Innovation” for IT?

Picture the Monday morning meeting that you have to attend after coming back from Symposium. It’s you and your CIO and SVPs. The Topic: What is one innovative/mind blowing idea should we (WE MUST!) start doing/implementing now.

For years we’ve heard about such topics as Real-Time Infrastructure, Server Virtualization, VOIP, Service-Oriented IT, ITIL and others.

I would submit that these topics are NOT innovative. To borrow a term, these topics are “birthright services” for I&O.

For some companies there are significant benefits to be gained by improving their implementation of some of these topics but you are not success in today’s game if you’re not doing this stuff! Every CIO has heard (heard the words but maybe not gotten the message) about these topics. Rehashing these same themes is not going to make an impact.

What’s innovative these days?

(Question from “capstick” on the Gartner Symposium Forums)

Honestly, I don’t believe that there’s anything really new. But there are a lot of “old” opportunities that a lot of IT groups aren’t exploiting.

The biggest one that I can think of is true collaboration with the business and a sense of partnership at all levels of the business and IT. At the top, that includes making sure that IT has a seat at the table. There needs to be a continuous dialog concerning what opportunities the business has and how IT can help to exploit them. Tools that provide the visibility (both ways) and facilitates that communication are part of that. But the behavior is the most important thing. Everything else is just an optimization exercise to squeeze out more work at less cost.

There are a few “game changing” technologies, but the real Innovation comes from process and culture changes, not from the tools themselves. IT should be a facilitator of Innovation and should be engaging the business to find the application and business value in the tools. To do that, we need to get out of the commoditization mindset and back into one of business partnership.

Creating a winning team in corporate America

Image your company as a sports franchise. Your managers have recruited the best athletes from around the world, the best coaches and you’ve provided them with the best equipment. The owners and board of directors are up in the skybox looking down on the field and anxiously anticipating a winning season.

Now for the complications:

Nobody actually sat down with the hiring managers and told them what game was going to be played. So the athletes and coaches are from a dozen different sports and disciplines. Additionally, they’re all equipped with their own specific equipment, balls, pucks, rackets, etc.
The playing field is completely shrouded in fog and your players can only see what’s happening within a few yards of where they’re standing. They only interact with other players that happen to enter within that circle of vision and they have no idea where they are relative to the goals, the competition or the rest of their team.

The coaches get feedback from the players that they can’t find the goals or even the ball. At the same time, the coaches are getting feedback from the skybox that the team is losing the game. To try to make sense of the game,  the coaches decide to mark up the field with some guidance. Each coach makes assumptions about the game being played and what the goals are. Unfortunately, each coach draws different plays and strategies directly onto the field and the team can’t tell which is which.

The Owners sees that their team isn’t winning. They can only see the people that come out of the fog right in front of them looking lost and confused. The owners have  the goals to directly under the skybox in the hope that the realignment will result in some of those wanderers scoring points.

The team gets frustrated with the inability to score and they try to figure out the problem on their own. They decide that the coaches and owners must be stupid or crazy. Small groups of players independently decide on strategies to fix the problem. Since the game has never been defined and they can’t directly see the goals, the players are forced to make assumptions.  Between them they decide to bring extra balls, a hockey stick, two tennis rackets and a team of seeing-eye dogs onto the field.

The coaches see the changes and begin to question their own assumptions about the game. They re-align around whatever small successes they perceive. They  try to keep the  game going by hiring pro hockey players, a pair of tennis stars and a dog trainer. The Board tells the coaches that they’re over budget, so the coaches fire the most highly paid of the original players to try to reduce expenses.
The fans (the users) become confused and disgruntled and start looking towards other teams and players to follow. Some of the fans get ambitious, form their own teams and enter the field in the assumption that they could play better.
The Board sees the money drying up and the lack any apparent scored goals. They fire the coaches and the rest of the original players. They look at the organization and determine where the team seems to be struggling. They hire 3 more animal trainers, a consulting tennis coach and they buy a zamboni to ice the field to make better use of the hockey players.

The dogs get run over by the zamboni. The animal trainers all defect to Las Vegas to train tigers. The hockey players join an off-broadway ice show. The tennis coaches try to recruit tennis players, but the board decides to hire professional cricket players for half the price.

The situation fails to improve.

Hoping to turn it around, management equips everyone with headsets so that they can communicate. New scoreboards are installed to better report the scores to management. Everyone is sent on motivational training and the markings on the ice are all repainted in neon green.

So, you now have a bunch of cricket players being coached by tennis coaches, sliding on the ice in dense fog trying to make sense of what the actual game is and where the goals are. However, you truly do have a group of talented individuals. Each individual is performing to the best of their abilities. Occasionally goals are scored through acts of personal heroics. But the overall efficiency, control and alignment of the organization is shot and you’re left wondering how you got here.

This scenario may seem extreme. But, surprisingly, it’s not that far off what’s happening in organizations on a daily basis. The larger the organization becomes, the more difficult it is to keep the pieces aligned and focused on common goals. The lack of a shared context leads to a lot of ambiguity, conflicting goals and strategies, a perception of others in the organization as “stupid” or “incompetent” and a considerable amount of misdirected and wasted effort. Groups adhere to their own agendas, often with no regard or awareness for corporate strategy. Impacts to other teams are only considered when something “breaks” and often, the organization continues to function by brute force and individual efforts rather than through good planning or alignment.

This goes beyond a simple communication problem. As an organization grows, alignment drifts, personal political agendas begin to overshadow the “good of the company” and the idea of “team” becomes a localized concept. We forget that the “team” is really the entire company and not just our little corner of the corporate world.
The larger the organization, the stronger the leadership needs to be. That doesn’t mean that the leaders need to micromanage. Instead, they need to provide clear direction and expectations (what game are we playing and what are the rules?) ensure that every level of the organization has the authority to make their own decisions within the rules (fans stay off the field. Coaches set the strategy. Stadium staff maintain the stadium, goals and markings. Equipment managers control the equipment selection, etc.) and provide feedback on what’s successful and what isn’t. Trust is a big part of successful leadership. It leads to empowerment, better decision making on the floor and a more responsive and agile organization. But direction is needed if you want to keep those trusted individuals aligned to common goals. You can’t just assume that everyone is playing the same game.

By recognizing what’s going on, opening up a continuous dialogue and providing your staff with the tools and information to make the right decisions, you can recapture that small-company alignment, passion and team dynamic. Couple that with the resources and talent pool of a large corporation and you have a potential championship team.

I Beleive…

A consultant’s only asset with any long-term value is reputation.

Technologies fall out of favour. Business Processes evolve. Companies are bought and sold. Ultimately, the only asset that a consultant has is their reputation and ethics. Many consultants (and consulting organizations) forget this and focus on the short-term value of inflated billing, placing inexperienced consultants, under-bidding and then running over budget, working on poorly considered client projects, etc. While this short-term approach may be financially profitable, it results in unhappy clients, a bad “street cred” and can ultimately lead to the ruin of the consulting organization or even the client companies.

Communication is at the heart of every successful project

A team that doesn’t communicate well internally, with the customer and with the vendors will fail. The project may be completed, but the results will be less than optimal, the project will be more expensive than required and the ongoing support costs will ultimately be higher. Clients, Management, Vendors and the direct project team need to function as a unified whole to ensure success.

Technology has no inherent value

The only value that technology has is in how it can bring value to the business. Implementing technology for the sake of technology is not only a waste of time and money, but can ultimately be detrimental to the business. Some companies don’t need a web site. Many organizations don’t need to engage in eCommerce. Implementing a multi-million dollar ERP system for a company with $500K worth of revenues isn’t going to magically drop them into the Fortune-50. Regardless of what the “other guys” are doing, your projected ROI (return on investment) should be the main driver behind any new technology initiative.

ROI (Return on Investment) doesn’t always mean direct revenue or cost savings

Your “return” on a project is nothing more or less than “business value”. Laying the groundwork to be able to exploit future opportunities, increasing your organizational agility, improving employee or customer satisfaction are all incredibly valuable to sustaining and growing your business. Many companies destroy their agility and their own futures by not quantifying these “soft benefits” or considering them as important as the hard dollars.

Nobody ever knowingly makes a wrong decision

This statement replaces the traditional “The Customer is Always Right”. If there are two diametrically opposed approaches, chances are that somebody is working with incomplete assumptions or data. By acknowledging that nobody knowingly makes a wrong decision, open communication of the relevant information can uncover where the disconnect has occurred.

If it’s not measured, it’s not managed

Project Management is a science and not an art. Deliverables should be objective, quantified (or at least enumerated in some way) and tracked. If an objective is not measurable, it can’t be tracked or monitored. If it can’t be monitored, it certainly can’t be managed. In many cases, Project Managers encounter deliverables that they feel can’t be objectively measured. If that’s the case, then the deliverable needs to be broken down or redefined to provide a clear set of exit or acceptance criteria. Committments need to be either time-based or event driven. “Whenever” often becomes “Never” or results in a last minute rush with predictably poor results.

Costs should not exceed the expected benefits

A client should clearly understand the benefits of the project, the projected value of these benefits to the organization and the costs of implementation, training and long-term support. If the costs exceed the potential benefits (direct and indirect), the project needs to be restructured or abandoned. Implementing a solution simply for prestige, empire building or billing purposes is irresponsible and unethical and can lead to disastrous long-term results.

Excessive analysis/planning/requirements definition, etc. are as crippling as no analysis/planning/requirements definition.

Most people and organizations are familiar with “Analysis Paralysis”, the inability to make a decision without analyzing every tiny detail, facet, risk, etc. to the exclusion of any real work. The new trend is a form of “Methodology Fundamentalism”, the tendency of an organization to adopt a methodology word-for-word rather than applying it appropriately for the tasks/project at hand. It’s important for everyone to understand the steps and the processes required to manage a project, but it’s equally important to know when the effort required to carry out a task outweighs the benefits. When a team can communicate effectively, there is a natural tendency to want to work using a cascaded development approach. A linear approach is appropriate for some projects, but where a cascade approach is applicable, accepting and embracing it up-front will make for a much more efficient and predictable project.

People shouldn’t be “shoe-horned” into roles as a client “make work” effort or in an attempt to increase billing.

Everyone has their own expertise, knowledge-base, interests and abilities. It is the responsibility of the Project Manager to understand where the strengths and interests of each team member lie. Furthermore, it is the PMs responsibility to ensure that everyone is engaged to the best of their abilities and with the best long-term outlook possible. Using resources inappropriately wastes everyone’s time and effort.

Ongoing Documentation is essential

Everyone should be working with the ultimate goal of becoming redundant. It takes very little effort to document throughout the project and revise the documentation as necessary. However, it can be an overwhelming or impossible task to document retroactively.