Saturday, August 16, 2008

Competition: A Good Thing

Whether in business or sports, competition can bring out the best in people and teams. ...

... "That's a good thing -- a truly Olympian feat should tax a champion to his fullest. If it had all somehow seemed too easy for Phelps in Beijing, it certainly doesn't now. Phelps got to seven the hard way. " ...


Via ESPN: Phelps' Olympic Run

Labels: , , , ,

Sunday, May 04, 2008

Constraints Drive Innovation

Amazon founder, Jeff Bezos, gives his take of business innovation, which he believes it driven by constraints that forces us to create new ways to approach the situation. ...

... "I think frugality drives innovation, just like other constraints do. One of the only ways to get out of a tight box is to invent your way out. " ...


Via Business Week: Jeff Bezos

Labels: , , , , , ,

Tuesday, January 22, 2008

Leadership is Plural, and Other Insights on Engagement

A colleague referred me to an interesting Harvard Business School article on leadership from Rosabeth Moss Kanter, author of Confidence: How Winning Streaks and Losing Streaks Begin and End.

Kanter discusses the importance of creating a culture where natural leaders can emerge, which is often the case during winning streaks (and often lacking during losing streaks). This is equally true in both sports and business.

Says Kanter:
Winning teams and successful organizations become increasingly less dependent on the person called the commander-in-chief—even though, ironically, the same top managers are more likely to stay in place during winning streaks. As a pattern of success continues, many people at many levels take on leadership roles.
By creating the right environment, these managers earn the respect and confidence of their team, which in turn ensures that the management will endure. It's a virtuous circle.

Kanter goes on to explain how this forms the three cornerstones of confidence:
Leaders can multiply on the field when leaders at the top establish the support structure to make further leadership possible. Leaders construct and reinforce the cornerstones of confidence... The mission statement for leaders has three imperatives, one for each stone: to ensure accountability, cultivate collaboration, and encourage initiative.
A quote I particularly liked from the article comes from Mike Krzyzewski, coach of Duke's men's basketball team: "Leadership is plural."

For more details, read the full article below...

How Leaders Build Winning Streaks — HBS Working Knowledge

Labels: , ,

Wednesday, December 19, 2007

Project Portfolio Management PPM Tools Market Leadership Analysis

CA's PPM software (previously Niku) makes strong showing in Forrester's recent project portfolio management software market analysis. ...

... "CA is moving up in its leadership position. Priced and built to perform as well in medium-sized shops as in large installations wrote Lewis Cardin, vice president at Forrester and the report's author. He added, CA's Clarity is a strong performer across the majority of important PPM offerings. " ...


Via CA: CA Named Leader in PPM Market

Labels: , , , , , , , ,

Wednesday, November 21, 2007

CIO Skill List Deemphasize Technology

Aspiring CIOs need to develop many skills and competencies beyond the realm of technology. ...

... "Kost sees the CIO role as encompassing jobs such as venture capitalist, economist and political visionary. Leadership, relationships and business are the pillars of the role ... " ...


Via ZDNet UK: CIO 2.0

Labels: , , , , ,

Monday, November 05, 2007

Leaders Challenge the Norm

Pete GossI recently had the pleasure of hearing this person speak about his life adventures (pretty extreme) and how his lessons of leadership translate to business and life, in general. The speaker's name is Pete Goss. Pete uses a story-based presentation style to share his nuggets of knowledge, with some Brit-humor tossed in. He is a yachtsman and an inspiration.

In this talk, Pete emphasized the importance of leaders to "challenge the norm", reinforced the need to break challenges into achievable pieces, and dared his audience to dream. See Pete's book.

Labels: , ,

Sunday, October 28, 2007

A Goose Learns to Lead: Meet Gregory

I just returned from a mind-altering three-day thought leadership summit in Connecticut, hosted by Judith Glaser, author of Creating We and The DNA of Leadership (both of which are landmark books for leading change and ensuring alignment in your organization or team).

