Monthly Archives: October 2013

harvard business review article-Professor Aries mentioned ‘resume’ success stories which lasted months or couple of years at best-organizational successses which dried up as principal actors who started them left the organization..

  1. The Hard Side of Change Management

    The Idea in Brief

     Two out of every three transformation programs fail. Why? Companies overemphasize the soft side of change: leadership style, corporate culture, employee motivation. Though these elements are critical for success, change projects can’t get off the ground unless companies address harder elements first.

    The essential hard elements? Think of them as DICE:

    • Duration: time between milestone reviews—the shorter, the better

     

    • Integrity: project teams’ skill

     

    • Commitment: senior executives’ and line managers’ dedication to the program

     

    • Effort: the extra work employees must do to adopt new processes—the less, the better

     

    By assessing each DICE element before you launch a major change initiative, you can identify potential problem areas and make the necessary adjustments (such as reconfiguring a project team’s composition or reallocating resources) to ensure the program’s success. You can also use DICE after launching a project—to make midcourse corrections if the initiative veers off track.

    DICE helps companies lay the foundation for successful change. Using the DICE assessment technique, one global beverage company executed a multiproject organization-wide change program that generated hundreds of millions of dollars, breathed new life into its once-stagnant brands, and cracked open new markets.

    The Idea in Practice

    Conducting a DICE Assessment

    Your project has the greatest chance of success if the following hard elements are in place:

    Duration

    A long project reviewed frequently stands a far better chance of succeeding than a short project reviewed infrequently. Problems can be identified at the first sign of trouble, allowing for prompt corrective actions. Review complex projects every two weeks; more straightforward initiatives, every six to eight weeks.

    Integrity

    A change program’s success hinges on a high-integrity, high-quality project team. To identify team candidates with the right portfolio of skills, solicit names from key colleagues, including top performers in functions other than your own. Recruit people who have problem-solving skills, are results oriented, and are methodical but tolerate ambiguity. Look also for organizational savvy, willingness to accept responsibility for decisions, and a disdain for the limelight.

    Commitment

    If employees don’t see company leaders supporting a change initiative, they won’t change. Visibly endorse the initiative—no amount of public support is too much. When you feel you’re “talking up” a change effort at least three times more than you need to, you’ve hit it right.

    Also continually communicate why the change is needed and what it means for employees. Ensure that all messages about the change are consistent and clear. Reach out to managers and employees through one-on-one conversations to win them over.

    Effort

    If adopting a change burdens employees with too much additional effort, they’ll resist. Calculate how much work employees will have to do beyond their existing responsibilities to implement the change. Ensure that no one’s workload increases more than 10%. If necessary, remove nonessential regular work from employees with key roles in the transformation project. Use temporary workers or outsource some processes to accommodate additional workload.

    Using the DICE Framework

    Conducting a DICE assessment fosters successful change by sparking valuable senior leadership debate about project strategy It also improves change effectiveness by enabling companies to manage large portfolios of projects.

    Example:

    A manufacturing company planned 40 projects as part of a profitability-improvement program. After conducting a DICE assessment for each project, leaders and project owners identified the five most important projects and asked, “How can we ensure these projects’ success?” They moved people around on teams, reconfigured some projects, and identified initiatives senior managers should pay more attention to—setting up their most crucial projects for resounding success.

    When French novelist Jean-Baptiste Alphonse Karr wrote “Plus ça change, plus c’est la même chose,” he could have been penning an epigram about change management. For over three decades, academics, managers, and consultants, realizing that transforming organizations is difficult, have dissected the subject. They’ve sung the praises of leaders who communicate vision and walk the talk in order to make change efforts succeed. They’ve sanctified the importance of changing organizational culture and employees’ attitudes. They’ve teased out the tensions between top-down transformation efforts and participatory approaches to change. And they’ve exhorted companies to launch campaigns that appeal to people’s hearts and minds. Still, studies show that in most organizations, two out of three transformation initiatives fail. The more things change, the more they stay the same.

    Managing change is tough, but part of the problem is that there is little agreement on what factors most influence transformation initiatives. Ask five executives to name the one factor critical for the success of these programs, and you’ll probably get five different answers. That’s because each manager looks at an initiative from his or her viewpoint and, based on personal experience, focuses on different success factors. The experts, too, offer different perspectives. A recent search on Amazon.com for books on “change and management” turned up 6,153 titles, each with a distinct take on the topic. Those ideas have a lot to offer, but taken together, they force companies to tackle many priorities simultaneously, which spreads resources and skills thin. Moreover, executives use different approaches in different parts of the organization, which compounds the turmoil that usually accompanies change.

    In recent years, many change management gurus have focused on soft issues, such as culture, leadership, and motivation. Such elements are important for success, but managing these aspects alone isn’t sufficient to implement transformation projects. Soft factors don’t directly influence the outcomes of many change programs. For instance, visionary leadership is often vital for transformation projects, but not always. The same can be said about communication with employees. Moreover, it isn’t easy to change attitudes or relationships; they’re deeply ingrained in organizations and people. And although changes in, say, culture or motivation levels can be indirectly gauged through surveys and interviews, it’s tough to get reliable data on soft factors.

    What’s missing, we believe, is a focus on the not-so-fashionable aspects of change management: the hard factors. These factors bear three distinct characteristics. First, companies are able to measure them in direct or indirect ways. Second, companies can easily communicate their importance, both within and outside organizations. Third, and perhaps most important, businesses are capable of influencing those elements quickly. Some of the hard factors that affect a transformation initiative are the time necessary to complete it, the number of people required to execute it, and the financial results that intended actions are expected to achieve. Our research shows that change projects fail to get off the ground when companies neglect the hard factors. That doesn’t mean that executives can ignore the soft elements; that would be a grave mistake. However, if companies don’t pay attention to the hard issues first, transformation programs will break down before the soft elements come into play.

    That’s a lesson we learned when we identified the common denominators of change. In 1992, we started with the contrarian hypothesis that organizations handle transformations in remarkably similar ways. We researched projects in a number of industries and countries to identify those common elements. Our initial 225-company study revealed a consistent correlation between the outcomes (success or failure) of change programs and four hard factors: project duration, particularly the time between project reviews; performance integrity, or the capabilities of project teams; the commitment of both senior executives and the staff whom the change will affect the most; and the additional effort that employees must make to cope with the change. We called these variables the DICE factors because we could load them in favor of projects’ success.

    We completed our study in 1994, and in the 11 years since then, the Boston Consulting Group has used those four factors to predict the outcomes, and guide the execution, of more than 1,000 change management initiatives worldwide. Not only has the correlation held, but no other factors (or combination of factors) have predicted outcomes as well.

    The Four Key Factors

    If you think about it, the different ways in which organizations combine the four factors create a continuum—from projects that are set up to succeed to those that are set up to fail. At one extreme, a short project led by a skilled, motivated, and cohesive team, championed by top management and implemented in a department that is receptive to the change and has to put in very little additional effort, is bound to succeed. At the other extreme, a long, drawn-out project executed by an inexpert, unenthusiastic, and disjointed team, without any top-level sponsors and targeted at a function that dislikes the change and has to do a lot of extra work, will fail. Businesses can easily identify change programs at either end of the spectrum, but most initiatives occupy the middle ground where the likelihood of success or failure is difficult to assess. Executives must study the four DICE factors carefully to figure out if their change programs will fly—or die.

    The Four Factors

    These factors determine the outcome of any transformation initiative.

    D. The duration of time until the change program is completed if it has a short life span; if not short, the amount of time between reviews of milestones.

    I. The project team’s performance integrity; that is, its ability to complete the initiative on time. That depends on members’ skills and traits relative to the project’s requirements.

    C. The commitment to change that top management (C1) and employees affected by the change (C2) display.

    E. The effort over and above the usual work that the change initiative demands of employees.

    Duration.

    Companies make the mistake of worrying mostly about the time it will take to implement change programs. They assume that the longer an initiative carries on, the more likely it is to fail—the early impetus will peter out, windows of opportunity will close, objectives will be forgotten, key supporters will leave or lose their enthusiasm, and problems will accumulate. However, contrary to popular perception, our studies show that a long project that is reviewed frequently is more likely to succeed than a short project that isn’t reviewed frequently. Thus, the time between reviews is more critical for success than a project’s life span.

    ROLL THE DICE 🙂  zk

