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
The Project50

The Project50

Turn an ordinary assignment into work people value, adopt, and keep using.
by Tom Peters 1999
4.04
247 ratings
Listen
Immersive
V2.3
Amazon Kindle Audible
Try Full Access for 3 Days
Unlock listening & more!
Continue

Key Takeaways

Turn assigned work into a project worth remembering ten years later

Work can matter. Peters argues that the unit of meaningful professional work is not a job title but a project: a piece of work with a beginning, an end, users, and a result. He calls a project designed to be memorable, distinctive, and consequential a WOW Project. In 1999, he saw technology and economic change pushing white-collar work toward this project-based model, much like mechanization had transformed physical labor.

Make it personal. In the film Smoke, a shopkeeper photographs the same Brooklyn street corner every morning for years and regards the work as his defining project. Peters uses this modest, self-chosen practice to show that scale is not the point. A project matters when it carries care, craft, and a clear human purpose.

Analysis

What's compelling is the shift from asking whether a task is important to asking what kind of work a person can take responsibility for and remember with pride. That makes the idea useful beyond corporate innovation: a project can be a personal practice, a service improvement, or a major public undertaking. The caution is that meaningful work cannot be demanded on every assignment. Some jobs are constrained by safety, routine, or limited authority. The principle is less that every task must become a masterpiece than that people should have room to shape at least some work around purpose and craft.

Reframe small annoyances as low-risk openings into larger change

Look beneath the task. Peters says an assignment is a starting point, not a binding definition. A request to revise a returns policy might reveal deeper problems: confusing processes, distrust of front-line staff, or an assumption that customers are a nuisance. A minor policy update can become a carefully scoped test of a better way to serve people.

Small work exposes culture. Peters describes a colleague who was asked to tidy a neglected company library. Instead of treating it as clerical cleanup, the colleague improved how the firm collected and shared knowledge. The lesson is not that every chore needs a grand redesign. It is that small tasks offer a manageable place to notice hidden assumptions, involve users, and demonstrate a better approach before proposing sweeping change.

Analysis

This is a practical account of how organizational change can begin without a grand launch. A small experiment makes assumptions visible and gives colleagues something concrete to evaluate. It also lowers the cost of learning: a flawed form or process can be revised more easily than an entire operating model. The useful restraint is to test whether the larger interpretation is real. Not every irritating procedure signals a deep cultural failure. Start with the user's actual friction, then earn the right to widen the scope through evidence.

Judge projects by user delight, beauty, and consequence, not compliance alone

Define better explicitly. Peters challenges the familiar definition of project success as finishing on time, within budget, and to specification. He proposes a broader set of tests, which he calls the Big Five: whether the result feels exceptional, is beautiful, changes the status quo, has meaningful impact, and earns enthusiastic users. Teams can discuss and score these dimensions rather than relying on vague claims of quality.

Design belongs early. Peters argues that grace, clarity, friendliness, and identity are not decorative extras to add at the end. They shape how people experience a process or product from the start. He also urges teams to ask directly who their users are, including whether women are being overlooked, and to include varied perspectives in design and decision-making.

Analysis

The Big Five give teams language for qualities that ordinary project dashboards often miss. A process can meet its specification and still frustrate its users; asking about beauty and delight forces attention onto the lived experience of the result. The inclusion principle is especially valuable when it challenges teams to question who they have treated as the default user. Peters sometimes describes women's preferences too broadly, however. The stronger practice is not to substitute one stereotype for another, but to involve diverse users and check assumptions against what they actually need.

Collect observations and outsiders' ideas before your assumptions harden

Train your attention. Peters recommends keeping an observation notebook for experiences that are unusually good, frustrating, or simply intriguing. A confusing form, excellent service at a shop, or an awkward event can all reveal design ideas worth adapting. The purpose is not to collect trivia; it is to build a supply of real-world material for improving current work.

Learn beyond your team. Peters describes people who record ideas on cards, in project journals, or in whatever format they can keep nearby. He also tells of a mentor who contacted authors of interesting articles and invited them to share what they knew. Together, the practices turn curiosity into a working habit: notice, record, make connections, and ask knowledgeable people how they see the problem.

