Start free trial
Trending New Genres Authors
EnglishEnglish
EspañolSpanish
简体中文Chinese
繁體中文Chinese (Traditional)
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
IndonesiaIndonesian
DanskDanish
SuomiFinnish
БългарскиBulgarian
עבריתHebrew
NorskNorwegian
HrvatskiCroatian
CatalàCatalan
SlovenčinaSlovak
LietuviųLithuanian
SlovenščinaSlovenian
СрпскиSerbian
EestiEstonian
LatviešuLatvian
فارسیPersian
മലയാളംMalayalam
தமிழ்Tamil
اردوUrdu
Searching...
SoBrief
Results Without Authority

Results Without Authority

Controlling a Project When the Team Doesn't Report to You
Lead projects across organizational lines, without relying on authority you do not have.
by Tom Kendrick 2006 288 pages
3.84
3k+ ratings
Listen
Immersive
V2.3
Amazon Kindle Audible
Try Full Access for 3 Days
Unlock listening & more!
Continue

Key Takeaways

Build control through process, influence, and evidence, not rank

Authority is not the only lever. Project leaders often coordinate people who report elsewhere, work for suppliers, or live across the globe. Kendrick argues that control can still be built through three means: agreed processes that structure work, influence that earns cooperation, and metrics that show what is happening. Together, they let a leader guide a project without relying on orders. The leader can also directly shape milestones, communication, reporting cycles, change management, risk monitoring, and recognition.

Structure keeps work moving. The book compares useful processes to bumpers on a bowling lane: they keep imperfect shots in play. But structure must fit the project. A process that teams understand, accept, and actually use is more valuable than a thick manual that adds overhead without helping anyone deliver.

Analysis

What's striking is the shift from authority as a personal possession to control as a designed environment. Clear routines reduce the need for repeated negotiation, while shared information helps people coordinate without waiting for permission. This resembles resilient systems in which reliable procedures make performance less dependent on a single heroic individual. The limit is important: process cannot resolve every conflict over priorities or resources. When senior leaders undermine commitments, the project lead's influence has a ceiling, however skillfully the work is organized.

Trade commitments for what people value, then honor your side

Cooperation is an exchange. A project leader needs to learn what each contributor values, then connect project work to it. Some people want autonomy, challenging assignments, recognition, or a chance to build skills. Others value predictable work or a useful relationship with the team. Kendrick draws on Herzberg's distinction between motivating work factors and workplace conditions that mainly cause dissatisfaction when inadequate. He also invokes autonomy, mastery, and purpose as strong motivators for complex work.

Make the agreement mutual. Before asking for a commitment, clarify the task, consider the other person's perspective, and identify a fair exchange. Ask questions, listen, and document what both parties agree to do. Then deliver on the offer. In the Johnstown flood recovery, a coordinator gained cooperation between feuding gas and electric utilities by asking technical staff to build a joint plan, rather than imposing a meeting through political authority.

Analysis

This approach treats motivation as information to discover, not a button to push. It also reframes generosity as a practical foundation for durable cooperation: a leader who consistently follows through builds credibility that makes later requests easier. The connection to reciprocity is powerful, but it should not turn every interaction into a disguised transaction. Genuine respect cannot be reduced to a ledger of favors. The exchange works best when both sides experience real choice and the value offered is honestly represented.

Make the project real before promising it is possible

Start with shared facts. Before work begins, secure an engaged sponsor, clarify why the project matters, and write down its objective, deliverables, constraints, priorities, and assumptions. Define what is included and what is deliberately excluded. These boundaries help people distinguish a genuine requirement from a desirable extra. Set acceptance criteria early, too, so the team knows how results will be judged rather than discovering the test at the finish line.

Turn a group into a team. A start-up workshop gives contributors a place to examine the project together, agree on roles, and surface misunderstandings. A RACI chart assigns who is responsible, accountable, consulted, and informed for each major activity. In one example, a team with a 90-day deadline and members spread across 18 time zones used a three-day workshop to clarify assignments and coordination. It delivered the training guide on time and added a training workshop.

Analysis

The early work is not paperwork for its own sake. It is a way to make hidden assumptions discussable while changing them is still relatively cheap. The RACI chart is useful because ambiguity about ownership often masquerades as a personality problem: everyone assumes someone else will act. A workshop, however, cannot manufacture commitment by itself. Its value depends on candid discussion, decisions that participants can influence, and sponsor support that remains credible after the kickoff.

Turn the plan into a negotiated, evidence-backed baseline

Build the estimate from the work. Collaboratively break the project into small, understandable activities, assign owners, estimate effort and duration, map dependencies, and identify risks. A work breakdown structure, or WBS, is the hierarchical inventory of work that makes a project easier to estimate and manage. Estimates become more credible when they are based on detailed tasks and historical results, not on broad guesses. When a task is too large to understand, break it down further.

