Facebook Pixel
Searching...
English
EnglishEnglish
EspañolSpanish
简体中文Chinese
FrançaisFrench
DeutschGerman
日本語Japanese
PortuguêsPortuguese
ItalianoItalian
한국어Korean
РусскийRussian
NederlandsDutch
العربيةArabic
PolskiPolish
हिन्दीHindi
Tiếng ViệtVietnamese
SvenskaSwedish
ΕλληνικάGreek
TürkçeTurkish
ไทยThai
ČeštinaCzech
RomânăRomanian
MagyarHungarian
УкраїнськаUkrainian
Bahasa IndonesiaIndonesian
DanskDanish
SuomiFinnish
БългарскиBulgarian
עבריתHebrew
NorskNorwegian
HrvatskiCroatian
CatalàCatalan
SlovenčinaSlovak
LietuviųLithuanian
SlovenščinaSlovenian
СрпскиSerbian
EestiEstonian
LatviešuLatvian
فارسیPersian
മലയാളംMalayalam
தமிழ்Tamil
اردوUrdu
Results Without Authority

Results Without Authority

Controlling a Project When the Team Doesn't Report to You
by Tom Kendrick 2012 288 pages
3.83
3k+ ratings
Listen
Listen

Key Takeaways

1. Project control depends on process, influence, and metrics

"Project processes are bumpers that enable the project leader to keep the ball rolling toward the final objective."

Process provides structure. Well-defined processes, when properly applied, act as guardrails that keep projects from veering off course. They establish a common framework for planning, execution, and monitoring, ensuring consistency and clarity across the team.

Influence drives engagement. Project leaders, especially those with limited formal authority, must rely on their ability to influence team members, stakeholders, and sponsors. This involves building relationships, understanding individual motivations, and aligning project goals with personal interests.

Metrics offer insight. Carefully selected metrics provide objective data on project progress, performance, and potential issues. They enable informed decision-making and help project leaders identify areas requiring attention or intervention.

  • Key processes: Change management, risk assessment, status reporting
  • Influence techniques: Active listening, negotiation, reciprocity
  • Essential metrics: Schedule variance, cost performance, quality indicators

2. Establish clear project objectives and secure sponsor commitment

"Control of your project demands that you get the WBS right as soon as is practical."

Define the vision. A clear, compelling project vision serves as a north star, guiding decisions and motivating the team. It should articulate the project's purpose, expected outcomes, and value to the organization.

Secure sponsor support. The project sponsor plays a crucial role in providing resources, removing obstacles, and maintaining organizational alignment. Establish a strong relationship with your sponsor and gain their commitment to:

  • Manage the project environment
  • Actively participate in project initiation
  • Support robust project management processes
  • Validate and revalidate project baselines
  • Protect the project from unnecessary changes
  • Facilitate organizational learning

Document objectives. Create a comprehensive project charter that clearly outlines scope, priorities, constraints, and success criteria. This document serves as a reference point throughout the project and helps manage stakeholder expectations.

3. Collaborate on planning to enhance team buy-in and control

"Collaborative planning builds on the project charter, initial scoping, and other documentation outlined in Chapter 5."

Engage the team. Involve team members in the planning process to leverage their expertise, increase commitment, and identify potential issues early. This collaborative approach enhances the quality of the plan and fosters a sense of ownership among team members.

Break down the work. Develop a detailed Work Breakdown Structure (WBS) that clearly defines all project tasks and deliverables. This process helps:

  • Identify dependencies and potential risks
  • Allocate resources effectively
  • Establish realistic timelines
  • Create a foundation for progress tracking

Assign ownership. Delegate responsibility for specific tasks and deliverables to team members. This not only distributes the workload but also increases accountability and motivation.

  • Use techniques like RACI charts to clarify roles and responsibilities
  • Match tasks to individual skills and interests when possible
  • Ensure each team member understands their commitments

4. Use metrics to measure progress and guide decision-making

"What gets measured gets done."

Select meaningful metrics. Choose a balanced set of metrics that provide insight into project health and progress. Avoid overwhelming the team with too many data points; focus on metrics that drive desired behaviors and support project objectives.

Establish baselines. Set clear performance baselines at the start of the project. These serve as reference points for measuring progress and identifying deviations from the plan.

Monitor and analyze. Regularly collect and analyze metric data to:

  • Track progress against plans
  • Identify trends and potential issues
  • Support data-driven decision-making
  • Provide objective evidence for project status reports

