40 Project Management Quotes Worth Repeating in 2026

Most lists of project management quotes are padded with lines nobody ever said. This one isn’t. Below are 40 project management quotes, every one from a real, well-documented source, grouped into six themes: planning, teamwork, leadership, deadlines, failure, and focus. Use them to open a 2026 kickoff deck, sharpen a retro, or win an argument about scope with a single sentence from Fred Brooks.

They also work as a quick gut check on process. If a quote about honest status reporting or saying no to scope creep makes your team wince a little, that reaction is worth paying attention to. It usually means the gap between what the quote describes and what your actual team’s day-to-day process looks like has grown wider than anyone’s said out loud.

A quick note on why the sourcing matters. The internet is littered with fake Lincoln and Einstein quotes, and nothing undercuts a presentation faster than a manager in the room pulling up Quote Investigator on their phone. Everything below traces to a book, a speech, or a recorded interview.

This isn’t a purely academic concern. Misattributed quotes tend to cluster around a handful of names precisely because those names carry unearned authority; crediting Lincoln or Einstein makes a mediocre line feel like settled wisdom instead of an opinion someone should still argue with. In a room where you’re trying to change a stakeholder’s mind about scope or timeline, that borrowed authority either helps you or, once someone catches the misattribution, actively works against you by making everything else you said sound less careful than it was.

Theme	Reach for it when	Standout voice
Planning	Kickoffs, roadmap reviews	Dwight D. Eisenhower
Teamwork	Team formation, retros	Michael Jordan
Leadership	1:1s, promotion conversations	Grace Hopper
Deadlines	Slipping timelines, scope fights	Fred Brooks
Failure	Post-mortems, hard weeks	Thomas Edison
Focus	Scope requests, feature creep	Steve Jobs

Quotes About Planning

Eisenhower planned the largest amphibious invasion in history, so when he talks about plans falling apart, listen. The theme running through this group: the plan document is disposable, the thinking behind it is not. Every quote here comes from someone who had to plan for conditions they couldn’t fully predict, a battlefield, a harvest, a boxing match, which is exactly the situation most projects are actually in, whether the team admits it or not.

“Plans are worthless, but planning is everything.” (Dwight D. Eisenhower, 1957 speech to the National Defense Executive Reserve)
“It is a bad plan that admits of no modification.” (Publilius Syrus, first-century BC Roman writer)
“The best-laid schemes of mice and men go oft awry.” (Robert Burns, “To a Mouse,” 1785)
“Everybody has a plan until they get punched in the mouth.” (Mike Tyson)
“The general who wins a battle makes many calculations in his temple ere the battle is fought.” (Sun Tzu, The Art of War)
“An ounce of prevention is worth a pound of cure.” (Benjamin Franklin, writing on fire safety in 1735)
“Plans are only good intentions unless they immediately degenerate into hard work.” (Peter Drucker)

Takeaway: plan hard, then treat the plan as a draft. The value was in the arguments you had while writing it.

Quotes About Teamwork

Two of the best lines here come from athletes, and that’s not an accident. Sports makes the gap between individual talent and collective output visible on a scoreboard every single week. Software projects hide it in missed sprints.

“Talent wins games, but teamwork and intelligence win championships.” (Michael Jordan, I Can’t Accept Not Trying)
“Alone we can do so little; together we can do so much.” (Helen Keller)
“Great things in business are never done by one person. They’re done by a team of people.” (Steve Jobs, 60 Minutes interview, 2003)
“The way a team plays as a whole determines its success.” (Babe Ruth)
“Here lies a man who knew how to enlist in his service better men than himself.” (Andrew Carnegie, the epitaph he chose for himself)
“None of us is as smart as all of us.” (Ken Blanchard)
“The strength of the team is each individual member. The strength of each member is the team.” (Phil Jackson)

Takeaway: Carnegie put it on his gravestone for a reason. Hiring people better than you and getting out of their way is the whole job.

Quotes About Leadership

“You manage things; you lead people.”

Grace Hopper, rear admiral and inventor of the compiler, compressed the entire management-versus-leadership literature into seven words. The rest of this group fills in the detail.

“You manage things; you lead people.” (Grace Hopper)
“Efficiency is doing things right; effectiveness is doing the right things.” (Peter Drucker)
“The manager’s function is not to make people work, but to make it possible for people to work.” (Tom DeMarco and Timothy Lister, Peopleware)
“The first responsibility of a leader is to define reality. The last is to say thank you.” (Max De Pree, Leadership Is an Art)
“Leadership is the art of getting someone else to do something you want done because he wants to do it.” (Dwight D. Eisenhower)
“If you don’t know where you are, a map won’t help.” (Watts Humphrey, the father of software quality)
“The day soldiers stop bringing you their problems is the day you have stopped leading them.” (Colin Powell, My American Journey)

