-
When IT Is Your Company’s “Piggy Bank”
February 10, 2012
-
4 Key Things a Project Manager Must Do
February 10, 2012
-
Essential Project Management
February 10, 2012
-
8 Traits of Top Project Managers - Part 1
February 9, 2012
-
Agile Project Management - Engaging Your Customer!
February 9, 2012
-
9 Tips to Avoid Traps in Project Planning
February 9, 2012
-
Why Projects Succeed - Executive Sponsorship
February 8, 2012
-
On Customer Participation in Agile Projects
February 8, 2012
-
A Project Charter for Lazy Teams
February 8, 2012
-
The Power of Process: How Bad Project Management Kills Great Ideas
February 7, 2012
Responsibility vs. Authority
July 4, 2007 | Author: PM Hut | Filed under: Role of the Project Manager
Responsibility vs. Authority
By Johanna Rothman
At a recent project management workshop, a participant asked was “I have responsibility but not enough authority to do what I need to do as a PM. How do I get things done?”
I can’t remember feeling as if I didn’t have the authority to get things done as a PM. I decided long ago, that if the company felt I needed to manage a project, then–by definition–I had the authority to do what I needed to do. I took the authority. I didn’t ask for it. I realize that doesn’t work for everyone. So here’s my take on responsibility vs. authority.
No manager ever has enough real authority to do what he or she wants to do. There’s always someone with a bigger title. (Even if you’re a CEO, you report to a board.) So even though titular authority is useful, it’s not enough.
If the project is strategically important to the organization, I can act first and ask forgiveness later. You can too. You’ll know if the project is strategically important by how many people ask about the status and what levels of people ask. The more people ask at the higher levels, the more strategic the project is.
If the project is not strategically important, why are you wasting time trying to accomplish it? In reality, if the project is important enough to the organization, you have the authority to do just about anything you need to do. (You need the self esteem to do what you need to do.) But if the project is not important enough to the organization, you can never get enough authority to do what you need to do.
Even if the project is strategically important, you may need to use your influencing skills to get done what you need. I attempt to lay the foundation for influence across the organization before I need it. Then when I need help, I can enroll other people to help me push my agenda forward. I’ve used sales, service, operations, and marketing people to help me move the project forward.
If you’ve been working in the organization for a while, you’ve probably built influence. If you haven’t paid attention to your relationships (aka politics), do so. Politics is not a dirty word. Politics is the way you can accomplish things in organizations, especially if you don’t have the resources to do it all yourself.
I see responsibility vs. authority differently than other people do. I see it more as responsibility to take authority, rather than wait for someone to give me the authority. Let me know what you think.
Johanna Rothman consults, speaks, and writes on managing high-technology product development. Johanna is the author of Manage It!’Your Guide to Modern Pragmatic Project Management’. She is the coauthor of the pragmatic Behind Closed Doors, Secrets of Great Management, and author of the highly acclaimed Hiring the Best Knowledge Workers, Techies & Nerds: The Secrets and Science of Hiring Technical People. And, Johanna is a host and session leader at the Amplifying Your Effectiveness (AYE) conference (http://www.ayeconference.com). You can see Johanna’s other writings at http://www.jrothman.com.
Article originally published at: http://www.jrothman.com/weblog/2006/02/responsibility-vs-authority.html
Related Articles
No comments yet.
feel free to leave a comment
Comment Guidelines: Basic XHTML is allowed (a href, strong, em, code). All line breaks and paragraphs are automatically generated. Off-topic or inappropriate comments will be edited or deleted. Email addresses will never be published. Keep it PG-13 people!
XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>
All fields marked with " * " are required.
- Agile Project Management
- Ask the Hut
- Certification
- Change Management
- Communications Management
- Computer Based Information Systems
- Concepts
- Corporate Transformation
- Cost Management
- Critical Chain Project Management
- Delegation
- History
- HR Management
- Implementing Project Management
- Integration Management
- Lessons Learned
- Management
- Miscellaneous
- People Issues
- PMBOK
- PRINCE2
- Procurement Management
- Program Management
- Project Lifecycle Phases
- Project Management Advantages
- Project Management Advantages
- Project Management as a Career
- Project Management Best Practices
- Project Management Charts
- Project Management Definitions
- Project Management Ethics
- Project Management for Beginners
- Project Management Guides
- Project Management Musings
- Project Management Office
- Project Management Proposals
- Project Management Templates
- Project Portfolio Management
- Project Workforce Management
- Quality Management
- Requirements Management
- Risk Management
- Scheduling
- Scope Management
- SCRUM
- Soft Management
- Time Management
- Training
- Uncategorized