Analysis

The notebook makes curiosity operational. Without a record, observations tend to fade or remain as vague impressions; written examples can be compared, discussed, and translated into a project decision. Inviting outsiders also interrupts the comfortable assumption that a team already understands its own field. The limitation is that a collection of anecdotes can mislead as easily as it can inspire. A striking experience is a useful prompt, not proof that the same solution fits another setting. The next step is to test the insight with the people who will use the result.

Recruit committed misfits and real users before asking executives for permission

Commitment creates energy. Peters argues that a project's importance on paper matters less than whether its champions care enough to persist and improve it. He advises shaping work until it offers a genuine challenge to its team, then recruiting people with different experiences and perspectives rather than selecting only familiar insiders.

Begin with a few believers. In recounting his own McKinsey project, which contributed to In Search of Excellence, Peters emphasizes the value of committed colleagues, including people with little formal power. The project benefited from room to experiment and from support beyond headquarters. Peters also recommends finding a wise adviser who can offer honest counsel, and bringing an enthusiastic user into the work early enough to influence what is built.

Analysis

The emphasis on commitment and varied collaborators recognizes that formal authority is not the only source of initiative. People who care about the problem can contribute knowledge and persistence that a title does not guarantee. An early user can also prevent the team from mistaking internal enthusiasm for actual usefulness. Still, passion is not a substitute for fair workloads or decision rights. Calling people to take risks without giving them time, support, or protection can turn inspiration into exploitation. Commitment works best when the organization makes meaningful participation possible.

Sell the story continually, but spend scarce energy on persuadable allies

Make the case brief. Peters treats project leadership as a continuing act of persuasion. He recommends explaining the project's purpose and benefits in a short pitch, then refining the story through repeated conversations with colleagues, users, and supporters. A memorable image or metaphor can help people understand what the project is trying to change.

Build support deliberately. Rather than starting with the most senior executive, Peters advises recruiting practical early supporters, maintaining contact with them, and using an advisory group to build credibility. He warns against spending scarce time trying to convert determined opponents. He also favors modest early resources, arguing that small budgets can preserve flexibility and encourage teams to demonstrate results before seeking wider backing.

Analysis

Treating persuasion as part of the work clarifies why good ideas often stall: people need a reason to contribute, not just a project plan to inspect. A concise story helps supporters explain the project to others, while an advisory group can make a proposal feel less isolated. The advice to focus on persuadable allies is a useful defense against endless debate, but it should not excuse ignoring legitimate objections. Criticism can expose risks that friendly supporters miss. The practical distinction is between addressing substantive concerns and pouring energy into people committed to blocking the effort.

Prototype in days, learn from failure, and rebuild what stays merely adequate

Make ideas testable. Quick Prototyping means building a rough, low-cost version of a small part of the project, putting it in front of a real or representative user, and using the response to revise the next version. Peters urges teams to break large work into small pieces they can try soon, rather than spending months polishing plans before encountering reality.

Treat failure as information. A test that fails quickly can reveal what needs to change before more time and money are committed. Peters encourages teams to recognize well-intentioned experiments, not just successful outcomes, and to abandon or redesign work that remains merely acceptable. He compares this process to practice in the arts: try, adjust, and try again until the result works for its audience.

Analysis

The central advantage of rapid trials is that they replace speculation with something users can react to. A rough draft of a form or a walk-through of a new process can expose problems that a polished slide deck conceals. Praising honest failure can also make experimentation safer, provided teams distinguish a thoughtful test from carelessness. Speed is not a universal virtue: decisions involving safety, law, or irreversible consequences require stronger safeguards. The transferable principle is to shorten the learning cycle wherever a test can be made responsible and informative.

Make progress visible with deadlines, concise lists, and deliberate celebration

Give work a rhythm. Peters favors simple tools that make the next action clear: a project binder for notes and decisions, short lists of responsibilities, and a visible timeline of milestones. He recalls how assigning dates to a project exposed dependencies that abstract planning had hidden. He also recommends brief standing meetings focused on what happened, what is happening, and what help is needed.

