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
Project Management for Non-Project Managers

Project Management for Non-Project Managers

Projects fail when business owners disappear. Turn vague needs into accepted results.
by Jack Ferraro 2012 256 pages
3.54
28 ratings
Listen
Immersive
V2.3
Amazon Kindle Audible
Try Full Access for 3 Days
Unlock listening & more!
Continue

Key Takeaways

Own the customer role: project teams cannot deliver benefits on your behalf.

You are part of delivery. A functional manager is not merely a department head lending staff to a project. As the customer, the manager explains how the business works, tests whether the proposed output is useful, helps users adopt it, and ensures that promised benefits are measured. The sponsor may secure funding and champion the vision, but often cannot manage the daily decisions that determine whether the change works in practice.

Make the partnership real. Ferraro describes a software project where the customer and provider disagreed about when delivery was complete and a $120,000 invoice should be paid. Testing was finished, but the customer wanted to see the application working in production. Their contract did not clearly settle the issue. The conflict exposed competing incentives and a weak working relationship, not just a technical problem.

Analysis

The customer role is a form of stewardship: someone must connect the project’s output to the people and operations that are supposed to benefit. That responsibility cannot be delegated entirely to a sponsor or project manager because neither necessarily owns daily adoption. The invoice dispute also shows why trust alone is insufficient. Shared goals need practical supports, including clear acceptance rules, decision rights, and measures of value. The model works best when the functional manager has enough authority and time to act. Where those are missing, the organization must address the capacity problem rather than quietly expecting one manager to carry the change.

Name the business need before anyone falls in love with a solution.

Begin with the problem. A project mission should state what the work will produce, who will use it, and what measurable result that use should achieve. That is more useful than a vague promise to modernize a system or improve satisfaction. Ferraro’s call-center example narrows a broad complaint into a testable aim: a new call-routing approach for global centers intended to cut average call time by 15 percent within three months.

Trace needs to work. The functional manager helps compare current and desired business processes, then checks that requirements support the future process. Requirements should be specific, measurable, achievable, realistic, and time-bound or traceable. For example, replace “fast report” with a defined response time and conditions. A requested feature that cannot be linked to a process or benefit may be unnecessary scope.

Analysis

This approach makes project definition an exercise in disciplined translation. Executives often speak in outcomes, users describe frustrations, and technical teams think in features. A precise mission gives those groups a shared object to examine. Process maps help because they make hidden handoffs and assumptions discussable rather than leaving them in people’s heads. There is a useful tension here: measurable targets create accountability, but they can also narrow attention to what is easiest to count. A strong business case therefore pairs operational measures, such as response time, with the broader benefit the change is meant to create.

Demand a living plan, not a polished schedule built backward.

Plan before scheduling. Ferraro’s practical sequence moves from objectives and scope to deliverables, resources, activities, estimates, dependencies, schedule, and budget. Starting with a software-generated timeline skips the hard questions: what is being created, why, and who will accept it? A deadline imposed first can produce attractive dates that conceal unrealistic assumptions. Plan what can actually be delivered within the available time and resources, then make the trade-offs explicit.

Keep detail near. A useful plan can show the next 30 days clearly while treating work further out as provisional. The team learns as it works, so the plan should be refined in cycles rather than frozen at the start. Short-term commitments also test whether the team can execute. Project tools can organize and report information, but cannot make weak estimates or incomplete scope reliable. Vendor statements of work should connect deliverables to measurable acceptance and payment terms.

Analysis

The emphasis on a short, revisable horizon is a sound response to uncertainty. A plan is not valuable because it predicts every future event; it is valuable because it makes current assumptions visible and supports correction. The distinction between planned work and actual work also matters. If dates are routinely edited to match reality, slippage disappears from view and management loses the chance to respond early. A 30-day plan is a diagnostic, not a guarantee. Its usefulness depends on candid reporting, realistic capacity, and decisions that can change scope, resources, or timing when evidence changes.

Manage tangible deliverables, not a blur of busy activities.