Key metric categories:

  • Schedule performance (e.g., milestone completion, critical path analysis)
  • Cost management (e.g., earned value metrics, budget variance)
  • Quality indicators (e.g., defect rates, customer satisfaction scores)
  • Risk metrics (e.g., number of identified risks, mitigation effectiveness)

5. Maintain effective communication throughout the project

"Communication is the one absolutely undisputed responsibility owned by the project leader, regardless of project type, other responsibilities, or authority."

Tailor communication. Adapt your communication style and methods to suit different audiences and situations. Consider cultural differences, communication preferences, and the level of detail required by various stakeholders.

Be proactive. Don't wait for problems to escalate before communicating. Regularly update stakeholders on project progress, achievements, and potential issues. This builds trust and allows for early intervention when needed.

Leverage multiple channels. Utilize a mix of communication methods to ensure your message reaches all team members and stakeholders:

  • Formal channels: Status reports, project meetings, presentations
  • Informal channels: One-on-one conversations, team-building activities, casual check-ins
  • Written communication: Email updates, project documentation, instant messaging
  • Verbal communication: Face-to-face discussions, phone calls, video conferences

Practice active listening. Encourage open dialogue and pay attention to both verbal and non-verbal cues. Use techniques like paraphrasing and asking clarifying questions to ensure mutual understanding.

6. Adapt leadership style to team dynamics and project needs

"Projects succeed because the people who work on them care, and collaboration and open discussion lead to caring."

Assess team needs. Recognize that different teams and individuals may require different leadership approaches. Factors to consider include:

  • Team experience and expertise
  • Project complexity and duration
  • Organizational culture
  • Geographic distribution of team members

Balance authority and collaboration. Find the right mix of directive and participative leadership styles. While some situations may require quick, decisive action, fostering a collaborative environment generally leads to better outcomes and increased team engagement.

Build relationships. Invest time in getting to know your team members personally. This helps build trust, improves communication, and makes it easier to motivate and influence team members.

Leadership techniques to consider:

  • Management by wandering around (MBWA)
  • Situational leadership
  • Servant leadership
  • Transformational leadership

7. Manage scope changes rigorously to stay on track

"Scope creep and other general scope meanderings can easily render a project unmanageable."

Establish a change control process. Implement a formal procedure for evaluating and approving scope changes. This process should:

  • Require clear documentation of proposed changes
  • Assess the impact on project timelines, resources, and objectives
  • Involve key stakeholders in the decision-making process
  • Maintain a record of all change requests and their outcomes

Educate stakeholders. Help project sponsors and team members understand the importance of scope management. Explain how uncontrolled changes can impact project success and the potential trade-offs involved in accommodating new requests.

Prioritize changes. When changes are necessary, work with stakeholders to:

  • Distinguish between "must-have" and "nice-to-have" additions
  • Consider the value vs. impact of each proposed change
  • Explore alternative solutions that minimize disruption to the project
  • Negotiate adjustments to project constraints (time, resources, quality) when accepting significant changes

8. Address conflicts and performance issues promptly

"To control a project, you need to know what is happening."

Monitor team dynamics. Stay attuned to interpersonal relationships and potential sources of conflict within the team. Early detection allows for proactive intervention before issues escalate.

Confront problems directly. When conflicts or performance issues arise, address them promptly and professionally. Use a structured approach:

  1. Gather facts and perspectives from all involved parties
  2. Identify the root cause of the problem
  3. Collaboratively develop potential solutions
  4. Agree on a course of action and follow-up plan

Provide constructive feedback. Offer specific, actionable feedback to team members. Focus on behaviors and outcomes rather than personal characteristics. Balance negative feedback with recognition of positive contributions.

Escalate when necessary. If unable to resolve conflicts or performance issues within your authority, involve appropriate stakeholders (e.g., functional managers, HR) while maintaining professionalism and respecting confidentiality.

9. Conduct regular project reviews to maintain alignment

"Reviews held at the end of each development iteration for projects using agile methods are both more frequent and less formal, and their agendas will exclude some of these items. Nonetheless, they serve essentially the same purposes."

Schedule periodic reviews. For longer projects, conduct formal reviews at least every six months or at significant milestones. These reviews serve multiple purposes:

  • Evaluate progress against project objectives
  • Identify and address emerging risks or issues
  • Realign team focus and motivation
  • Celebrate achievements and recognize contributions