Protect momentum. Small celebrations recognize progress and help keep a team engaged through setbacks. Peters urges managers to acknowledge both successes and useful failed tests, while assigning someone to care about the final details that separate a finished result from an almost-finished one. These practices work best when they support the project's purpose, rather than becoming paperwork or rituals performed for their own sake.

Analysis

Simple coordination tools can make an ambitious project less mysterious: a timeline exposes what must happen next, and short summaries let people see decisions and ownership. Celebration adds an emotional signal that progress matters, especially when the final result is distant. The danger is mistaking visible activity for actual movement. A full binder, crowded calendar, and endless milestone updates can become a new bureaucracy. Each tool should answer a practical question: what changed, who owns the next step, and what did the team learn?

Hand successful projects to operators, then place pioneers where they can spread

Design the handoff. Peters argues that the person who launches a bold project may not be the right person to run it as a permanent operation. Mainstream adoption requires procedures, systems, and colleagues who can maintain the work beyond its original team. He recommends finding a successor who shares the project's purpose but has the skills and patience needed for the next phase.

Let the work travel. The original team should help its members find positions where they can carry useful ideas into other parts of the organization. Peters also urges project leaders to document what happened, thank contributors, celebrate the result, and then move on. A project has greater staying power when its methods and advocates continue beyond the excitement of the launch.

Analysis

This is a strong account of institutional change as a transfer of ownership, not a victory lap. The project is not fully successful if it depends forever on its founder's energy or disappears when the team disperses. A careful handoff preserves both the practical knowledge and the people capable of adapting it. Standardization can, however, flatten the qualities that made the work valuable. The successor's job is not merely to preserve procedures, but to protect the original user benefit while making the result dependable at a wider scale.

Analysis

The Project50 is a business and work-life argument presented as a highly practical field guide. Its structure follows a project's development, but its deeper subject is the status of work itself. Peters objects to treating professional labor as a bundle of tasks managed through schedules and budgets. He instead frames work as a series of authored efforts that can reveal skill, values, and initiative. The memorable project is both a product and a public account of what its makers believe matters.

The book's most useful conceptual move is to put creation, persuasion, experimentation, and handoff inside project management. This corrects a common imbalance in the book's imagined opponent: a plan can track tasks while doing little to establish whether the work deserves to exist, whether anyone wants it, or whether the organization will keep using it. The emphasis on user involvement and rapid tests gives Peters's exuberant language a practical backbone. Beauty and delight are not left as pure slogans; teams are asked to discuss them, seek feedback, and revise deliverables.

Its energy also creates tensions. The insistence that any task can become exceptional is empowering when it helps people find room to act, but it can understate how unevenly autonomy and resources are distributed. The appeal to do more with little can become an excuse for organizations to rely on unpaid initiative. Likewise, a team's desire to be revolutionary can become self-congratulation unless users and outcomes provide external checks. Peters's own remedy is partly embedded in the book: invite users early, test ideas in the world, and judge results by their effect rather than by the champions' excitement.

The strongest reading is therefore neither literal nor dismissive. Not every assignment needs to be a defining achievement, and not every opponent is merely an obstacle. But each project can be examined for its potential to improve an experience, reveal a better method, or create work worth owning. The practical legacy is a wider definition of execution: make something worth doing, build the support to do it, test it honestly, and ensure it can survive its creators.

Summary in 30 Seconds
A project deserves more than completion on time and within budget: assess whether it improves users' experience, creates meaningful impact, and earns genuine enthusiasm. Start with a small, low-cost test, involve users early, and use their responses to revise the work. Build support through committed colleagues and concise persuasion, track progress with clear milestones, and hand successful work to operators who can sustain it.
Contains spoilers

Last updated:

Report Issue

Review Summary

4.04 out of 5
Average of 247 ratings from Goodreads and Amazon.

Readers find The Project 50 motivating but polarizing. Many praise its energetic approach to transforming work into meaningful projects, appreciating Peters' emphasis on creativity and impact. The book's unconventional style, with abundant exclamation points and repetitive formatting, resonates with some but irritates others. Criticisms include a lack of concrete instructions and difficulty in practical implementation. Despite mixed reactions, most agree the book offers valuable insights on project management and workplace enthusiasm, though its intense approach may not suit all tasks or personalities.

