Wednesday, January 16, 2008

CIO Role Shifts Reporting Relationships

To keep IT relevant and better connected to the overall business strategy, shouldn't the CIO report to the CEO? The data supports a different trend. As CIOs have aligned more investments with the business, has their influence dimished? Or, is reporting relationship irrelevant in the grand scheme of things? No doubt about it ... the sand keeps shifting ...

... "The increasing prominence of the CFO in IT management signals a change in the way companies view technology strategy and deployment. " ...


Via CIO Insight: Meet Your New Boss

Labels: , , , , , , ,

Saturday, January 05, 2008

Mindset then Tools

Good advice for influencing innovation in your enterprise. Do more of this to innovate: experiment, invest resources, create burning platforms, and understand your customers' problems. ...

... "Do not train your employees on creativity techniques or bring in innovation software until you have addressed your underlying cultural issues (the mindset). " ...


Via Steve Shapiro: Innovation Mindset, Not Tools

Labels: , , , , , ,

Saturday, May 19, 2007

Effective Use of Office Politics

Guy gleans some simple truths from Penelope Trunk. Need to influence the organization on your project. Try this. ...

... "Office politics is about helping people to get what they want. This means you have to take the time to figure out what someone cares about, and then think about how you can help him or her to get it. " ...


Via Guy Kawasaki at How to Change the World: Myths of the Workplace by Penelope Trunk

Labels: , , , , ,

Thursday, May 17, 2007

Innovation: Influence of Relationships Survey

Survey delves into influence of relationships on innovation process. ...

... "Some data suggests that the quality of the relationships with decision-makers in a given organization may influence whether ideas are advanced (e.g., funded for the first time). The purpose of this study is to investigate whether this is indeed the case. " ...


Via Univ of Penn Wharton School: Survey on Idea Advancement for Knowledge

Labels: , , , , , ,

Tuesday, May 15, 2007

Project Influence: Check Your Ceiling

Need to focus your project team on getting work done: lower the ceiling. Need to get your team in a creative mood: raise the roof. ...

... " These researchers feel people under high ceilings are primed to think broadly because of the sense of freedom associated with the space, while the containment of a lower ceiling encourages people to think small and focused." ...


Via Good Morning Thinkers: The Roof

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: , , , , , , , ,

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: , , , , , , , , , , , , , , ,

Sunday, December 03, 2006

Managing from the Bottom Up

Yesterday I entered a post about Best Buy's new Results-Only Work Environment (ROWE), and how allowing employees total freedom as to where and how they work, focusing instead on results, has shown a 35% productivity improvement. Granted, this may not apply in every environment, but the premise of focusing on results over rules is sound.

What I failed to mention is that this initiative didn't come from the top. In fact, CEO Brad Anderson didn't even know about it untill it was well under way and showing tangible benefits. And that's just the way he likes it.

Kudos to Anderson for allowing the flexibility in his organization for innovation from within, and the courage to try new things. That is what a learning organization is all about.

Anyone who ever brought about major transformation (think Martin Luther King, Ghandi, Jesus), usually did it in a bottom-up approach, not by first convincing "management."

One other thing I failed to mention. While it's uncertain to what extent it played in encouraging this particular situation, a primary consultant to the Best Buy organization is Marcus Buckingham, the talent management guru and author of three of the most enlightening management books I've read (First Break All the Rules, Now Discover Your Strengths, and The One Thing You Need to Know). I'd venture to say that his influence has at least indirectly encouraged this people-focused mentality.

Labels: , , , , , , , ,

Sunday, October 08, 2006

Influence the Culture: Achieve the Goal ...

More evidence that influencing culture is the strongest lever in positioning an organization for success, however it is defined. ...

... "The chief executive knew he could not personally cause the needed innovation, but he could help create a culture and lead his managers in a way that would foster innovation - a culture that encouraged the traits of Adaptability and Involvement. " ...

Via Inc: Building a High-Performance Culture

Labels: , , , ,

Tuesday, September 26, 2006

Leading and Influencing: The Project Manager's Secret Weapon

There's an excellent article by Frank Saladis on allPM about how to lead and influence others. Topics such as boosting your credibility, practicing empathy, and maintaining organizational awareness are discussed, as well as some good tips for engaging team members and obtaining buy-in.

From my experience, these are the things a project manager needs to get right. The rest is just details.

Here's the article. Well worth reading.

Positive Leadership in Project Management – Team Building, Influencing and Leadership By Frank P. Saladis, PMP :: ALLPM Project Management :: Project Manager - Project Management - Information - Forum Manager- PM Tools - Articles -PMI

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

Wednesday, May 24, 2006

Software Selection Process; Everything You Need to Know

There's a good writeup on ProjectPerfect offering guidelines and principles for selecting software---from the gathering of internal support through the evaluation and selection process itself.

It's definitely a valuable read for anyone involved in the software selection process.