At the summit, which we collectively titled The First International Creating We Summit, we engaged in deep conversation and shared the most groundbreaking tools for facilitating real change. Present were the leading thinkers from a variety of disciplines, including organizational development, neuroscience, psychology, and more. The mutual benefits and shared learnings were so great that we realized we need to keep working together on an ongoing basis.

Rest assured, more will come from this, so stay tuned. Meanwhile, we got to preview a new video from Judith Glaser, called The Leadership Secrets of Gregory Goose. Don't let the title, or the simplicity, fool you. This animated short packs a wallop in its short 6 1/2 minutes, and is bound to generate discussion among leadership teams who watch it. The purpose of the video is to help leaders understand how sharing power releases the leadership instincts in others.

Here's a brief snippet, along with information for ordering it (the package comes with a facilitators guide and power point presentation, so you can conduct your own workshop with the video). If you order it, tell them PMThink sent you.

The Leadership Secrets of Gregory Goose by Judith E. Glaser :: Benchmark Communications, Inc.

Labels: , , , ,

Thursday, October 11, 2007

Leadership Lessons from the Movies

Anyone who knows me is aware that I have many interests, and one of my passions is film (in fact, one of these days I'm going to make good on my personal committment to write a screenplay). I enjoy all genres, especially independent and international cinema. In fact, I could probably start my own rental agency with my DVD collection (I'm, of course, also a home theater buff). No matter the film, I usually come away with some kind of lesson.

Needless to say, I found this article from Mike Hofman on Inc.com to be fascinating. In the article, Hofman highlights 10 films that have particularly relevant lessons for leaders:

- Apollo 13
- The Bridge on the River Kwai
- The Dead Poets Society
- Elizabeth
- Glengarry Glen Ross
- It's a Wonderful Life
- Norma Rae
- One Flew Over the Cuckoo's Nest
- Twelve Angry Men
- Twelve O'Clock High

You don't need to have seen the films to benefit from the lessons. Curious as to what the lessons are from each film? Read on.....

Everything I Know about Leadership, I Learned From the Movies, Planning and Strategy Article - Inc. Article

Labels: ,

Sunday, October 07, 2007

The Innovation Investment

Innovation is not free. Research projects need funding. And, it costs money for the salaries of innovation evangelists. Fresh from PDMA event, Jeffrey offers insights on the diminishing returns of operational efficiency and the need to innovate in order to grow. ...

... "Without defining an objective and consistently reinforcing the efforts of a group of people who support and enable an innovation process, most firms simply won't generate a lot of new ideas. " ...


Via Innovate on Purpose: Cheap Innovation

Labels: , , ,

Friday, September 14, 2007

Evidence-Based Management: Just the Facts

I just mentioned about Bob Sutton's excellent blog site. Well, it turns out that he and Jeffrey Pfeffer have a shared site on Evidence-Based Management (based on their book, Hard Facts, Dangerous Half-Truths, and Total Nonsense). In fact, that site also links to Sutton's blog.

There are a number of compelling studies there. I assure you, after seeing their material, you will never look at management the same way. The site also lists the 5 Principles of Evidence-Based Management (EBM):

1) Face the hard facts, and build a culture in which people are encouraged to tell the truth, even if it is unpleasant

2) Be committed to "fact based" decision making -- which means being committed to getting the best evidence and using it to guide actions

3) Treat your organization as an unfinished prototype -- encourage experimentation and learning by doing

4) Look for the risks and drawbacks in what people recommend -- even the best medicine has side effects

5) Avoid basing decisions on untested but strongly held beliefs, what you have done in the past, or on uncritical "benchmarking" of what winners do

Here's the link. I encourage you to visit it often for true leadership enlightenment.

Evidence-Based Management (EBM)

Labels: , ,

Leadership Wisdom from the Blogosphere