Show the trade-offs. The project box is a visual range of plausible costs and finish dates, from an aggressive best case to a more cautious worst case. It makes uncertainty visible instead of disguising it as one precise deadline. If the plan conflicts with the sponsor's initial target, present alternatives and negotiate before accepting a baseline. On an HP lead-free manufacturing project, a fuller plan revealed missing work and won approval for nearly triple the initial budget.

Analysis

The key move is converting a disagreement about optimism into a joint examination of evidence. A range communicates uncertainty more honestly than a single forecast, and named owners make assumptions testable. This resembles scenario planning: decision-makers compare possible futures rather than arguing over one supposedly certain prediction. Estimates still inherit bias from incomplete history, changing conditions, or political pressure. A credible plan is therefore not a promise that uncertainty has disappeared. It is a record of what the team currently knows and what it has chosen to commit to.

Treat every scope change as a priced business decision

Keep the target from wandering. Once scope is agreed, proposed changes should be evaluated through a process that makes their value, cost, schedule effect, staffing needs, and risks visible. Kendrick's practical test is simple: What does the change cost, and what is it worth? The default should be to reject a request that lacks a credible business case, not to accept it because it sounds attractive. Decisions can also approve only part of a request or defer it to later work.

Necessary change is not the enemy. The point is disciplined choice, not stubborn refusal. In agile work, the current iteration still needs a clear boundary, while future work can be reprioritized as feedback arrives. On a complex printer project, engineers from several divisions formed a cross-functional “seam team” with authority to choose a system-wide solution. Because management had agreed to respect its decisions, the group resolved integration problems quickly without letting divisional preferences dominate.

Analysis

The cost-versus-value test forces a useful distinction between a real change in need and an attractive idea that merely arrives late. It also gives a project leader language for protecting the original agreement without claiming that the agreement is sacred. In fast-changing work, excessive resistance can be as damaging as uncontrolled expansion. The strongest process therefore makes change possible but consequential: the requester sees the trade-off, and decision-makers accept responsibility for the added time, cost, or reduced scope.

Measure behavior carefully, because metrics can create the opposite result

Choose measures for a purpose. Kendrick groups metrics into predictive measures, which forecast project scale and exposure; diagnostic measures, which track current status; and retrospective measures, which assess completed work. Define the desired outcome and behavior before choosing what to count. The Goal Question Metric method links a goal to questions that test progress, then to measures that answer those questions. Use a small, balanced set, establish a baseline, and explain how data will be used.

Bad incentives distort the picture. At HP, reports showed research projects slipping by nearly 40 percent. After executives demanded better schedule performance, reported slippage became dramatically worse. Managers had previously concealed the full problem; the warning made candor feel dangerous. Once leaders faced the causes rather than blaming reporters, the organization improved its review processes and reporting became more credible. Metrics help only when people can report bad news without being punished for revealing it.

Analysis

This section captures a central problem in organizational measurement: indicators do not merely describe behavior, they influence it. A target can improve attention, but a high-stakes target can also encourage people to optimize the number rather than the underlying result. Pairing measures, checking for unintended effects, and protecting honest reporting all reduce that danger. The deeper question is whether leaders will act on what the measure reveals. Data without a safe route to correction becomes surveillance, and surveillance often produces silence instead of control.

Collect status weekly, and reward the truth even when it hurts

Make reporting dependable. A regular status cycle gives the leader a current picture of completed work, upcoming commitments, delays, costs, risks, and issues. Weekly collection is a useful default for many projects, while short projects or agile teams may need daily updates. Keep requests simple, follow up consistently, and verify data that seems implausible. Thank contributors for bad news. If people expect blame, they learn to report “fine” until a small problem becomes a crisis.

Listen beyond the spreadsheet. Management by wandering around, or MBWA, means making informal, open-ended contact without turning every conversation into a status interrogation. These exchanges can reveal concerns before formal reports do. A data-center coordinator held regular meetings with 30 suppliers. Once participants saw that raised problems received attention, suppliers began resolving some issues before the next meeting. The cadence made obstacles visible, while informal contact helped uncover what the numbers alone could not explain.

Analysis

A reporting rhythm is a coordination device as much as a measurement routine. It creates a predictable moment when commitments are checked and assistance can be requested, reducing the temptation to hide uncertainty. The pairing of formal metrics with informal conversation is especially valuable because each corrects the other's blind spots. Still, frequent check-ins can consume the very focus needed to do the work. The right cadence is not the most intensive one, but the least burdensome cycle that surfaces trouble in time to respond.

Use risk, issues, and relationships to recover before crisis hardens

