Categories
- Agile (6)
- Architecture (1)
- art (2)
- Big Data (1)
- books (11)
- Cars (1)
- Change (9)
- common sense (3)
- Contracting (1)
- Cool (1)
- Design (5)
- development (1)
- emotions (3)
- entrepreneurship (2)
- google (1)
- great quotes (2)
- happiness (1)
- innovation (3)
- IT (8)
- IT Architecture (3)
- Knowledge Transfer (2)
- leadership (3)
- Lean (1)
- links (1)
- literature (1)
- lyrics (1)
- management (9)
- Media (1)
- Negotiating (1)
- networks (1)
- people (5)
- Personal Improvement (8)
- planning (5)
- productivity (3)
- Programming (1)
- Project Management (23)
- Projects (1)
- psychology (3)
- Requirements (5)
- Risk (2)
- scrum (2)
- strategy (6)
- struggle (1)
- summer (1)
- teams (5)
- Test Automation (3)
- thinking (5)
- Training (2)
- Travel (1)
- waterfall (4)
Tag Cloud
Agile
Architecture
art
Big Data
books
Cars
Change
common sense
Contracting
Cool
Design
development
emotions
entrepreneurship
google
great quotes
happiness
innovation
IT
IT Architecture
Knowledge Transfer
leadership
Lean
links
management
Media
Negotiating
people
Personal Improvement
planning
productivity
Programming
Project Management
Projects
psychology
Requirements
Risk
scrum
strategy
teams
Test Automation
thinking
Training
Travel
waterfall
Thinking Strategically as a PM
Posted by Rich Crowley in Project Management, strategy
I once managed a project that involved launching a new product for a financial services company. The initial few weeks of the project were very chaotic.
Product development had not fully defined the specs of the product they wanted to launch which prevented the administration area from fully understanding what it would take to do their jobs once the product was launched. IT needed requirements from both sides before it could provide a meaningful contribution but the product development folks wanted to understand what systems limitations to consider before finalizing the product spec. Sprinkled in were various other challenges like compliance constraints, overlaps with another product launch, summer vacation season and a very tight timeline.
As the PM, I found one of the key contributions I made to this project was ensuring all stakeholders were operating with the same information. Overcommunicating was the risk but it was better than the alternative of having the various areas doing their thing with incorrect information about what the other teams were doing.
I had regular meetings with a group that included the sponsor and the key managers from the affected business units. These were all senior people. In these meetings, I always went in prepared with an agenda of those things that were really hurting us and where I needed these managers to help by influencing their teams in ways I could not.
The result of the project was a successful product launch in spite of the frenetic activity of the project over a 10-12 week period. Towards the end of the project, the sponsor provided feedback to me that although I had done a decent job of managing the project, he didn’t feel I thought strategically enough during the project execution. He felt my meetings with him and his peers focused too much on tactical issues that he didn’t feel were his to resolve.
I’ve thought much about this feedback since but still struggle with this notion. I respect that there is value in getting senior managers engaged at the strategic level within a project and in that respect his assessment was correct. However, I also believe it is equally important for senior stakeholders to work with the PM to help resolve tactical issues that people reporting up through their chain of command aren’t able to resolve on their own.
In subsequent projects, my approach has been to try to deal with such senior people by tying those tactical concerns I have to the strategic objectives the project is trying to accomplish that the sponsor is most concerned about.