Posted in Uncategorized | 3 Comments

Performance Management

The article “Performance Management at the Wheel” the reading for class 10/24/13 was very interesting. I think the research was very straight forward and as to five performance management activites associated behaviors like, performance development, providing feedback, employee development, year-end appraisals and empowerment. These five developmental areas have a major part in my yearly evaluation at my current job.

I have often times wondered why my manager insisted on my input during my evaluations and this study makes me understand that he is using technique from the reading to 1) set expectations as to how I should be developing in my career, and in doing so 2) the manager will offer feedback as to how he can help me in my future career goals. This has always been a major part and I often times wonder why is he so interested in my career progress.   3) This eventually leads to the end of the year and there is no surprise about my final evaluation, because we had both focused on ways of development and growth following the coaching. This will make me be more thrusting and be willing to accept his constructive feedback and be a more engaging employee at the firm.

rgb

 

 

Posted in Uncategorized | 5 Comments

Adhocracy in a Machine Bureaucracy

I read an interesting article on BBC – http://www.bbc.co.uk/news/business-24622247 – and in the Economist – http://www.economist.com/news/business/21587792-radical-boss-haier-wants-transform-worlds-biggest-appliance-maker-nimble about Haier and their structure.

Haier, a Chinese manufacturing and appliance company, is a large company with 80,000 employees around the world.  It was a failing company in the late 1980s until Zhang Ruimin, it’s current CEO, turned it around and made it what it is today – a thriving international manufacturing company with high-quality goods.  He is known for adopting abnormal management practices and structures.