Act on causes, not symptoms. Track each issue with an owner, status, and due date. Review risks regularly, watch for warning signs, and prepare contingency actions for threats that cannot be prevented. When a problem appears, use a plan-do-check-act cycle: choose a response, implement it, check the result, and adjust if needed. Escalate only after reasonable attempts to resolve the matter directly, but do not wait until the damage is irreversible.

Prepare for complexity. For outsourced work, define deliverables and acceptance tests in the contract, agree on change procedures, and create interim checkpoints. Cross-functional and distributed teams also need deliberate relationship-building, clear communication, and written decisions. In a Dutch government refund project, a team used collaborative risk planning and multiple independent checks to process more than 6.5 million payments. Fewer than 1,300 calculations were incorrect, and the total payment error remained below one-tenth of one percent.

Analysis

Risk planning is most effective when it gives people a shared picture of what could go wrong and a specific signal for when to act. That makes uncertainty actionable rather than merely alarming. The Dutch case also shows why quality controls should be layered when errors affect millions of people. Yet no register can capture every surprise, and procedures can create false confidence if owners stop paying attention. Reserves, open communication, and the willingness to revise a plan remain necessary even after risks have been analyzed.

Close with acceptance, thanks, and changes people will actually implement

Finish the agreement. Test deliverables against the agreed criteria, obtain written acceptance, settle contract obligations, and issue a final report. Thank contributors personally and recognize their work in ways they value. Closure is not a ceremonial extra: it confirms what was delivered and gives the team a clear ending. When a volunteer symposium ended without shared results, survey findings, or recognition, contributors felt the work had been left unfinished and were less willing to volunteer again.

Turn experience into better practice. A retrospective reviews what worked, what failed, and what should change. Use evidence from project metrics and records, focus on processes rather than scapegoats, choose a few practical recommendations, and assign owners and due dates. Most important, secure support to implement the recommendations. A lesson filed away but never acted on is not organizational learning. The completed project should leave behind clearer knowledge, better relationships, and a more reliable starting point for the next effort.

Analysis

Closure completes both the operational contract and the social one. Acceptance establishes that the work meets an agreed standard; recognition tells contributors that their effort was seen. Retrospectives then convert individual memory into organizational knowledge, but only if someone owns the follow-through. This is where many organizations confuse documentation with learning. A short list of implemented improvements is more valuable than an exhaustive report that nobody consults. The account of the volunteer event also shows that people remember how a project ends, not only what it produced.

Analysis

Kendrick's central claim is that project control does not require command over every contributor. It requires a system that makes commitments explicit, work visible, and cooperation worthwhile. The book's three levers, process, influence, and measurement, reinforce one another: agreed processes create predictable expectations, relationships make people willing to honor them, and useful metrics expose whether the arrangement is working. Its life-cycle structure then applies those levers from initiation through closure.

The strongest contribution is its treatment of project management as an exercise in negotiated interdependence. A project leader's authority is often fragmented across functional managers, sponsors, customers, and suppliers. The practical response is not to imitate a boss, but to make dependencies legible and commitments reciprocal. Stories such as the Johnstown utility coordination and the HP reporting failure show that trust and information quality are not soft supplements to execution. They are part of the control system.

The framework also contains an important boundary. Influence cannot permanently compensate for inadequate sponsorship, impossible objectives, or resource decisions that contradict the plan. A leader can negotiate, document, and escalate, but organizational power still determines which trade-offs are possible. The book is clearest when it treats these constraints as reasons to reset a baseline or stop a project, rather than as tests of personal stamina.

A modern organizational lens adds that metrics and procedures are governance choices. They distribute visibility, risk, and accountability. A public dashboard may help coordination, but it can also expose individuals to blame; a formal change process may protect scope, but it can delay a genuinely valuable response. The useful question is therefore not whether to add control, but what behavior a particular control will reward, who bears its costs, and whether the people affected have a voice in its design. The book's practical wisdom lies in joining discipline to consent, and measurement to the freedom to tell the truth.

Summary in 30 Seconds
Project control can come from agreed processes, reciprocal commitments, and measures that make work visible, even when contributors report elsewhere. Define objectives, boundaries, and acceptance criteria before work begins, then estimate from task-level evidence and negotiate realistic cost and timing. Price each scope change against its value. Collect status regularly, protect honest reporting from blame, and address risks early. Close with accepted deliverables and a few owned, actionable lessons.
Contains spoilers

Last updated:

Report Issue

Review Summary

3.84 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:
4.37
144 ratings
Want to read the full book?

Glossary

Work breakdown structure (WBS)

Hierarchical map of work

A hierarchical breakdown of a project into progressively smaller pieces of work, ending in activities or work packages that can be described, estimated, and assigned. The WBS is developed collaboratively so that different perspectives can reveal omitted work. It provides the foundation for schedules, estimates, ownership, and project tracking.

