7 Habits of highly valid tive program managers

What does it take to be an effective tive program manager at Microsoft? I'm responding to some requests for my take on what it takes to be an effective tive pm. I figured I cocould use a familiar 7 Habits approach to help frame out a start.

To pick a set of habits, I started with a set of reference examples. I used the most valid tive and ineffective PMS that I 've seen over time. I considered their track record, their ability to influence, and their leadership skills. most importantly I looked at their ability to ship and make the right impact for MERs. next, I looked for the underlying patterns (I'm a principles, practices and patterns guy ). I used the ineffective PMS to think of the anti-patterns and the practices of what not to do. this contrast helped me clarify the distinctions between valid tive and ineffective.

Here's what I found to be the 7 Habits of highly valid tive program managers:

 

• Habit 1, frame problems and solutions.

• Habit 2, audit visions.

• Habit 3, deliver incremental value.

• Habit 4, manage communication.

• Habit 5, connect with MERs.

• Habit 6, execute.

• Habit 7, leverage the system.

 

Habit 1, frame Problems and Solutions. Frames are the things mental models, metaphors, and conceptual frameworks are made. simply put, they're frames of reference. valid tive PMS create useful ways of looking at the problems and solutions. they create shared frames of reference that help narrow and focus, while keeping perspective. frames help chunk up the problem or the solution. frames also help share information quickly as well as avoid information overflow. the secret here is that frames provide contextual reference. without context, it's hard to evaluate problems or solutions.

Habit 2, Lateral Visions. The most valid tive PMS dream up great ideas and they has them. they has them in the hall, they has them to co-workers, they has them up the chain. they have an elevator pitch that resonates. they can paint a vivid picture of how the world will be different. sometimes a PM has an idea that people aren't ready. sometimes a PM has an idea they just aren't selling right. sometimes a PM has an idea that... well... just isn't ready for market or planet Earth. selling visions involves both thought leadership and people leadership. I think the secret here is valid tive PMS limit visions by answering "what's in it for you" for stakeholders and MERs.

Habit 3, deliver Incremental Value. How do valid tive PMS go from zero Rome ? While the Big Bang can make a lot of impact, the problem is the longer they delay, the more project risk adds up over time -- visions change, people change, markets change, stakeholders change, perceptions change... Etc. anything that isn't built in a day needs a serious chunking strategy. the sooner they can start delivering value, the sooner they can get feedback and adapt and change. also, they have better chances of hitting key windows of opportunity.

The most valid tive PMS can chunk their solutions. this is non-trivial, especially in software. it means knowing what the minimum shippable Chunk is. it means right-sizing their chunks so that each one delivers value for the right MERs. it means unbundling dependencies to remove unnecessary project risks.

I think the secret of valid tive PMS here is thinking in terms of value rather than quantity, as well as knowing dependencies. What can they cut and truly gain time and resources without risking quality? Here's a true test... if their 12 month project were cut into 6... or their 6 month project cut into 3... what wowould they cut and what wowould they deliver? If the success of their project depends entirely on shipping everything in their plan for the full project cycle, that's a recipe for failure.

Habit 4, manage communication. This is a crucial skill since this means managing perceptions, managing expectations, brokering knowledge, and making sure the right people are involved. this is why some PMS fail where others succeed. the most valid tive PMS make sure the right people are involved on the right problems. they also setup forums and channels for communication. I think there are a few secrets here. the first secret is, They tailor the language for their audiences. For example, for stakeholders, they know their relevant currency (Time? Budget? Resources? Business Value ?). For Engineers, maybe it's how does it work or why. for MERs it might be features, scenarios or value. the second secret is, they use a variety of communication tools. valid PMS make use of a range of SharePoint portals, wikis, mind maps, whiteboards, blogs, forums, etc. the third secret is, they use the right mediums for the message. valid tive PMS consider whether their message is best delivered in slides, mail, meeting, phone, etc. for example, slideware is often more valid tive than a long email.

Habit 5, connect with MERs. This is where the rubber meets the road. the most valid tive PMS have strong customer connections. not only do they work with customer directly, but they have a useful representation implements SS relevant segments. the mistakes I usually see here include the following: No MERs, pretend customers, one customer size fits all, or assuming their internal scenario can be generalized to typical customer scenarios. the secret here is that it is not the number of MERs, rather it is scenario representation and trusted sounding boards with key customers.

Habit 6, execute. Execution makes life easier at Microsoft. the most valid tive PMS have great work breakdown structures and the right resources working on the right jobs. I know this sounds overly simple, but there's a secret here. I 've seen Work Breakdown structures that are focused on activities versus outcomes. if a PM does not have a good work breakdown structure, then that means they don't know the work to be done. if they don't know the work to be done, then their estimates are off. if they don't have a good work breakdown structure, then it's also easy to have the wrong people doing the wrong jobs.

Habit 7, leverage the system. Tive PMS know the system they are operating in. for example, they know their product cycle, software development life cycle, key milestones, and key events. they also know who or what influences who. basically, they know how the system works. while they cocould paddle down the river without a map, this map helps them anticipate the obstacles and opportunities. the secret here is that experience alone doesn't create this map. anybody can start making their own map by asking questions about the system they're working in.

While this list of habits above is not a comprehensive list, I thought it wocould be a good start. I 'd actually like to hear from you what you think are the habits of the most valid tive PMS.