Define the outputs. A deliverable is a tangible, verifiable work product, such as a process map, specification, software interface, or training package. Activities are the actions taken to create it. Ferraro calls the organized hierarchy of these outputs a deliverable structure, also known as a work breakdown structure. It links the project mission to concrete work, clarifies who creates each item, and identifies who accepts it. Stakeholders can then judge progress by completed work rather than by a list of meetings and tasks.

Make acceptance visible. Each major deliverable needs an objective and clear criteria for completion. The structure should include more than technology: business analysis, integration, testing, communication, and project management work may all be essential. In Ferraro’s website example, a technically complete portal would not guarantee adoption by wholesalers with long-standing phone relationships. Communication and user readiness were part of the work, not decorative extras.

Analysis

Deliverable-based planning turns an abstract promise into inspectable evidence. It also gives teams room to decide how to do the work while preserving agreement about what must result. That distinction can reduce micromanagement and make accountability fairer: people can be judged against an agreed output instead of an endless activity log. The method has a limit, however. Some benefits, such as trust or improved judgment, do not arrive as a single artifact. Such outcomes need observable indicators and ongoing evaluation, or a project may mistake finished documents for finished change.

Sequence the work visibly so dependencies expose decisions before delays.

Tell the work’s story. A flow diagram shows which deliverables can proceed in parallel, which depend on earlier work, and where a decision or approval is needed. The functional manager need not build the technical schedule, but should help stakeholders agree on the major relationships. In Ferraro’s fulfillment project, a partner’s technical specifications were needed before the team could finalize requirements. The partner controlled that input, making the dependency both a planning fact and a risk.

Use dependencies to challenge assumptions. A learning-system project had 16 high-level work areas and an 18-month implementation target, yet stakeholders could not see what had to happen before a pilot. The team identified the deliverables essential to a 10-course pilot, then mapped their sequence. That visible logic helped explain why the pilot could not begin immediately and revealed where work could start in parallel.

Analysis

A simple dependency map is a boundary object: technical specialists, managers, and users can discuss the same picture without needing identical expertise. It reveals more than timing. It surfaces who controls a prerequisite, what decision is outstanding, and what rework may follow if work starts too soon. The map should remain simple enough to invite correction. A diagram that appears authoritative can conceal disputed assumptions just as easily as a spreadsheet can. Its value comes from the conversation around it, especially when stakeholders are allowed to challenge both the sequence and the reasons behind it.

Turn risk into a quantified conversation before uncertainty becomes an issue.

Describe a possible event. A project risk is an uncertain future event that could affect scope, schedule, cost, or quality. An issue is what the team faces after such an event occurs. A useful risk statement identifies the event and its likely impact, so stakeholders can judge probability, severity, and response. Ferraro recommends embedding risk thinking throughout planning, not treating it as a separate spreadsheet exercise.

Choose a response. Teams can accept, avoid, transfer, or mitigate a risk, then monitor it as conditions change. In a mortgage workflow project, the team worried that loan volume might exceed system capacity. Before launch, it tested the system at five times the projected volume. When loan volume later surged, that preparation gave the team a clearer view of capacity needs. Open discussion also exposed a separate risk: support staff lacked enough experience with the new technology.

Analysis

Risk discussion is useful when it changes a decision, a plan, or an allocation of responsibility. Naming uncertainty does not mean predicting the future perfectly; it means refusing to let assumptions masquerade as facts. The mortgage example also shows why risks should be revisited as opportunities arise. A test that seemed optional can become valuable when a potential failure would undermine the project’s benefits. Not every risk deserves an elaborate model, though. A lightweight probability and impact judgment may be more honest and actionable than numerical precision unsupported by evidence.

Make change stick through coalitions, visible wins, and uncomfortable decisions.

Change needs internal leadership. A functional manager must connect the project to organizational strategy, build support across peers and affected groups, communicate why the change matters, and address resistance. Ferraro describes a system upgrade that could not justify its cost without major process changes. The manager responsible for the main user department resisted changes that threatened established authority, and her influence in the project diminished. Her strong operational skills could not substitute for willingness to lead the transformation.