Prepare thoroughly. Gather and analyze relevant project data, including:

  • Performance metrics and trends
  • Status of key deliverables and milestones
  • Budget and resource utilization
  • Risk and issue logs
  • Stakeholder feedback

Involve key stakeholders. Include team members, sponsors, and other relevant parties in the review process. This ensures a comprehensive assessment and helps maintain organizational alignment.

Take action. Use review outcomes to inform decision-making and course corrections. Document agreed-upon actions, assign responsibilities, and follow up to ensure implementation.

10. Recognize and reward team contributions to boost motivation

"Even if you are not initially successful, don't give up. Continue to collect information on the issues and plan to propose the changes again later on."

Understand motivators. Recognize that different individuals are motivated by different factors. Some common motivators include:

  • Recognition of achievements
  • Opportunities for professional growth
  • Increased responsibility
  • Work-life balance
  • Financial incentives

Use a mix of recognition methods. Employ both formal and informal recognition techniques to acknowledge team and individual contributions:

  • Formal: Performance awards, bonuses, promotions
  • Informal: Verbal praise, written thank-you notes, public acknowledgment in meetings

Be timely and specific. Provide recognition promptly when deserved, and clearly articulate the reason for the recognition. This reinforces desired behaviors and performance.

Foster a culture of appreciation. Encourage team members to recognize each other's contributions. This builds a positive team dynamic and reinforces collaborative behavior.

Recognition ideas:

  • Celebrate project milestones with team events
  • Feature team member achievements in project communications
  • Provide opportunities for high-performing team members to present to senior leadership
  • Offer professional development opportunities as rewards for exceptional performance

Last updated:

FAQ

What's Results Without Authority about?

  • Project Management Focus: The book by Tom Kendrick focuses on managing projects effectively without formal authority over team members.
  • Strategies for Control: It provides strategies for gaining control through processes, influence, and metrics, applicable in various project environments.
  • Collaboration and Influence: Emphasizes the importance of collaboration, influence, and communication in achieving project goals.
  • Practical Techniques: Offers practical techniques and tools, such as the RACI model and earned value management, to help project leaders maintain control.

Why should I read Results Without Authority?

  • Enhance Project Management Skills: Essential for improving project management skills, especially in environments with limited authority.
  • Real-World Application: Valuable for project managers in matrix organizations or cross-functional teams, providing actionable insights.
  • Comprehensive Framework: Covers initiation, planning, execution, and closure, ensuring a holistic understanding of project management.
  • Builds Influence and Relationships: Teaches how to build influence and maintain relationships, crucial for project success.

What are the key takeaways of Results Without Authority?

  • Influence Over Authority: Influence can be more effective than authority in managing teams, emphasizing trust and relationships.
  • Effective Communication: Clear and effective communication is crucial throughout the project lifecycle.
  • Control Through Process: Establishing clear project processes is vital for maintaining control, especially with limited authority.
  • Managing Scope Changes: Rigorous management of scope changes is necessary to avoid project failure.

How does Results Without Authority define project processes?

  • Structured Approach: Project processes provide a structured approach to managing projects, serving as a substitute for authority.
  • Importance of Buy-In: Gaining team buy-in for these processes enhances commitment and cooperation.
  • Examples of Processes: Discusses specific processes like change management, risk management, and quality management.

What is the RACI model mentioned in Results Without Authority?

  • Definition of RACI: A responsibility assignment matrix that clarifies roles and responsibilities within a project.
  • Enhances Clarity: Ensures everyone understands their specific roles and who to consult for decisions.
  • Facilitates Communication: Allows for a structured approach to discussing responsibilities, essential for project success.

How does Results Without Authority address project scope management?

  • Scope Definition: Emphasizes the importance of clearly defining project scope during the initiation phase.
  • Change Management Process: Outlines a disciplined process to handle scope changes effectively.
  • Consequences of Poor Scope Control: Warns that failing to manage scope can lead to project failure.

What is earned value management (EVM) as described in Results Without Authority?

  • EVM Overview: A project management technique that integrates scope, schedule, and cost to assess project performance.
  • Key Metrics: Uses metrics like Planned Value (PV), Actual Cost (AC), and Earned Value (EV) to identify variances.
  • Benefits of EVM: Helps detect issues early and take corrective actions, revealing adverse trends early in the project timeline.