In his current move, he is removing middle managers and creating teams with members from different units – sales, manufacturing, etc. – that are based around ideas with their own performance metrics.  The units leaders are the employees that have submitted ideas to the company and won approval from their fellow employees.  Within those team, there is a “catfish” – a second-in-command that is looking for a chance to take control of the team if the leader ever fails.  Team members can leave whenever they want and join another team, or they can join two or three teams – being a leader in one and a “catfish” in another.

To me, this loose structure seems great in theory but to manage a multi-national company that requires the standardization of products, it can create some inconsistencies.  Creating an ad-hoc structure in a manufacturing company seems like a complex move.  The risks seems high but if it works out, the reward might be even greater.

Let me know what you think about Zhang Ruimin and his strategy.

Posted in Human Resources, Structure | 4 Comments

Management VS Leadership

Hi all,

Before going to bed, I wanted to finish this day with some glorious thoughts that may lead to a potential discussion. So the fact that our upcoming class (10/17) will focus on the complexity of employee relations and how leadership style and the changes of style can improve the effectiveness of staff management, I told myself, “before proceeding, I should start by drawing the line between the concepts of leadership and management. Are they the same? Or are they different? Or better yet, how different or similar are these two definitions?” As I was doing some research to answer this question, I bumped into an interesting article I found in the Wall Street Journal. The article begins with a blunt statement “Leadership and management must go hand in hand. They are not the same thing. But they are necessarily linked, and complementary. Any effort to separate the two is likely to cause more problems than it solves.”

Then, in a 1989 book by Warren Bennis “On Becoming a Leader,” the article lays out the following differences in a very clear way:

– The manager administers; the leader innovates.

– The manager is a copy; the leader is an original.

– The manager maintains; the leader develops.

– The manager focuses on systems and structure; the leader focuses on people.

– The manager relies on control; the leader inspires trust.

– The manager has a short-range view; the leader has a long-range perspective.

– The manager asks how and when; the leader asks what and why.

