Monday, August 16, 2010
Suppressing Your Feminine Side May Be Bad for Business [Kimberly Wiefling]
You see, I was working in high-tech, and for over a decade I’d painstakingly stamped out any semblance of femininity in my work. After earning a masters degree in physics, a field in which women are almost as scarce as on-time schedules, I’d entered the high-tech engineering world, a profession with an equally abysmal track record of attracting women. Why on earth would I want to associate myself - in any way - with anything female in my work? I was sure I would appear weak and ineffective to my colleagues, and quite possibly my salary would decrease.
Maybe I was being a little paranoid, but until recently, I have done my best to ignore the gender issue in my career. I've steered clear of “radical feminism,” and I most certainly didn’t want to be perceived as “nurturing.” However, this past year I’ve been working on a book project, Scrappy Women in Business, which prompted me to reflect on the role of women in the workplace, and my own experience as a female in a predominantly male work environment. As a result of this, and the changing nature of the work environment, I’ve come to value what my wife’s colleague called my "feminine power." But my initial hesitancy wasn't completely unfounded, given the research on women in the workplace.
Even If I’m Not Nurturing, Chances Are People Will Think I Am
It turns out that it might not matter whether I am nurturing or not – being a woman, it’s likely that I will be perceived as nurturing by CEOs and other top executives. Catalyst, the leading global nonprofit dedicated to expanding opportunities for women in business, published a study in 2005 under the intriguing title Women "Take Care," Men "Take Charge:" Stereotyping of U.S. Business Leaders Exposed. Their research demonstrated that, although women and men often lead in similar ways, they are perceived very differently by both male and female senior executives. Regardless of the reality, women are perceived to be better at supporting and rewarding while men are perceived to be better at delegating and influencing upward.
Unfortunately, these unconscious biases impact the perception of competence and fitness for promotion, though with the growing emphasis on teamwork and collaboration these days, I’m not sure in which direction. We can, however, measure the results by observing the difference in participation of women and men at various levels in the professional world, and in the relative compensation of women and men.
Justice is Blind
Back in the 1970’s women represented only 10% of the musicians in an orchestra. That number has risen over the years to over 35%, and a Princeton University study in the year 2000 found that a big chunk of that gain was due to the switch to blind auditions. When the decision-makers can’t see whether the musician is a women or a man, more women are hired. And a study by The Anita Borg Institute on the recruitment, retention, and advancement of technical women found that women are sometimes preferentially eliminated during the resume review process, even if the interview process is unbiased. Another study specifically comparing evaluations of resumes by randomly assigning a woman’s name found that resumes bearing a woman’s name were rated lower by both women and men. (Perhaps women should use initials instead of first names on resumes, or hiring managers should have the names masked before reviewing them.)
Of course we’re all biased in many ways. All human beings are. Our assumptions and beliefs unconsciously influence our decisions, and our brains are clever enough to keep this process hidden from us so that we think we are making rational decisions based on the facts. Don’t think you’re biased? You can find out in about 15 minutes. Harvard University’s “Project Implicit®” provides a test in exchange for using your data in their studies. You will be randomly assigned one of a variety of bias studies, but you can repeat the process to experience them all. Based on experimenting with this several years ago, I found that I have a slight tendency to associate technical topics with women. Go figure!
Just Because You’re Paranoid Doesn’t Mean People Aren't Out to Get You
According to US Department of Labor statistics, only 10% of employed engineers were women at the turn of the century (2001). And while the salary differential in engineering has largely disappeared, the employment differential remains large in all but the life sciences. Even project management remains a profession with some degree of gender disparity—in both employment and pay. The 2010 PMI Salary Survey suggests that only 40% of US project managers are women (based on survey responders), and that the salaries of women project managers are “considerably lower” than that typical for men (about 10%). Karen Klein’s 2005 article “It’s a Women’s World, Too” does make the point that women are entering the project management profession at rates around double that of men, but still acknowledges that female project managers face barriers to success that are peculiar to women, such as excessive humility and a tendency towards self-criticism.
In spite of the possible risk, and because I’m past typical childbearing age (something executives admit is a real barrier for women in hiring and promotion in off-the-record true confessions), I’m less inclined to eschew my feminine qualities in my work these days. I’ve found that these qualities have become increasingly valued for their importance in delivering extraordinary business results. The incredible diversity of teams, increased focus on alliances and partnerships, the growth of open innovation, crowd-sourcing, and collaboration on a massive scale (facilitated by the internet), have all made people keenly aware of the power of group genius and the importance of a more collaborative style of leadership. I’ve noticed that the work I do as a project manager increasingly involves facilitating interaction rather than giving direction; perhaps it was always about that and I just didn’t notice because I was suppressing my nurturing side.
It turns out that female versions of leadership improve bottom line business results. Companies with higher proportion of women on their top management teams enjoyed 35% greater ROE (Return on Equity) than those with the lowest. Although I’m wary of the trap of stereotypes, in the past couple of years I began to wonder if maybe women and men really do lead in some fundamentally different way. And, with more profit at stake, I hope it’s something that can be learned by anyone, even nurturing-averse me.
There are plenty of pop psychology discussions about gender differences, including the somewhat unimaginatively titled “Are Women Better Project Managers Than Men” on the Toolbox for IT Project and Program Management Blog. Puh-LEESE! This kind of conversation is similar to my Japanese friends asking me to describe Americans. “Which one?” I ask. Like all simplistic questions, the answer to whether men or women are better project managers is, “It depends.” It depends on which woman, or which man, and which project, and in which situation. While statistics can help us understand trends in the aggregate, it’s foolish to apply that data to any specific individual or situation. Those who carelessly apply averages to individuals do both parties an injustice. Let’s not deepen the gender divide by participating in these kinds of debates. Instead, let’s look at facts.
The Road to the Top Winds Uphill All the Way
Is there gender bias at work in project management, and the business world in general? In my project leadership role I make it a practice to focus on the results produced, not the intentions of my team. Customers care about results, not intentions. I think the same approach may work well in this situation. I have no real way of knowing whether there is bias in the process, but I do know that there is a difference in the outcome – the participation and compensation of women relative to men. The measurable data from Catalyst certainly demonstrate a disparity:
• Percentage of women in the U.S. labor force: 46.3%
• Percentage of women in management, professional and related occupations: 50.6%
• Percentage of female Fortune 500 corporate officers: 15.4%
• Percentage of female Fortune 500 board seats: 14.8%
• Percentage of female Fortune 500 top earners: 6.7%
• Percentage of female Fortune 500 CEOs: 2.4%
Of course, root cause analysis is important, but the root cause of being overweight has been well known for years and still I can’t lose 5 kilograms. I personally don’t care whether the remaining disparities between women and men in project management—and the business world in general—are a result of accident, unconscious bias, or a devious plot. The causes no longer interest me. Making and measuring progress does. What’s measured tends to get attention, and frequently improves.
Good intentions or accidental bias can no longer be acceptable as a defense for inequitable results. After all, if I accidentally run you over and land you in the hospital, you’re just as injured as if I’d driven purposely in your direction with intent to harm.
The Coming Shortfall in Working Age Population in the Developed World
Based on a report by the Stanford Center on Longevity, (PDF) it looks to me like it’s in all of our best interests to make workplaces more attractive to human beings in general, and—in fields where they are under-represented—to women in particular. In a decade or two, the shortage of working-age people will be an economic crisis in some parts of the world. Japan and Germany in particular will face at least a 20 percent shortage in the coming decades (That’s why I don’t worry about women’s equality in the workplace in Japan – it’s coming!). We'll need everyone's participation if businesses are going to successfully meet the challenges facing humanity.
The Anita Borg Institute found that technical women leave their companies in mid-career at twice the rate of men. (Read more about this and the reasons why if you like.) Companies are losing women, especially at the mid-career stage. Catalyst reported that women cite four major reasons why companies lose female talent: “lack of flexibility (51%); glass ceiling issues (29%); unhappiness with work environment (28%); and feeling unchallenged in their jobs (22%). Only 5% report being downsized and only 3% say they were victims of sexual harassment.”
Of course, the workplace isn’t all that hospitable to men either. A Gallup Institute study on wellbeing concluded that 77% of all workers hate their jobs. HATE! Wow. That’s much worse than being unhappy with the work environment or feeling unchallenged in a job. I’m no expert at organizational development or the link between worker satisfaction and profit, but I’m guessing this is NOT good for project success or bottom line profits. A little more nurturing probably wouldn’t hurt any of us, or our chances for project success either.
If Being More Nurturing Will Increase Project Success, Bring on the Nurturing!
I was educated as a scientist, and if I were just looking at past data I’d conclude that expressing my so-called feminine side in the high-tech business world would put me at a bit of a disadvantage. But that’s kind of like driving while only gazing into the rearview mirror. With almost everyone hating their jobs, increased emphasis on collaboration, and the coming shortfall in skilled workers, I’m thinking that a more nurturing work environment is going to be a competitive advantage.
In fact, I’ve been experimenting with a more nurturing approach in my work in Japan, and it’s yielding excellent results: noticeably improved performance in various individuals, faster response to my requests, and more enjoyable working relationships. It’s working so well that I’m tempted to try it out on this continent. My only concern is whether it’s possible to be both scrappy and nurturing at the same time. Considering the potential 35% higher ROE, I’ll have to give it a go purely for financial reasons.
Nurturingly yours, - Kimberly
P.S. Scrappy Women in Business – Living Proof that Bending the Rules Isn’t Breaking the Law, will be available in July 2010. This book, and the associated website invite women to draw inspiration from each other’s stories. It’s just a small drop in the bucket, but it is one drop.
©2010 Kimberly M. Wiefling. All Rights Reserved. Published on the SD Forum Engineering Leadership Blog by permission of the author.
More...
Monday, July 19, 2010
Guy Kawasaki on Entreprenuership 2.0 [Shriram Natarajan]
Guy Kawasaki talked about "Entreprenuership 2.0" at UCSC extension in Santa Clara on Wednesday, July 7th. Guy Kawasaki is a managing director of Garage Technology Ventures, an early-stage venture capital firm and a columnist for Entrepreneur Magazine. Previously, he was an Apple Fellow at Apple Computer, Inc. Guy is the author of nine books including The Art of the Start, Rules for Revolutionaries, , and The Macintosh Way. He has a BA from Stanford University and an MBA from UCLA as well as an honorary doctorate from Babson College.
Alison van Diggelen of Fresh Dialogues collected the questions that the participants had enterred beforehand and asked them of Guy.
It was a wide ranging talk on Guy's opinions on various topics.
On Apple
Seeing the Mactinosh was one of the three all time (legal) highs he has experienced. Other highs were: meeting his wife and playing hockey (in no particular order).
Microsoft or Nokia could have made the iPhone. They should hire the right people and use their almost infinite cash to build products that people actually want. Microsoft or Nokia could have been the iPad maker -- had they just gotten their act together after seeing the iPhone.
Apple is a company that is dedicated to making the coolest products around. The company culture is decidedly inclined towards creating nifty, awe inspiring industrial designs. HP (to bash another company, he said) was built on two guys building oscilloscopes. They would gravitate towards stodgy businesses with safe markets. Apple's founders on the other hand could barely stay out of jail during their salad days.
On Marketing
The best way to market anything is to make sure that you have a great product. It is easy to market good stuff. It is draining to market "crap". Example: It does not take a genius to market the iPad; on the other hand marketing the "Kin" would be an uphill battle.
For a marketer today, social media awareness and presence is key. If you do not do social media today, you are not marketing. Guy opines that this is a fundamental way to do business today and in the future; to the exclusion of traditional marketing tools of focus groups and user surveys. The people are talking to you and about your company/products in various forums. All a marketer has to do is to plug into them to be successful.
On failure
Guy listed his various failures.
His job was to evangelize the Mac way of life to developers and thereby secure the market share for the better product. However Apple lost that battle overwhelmingly to Microsoft.
He does not have a net worth greater than $100 million. He has failed in terms of the movers and shakers of the valley.
He does not own a professional sports team (say the Sharks).
Despite his failure on behalf of Apple, he is best known for his role there. He went on to say that the valley is very forgiving of good faith errors/failures. There are no dynasties (continued success) or pariahs (continued failures). For entrepreneurs, the message is: there will be failures. It will not be the end as long as you learn and stay in the fight.
On investing
He would much rather invest in a couple of engineering graduates that build a product that they would like to use instead of a couple of MBAs from an A-list school with a snazzy slide deck.
He would invest in people that are hungry (living on soy sauce and rice) rather than first-25 employee/VP level person of a highly successful company. His thinking is that if you are a senior employee in a highly successful company you are accustomed to certain comforts and a certain size of bank roll. Also if you are said senior employee, you should be able to fund your ideas and not rely on venture capital.
On success
He is living proof that you can fool most people most of the time. He had no formal training in hardware or programming or computers. He was not even the earliest or most passionate Apple fanatics. He mostly got into Apple via nepotism or his familiarity with the original Mac Evangelist. He considers his key to success is his ability to grind it out. Hard work and passion. As an example, he built his twitter fan base from the ground up and by persistently posting good links.
In another context, he facetiously mentioned that the top five criteria for success were: "luck, luck, luck, luck, luck".
On Steve Jobs
Steve is one of a kind person across all time. The combination of perfectionism, sense of style and hunger to change the world is not possible. Guy would have been worth a couple of billion today had he stuck with Apple over the years. He would have to to put up with Steve for 25 years in the bargain.
In response to someone's questions about Steve Jobs' recent emails about the new iPhone's antenna: Guy thinks that this is probably just to indulge in the pleasure of seeing the response that these actions garner.
On twitter
Twitter occupied a disproportionate amount of time in the chat. He has added a quarter of million subscribers the old fashioned way: one at a time.
The rules of normal interaction seems to apply in twitter (or other social media as well):
- do not take "crap" from anyone (use tweetdeck to filter out and twitter itself to block people you do not like)
- if someone talks to you, talk back
- provide value in your interactions (good links in tweets/updates)
- provide content that is compelling to folks beyond your immediate earshot (measure content quality by the number of retweets)
- if you have provided considerable value over time, it is then kosher to do a little self promotion.
One aspect to his twitter toolkit is taken from the 24 hour news/sports channels: if you watch long enough, you will see the same stories repeat. That is an indication that you are spending too much time on the channel. It also is a tool for Guy to maximise the reach of his message.
Another axiom he has is: if you are not irritating a few people, you are not doing it right.
The only rule on twitter usage is quite simply this: if it works for you, it is right.
On entrepreneurship
Guy's advice to entrepreneurs is:
1) "Ask a woman."
Present your idea to women. They are not predisposed to destruction and could give you constructive ideas on your plan.
2) Build it and you will be funded.
A working prototype is more powerful than any powerpoint slides that you present. Any revenue stream is more powerful than spreadsheets about future monetisation. This goes for securing other funding as well.
3) Market yourself and your ideas
Establish yourself as a goto person in a niche. Build a network of people that look to you for the latest and greatest in a particular area.
4) The time is now:
This is a great time to be an entrepreneur: software is free, marketing is free and limited only by your imagination, labour is cheap, costs are low.
The silicon valley's entrepreneurial spirit is only due to the Stanford engineering department. So if any area that wants to reproduce the SiValley magic, he asks them to focus on their engineering school(s).
You can get more snippets and video at the Fresh dialogues page.
-------------------------------------------------------------------
Shriram Natarajan blogs at http://words.sangram.info/.
More...
Monday, June 14, 2010
How a Failure in Engineering Leadership Caused the Deep Horizon Oil Spill [Elizabeth J. Agnew]
Mike Williams survived the blowout on The Deepwater Horizon and he shared his story on 60 Minutes in May. What I found fascinating, in addition to how he survived, was his description of a catalyzing moment in the board room, just one of the many leadership mistakes that led to the disaster.
The rig had been working for seven years, and was just finishing up the largest drilling project to have ever been completed. The crew was preparing to close the cap of the oil well. Managers from BP were on site to celebrate a successful completion.
Here’s an excerpt from the 60 Minutes interview explaining what happened the morning of the accident:
Williams says, that during a safety meeting, the manager for the rig owner, Transocean, was explaining how they were going to close the well when the manager from BP interrupted.
"I had the BP company man sitting directly beside me. And he literally perked up and said 'Well my process is different. And I think we're gonna do it this way.' And they kind of lined out how he thought it should go that day. So there was short of a chest-bumping kind of deal. The communication seemed to break down as to who was ultimately in charge," Williams said.
The largest environmental disaster in US history starts because of chest bumping! This may not be surprising, but it certainly is ridiculous, disappointing, and embarrassing.
This highlights the importance of communication in the engineering world. I was told that the technical communications course I took senior year at Cornell would be the most important course I took. And I’ve found that to be true. What if there was a way (and there is) for those two men to have seen themselves on the same team, to have put their different ideas in a pile, then agreed on a way discuss the project that would result in the best all-around process? What if they were trained in how to maintain sight on the bigger picture, on all the forces at play, and not just on being “right”? What if the system was set up so that “being right” was the same thing as “finding the right answer together”?
Later in the segment we learn that if BP hadn’t won the argument, there probably wouldn’t have been a blowout:
In finishing the well, the plan was to … place three concrete plugs, like corks, in the column. The Transocean manager wanted to do this with the column full of heavy drilling fluid - what drillers call "mud" - to keep the pressure down below contained. But the BP manager wanted to begin to remove the "mud" before the last plug was set. That would reduce the pressure controlling the well before the plugs were finished.
"If the 'mud' had been left in the column, would there have been a blowout?" Pelley [the CBS interviewer] asked.
"It doesn't look like it," Bea [the expert; a UC Berkeley engineering professor] replied.
In all the cleanup work and ongoing efforts to stop the leaking, let’s not forget how this clusterf*** started. The way we’re working together IS. NOT. WORKING.
We need to:
- Bring real leadership and communication training to all ruff-n-tuff engineering leaders out there
- Teach leaders how to deepen their identity to Self so they get their egos out of the damn way when solving technical problems that have widespread, multifaceted implications.
- Provide technical tools and processes for the skill of communicating so that when differing ideas are put on the table there is a reliable, impersonal way to choose the best one.
We NEED to change the way we solve problems together if we are ever going to a) avoid the next mega-disaster and b) fix all the mega-disasters that are already ruining our planet.
Source: http://www.cbsnews.com/stories/2010/05/16/60minutes/main6490197.shtml
About: Elizabeth J. "Liz" Agnew works with individuals and teams of technical professionals on leadership development, collaboration, and strategic planning. She offers complimentary consultations with no obligation. Visit www.integrative-leadership.com or email liz@integrative-leadership.com to learn more.
More...
Friday, May 28, 2010
The Strong Boss [Matt Schlegel]
As I began to interact with my client’s team, I discovered that the team was very good at reacting to direction from the boss. The team understood that the boss highly valued action; therefore, they took direction from the boss and turned that into action as quickly as possible. There was very little need to highlight problems since the boss set the agenda on the important problems to address. Also, the team minimized analysis and planning activities since these activities took time and slowed progress toward action-oriented results.