Takeaway: a project lead’s output is measured in unblocked people, not in tickets personally closed. Powell’s line about soldiers stopping bringing problems is the warning sign worth watching for: silence from a struggling team member is rarely a good sign.

Quotes About Deadlines and Schedules

This group has the highest quote-to-scar-tissue ratio on the list. Two entries come from Fred Brooks’s The Mythical Man-Month, written in 1975 about IBM’s OS/360 project and still the most-cited book on why schedules slip. Parkinson’s line predates it by twenty years and explains the other half of the problem.

“Work expands so as to fill the time available for its completion.” (C. Northcote Parkinson, The Economist, 1955)
“Adding manpower to a late software project makes it later.” (Fred Brooks, The Mythical Man-Month (Brooks’s Law))
“How does a project get to be a year late? One day at a time.” (Fred Brooks, The Mythical Man-Month)
“I love deadlines. I love the whooshing noise they make as they go by.” (Douglas Adams, The Salmon of Doubt)
“You may delay, but time will not.” (Benjamin Franklin, Poor Richard’s Almanack)
“While we are postponing, life speeds by.” (Seneca, Letters to Lucilius)
“Real artists ship.” (Steve Jobs, to the Macintosh team, 1983)

Takeaway: projects rarely die from one big slip; they die from thirty small ones nobody escalated. That’s Brooks’s “one day at a time,” and it’s the strongest argument for honest weekly status. A status report that says “on track” every week until the week it suddenly isn’t has usually been quietly slipping for a month, one small unreported delay at a time.

Quotes About Failure and Recovery

Post-mortem season material. Edison’s line gets mocked as motivational-poster fodder, but he said it about literal filament experiments; it’s a testing philosophy, not a platitude. Beckett’s is the one to keep above your desk.

“I have not failed. I’ve just found 10,000 ways that won’t work.” (Thomas Edison)
“Ever tried. Ever failed. No matter. Try again. Fail again. Fail better.” (Samuel Beckett, Worstward Ho)
“It’s fine to celebrate success but it is more important to heed the lessons of failure.” (Bill Gates)
“Failure is not fatal, but failure to change might be.” (John Wooden)
“Never give in, never, never, never, never, in nothing great or small, large or petty, never give in except to convictions of honour and good sense.” (Winston Churchill, Harrow School speech, 1941)
“I’ve failed over and over and over again in my life. And that is why I succeed.” (Michael Jordan)
“Whether you think you can, or you think you can’t, you’re right.” (Henry Ford)

Takeaway: a failed project only stays a failure if the lessons never make it into the next project’s plan. Run a real retro, write the lesson down somewhere the next team will actually see it, and the failure paid for something.

Three Famous Fakes to Watch For

Since the sourcing is the whole point of this list, it’s worth naming a few of the most common offenders so you recognize them the next time they show up in someone else’s deck.

“It is not the strongest of the species that survives, but the most adaptable to change.” Constantly credited to Charles Darwin. It doesn’t appear anywhere in Darwin’s actual writing. Researchers have traced the phrasing to Leon C. Megginson, a Louisiana State University business professor, who paraphrased Darwin’s ideas in a 1963 address and got shortened and misattributed over the following decades.
“The definition of insanity is doing the same thing over and over and expecting different results.” Attributed to Albert Einstein constantly, with no documented source anywhere in his letters, papers, or recorded interviews. The earliest known appearances trace to recovery-program literature from the 1980s, decades after Einstein’s death.
“Build a better mousetrap, and the world will beat a path to your door.” Credited to Ralph Waldo Emerson in business seminars for over a century. No version of that exact sentence appears in his published essays or journals; the closest match is a much longer, differently worded passage that a later editor condensed and put in quotation marks.

None of these are malicious. They’re just quotes that sounded plausible enough to survive being repeated a few thousand times without anyone checking. That’s exactly the failure mode this list was built to avoid.

A quick habit fixes most of this before it ever reaches a slide: search the exact phrase in quotation marks alongside the name you’re about to credit. A real quote with a real source usually turns up a book title, a page number, or a dated speech within the first couple of results. A fake one turns up thousands of inspirational-image accounts all repeating the same unsourced line back at each other, with nothing older than a Pinterest board behind any of them.