I just came across Bob Sutton's blog site. Along with Jeffrey Pfeffer, Sutton is the co-author of one of my favorite leadership books of all time, Hard Facts, Dangerous Half-Truths, and Total Nonsense.

Sutton's most recent book is, The No Asshole Rule: Building a Civilized Workplace and Surviving One that Isn't, another gem.

I highly recommend his blog site as well, which is full of sage (and, unfortunately, uncommon) wisdom on leadership.

I noticed his blog entry on why people become corrupt when they come to power. Someone pointed out Abraham Lincoln's quote, "Nearly all men can overcome adversity, but if you want to test a man's character, give him power."

This is a major element of my Napoleon on Project Management book as well. In fact, if I were to use the "No asshole" paradigm, I could almost sum up the book by saying that Napoleon didn't start out as an asshole, then he became one when he was at the height of his power, and by the time he realized it and changed, it was too late.

Enjoy...

Bob Sutton

Labels: ,

Tuesday, July 31, 2007

Chaos and Order: The Ingredients for Project Success

In my upcoming book, Managing the Gray Areas, there's a chapter on the need for both structure and flexibility----order and disorder. I've been exchanging some emails on the subject with Garry Booker of Project Frontier, who I'm happy to say is our newest PMThink blogger.

As it happens, Garry has been on the same path lately, and has been writing on the idea of managing outcomes (which require order) and actions (which by nature are chaotic) with the goal of achieving a chaordic organization.

A chaord (a term coined by leadership guru and former Visa CEO Dee Hock, made up from the words "chaos" and "order") refers to a state where systems and life "thrive on the edge of chaos with just enough order to give them pattern, but not so much to slow their adaptation and learning." In a chaordic organization, neither hierarchy or anarchy rule.

This is food for thought for project managers, PMO leaders, and executives.

More to come. Meanwhile, here are some links to definitions, and more about Dee Hock.

http://www.chaordic.org/definitions.html

http://en.wikipedia.org/wiki/Dee_Hock

Labels: , , ,

Thursday, July 05, 2007

Followup to Napoleon on Project Management Announced

Now that the press release is out, I'm pleased to announce the followup book to Napoleon on Project Management.

Tentatively titled Managing the Gray Areas, the book touches on many topics, such as principles, ethics, decision-making, incentives, staffing, critical thinking, and communication. For those familiar with my writings on lessons from history, rest assured that there will be plenty of lessons from history, as well as from philosophy, science, art, medicine, and business. Ultimately, it's a book about leading with humanity.

I'm also happy to announce that the book will be published by RMC Publications, the publishing arm of Rita Mulcahy's RMC Project Management. Many of you are familiar with Rita and her organization from their superb training products and services. Making this deal especially appealing was their shift in strategy toward taking on a small selection of new books (including general management and leadership books), and building products and services around them. I'm honored to be the first author to be signed to their organization under this new strategy.

I decided to write this book to address the many challenges that leaders face for which there is no easy answer. While consultants and magazine articles promote quick fixes and universal formulas, management is never that simple. In the book, I address tough questions, such as:

  • How do you balance the need for responsiveness to the customer with the need for process control within your department or team?
  • How do you maintain visibility of available resources without adding undue bureaucracy to your staff?
  • How can you manage your time effectively, yet remain available to your people?
  • Are recurring meetings effective or are they time wasters?
  • When should you share the big picture with your team and when is it prudent not to?
  • Should one person be expected to serve as a strategist and a tactician?
  • Which is better; a generalist or a specialist?
  • Which will give the biggest return; a good image or high quality?
  • What should you do when an ethical dilemma challenges your core principles?

A while back, I entered some blogs on PMThink related to these topics, based on the two-day seminar I conducted in Philadelphia with productivity consultant Jerome Jewell. Since then, I did some fine-tuning and further research and saw the need for this book.

Of course, you can expect to see more blogs related to my research as I write the book, and from time to time I may ask for your opinions and examples. Meanwhile, here's the press release from RMC Publications...