Your rating:
4.51
292 ratings
Want to read the full book?

Glossary

WOW Project

Memorable, consequential work

Peters's term for a project designed to be distinctive, engaging, and meaningful to its makers and users. A WOW Project aims beyond acceptable completion toward work that people remember, value, and may enthusiastically recommend. Its worth is judged through qualities such as user response, design, innovation, and impact, not by schedule and budget alone.

Quick Prototyping

Rapid, low-cost project tests

A method of advancing work through small, practical versions that can be tested with users quickly. The team builds a rough approximation, gathers feedback, records what it learns, adjusts the work, and tests again. Peters presents this repeated cycle as a central way to replace prolonged planning with evidence from real use.

Culture of Prototyping

Routine experimentation at work

An organizational norm in which trying rough versions, learning from results, and revising are regular parts of work rather than occasional special procedures. In Peters's account, creating this culture requires more than telling teams to experiment. Organizations must teach, practice, discuss, and reward prototyping until it becomes an ordinary way to develop projects.

Big Five

Five project quality tests

Peters's proposed criteria for keeping a project focused on more than conventional delivery measures: whether it is exceptional, beautiful, revolutionary, impactful, and capable of earning enthusiastic users. Teams can define what each criterion means for their project and assess progress against them. The terms are intended to keep ambitious qualities visible during practical work.

Raving Fans

Enthusiastic project users

A standard Peters adopts from Ken Blanchard and Sheldon Bowles's book of the same name. It asks a project team to aim beyond basic customer satisfaction toward users who are genuinely enthusiastic about the result. Peters recommends involving such users early, learning what they value, and using their feedback to shape and improve project deliverables.

FAQ

What's "The Project50" by Tom Peters about?

  • Reinventing Work: "The Project50" is part of Tom Peters' series aimed at transforming how we perceive and undertake work, emphasizing the importance of projects in the new economy.
  • WOW Projects: The book focuses on turning every task into a "WOW Project," which is dynamic, memorable, and impactful.
  • White Collar Revolution: Peters discusses the impending transformation of white-collar work due to technological advancements and globalization.
  • Practical Guide: It provides 50 actionable ideas to help individuals and organizations create projects that stand out and make a difference.

Why should I read "The Project50"?

  • Transformative Approach: It offers a fresh perspective on how to approach work, encouraging creativity and innovation.
  • Actionable Advice: The book is filled with practical tips and strategies that can be applied immediately to improve project outcomes.
  • Inspiration for Change: Peters' enthusiasm and passion for making work meaningful can inspire readers to take charge of their professional lives.
  • Relevance to Modern Work: The concepts are highly relevant to today's rapidly changing work environment, making it a valuable resource for professionals.

What are the key takeaways of "The Project50"?

  • Reframe Assignments: Never accept a project as given; always look for ways to make it memorable and impactful.
  • Embrace Prototyping: Quick prototyping and testing are essential for successful project implementation.
  • Sell Your Project: Effective project management involves selling your ideas to gain support and enthusiasm from others.
  • Celebrate Success and Failure: Recognize and celebrate both successes and failures to maintain momentum and encourage innovation.

How does Tom Peters define a "WOW Project"?

  • Dynamic and Stimulating: A WOW Project is exciting and engaging for everyone involved, from team members to end-users.
  • Memorable and Impactful: It should be something that participants will remember and be proud of years later.
  • Revolutionary and Beautiful: The project should challenge the status quo and be aesthetically pleasing.
  • Client-Centric: It aims to create raving fans among its clients and users.

What is the "White Collar Revolution" mentioned in "The Project50"?

  • Technological Impact: The revolution is driven by advancements in information systems, technology, and globalization.
  • Job Transformation: Peters predicts that most white-collar jobs will change dramatically, requiring new skills and approaches.
  • Professional Service Firm Model: He suggests that individuals and organizations adopt the attributes of professional service firms to thrive.
  • Project-Centric Work: The future of work will be centered around projects, making them the fundamental unit of work.