Create momentum without declaring victory. The book recommends early, measurable progress, with meaningful wins appearing within roughly 30 to 45 days and further progress visible every 30 to 60 days. But a pilot is not proof that an enterprise-wide change is complete. Lasting adoption may require training, revised measures, and changes to organizational systems. Keep urgency alive while embedding the new practice into everyday work.

Analysis

This view treats resistance as information about power, identity, and perceived loss, not merely stubbornness. A future-state process can redistribute work and status, so leaders must make those trade-offs explicit rather than hiding them behind technical language. Coalitions help because authority in matrixed organizations is distributed across expertise and relationships. Yet the case of the resistant manager deserves care: career consequences are not a reliable measure of whether resistance was unreasonable. Good change leadership should invite evidence about who bears the costs, provide fair participation, and distinguish self-protection from legitimate operational concerns.

Protect throughput by limiting multitasking and trimming process theater.

Busy is not the same as productive. In matrix organizations, people are often spread across competing projects. Ferraro argues that frequent task switching delays completion and increases errors, while unclear priorities intensify the problem. He recommends judging a multi-project system by valuable projects completed, or throughput, rather than by how fully each employee appears utilized. That requires a transparent way to decide what work comes next and to protect focus.

Trust evidence over status colors. In the Standish Group figures cited for 2009, 32 percent of projects succeeded under the report’s definition, 44 percent were challenged, and 24 percent failed. Ferraro warns that red, amber, or green reports can hide reality: in one program, all 10 subprojects were reported green even as the integrated schedule slipped by three months. Controls and tools help only when they expose problems instead of rewarding reassuring appearances.

Analysis

This takeaway challenges a familiar management reflex: maximizing visible utilization can make work look efficient while delaying completed outcomes. The more useful unit of attention is the flow of work through a constrained system, alongside quality and realized value. The warning about status colors is equally important because reporting systems shape behavior. If red status triggers blame, people have incentives to preserve green rather than surface trouble. The cited project statistics are historical and should not be treated as current forecasts. Their lasting value is diagnostic: organizations need measures that encourage truthful signals and timely intervention.

Analysis

Ferraro’s central argument is that project success depends on an often overlooked translator: the functional manager who understands the operating business and must make that knowledge usable to a temporary project team. The book therefore recasts project management from a specialist’s toolkit into a relationship between provider and customer. Its practical tools, including mission statements, process maps, deliverable structures, dependency diagrams, and risk discussions, all serve that same purpose: turn divergent assumptions into visible decisions.

The book is strongest when it insists that outputs are not benefits. A system can pass technical acceptance and still fail to change work, serve customers, or produce the promised savings. This distinction connects project control to organizational learning: prototypes, short planning horizons, and honest feedback help people revise their understanding before expensive commitments harden. The recurring stories make abstract process failures tangible, especially the contract dispute, the hidden process redesign, and the falsely green program schedule.

The framework also places a substantial burden on functional managers. It assumes they can make time, influence peers, and speak candidly about political trade-offs, even while maintaining daily operations. That is often the hardest constraint, not a lack of templates. Organizations should therefore treat customer participation as planned capacity, clarify decision authority, and reward surfacing bad news rather than punishing it. Otherwise, the book’s call for ownership risks becoming a demand for unpaid extra labor.

Some claims and figures reflect the book’s 2012 setting, particularly the cited 2009 project-success statistics and its account of project-management practice. These are best read as evidence of the author’s concern, not timeless rates. The more durable contribution is a diagnostic habit: ask whether work is tied to a business need, whether its outputs can be accepted, whether prerequisites are understood, and whether uncertainty changes action. That is a portable discipline, not a promise that planning can eliminate surprise.

Summary in 30 Seconds
Projects should begin with a measurable business need, defined users, and criteria for acceptance. Build plans from outputs, resources, dependencies, estimates, and budget rather than imposed dates. Review the next 30 days in detail and keep later work provisional. Quantify risks, test likely capacity, and limit multitasking. Visible progress within 30 to 45 days helps adoption, but lasting change also requires training, revised measures, and sustained leadership.
Contains spoilers

Last updated:

Report Issue

Review Summary

3.54 out of 5
Average of 28 ratings from Goodreads and Amazon.