RMC Publications Signs Agreement with Best-Selling Author Jerry Manas

Labels: , , ,

Monday, June 18, 2007

The Thinking Person's Guide to Leadership

Every once in a while, I come across a website that's a goldmine of information. Fred Nickols' "Skullworks" is a good example. He has a wealth of thought provoking articles, by himself and others, in areas such as consulting, organizational development, training & performance, strategy, and more.

One article I found particularly interesting is the one on generalists vs. specialists, which happens to be one of the topics on my upcoming book (more on that soon).

As many knowledgable leaders know---and Fred Nickols is no exception---leadership and management are by no means simple. They require serious thought and carry significant responsibility. Reading just one or two of these types of articles a week can help make the difference between being a good leader and a great one.

Nickols runs a consulting company called "Distance Consulting," which focuses on helping organizations help themselves, a noble cause indeed. Here's the link to his articles.

Articles by Fred Nickols

Labels: , , , ,

Sunday, May 27, 2007

Leadership Wisdom : Pig Style

I recently came across an excellent leadership blog site called PigWisdom. It's run by Jack Hayhow, author of The Wisdom of the Flying Pig, and it's full of brief little stories and tips that can energize and enlighten any leader.

I noticed one of the chapters in Hayhow's book borrows it's title from the old adage, "Don't try to teach a pig to sing---it wastes your time and annoys the pig."

It's a cute saying, but many leaders try to do just that by having employees work out of their natural area of strength. As gurus from Peter Drucker to Marcus Buckingham have preached, this is not a wise use of our resources. Plus, it annoys the human.

Meanwhile, here's the PigWisdom blog site. Enjoy.

PigWisdom.com

Labels: , , ,

Tuesday, May 08, 2007

New CIO Role: Enhance Customer Experience

San Francisco Giants' CIO creates new role for himself. ...

SF Giants leverage information technology to improve the customer experience ...

... "Schlough's role, he says, is not to maintain operations but rather to help make the customer experience memorable. " ...


Via CIO: Customer Leadership From IT

Labels: , , , ,

Thursday, May 03, 2007

IT Org Model Seeks to Integrate Distributed Teams

Government reorganizes IT leadership in order to increase performance on key projects and initiatives. ...

... "The idea is for the governor's respected Chief Information Officer Michael Locatis to forge better collaboration and expertise-sharing among information technology teams now scattered across 20 agencies ... " ...


Via GovExec: Reorganizing for IT Project Success

Labels: , , , , , , ,

Wednesday, April 04, 2007

Who Should Manage IT Projects?

Who should manage the big projects? Professional project managers and management methods are a step in the right direction. We need to make this happen and embrace this specialization. ...

... "IT professionals should not be allowed to manage these projects. Traditionally, the IT professionals have come up through the ranks ... Leave the task of running one of these huge projects to specialists, just like everything else we do these days. " ...


Via Computerworld: Action

Labels: , , , ,

Monday, March 26, 2007

Project Sabotage

If you wanted to sabotage a project even if leadership showed support for it, what would you do? Leadership support is necessary, but not sufficient. Look out for these signals. Have a strong change plan than purely compliance-driven, unless absolutely necessary. ...

... "Confuse meetings with plausible, but pointed, questions. Be too busy to do what's expected of you, e.g., fail to supply data or other resources. Or send a subordinate in your stead " ...


Management Support: Panacea?

Labels: , , , , , ,

Wednesday, March 07, 2007

Leadership Responsibility For Achieving IT Project Success

Good set of anecdotes for the role of CIO and business leaders to sense and respond to market dynamics and project risks in order to achieve success. Success sometimes means an earlier project kill, so that investment can be shifted to new opportunities. ...

... "McCaig says governance must sit separately to retain its impartiality, because it is the compass for the business in terms of technology-based change projects. " ...


Via IT Week: Role of Leadership for IT Project Success ...

Labels: , , , ,

Monday, March 05, 2007