Here's just a sampling of some of the great tips in the article...

    • Tell the vendors at the start what the process for selection will be. They will appreciate knowing what the path is, and how you will reach a decision. It assists their planning as well. You will get far better service if they know when you are going to make a decision.
    • Consider an external person to do the negotiation. If negotiations are tough and the vendor feels they have been squeezed dry, it is better for the person who did the squeezing to be gone so that there are less lingering traces of animosity.
    • It is a bit like herding cats but you need to keep a single point of contact with each vendor. If vendors can see a chance to influence people at different levels you will soon find all sorts of pressures being applied to you.
    • Treat it as a team selection decision, and make sure your team know the process. If you set the path and the criteria from the start, it will help manage expectations internally.
    • It is useful to get written agreement from each vendor to comply with the process as a condition to being considered.
    • Beware the trap of having their top technical person available all through the sales cycle only to be replaced at the point of implementation by someone who has been with the company for a week. If the vendor is also involved as an implementer, have the implementation team named in the contract.
    • The purchase process should be costed into the budget just as the cost of the software and implementation are costed. There can often be many man months of effort required to manage the process and, if not done effectively, will cause major cost blowouts when the wrong software is purchased.
    • Another factor touched on a number of times is that much of the work is sequential. There will be gaps in the process – for example between requesting a demonstration, and organising the people to participate. During that lull in proceedings, other work can be done that will contribute to later activities. A software purchase can result in a very complicated schedule.
Here's the full article...

A Software Purchase Process

Labels: , , , , , ,

Monday, March 13, 2006

IT Strategy: Corporate Interests Can Influence Architecture and Career Path ...

Ancedotal evidence illustrates the impact of external forces when enterprise architecture transformation is being considered. Those forces can impact the architecture and the career path of those involved. Who said enterprise architecture wasn't risky business? Ethan Butterfield reports on the status of Massachusetts' Enterprise Technical Reference Model. ...

... "Without mentioning Microsoft by name, John Weathersby, executive director of the Open Source Software Institute of Oxford, Miss., said powerful corporate interests used their leverage to aggressively fight the state’s initiative. It demonstrates the lengths to which some will go to try to slow the adoption of open standards within public-sector IT environments, he said. " ...

IT Strategy: Corporate Interests Can Influence Architecture and Career Path: Via GCN: Loss of advocate Quinn doesn’t slow down state’s effort ...

Labels: , , , , , , ,

Sunday, February 19, 2006

Innovation: Influence Culture to Succeed ...

Jeffrey Phillips explores the innovation culture: free flow of ideas and people open to collaboration. Should compensation systems be changed to influence the culture? What works best? I've seen researchers share in the patent filing (prestige) and receive a modest reward from revenue performance (financial). ...

... "We've grown our cultures to assume that if it needs to be done, I'll do it myself. Basically, in many firms, we encourage competition and knowledge/information hoarding. " ...


Innovation: Influence Culture to Succeed: Via Innovate on Purpose: Biggest roadblock to corporate innovation ...

Labels: , , , , , ,

Thursday, February 02, 2006

IT Governance: Centralized or Distributed ...

VA CIO seeks centralized IT governance model to further influence and control software investment performance and operations ...

... "McFarland has oversight and funding powers over development projects, but not direct control. It's no secret, he says, that he favors further centralizing the IT governance structure. " ...

IT Governance: Centralized or Distributed: Via GovExec: Systems Doctor ...

Labels: , , , , ,

Sunday, October 16, 2005

Project Management Maturity Tied To Organizational, Technical Support Systems

PM Forum reported this week that PriceWaterhouseCoopers just released a survey on project management maturity. The entire study is available on the PriceWaterhouseCoopers web site

The PM Forum news brief lists the key findings. Most notably, it highlights, "Project failures are often a consequence of aspects that are organizational and over which the project managers have little influence." Another notable finding is, "The extent to which project management software is used is correlated to maturity levels."

So, before putting all the blame on project managers for your organization's project management maturity woes, take a look at how the surrounding organizational structure supports the goals at hand, and whether software and processes are set up to be enablers and not barriers.

Labels: ,

Wednesday, September 14, 2005

SOA IT Governance

Via Flashline Community Weblog: SOA needs ITG

... "But is increasing the willingness of developers to fall into line really the most effective strategy for enforcing policies, EA, SOA, or otherwise? Is that governance? " ...


Governance is making the decision on the architecture standards. Execution is about operationalizing the policies through software development. Developers should have an ability to influence the architecture roadmap so that right standards make it to governance. ... a continuous improvement cycle.

Labels: , , , ,

Tuesday, September 06, 2005

PMForum Announces Project Management Soft Skills Survey

Hello PMThinkers! Your help is needed! PM Forum is inviting readers to participate in an important survey on Project Integration Management, including managing stakeholder relations, negotiation and teamwork. It only takes 20 minutes and can help influence advancements in the field. Results will be published in PM World Today (and of course we'll post a link when it's available).

Here's the link...

PMFORUM, Connecting the World of Project Management PMFORUM Breaking News: PMFORUM READERS INVITED TO PARTICIPATE IN PROJECT INTEGRATION MANAGEMENT SURVEY

Labels: , , , ,

Tuesday, August 23, 2005

Project Managers Can Influence Without Authority

Sailing through the seas of organizational politics can be tough stuff for project managers, especially when there's a need to influence without being in a position of authority.

This white paper from Silicon.com outlines how to create a political plan and "turn potential victim scenarios into win-win political victories.

Caution: To read the white paper, you need to register, but it's a free registration.

Leading With Power from Emprend White Papers at silicon.com

Labels: ,