Project Management for Non-Project Managers receives mixed reviews. Some readers find it practical and useful, especially for those new to project management. They appreciate the relatable examples and transferable approaches. However, others criticize it for being bureaucratic at times and containing outdated information. Positive aspects include the emphasis on practical project management and the concept of earning the right to change project status. Critics argue that some content reinforces negative stereotypes about project managers. Overall, the book is seen as a good basic text for non-project managers, despite its flaws.

Your rating:
4.21
73 ratings
Want to read the full book?

Glossary

provider/customer relationship

Project delivery partnership

The working partnership between the project manager or team providing project outputs and the functional manager or business customer receiving and using them. The customer contributes business knowledge, clarifies needs, reviews deliverables, and supports adoption. The provider contributes project-management capability and organizes the work. The relationship is meant to align both parties around measurable business benefits.

project organization

Temporary project structure

The temporary organization assembled for a particular project. It includes the project team that creates deliverables, the customer team that uses them and pursues benefits, advisory participants who must be consulted, and sponsors who provide authority or funding. It is broader than the project team alone and is intended to connect delivery work with the people affected by the change.

deliverable structure

Hierarchy of project outputs

A structured breakdown of the tangible work products a project must create. Ferraro uses this term for what is commonly called a work breakdown structure. Unlike an activity list, it organizes outputs such as analyses, process maps, software, and training materials. It links the project mission to responsibilities, acceptance criteria, estimates, and later scheduling.

progressive elaboration

Iterative planning and refinement

The repeated refinement of a project plan as the team learns more about the work. Near-term activities receive specific detail, while distant work remains less defined until it approaches. This recognizes that estimates and requirements can change as deliverables are developed and used. Planning and execution proceed in cycles rather than as a single, completed phase.

scope creep

Uncontrolled scope expansion

The gradual addition or alteration of project requirements without sufficient review of their effects on cost, schedule, or other work. It can grow from rushed or unclear requirements, informal customer requests, changing business conditions, or features that are not linked to the business process. Managing it requires clear scope, traceable requirements, and an agreed change process.

SMART model

Requirements quality checklist

A checklist Ferraro applies to requirements: specific, measurable, attainable, realistic, and time-bound or traceable. It helps customers examine whether a requirement has a clear meaning, can be verified, is feasible under actual constraints, and can be connected to timing and downstream design or testing. The book stresses that vague words such as “fast” are not sufficient acceptance criteria.

brain writing

Structured written risk generation

A facilitated technique for generating project risks in which participants independently write risk statements, pass them to others, and build on one another’s ideas. The written format encourages contributions from people who may speak less in a group discussion. Statements identify a possible future event, its outcome, and the project objective it could affect.

critical path

Longest schedule-driving sequence

The sequence of dependent project activities with the longest total duration from project start to completion. A delay to an activity on this path delays the planned completion date unless the schedule is changed. Activities on other paths may have slack, meaning some delay can occur without moving the overall project finish.

red, amber, or green (RAG) ranking

Color-coded project status

A status-reporting approach that labels a project or work area red, amber, or green to signal perceived health. Ferraro cautions that the rating can be subjective and shaped by fear of blame. A green label is not evidence of progress unless it is supported by actual deliverables, credible schedule information, and visible resolution of risks.

About the Author

Jack Ferraro, PMP, is an experienced project management professional and president of MyProjectAdvisor®. With 22 years of experience in managing complex projects and working with project teams, Ferraro has established himself as an authority in the field. His company provides consulting, coaching, and training services in project management. Ferraro's expertise is reflected in his book, which aims to make project management principles accessible to non-project managers. His approach combines practical insights with theoretical knowledge, drawing from his extensive experience in the industry. As a certified Project Management Professional (PMP), Ferraro brings credibility and depth to his teachings in project management.

Download PDF

To save this Project Management for Non-Project Managers summary for later, download the free PDF. You can print it out, or read offline at your convenience.
Download PDF
File size: 0.31 MB     Pages: 15

Download EPUB

To read this Project Management for Non-Project Managers 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.36 MB     Pages: 19
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...