Quotes About Focus and Scope

Scope creep rarely announces itself. It arrives as a series of individually reasonable requests, each one small enough to seem harmless, until the project bears no resemblance to what got approved. This group is about the discipline of saying no early enough for it to matter.

“Deciding what not to do is as important as deciding what to do.” (Steve Jobs, D8 conference, 2010)
“Focus is about saying no.” (Steve Jobs, D8 conference, 2010)
“It’s not the daily increase but daily decrease. Hack away at the unessential.” (Bruce Lee)
“Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.” (Antoine de Saint-Exupéry, Wind, Sand and Stars)
“There is nothing so useless as doing efficiently that which should not be done at all.” (Peter Drucker, The Effective Executive)

Takeaway: the projects that stay on schedule are usually the ones where somebody said no to a reasonable-sounding request in week two, not the ones with the cleverest recovery plan in week twelve.

How to Actually Use These Quotes

One per deck. That’s the rule.

A single well-chosen line on a kickoff slide frames the conversation; five of them turn your presentation into a fortune cookie. The best use is surgical: when a stakeholder proposes adding four engineers to a late project, Brooks’s Law on one slide does more than twenty minutes of pushback. When the team is arguing over a plan that reality has already invalidated, Eisenhower ends the argument.

Where you use a quote matters as much as which one you pick. A retro opener works better with something from the failure or teamwork groups than with a deadline quote that risks sounding like blame dressed up as wisdom. If your team’s retros have gone stale, a specific structural change tends to help more than a quote ever will; a rundown of team meeting formats worth trying is a better fix for a retro nobody looks forward to than any slide.

The same logic applies to status reporting. A Brooks or Parkinson line at the top of a weekly update signals that the team understands why timelines slip, which lands very differently than the same update with no framing at all. If your project keeps hitting the same wall regardless of which quote opens the meeting, it’s worth stepping back and checking whether the actual problem is one of the more common, structural ones covered in a rundown of recurring project management challenges and how to fix them, rather than something a well-chosen sentence can paper over.

And attribute correctly. If a quote in some other list sounds too perfectly suited to Lincoln or Einstein, it almost certainly isn’t theirs, so check it before it goes in front of your team.

FAQ

What is the most famous project management quote?

Probably Dwight D. Eisenhower’s “Plans are worthless, but planning is everything,” from a 1957 speech. It’s quoted constantly in project circles because it separates the disposable artifact (the plan document) from the durable asset (the shared understanding built while planning).

What is Brooks’s Law?

Brooks’s Law, “adding manpower to a late software project makes it later,” comes from Fred Brooks’s 1975 book The Mythical Man-Month. New people need onboarding from the very people doing the work, and every added person multiplies communication paths, so late projects usually slow down when you staff them up.

What is Parkinson’s Law in project management?

Parkinson’s Law states that “work expands so as to fill the time available for its completion.” C. Northcote Parkinson coined it in a 1955 Economist essay. In practice it’s the argument for shorter, firmer deadlines: a task given three weeks will take three weeks, even if it needed one.

How do I know if a project management quote is real?

Look for a primary source: a named book, speech, or recorded interview. Quote Investigator and Wikiquote both track misattributions. Be especially skeptical of quotes credited to Lincoln, Einstein, or Churchill; they attract fabricated lines more than anyone else.

Where should I use quotes in project work?

Kickoff decks, retro openers, and status-report headers are the natural spots. Use one quote per document, pick it to match the specific tension in the room, whether that’s scope, schedule, or morale, and always include the attribution.

Why do fake quotes spread so easily in business and project contexts?

Three things make a fake quote sticky: it sounds plausible coming from that person, it’s short enough to fit on a slide, and it confirms something the reader already believed. A line that sounds exactly like something Einstein or Lincoln would say gets forwarded without anyone checking, because checking feels unnecessary when the quote already matches the reader’s expectation of who that person was. Verification is boring precisely because a good fake doesn’t feel like it needs any.

Are there project management quotes from women and underrepresented voices worth including?

Yes, and this list includes two of the strongest: Grace Hopper’s line on leadership and Helen Keller’s on teamwork both hold up against anything else here. The genre still skews heavily toward a handful of repeated male business-book authors, mostly because that’s who got quoted and republished in twentieth-century management literature in the first place, not because sharper lines don’t exist elsewhere. Anyone building a recurring quote rotation rather than a single deck should spend the extra research time widening that source list rather than defaulting to the same reprinted names.