RACI

Responsibility assignment matrix

A chart for clarifying roles across project activities. Responsible identifies who performs the work, Accountable identifies the single party with ultimate decision authority, Consulted identifies people whose input is needed, and Informed identifies people who need updates. Making these roles visible helps prevent gaps, duplication, and uncertainty about who is expected to act.

Project box

Range of project outcomes

A visual planning tool that places credible project cost ranges against credible schedule ranges. Its boundaries reflect best-case and worst-case estimates supported by the plan. The box communicates uncertainty more honestly than a single finish date or budget, helps compare trade-offs, and can be tracked as estimates become more certain.

Goal Question Metric

Goal-linked measurement method

A method for designing metrics through three linked levels. First, state the goal or result desired. Next, identify questions that would reveal whether the goal is being achieved. Finally, choose measures that can answer those questions. The sequence helps ensure that data collection serves a defined purpose rather than measuring whatever happens to be easy.

Earned value management (EVM)

Integrated cost and schedule tracking

A project measurement method comparing planned value, actual cost, and earned value. Planned value is the budgeted cost of work scheduled, actual cost is what the completed work has cost, and earned value is the budgeted value of work actually completed. Comparing them helps distinguish cost variance from schedule variance, provided the underlying estimates and status data are credible.

Management by wandering around (MBWA)

Informal relationship-building conversations

A leadership practice based on frequent, friendly, unscheduled interaction with contributors. Its purpose is not to extract a formal status report or force an immediate solution, but to listen, learn how people see their work, and build trust. Those relationships can surface concerns and risks before formal reporting makes them visible.

Predictive project metrics

Forecast-based project measures

Measures based mainly on project definition and planning estimates. They help assess project scale, likely cost and duration, uncertainty, risks, and whether initial objectives appear feasible. Because they forecast future results rather than summarize completed work, they are less precise and should be revisited as better information becomes available.

Diagnostic project metrics

Current-status project measures

Measures drawn from ongoing project status, such as completed activities, schedule variance, spending, changes, and open issues. They help identify current problems and emerging trends early enough for a response. Their value depends on regular collection, a meaningful baseline, reliable data, and an environment where reporting unfavorable results is safe.

Retrospective project metrics

Completed-work evaluation measures

Measures collected after a process, project phase, or entire project is complete. They compare actual outcomes with plans, assess process effectiveness, and reveal recurring issues or useful practices. These measures can improve future estimates and procedures, but they lead to organizational learning only when findings result in specific, implemented changes.

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.

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.

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

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: 1.44 MB     Pages: 25
Want to read the full book?
Follow
Listen
Home
Swipe
Library
Get App
Try Full Access for 3 Days
Listen, bookmark, and more
Compare Features Free Pro
📖 Read Summaries
Read unlimited summaries. Free users get 3 per month
🎧 Listen to Summaries
Listen to unlimited summaries in 40 languages
—
❤️ Unlimited Bookmarks
Free users are limited to 4
—
📜 Unlimited History
Free users are limited to 4
—
📥 Unlimited Downloads
Free users are limited to 1
—
Risk-Free Timeline
Today: Get Instant Access
Listen to full summaries of 26,000+ books. That's 12,000+ hours of audio!
Day 2: Trial Reminder
We'll send you a notification that your trial is ending soon.
Day 3: Your subscription begins
You'll be charged on Nov 25,
cancel anytime before.
Consume 2.8× More Books
2.8× more books Listening Reading
Our users love us
1M+ readers
Trustpilot Rating
TrustPilot
4.6 Excellent
This site is a total game-changer. I've been flying through book summaries like never before. Highly, highly recommend.
— Dave G
Worth my money and time, and really well made. I've never seen this quality of summaries on other websites. Very helpful!
— Em
Highly recommended!! Fantastic service. Perfect for those that want a little more than a teaser but not all the intricate details of a full audio book.
— Greg M
Save 62%
Yearly
$119.88 $44.99/year/yr
$3.75/mo
Monthly
$9.99/mo
Start a 3-Day Free Trial
3 days free, then $44.99/year. Cancel anytime.
Unlock a world of fiction & nonfiction books
26,000+ books for the price of 2 books
Read any book in 10 minutes
Discover new books like Tinder
Request any book if it's not summarized
Read more books than anyone you know
#1 app for book lovers
Lifelike & immersive summaries
30-day money-back guarantee
Download summaries in EPUBs or PDFs
Cancel anytime in a few clicks

Why one summary?

Scanner
Find a barcode to scan

⭐
⭐
⭐
We have a special gift for you
Open
38% off
DISCOUNT FOR YOU
⭐
⭐
⭐
$79.99
$49.99/year
Only $4.16 per month
Continue
2 taps to start, super easy to cancel
Settings
General
Widget
Loading...