How can I maintain control during project execution according to Results Without Authority?

  • Status Collection: Regular status collection is crucial for staying informed about project progress and issues.
  • Use of Diagnostic Metrics: Recommends using diagnostic metrics to assess project performance continuously.
  • Informal Communication: Maintaining informal communication helps understand the context behind the data.

What strategies does Results Without Authority recommend for project planning?

  • Collaborative Planning: Emphasizes the importance of collaborative planning to ensure team understanding and agreement.
  • Defining Deliverables: Clearly defining project deliverables and success criteria is essential for maintaining control.
  • Engaging Stakeholders: Engaging stakeholders during planning helps align project goals with organizational objectives.

How does Results Without Authority suggest handling project risks?

  • Risk Monitoring: Ongoing risk monitoring is necessary throughout the project.
  • Contingency Planning: Advises developing contingency plans for significant risks and revisiting them periodically.
  • Visibility of Risks: Keeping risks visible encourages proactive management and awareness.

What is the importance of capturing lessons learned in Results Without Authority?

  • Continuous Improvement: Essential for continuous improvement in project management practices.
  • Future Project Planning: Helps inform future project planning and decision-making.
  • Team Reflection: Conducting a retrospective analysis allows the team to reflect and solidify their learning.

What are the best quotes from Results Without Authority and what do they mean?

  • “Control of a moving vehicle involves the use of the steering wheel, the accelerator, and the brake.”: Illustrates the need to balance processes, influence, and metrics in project management.
  • “What gets measured gets done.”: Emphasizes the importance of metrics in driving project performance.
  • “Projects succeed because the project team cares about them.”: Highlights the significance of team engagement and commitment in achieving project goals.

Review Summary

3.83 out of 5
Average of 3k+ ratings from Goodreads and Amazon.

Results Without Authority receives mixed reviews. Many readers find it valuable for its insights on project management without formal authority, praising its comprehensive coverage and practical advice. Some highlight its usefulness for new project managers and its focus on relationship-building. However, others criticize it for being too detailed, repetitive, or not delivering enough on its promise of managing without authority. The book's waterfall approach and extensive metrics discussion are seen as drawbacks by some. Overall, it's generally recommended for traditional project management contexts.

Your rating:

About the Author

Tom Kendrick is a seasoned project management professional with over 35 years of experience. He has held senior positions at major corporations like Hewlett-Packard and Visa. Kendrick is a certified Project Management Professional (PMP®) and has authored several well-respected books on project management. His expertise particularly shines in the areas of project risk identification and management. Kendrick's extensive background in both practical project management and writing has established him as a respected authority in the field, making his insights valuable for both new and experienced project managers.

Other books by Tom Kendrick

Download PDF

To save this Results Without Authority summary for later, download the free PDF. You can print it out, or read offline at your convenience.
Download PDF
File size: 0.42 MB     Pages: 13

Download EPUB

To read this Results Without Authority summary on your e-reader device or app, download the free EPUB. The .epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.
Download EPUB
File size: 3.11 MB     Pages: 12
0:00
-0:00
1x
Dan
Andrew
Michelle
Lauren
Select Speed
1.0×
+
200 words per minute
Create a free account to unlock:
Requests: Request new book summaries
Bookmarks: Save your favorite books
History: Revisit books later
Ratings: Rate books & see your ratings
Try Full Access for 7 Days
Listen, bookmark, and more
Compare Features Free Pro
📖 Read Summaries
All summaries are free to read in 40 languages
🎧 Listen to Summaries
Listen to unlimited summaries in 40 languages
❤️ Unlimited Bookmarks
Free users are limited to 10
📜 Unlimited History
Free users are limited to 10
Risk-Free Timeline
Today: Get Instant Access
Listen to full summaries of 73,530 books. That's 12,000+ hours of audio!
Day 4: Trial Reminder
We'll send you a notification that your trial is ending soon.
Day 7: Your subscription begins
You'll be charged on Feb 25,
cancel anytime before.
Consume 2.8x More Books
2.8x more books Listening Reading
Our users love us
50,000+ readers
"...I can 10x the number of books I can read..."
"...exceptionally accurate, engaging, and beautifully presented..."
"...better than any amazon review when I'm making a book-buying decision..."
Save 62%
Yearly
$119.88 $44.99/year
$3.75/mo
Monthly
$9.99/mo
Try Free & Unlock
7 days free, then $44.99/year. Cancel anytime.
Settings
Appearance
Black Friday Sale 🎉
$20 off Lifetime Access
$79.99 $59.99
Upgrade Now →