Periodically Recenter on Your Principles

Take a break. Reconnect with your principles. ...

... "Am I doing everything possible in my current project to hold to the principles that got me into all this? " ...


Via tompeters!: Succeed

Labels: , , , ,

IT Project EQ Change Project

For an IT project to have impact, it must affect change. For change to stick, leaders must provide support. Recent study looks at IT projects and the distance of senior leaders, such as CEOs. ...

... "We have to get good at how our organisation handles change - that's nothing to do with IT, but no IT project worth its salt doesn't affect change, said Green. " ...


Via ITPro: CEO IT Imperative

Labels: , , ,

Tuesday, February 20, 2007

Just the Facts: Evidence-Based Management

I recently read an enlightening book by Jeffrey Pfeffer and Robert I. Sutton, titled, Hard Facts, Dangerous Half-Truths, and Total Nonsense: Profiting from Evidence-Based Management.

The premise of the book is that many organizations follow the guru du jour, or manage according to the book of "someone said so." As the book points out, if we only looked at the evidence, we'd see that may of these so-called truths are anything but.

Here are some examples of the lessons the book has to offer, always supported by evidence:

1) Forced ranking of employees doesn’t work, especially where people’s performance depends on interdependence with others. Furthermore, a survey of over 200 HR professionals by the Novations Group found that forced ranking (employed by more than half of the companies) resulted in lower productivity, injustice, skepticism, less employee engagement, reduced collaboration, lower morale, and mistrust in leadership.

The authors add that, if an organization trains people right and places them in an effective system, there’s no reason why 10 or 20 percent would automatically become incompetent every year.

2) Beware of your biases as a manager. Studies of NBA drafts showed that players picked earlier and paid more were less likely to be traded and had longer careers, regardless of their actual performance.

3) In the war for talent, don't forget that bad systems cause far more damage than bad people. Try redesigning systems and jobs before judging individuals. And don’t give people objectives unless the system and staffing can support it.

4) Watch out for dangerous incentives. One organization's salespeople shipped too far ahead of schedule just to win a prize. Some salespeople would hold customer returns in the trunk of their car so they still get their commission for that period. Others opened bad credit accounts because any order counted as a good order. In another company, incentives to complete truck routes early led to increased accidents and overloading of trucks to avoid multiple trips.

5) Strategy isn’t all it’s cracked up to be. Operational execution often has a greater impact on performance. The CEO of Wells Fargo once said, “I could leave our strategic plan on a plane and it wouldn’t make any difference. No one could execute it.” In U.S. football, virtually every play is designed to go for a touchdown. Unfortunately, reality gets in the way, as do mistakes in execution.

The authors point out that time spent pursuing strategic options could be better spent solving operational problems or focusing on customer needs. Organizations such as eBay and Intel use a “learn as you go” approach, putting something in the market and tweaking accordingly. Doing the right things is important, but not at the expense of doing them effectively.

6) Many changes, including mergers and acquisitions, ERP implementations, Six Sigma programs, Business Process Reengineering, cost cutting initiatives, and others, carry risks that outweigh the benefits and can be easily misapplied. People tend to underestimate the costs and overestimate the gains.

However, if it is determined that the change is still needed, the authors suggest we:

a) Ensure dissatisfaction with the status quo (i.e. the burning platform)
b) Communicate the same message repeatedly about the need for the change
c) Express extreme confidence in the change, but listen to concerns and adjust accordingly
d) Expect setbacks, errors, and miscommunication; Learn from it and revise processes. Never point fingers.

7) Based on proven evidence, in order to gain respect and trust, leaders should:

a) Act "as-if" - Be sure to act and talk like a leader
b) Have some sense of modesty. Understand the difference between knowledge (knowing things) and wisdom (knowing what you know and knowing what you don’t know).
c) Know when to get out of the way.
d) Above all, be an architect of systems, teams, and cultures.