– The manager has his or her eye always on the bottom line; the leader’s eye is on the horizon.

– The manager imitates; the leader originates.

– The manager accepts the status quo; the leader challenges it.

– The manager is the classic good soldier; the leader is his or her own person.

– The manager does things right; the leader does the right thing.

 

Based on what I’ve learned in class, this makes sense. For instance, in class we have seen the structure of organizations, groups etc. The person at the top usually holds a managerial position, but does that make him a leader? Structure may be the design in which the organization is built upon, but I would say that people are the energy, the spirit that gives life to the organization. Given these thoughts, I can connect it with the following: “manager focuses on system and structure while the leader focuses on people.” Both managers and leaders are some sort of compasses suited for different functions. The manager focuses on the necessary design and builds the road to direct and facilitate the work and the goal of the team. A leader is the one that sparks the necessary spirit to make the organization work appropriately while also keeping a sense of purpose. Without management, a driven team may not have direction, without a leader, a well-deigned structure may not have the power for which it was built for in the first place. Just like “management go hand in hand” I think structure and people go hand in hand as well. If we have two concepts, therefore I believe that there is a relationship between these two actions,  there’s got to be an interesting balance between the two. Too much focus on the structure may create a negative bureaucracy, compromising the efficiency of the institution, while too much focus on the people may create conflict and unnecessary politics. These are thoughts that came up to mind, and I will appreciate anyone who can bring their own thoughts. Whether there is an agreement of disagreement, anything is appreciated!

Thanks a lot, best always!

Andres

Posted in Uncategorized | 2 Comments

Email Etiquette

Earlier in the semester, we were read a posting of an employee who went away on vacation and left an away message stating that she was out of the office.  Her boss emailed her and basically informed her that she would need to respond to messages while away and that her away message was not professional.  I was one that was adamant about not having to answer your boss back being that you deserve your full vacation experience.  My tune is changing since at work this week, I have been trying to contact several doctors and they all have various away messages.  I feel like the boss.  Is anyone working around here?  With the various away messages however, I think there is a correct way and a wrong way to leave away messages.

In one of the clinician’s away message, it simply stated that “I will be away from 10/5 – 10/15 and will not be responding to emails nor phone calls.”  Now that I thought was totally absurd.  If I am a social worker or a school counselor for example trying to coordinate care on one of our high risk patients and I got that away message, who would I attempt to contact?  In another clinician’s away message, who was away on the same conference, they stated that they would “be away 10/5 – 10/15 and would be responding to urgent emails only.  For routine issues that can not wait, please contact Dr. X who is covering my patients at (212) 555-5555.”  Now, although this clinician is out the same time as the previous clinician, I believe this away message was handled more professionally.  It gave a covering doctor and it made me feel at ease that atleast if something major were to occur that this doctor would read about it if I were to write an email about it.

All doctors are supposed to use the email address provided by the hospital when it comes to sharing the hospital’s patient info.  Since my hospital is a teaching hospital, many of the doctors have their med school’s email addresses as well.   The hospital’s email is not really convenient, I must admit, especially in the age of smart phones where email can be linked directly to your phones and tablets.  The method of reaching these doctors has been emailing their med school email addresses if you wanted a speedy response.  This is not the correct way of doing things however.  In trying to follow the proper protocol I emailed a doctor at their hospital’s email.  My email was answered with an automated response message which stated that “I do not check this email often.  If you need me, please contact me at john_doe@medschool’s name.com ”  This left me quite confused because if audited the hospital could be fined for a violation of patient information.  This doctor could have just had his hospital email forwarded to his medical school’s email address like I am sure many of them do.  To put that you do not even check your email was so offsetting in my opinion.  In the rise in integrating technology into our structures, we need to learn the “dos and donts” of email.  Once viral, things can not be taken back and things are forwarded every day.  What messages are we sending to others with these away messages? There is a right way and a wrong way.  I think there needs to be an email etiquette 101 course established at each job!

Posted in Uncategorized | 4 Comments