What are some of the best quotes from "The Project50" and what do they mean?

  • "Be distinct or extinct!" - This emphasizes the importance of standing out in a competitive work environment.
  • "Make every project a WOW!" - Encourages readers to approach every task with the goal of making it exceptional.
  • "Reward excellent failures." - Suggests that taking risks and learning from failures is crucial for innovation.
  • "The work can be beautiful!" - Reminds us that work should not only be functional but also aesthetically pleasing and fulfilling.

How does Tom Peters suggest we "sell" a project in "The Project50"?

  • Develop a Pitch: Create a succinct and compelling sales pitch for your project that can be delivered in a few minutes.
  • Create Buzz: Constantly work on generating excitement and visibility for your project through creative marketing.
  • Engage Supporters: Build a network of supporters and keep them informed and engaged throughout the project.
  • Ignore Enemies: Focus on building alliances and ignore detractors who are unlikely to be convinced.

What role does "prototyping" play in "The Project50"?

  • Quick Testing: Prototyping allows for rapid testing and iteration, which is crucial for refining project ideas.
  • Feedback Loops: Short feedback loops help in making quick adjustments and improvements to the project.
  • Culture of Prototyping: Peters advocates for creating a corporate culture that embraces prototyping as a way of life.
  • Encourages Innovation: Prototyping fosters a playful and experimental approach, leading to innovative solutions.

How does "The Project50" address the concept of "impact"?

  • Worth Doing: Every project should be evaluated on whether it makes a noticeable difference and is worth doing.
  • Long-Term Legacy: Projects should be designed to have a lasting impact and contribute to one's professional legacy.
  • Client Satisfaction: The ultimate measure of impact is the creation of raving fans among clients and users.
  • Continuous Evaluation: Regularly assess whether the project continues to align with its intended impact and goals.

What is the significance of "celebrating failures" in "The Project50"?

  • Encourages Risk-Taking: Celebrating failures encourages team members to take risks and innovate without fear of repercussions.
  • Learning Opportunities: Failures are seen as valuable learning experiences that can lead to future successes.
  • Maintains Morale: Recognizing and celebrating failures helps maintain team morale and motivation.
  • Part of the Process: Peters views failures as an integral part of the creative and prototyping process.

How does "The Project50" suggest handling project "exit" strategies?

  • Transition to Mainstream: Successfully transitioning a project to the mainstream involves embracing systems and procedures.
  • Succession Planning: Recruit a successor who is passionate and skilled in administration to ensure the project's longevity.
  • Celebrate Achievements: Host a grand celebration to acknowledge the team's efforts and successes.
  • Move On: After ensuring a smooth transition, move on to the next WOW Project to continue making an impact.

What is the "Movement" that Tom Peters refers to in "The Project50"?

  • The Work Matters!: Peters advocates for a movement that emphasizes the importance of meaningful and impactful work.
  • Anti-Dilbert Stance: The movement opposes the acceptance of powerlessness and mediocrity in the workplace.
  • Empowerment: It encourages individuals to take charge of their work and strive for excellence and innovation.
  • Community Engagement: Peters invites readers to join the movement and engage with like-minded individuals through his website.

About the Author

Tom Peters is a renowned business author and speaker born in Baltimore in 1942. He graduated from Cornell in civil engineering and earned an MBA and Ph.D. from Stanford. Peters served in the U.S. Navy, including two deployments to Vietnam, and worked at McKinsey & Co., becoming a partner and co-founding their Organization Effectiveness practice. He has authored numerous influential books on management and leadership, receiving recognition from various institutions worldwide. Peters now resides on a Vermont farm with his wife, while maintaining a passion for travel, reading history, and collecting unique experiences and friendships.

Download PDF

To save this The Project50 summary for later, download the free PDF. You can print it out, or read offline at your convenience.
Download PDF
File size: 0.36 MB     Pages: 19

Download EPUB

To read this The Project50 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.38 MB     Pages: 23
Want to read the full book?
Follow
Listen11 mins
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...