These are but a few of the valuable nuggets in the book. The book offers additional tips as well, plus loads of supporting stories, examples, and research. Perhaps most valuable is the chart on the various types of changes and risks associated with them. I highly recommend this book to all leaders.

Labels: , , , , , , , , , , ,

Friday, February 16, 2007

Project Controller: The Project Manager's Best Friend

Halleluyah! Finally, there's an article saying what I've been saying for years. With projects becoming more and more complex, and leadership and stakeholder management requiring more attention than project managers have time for, there's a need for another role to manage the "control" aspects of the project.

This article by Robert Wourms on Projects@Work details how organizations such as State Farm have had success doing just that. Bring on the Project Controller. As a member of the leadership team for PMI's new standards for program management and portfolio management, I witnessed first hand how valuable this role was, as it freed the program manager up to actually lead the program.

The article shows how the project controller's role can include tasks such as:

1) Educating the team on processes
2) Facilitating Planning and Control sessions
3) Developing the project schedule
4) Controlling progress
5) Tracking and analyzing costs
6) Managing Issues, Risks, and Changes
7) Documenting and delivering status information

So what's left for the project manager to do? Plenty. Supporting this, the article offers a valuable table outlining the role of the project manager vs. the program controller. Read on...

http://www.projectsatwork.com/content/Articles/221443.cfm

Labels: , , , , , , , , , , , ,

Agile Project Management: Mainstream at Last?

There's an excellent writeup on the LeadingAnswers blog site about the rise, fall, and rediscovery of Agile Project Management. I like the "Universal Lifecycle of New Technology" which outlines how ideas take flight, and then, after people inevitably misapply or overuse it, it fails, only to be resurrected successfully later with a slight twist.

I've seen this happen with a variety of non-technology processes and ideas as well, including TQM, Six Sigma, Critical Chain, PMOs, and---dare I say it---Project Management in general, all of which are currently in various stages of this lifecycle.

The article is well worth reading. For fans of Agile Project Management or those curious in the concepts, LeadingAnswers is a valuable site.

By the way, as a proponent of Geoffrey Moore's Crossing the Chasm book on marketing disruptive technology, I was also interested to see that the article has a link to a white paper titled, "Crossing the Agile Chasm."

LeadingAnswers: Leadership and Agile Project Management Blog: The Rise, Fall and Rediscovery of Agile Methods

Labels: , , , , ,

Thursday, February 01, 2007

Technology Evangelist: Leadership Role Understood

Are technology evangelists engaging and empathetic? This survey thinks so. Understand what makes these folks tick. ...

... "Technology evangelism requires a commitment to the product or service being sold, as well as to the company and its management. A technology evangelist is attached to a cause that embodies a vision, makes people feel better, generates impressive effects, initiates selfless actions, and polarizes people to act positively. Evangelism also requires specific attitudes, strategies, and techniques that are quite distinct from those found within sales or marketing environments. " ...


Via Growth Resources, Guy Kawasaki: Technology Evangelists: A Leadership Survey (PDF) ...

Labels: , , , , , , , ,

Wednesday, January 31, 2007

Project Management Excellence: Hospital Veteran Recognized

Healthcare leadership celebrates excellence. IT project manager makes the list. Users queue up for IT services. Pinch me. I must be dreaming. ...

IT project manager recognized for excellence.

... "Halle H. McNaney, 13-year Medical Center veteran, has orchestrated the roll-out with such efficiency that outpatient sites are now literally lining up at the door, waiting to be next in line for implementation - perhaps a first for the introduction of a new IT project. " ...


Via University of Rochester Medical Center: Excellence Awards Recognize Employees, Teams

Labels: , , , , ,

Sunday, January 28, 2007

Empathy: Lessons from Iwo Jima

I just saw Clint Eastwood's magnificent film, Letters from Iwo Jima, this weekend. Of course, as usual I end up looking at everything through the lense of leadership and project management lessons, which drives my wife crazy.