The figure illustrates the problem-solving dynamics of this organization. The leadership style of the boss created a strong tendency towards action – Git ‘er Done (step 7). The team members attracted to this type of organization are those that respond well to that leadership style. For instance, once the boss set the direction, the team found little need for further conversation about the problem (step 1). By moving directly to step 2, people would organize and figure out how they would respond to the boss’s direction. Ideas would be generated (step 3), but the team would find there was little value in analyzing the ideas (step 4) and building plans (step 5) around those ideas. Rather, the team would present a promising idea (step 6) to the boss for review and approval. The boss, being the smart strategic person that she is, would be able to quickly assess the idea and approve it, modify it or send the team back to the drawing board. In that way, the team would quickly move into the Execution Phase (step 7.)
This action-oriented problem-solving style is very effective in that it produces results quickly. One way to characterize this method is as an iterative method. Another description is “Fail Fast.” This is a great methodology to try different approaches and quickly iterate to a successful solution. And, because the leader in this case was as talented as she is, the probability was high that the ideas she directed the team to pursue would be successful. The cost of this approach is that she had to spend a tremendous amount of energy setting direction, reviewing ideas and monitoring results.
In working with this team, I found that I had to start at the end with the neglected Debrief Step (step 8), reviewing with the team how they solve problems, and determine what was working well and what not so well. Out of this discussion came a list of potential problems (step 1) that the team considered important to address. Reviewing this list with the strong leader, we quickly came into agreement on the important problems. The big difference was that the problems were now the team’s problems, not the boss’s problems – the team was highly vested in solving these problems.
Working with the team, I had them spend more time on analyzing different ideas for solutions and putting together a well-thought-out plan before presenting the plan to the boss. The team put together a terrific proposal in which they genuinely held pride. They presented that to the boss who was equally pleased and gave the team permission to move forward, which the team did with considerable enthusiasm.
The strong boss learned how her personal leadership style was impacting the performance of the team. The problems she experienced with her team were as much the result of her own behavior as that of her team. By allowing the team some say in choosing the problems to solve, the team delivered great results and took far less oversight from the boss, which made the strong boss happy.
-------------------------------------------------------------------
Matt Schlegel developed his problem-solving methodology over the past decade. He continues to use the process to help companies solve big challenges, and folds those experiences into the refinement of the process. He also consults for companies developing products jointly with Asian companies. Matt can be found at www.sakinoconsulting.com.
More...
Sunday, May 2, 2010
Automate As Much As You Can [Rino Jose]
Automation is the ultimate delegation
One of the classic traits of an effective leader and manager is that they delegate work. They find ways to offload work to others so that they can focus on activities that have higher value to the organization. If the work that's delegated is challenging because it requires intelligence and insight, then this provides junior executives and managers with an opportunity to develop their skills. If, on the other hand, the work is doesn't require insight and thought, it becomes a distraction that prevents people from working on things that matter more. When this happens, the work should be delegated further.
Of course, the ultimate delegation is to simply automate the work. If you can automate any of your work, you should. Having people do work that can be done for them is a waste of time, effort, and money..
Capture what you've learned
Automation enables you to capture and use what you've learned. It's a way of documenting the lessons your team and organization have learned over time. It lets you leverage your project retrospectives, postmortems, and brainstorming meetings. It helps puts into practice what you've decided to do.
People are overloaded today. It's hard to find anyone who has the spare time to shepherd change through an organization. If, however, change can be automated -- at least in part -- the effort of realizing change can be greatly reduced.
Don't keep reinventing the wheel
If you haven't automated how you do typical tasks or how you collect status or how you manage projects, then your organization will reinvent these things differently each time. If you have multiple teams within your organization, each team will develop their own way of doing things. There won't be consistency in how anything is done.
Not only will people be wasting their time reinventing new ways for doing the same thing, but they will multiply the effort it takes you to understand the status of anything. You won't know where your team is at any given time. You won't have a clear view of where projects will land or where the bottlenecks are. Some people will give you spreadsheets. Some people will give you subjective reports with lots of handwaving. You'll have information fragments that don't fit together. When things go wrong, you'll be surprised. When you ask why, people will externalize blame. It might not be anyone's fault -- lacking consistency is really to blame.
Automate to get into a rhythm
Stop doing things differently each time. Use templates for your meetings. Document your workflows (more in an upcoming post). Use tools to automate as much as you can.
Automation helps you get into a rhythm. It provides the infrastructure for your work. It enables you to apply your skills and insight directly to your problems instead of wasting effort on figuring out how to apply them.
When you automate things, people know what to expect. Each time you perform a certain type of work, it becomes easier to do. Every team starts executing consistently. Your teams will find their rhythm and their pace. Your teams will develop organizational momentum.
Keep questioning what you automate
Building organizational momentum is great. Teams are more effective. People have greater impact. Everything runs better. However, don't forget to question what you automate.
When we learn new lessons or when the environment in which we work changes, we need to ask if we're still automating the right things. If something is no longer necessary, we should drop it. If we're missing something, we should add it. If what we're automating isn't working, we need to fix it.
We automate to make ourselves more effective, not to stop thinking. It's ok to create and use cogs to make our jobs easier; it's not ok to become one.
(originally posted on Management Revolution)
_________________________________________
Rino Jose is the principal co-founder of Lakeway Technologies, a startup that develops web apps for automating engineering and project management. He has developed software and managed software teams professionally for over 15 years. As a manager and management consultant, he has led turnarounds for multiple engineering teams. Rino holds a B.S. from U.C. Berkeley and a Ph.D. from the University of Pennsylvania with cross-disciplinary focus between Engineering, Computer Science, and the Wharton Business School.
More...
Wednesday, April 28, 2010
All in the Family [Matt Schlegel]
People who work together for many years come to know each other’s strengths and weaknesses very well. They come to accept one another and resolve to work with each other through any situation. This resolution often requires being sensitive to other’s feelings and needs and taking an approach that minimizes conflict and drama in order to keep focused on getting the job done. The downside of this approach is that people will tend to downplay problems for the sake of maintaining group harmony.
My client is a group of some of the kindest, most helpful people I have ever had the pleasure to work with. Some of the adjectives that I would use to describe this group are helpful, creative, analytical, cautious and enthusiastic. Two adjectives that I would not use to describe this group are perfectionist and assertive. Yes, this group appears to have weeded out anyone who would be unwilling to put up with the problems of others and anyone who would be assertive to the point of ruffling feathers. Not that this does not happen from time to time, but this is the exception rather than the rule.
The figure shows the problem-solving dynamic that tends to occur at the company. First, there is a great reluctance to acknowledge that there is a problem in the first place. There are no systems in place to identify and report problems to the group in a systematic way. As such, most problems are raised via the squeaky-wheel method. (Cliché: Squeaky wheel gets the grease.) Once someone has a big enough problem and shares that with the right person at the company, the helpful nature of the team kicks in. They want to solve the problem for that person. The company has great strength in creativity and analysis. They bend over backwards and find a creative solution to solve that particular problem. The team will get the thrill of moving towards solving the problem. If the problem is easy enough, it will get addressed. However, if solving the problem requires any transformative change to the way the team has historically worked, there is no one there assertive enough to move the team through that transformation. The problem is addressed to the point that the squeak stops, and the team moves on to the next squeak.
With this client, my two main jobs have been to fill the role of the perfectionist and the asserter. I have helped the company put in place the tools for collecting data, analyzing the data and reporting problems. As the data reveal the problems, the helpful nature of the team kicks in and moves the team smoothly through the problem-solving process. Then, it is my role to serve as the asserter to nudge the team through any transformative changes that will help them resolve their longer term, systematic problems.
This problem-solving framework gives me the tools to understand both the steps of effective problem solving and the interpersonal dynamics that will influence the team’s progression through those steps. It also gives me the tools to explain to my client what may be missing in their skill set that is impeding them from becoming effective problem solvers.
---------------
Matt Schlegel developed his problem-solving methodology over the past decade. He continues to use the process to help companies solve big challenges, and folds those experiences into the refinement of the process. He also consults for companies developing products jointly with Asian companies. Matt can be found at www.sakinoconsulting.com.
More...
Saturday, April 24, 2010
Meetings as Performance [Rino Jose]
When your meeting is a performance, you'll approach it differently. You'll spend time preparing for it. You'll work to make sure everyone's engaged. You'll discuss things that matter. You'll become more animated. You'll think through what you're going to say. Your meetings will have life and energy. Your meetings will have an arc and a story. Your meetings will have a point.
When you play the role of someone on stage, the attendees play the role of the audience. Certain expectations are established naturally. You are there to inspire, entertain, elucidate; they are there to watch, listen, participate -- no cell phones or e-mail during the performance. When you perform well, no one will be bored, and people (including yourself) will look forward to each meeting.
Looking at meetings this way gives you a chance to hone your presentation skills and to practice public speaking. Weekly meetings, in particular, give you a great venue to experiment with different styles and approaches. Vary what you do each week. See what works best for you. Build up your repertoire.
Another benefit to viewing meetings as a performance: it helps you lead change. When you deliver a solid performance, you connect with your audience at an emotional level. You'll find it easier to deliver tough messages and convince people to try something new. When people decide to change, it's usually based on emotion first and then rationalized afterwards. If you can get people to laugh, you can get them to change.
(originally posted on Management Revolution)
_________________________________________
Rino Jose is the principal co-founder of Lakeway Technologies, a startup that develops web apps for automating engineering and project management. He has developed software and managed software teams professionally for over 15 years. As a manager and management consultant, he has led turnarounds for multiple engineering teams. Rino holds a B.S. from U.C. Berkeley and a Ph.D. from the University of Pennsylvania with cross-disciplinary focus between Engineering, Computer Science, and the Wharton Business School.
More...