The Case of Effective Leadership

Our interesting class discussion about this case has left me even more intrigued about Joanne Stevens’ action.  Specifically, what can she do now to correct the outcome of the group’s decision?  I said in class, she should not admit to her mistake of giving the group authority to develop their own standards, she should instead turn it around by saying it was a test.  I thought to myself, as Iris suggested, this may come as an insult to the group and indeed create some serious implications.  Maybe instead she should clarify what her expectation of the group is.  She clearly explained to them that the case load standards established several years previously were too low.  Instead of asking the group to establish their own standards, what she truly wanted, was for them to establish a way to increase the standards.  A mistake was clearly made in her directions. 

In “Speeding up Team Learning”, by Edmond, Bohner, and Pisano, creating an environment that encourages team learning requires the leader to serve as a “fallibility model” in other words, a leader should admit their mistake to the group to encourage discussion of concerns and errors without fear of punishment.  Clearly, this case was not set in a learning environment, so admitting to a mistake is not conducive.  The participative style is more appropriate in a learning environment or an environment with the leader present, not absent.  So I stick with my initial thought, she should turn it around by saying it was a test, the ultimate decision resides with her since the group is not thinking along her lines.

Posted in Human Resources, Structure | 2 Comments

Teams and Thoughts

I didn’t quite wanted to let a great productive evening and a mind saturated with ideas go to waste, so here I sit down to write down my very first blog ever.

I always thought I am not a team player.  I do not do so well in teams as I would do by myself. I prefer solo work rather than group work. Like we discussed in class today, personality, culture, they all make a difference. People’s personality matter a lot. Some people work alone while some work well in groups. I often wonder whether it is the inability to coordinate or just being out of tune with the group. I always wondered why? Even in my undergraduate courses, when we had to work in teams, I used to loathe it. I would rather ask people to assign each a part of the group work, I would then work on that part individually and just submit it to the group, that is how I could work in a group.  As I read the article, why teams don’t work, I agreed on most of the things Hackman said about the teams.  When I read the part about the deviant, I literally said to myself, yes that’s me. I am the deviant; I do not always go with the group flow. I have a tendency to ask questions; Why? Why? Sometimes people do question me, why do you always have to disagree? Why can’t you just agree with us and then we can go ahead and work together. If I had read that article before, I certainly would have the answer, Oh yes I am the deviant!  Hackman writes, every group needs a deviant so that the group can be forced to think outside the box, think critically. However I do not agree that every team needs a deviant. Sometimes those so called deviants could be a real impediment for the group progress as the group might not get anywhere, simply because it is stuck at the very first questions posed at the group. I think my blog is getting long but I feel like I must add this piece to my blog- a question I faced in an interview for a job.  The question started after my answer to the previous question, which I had replied; Yes two heads are definitely better than one.  “So you are working on a team, the success of the team depends on each and every member doing his or her job well and contributing to the group, what if one of your team member lags in his/her responsibility and simply underperforms, how will you handle that situation?”  I secretly thought that person could easily have been me but I answered,  “well in that case, I would want to speak to that person in private and ask what was the underlying problem with him or her that had hindered him/her from performing at his/her level best. Then, may be we could resolve the problem that person was focusing on.”

By the way I didn’t get that job and I joined MPA program; hoping to be better equipped to answer any questions an organization may have.  Tonight I leave you with the same question, “What would you do if one of the members in the group is underperforming, hampering the group’s overall success?”

Posted in Culture, Uncategorized | 10 Comments

Public vs Private Management

 

Am I to understand that the differences between Public and Private Management is that Government/ Public management tend to have relavitevly short time horizons dictated by the duration of a political calendar and private management have a longer time horizon or agenda dedicated towards market developments? The question would be even in a political or public policy planning agenda would’nt the same long term planning as the private management sector be the same, so why is there a distinction between the two?

I understand that politicians have term limits but on the whole I think every organization must have some long term planning policy even after term limits have expired.

RGB

Posted in Uncategorized | 1 Comment