The film offered numerous contrasting examples of good leadership and poor leadership. The differences weren't hard to spot. Besides strategic intuition, what separated the effective leaders from the rest of the pack (on both the Japanese and American sides) was an undeniable sense of empathy (much like the film's director, Clint Eastwood, did in making the film from the Japanese perspective).

Empathy, a key component of Daniel Goleman's Emotional Intelligence, is an undervalued trait in leadership. Equally important is the wisdom to know what to do with that empathy. In the film, the leaders who showed empathy and restraint were able to make the right decisions, even in the heat of battle. Their moral compass served them well. Ironically, it was empathy that led them to be able to predict the moves of the enemy as well.

Then there were the less effective leaders who blindly followed rules, thought only of themselves, were obsessed with power, and looked at people as objects to be used. Go see the movie. You'll see leadership styles worthy of emulation, and those to avoid. Ultimately, the film is about human decency and indecency.

Labels: , , , , , , , ,

Thursday, January 25, 2007

Project Execution

Tom Peters and crew on strategy implementation through execution ... here's a chance for the project manager to shine ... Get the leadership support. Break the plan into chunks. Schedule the first chunk and resource the team. Start driving. ... Sounds simple. ...

... "Great execution happens in small manageable chunks by taking large plans and breaking them into manageable parts. Otherwise, the path to execution can seem so overwhelming, people can't conjure up the energy. " ...


Via tompeters!: Execution through Projects

Labels: , , , , , , , , , ,

Monday, January 22, 2007

Management Truths: Can You Handle It?


Jack says you can't handle the truth. But if you're ready, I highly recommend Stephen Robbins' excellent book, The Truth About Managing People... And Nothing But the Truth.

Robbins has sold over 2 million copies, and I can see why. In plain, simple language, Robbins outlines 63 truths, supported by evidence, stories, and examples. Each truth is only a few pages, so you can open the book up at almost any page and find a gem. The whole book is under 200 pages in a small paperpack format.

The 63 common-sense truths span the areas of hiring, motivation, leadership, communication, team building, conflict management, job design, performance evaluation, coping with change, and managing behavior.

A few good lessons (paraphrased):

1) Productivity usually breeds satisfaction, rather than the other way around.

2) When interviewing, don't go on traits. Instead probe about past behaviors (i.e. "Tell me about a time when you ....")

3) Put people in jobs that match their personalities.

4) Out of all the traits people have, conscientiousness is the most frequent predictor of success.

5) Specific stretch goals produce higher output than generalized goals like "do your best."

6) Not everyone wants to participate in setting their goals. It depends on their nature, ability, time available, and other factors.

7) Judge behaviors, not people.

8) There's something to be said for "looking the part of the leader."

9) Expect the best and people will deliver. Expect the worst, and people won't dissapoint.

10) Experience isn't always a good indicator of success.

11) There's no ideal leadership style. Directive or supportive styles can work in different situations.

12) Teams often create negative synergy. Beware of loafers. Be sure to identify and measure individual efforts as well as team efforts.

13) Honor the work-life balance. Give flexibility and options.

14) Beware of the quick fix. What works for one company or problem doesn't always work for another.

For many more, and further explanations and examples, read the book!

Labels: , , , , , , , , , ,

Monday, January 08, 2007

Leadership Practices: Sound Advice

There's an excellent article on leadership practices in this month's CIO Magazine from Susan Cramm, an executive coach and president of the coaching firm, Valuedance.

Cramm lists a number of things that IT leaders can do to practice "safe leadership." It seems like motherhood and apple pie, but it's a good reminder of the basics that we so easily forget. This includes the following (I've paraphrased the descriptions in parenthesis):

Foster good relationships (Learn the business and get around more among your customers.)

Forge a shared IT vision, strategy, and tactical objectives (Co-create this with your customers and other IT leaders. Agree on decision responsibilities. Understand the appropriate technical and business areas involved.)

Deliver on time, on budget (But beware of big, waterfall-style projects. Limit the number of projects. Less is more.)

Develop quality solutions (Have appropriately scaled methodologies, frameworks, policies, and tools, but beware.. It's easy to lose credibility here.)

Realize business value from IT investments (Use operational measures meaningful to the business. Measure during and after the project to insure business value is achieved. Hold business partners accountable for insuring benefits realization.)

Here's the full editorial...

Leadership Under the Influence - Editorial - CIO

Labels: , , , , , , , ,

Saturday, January 06, 2007

Leadership Style Match-Up: GE Alums

Bloomberg article contrasts CEO leadership styles - pitting the macho military style of Nardelli versus the more personable, relationship-building style of Immelt. ...

... Jack Welch on Immelt: "he said Immelt has stuff, he has real stuff. " ...


Bloomberg.com: Read

Labels: ,

Friday, December 22, 2006

The Great Innovator: Santa

Santa's innovation leadership style
Inspiration from the big guy in the red suit ... Oh, and yes, he really does exist. ...

... "Santa is an innovation master. Analyze his leadership style, and his operational insight, motivational style, ... " ...


Via Jim Carroll: Why Santa rocks at innovation! ...

Labels: ,

Thursday, December 21, 2006

Influencing People: The Project Manager's Secret Weapon

I recently attended a presentation on self-awareness and influence by Dr. Charles Dwyer, Academic Director of the Aresty Institute’s Leading and Managing People program in the Wharton School. I was so impressed with the presentation that I bought his book, The Shifting Sources of Power and Influence.

This book was a real eye-opener, and a jewel for anyone in project management. In the book, Dwyer states three major challenges we all face:

  • Dissonant Value Systems (i.e. people’s conflicting value systems, made even more visible by the advent of the media, internet, etc.)
  • Diffused Power (i.e. power being spread around in a matrix fashion, with more and more decentralization and special interest groups, etc.)
  • Limited Resources (We all face a limited set of resources, made even more challenging by our lack of a mindset geared towards accepting tradeoffs, or a good mechanism to guide operational priorities)

Sound like any projects you know?

Dwyer goes on to caution that public statements, such as vision, mission, organizational values, etc. may be useful for articulating the values of the leadership or giving people a sense of structure, but do not in themselves change anyone’s value systems. Many leaders assume they can use these statements to change people’s value systems to match organizational values, but this is a myth.

What is needed instead is the ability to influence others by getting them to change their behavior to match your values. To do this, have a clear picture of what you want the unit to look like; set specific, measurable objectives; and insure that people have a way of achieving those objectives.

According to Dwyer, some tried and true methods include asking people for help, offering or implying something in return, or influencing indirectly (i.e. working through someone else who’s in a better position to influence).

Dwyer points out five guidelines for influencing people (I’ve paraphrased them):

  1. Insure they have adequate capability (Do they know what to do, have the competence and self-confidence to carry it out?)
  2. Address their perception of “Potential Value Satisfaction” (WIIFM or “what’s in it for me”)
  3. Address their perception of the probability of value satisfaction (i.e. Do they trust you? You must build trust through visible examples.)
  4. Address their perception of cost (Do this by giving them alternatives or a sense of options, and helping them understand the costs and implications.)
  5. Address their perception of risk (Try to assume or distribute some of the risk. Don’t ignore it.)

These are the five things everyone weighs in their mind when someone attempts to influence them. In essence, the five elements (four of which are perceptions) make up an equation for behavior. We can influence people’s behavior by addressing this equation (I’ve paraphrased for simplicity):

Behavior=Capability + (Perceived Value * Trust factor) – (Perceived cost and risk)

These are just some of the gems of wisdom in Dwyer's book. He offers reams of memorable examples, often with a humorous style. With 90% of a project manager's job being communication (including influence), I highly recommend Dwyer’s book for project managers, or anyone in a leadership position for that matter.

Labels: , , , , ,