1장
When Leadership Meets Execution: The Art of Making Projects Happen
Scott Berkun's "Making Things Happen" has become a project management bible for a reason. Originally published as "The Art of Project Management," this revised edition has made bestseller lists and launched Berkun into speaking engagements worldwide. What makes this book special isn't just its comprehensive approach to project management-it's Berkun's ability to translate his experiences from Microsoft's trenches (where he worked from 1994-2003 on projects like Internet Explorer) into universal principles that apply across industries. The book has garnered praise from tech leaders and business publications alike, with Fast Company calling it "a realistic guide to getting things done." Even outside tech circles, creative professionals and team leaders have embraced Berkun's practical wisdom, making it one of the most recommended management books of the past decade.
2장
The Fundamental Challenge: Turning Ideas into Reality
At its core, project management is about making things happen-transforming ideas into tangible outcomes through deliberate planning, execution, and leadership. This applies to everyone involved in projects, regardless of their job title. While many assume project management is a modern invention, Berkun reminds us it's part of humanity's long history of creation, from the pyramids to the Panama Canal.
What makes project management challenging is that it requires balancing seemingly contradictory attitudes: having ego while putting the project first; knowing when to take control versus when to delegate; tolerating ambiguity while pursuing perfection; communicating both orally and in writing; acknowledging complexity while championing simplicity; being both impatient and patient; balancing courage with healthy fear; and being simultaneously a believer and skeptic.
Few people naturally possess all these traits in perfect balance. Project managers inevitably make mistakes in calibrating these forces, but awareness of these paradoxes helps them step back, reconsider actions, and make smarter decisions.
The pressure inherent in project management often causes new managers to retreat to the sidelines, merely tracking others' efforts rather than facilitating or participating in them. When leaders consistently avoid pressure by getting out of the fray, they're not leading but hiding, adding little value. Others retreat into excessive documentation and process, confusing the tools with the actual goal.
Good project managers understand their unique value comes from their broader perspective across the team. By regularly engaging with team members informally, they gain real insight into project status and can make valuable connections-like discovering that one developer has already solved a problem others are struggling with. These small bits of timely information transfer help mediocre teams become good and good teams become great. As Berkun puts it, "Social networks are always stronger than technological ones," and PMs play a critical role in maintaining healthy information flow.
3장
The Truth About Schedules: Navigating Uncertainty
People are chronically late in daily life, which explains why project schedules often fail. We estimate based on weak assumptions and predict outcomes assuming best circumstances, while simultaneously distrusting schedules. Despite their unreliability, schedules serve crucial purposes beyond just measuring time.
Schedules fulfill three essential functions: making commitments about delivery timelines that serve as contracts between team members; forcing everyone to see their work as part of a whole and consider dependencies; and providing a tool to track progress and break work into manageable chunks. The psychological power of schedules as "forcing functions" helps teams think through their work carefully, even if the schedule itself proves inaccurate.
The foundation of all schedules is what Berkun calls "the rule of thirds": for every day spent writing production code, a day should be spent planning and designing, and another day testing and refining. When schedules slip, it's because hidden or ignored costs were never accounted for.
Early in projects, schedules are created when hundreds of decisions have yet to be made. Barry Boehm found that schedule estimates made during initial planning can be off by as much as 400% in either direction. People often confuse precision (specific dates) with accuracy (reflecting reality). Schedule accuracy improves as the project progresses, narrowing to about 20% variance during implementation.
The most depressing aspect of schedule management is that even with most factors accounted for, schedules easily slip because of interdependencies. Each decision becomes the foundation for future decisions, so early oversights have amplified impacts later. This compounding behavior is easy to underestimate because cause and effect are often separated in time. Compound probability works against project managers-if your team is 90% likely to make dates each week, the cumulative probability of success decreases over time.
The best way to create reliable schedules is to establish clear checkpoints before creative work begins at full speed, build with skepticism rather than optimism, and invest in design to generate reliable confidence.
4장
Defining the Project: How to Figure Out What to Do
Few agree on how to plan projects, with people often wasting time debating how planning should be done. Planning brings together different organizational roles making major decisions, causing people to assert their worldviews. As Fred Brooks notes, deciding what to build is the hardest part of software development, with errors crippling results.
Planning should never be a binary competition between business and engineering perspectives, but rather a synthesis of what everyone contributes. A project manager must recognize that each perspective offers unique value that cannot be replaced by another. For successful projects, everyone involved in planning must understand all three key perspectives:
The business view focuses on profit and loss factors including sales, expenses, competition, and costs. When engineering teams lack this understanding, management decisions often appear illogical. Good business perspective answers questions about why the project exists, what customer needs it addresses, cost/revenue projections, competitive advantages, and market timing.
The technology view prioritizes how things should be built-a construction and materials mindset with its own aesthetic. Engineers often evaluate products based on technical merits rather than customer satisfaction or business success, leading to confusion when technically inferior products outsell superior ones.
The customer perspective is the most important yet often receives the least support in organizations. It focuses on understanding who customers are, what they do, and how improvements would help them. Without this information, engineering and business are "shooting in the dark."
The three perspectives-business, technology, and customer-always overlap, and the best planning requires laying them out equally to identify similarities and differences. Strategic decisions should intentionally favor one perspective over another when necessary. By exploring all three perspectives, teams can identify opportunities that simultaneously address multiple goals.
Despite claims of caring about customers, many organizations don't effectively integrate customer research into their decision-making. The most common mistake is over-reliance on a single research method, as each approach has specific strengths and limitations.
5장
Crafting a Powerful Vision: The North Star of Your Project
Project leaders face the challenge of keeping teams focused on the same goals over time. The vision document, the most important planning material, helps address this by documenting core objectives. A finalized vision document marks the end of the planning phase, just as completed specifications signal the end of the design phase.
Since everything derives from the high-level vision, team leaders should invest significant energy in creating a vision with five essential qualities:
1. Simplifying: A good vision simplifies the project by providing answers to core questions and giving everyone a decision-making tool. It should be actively referenced in discussions, emails, and meetings during early project phases.
2. Intentional (goal-driven): The vision establishes the project's first goals, setting the standard for what good goals look like. Well-written goals define clear intentions and provide enough information for team members to recognize completion.
3. Consolidated: An effective vision consolidates ideas from research, analysis, and strategic planning, presenting them cohesively without requiring readers to do the work of connecting concepts themselves.
4. Inspirational: True inspiration comes from addressing genuine problems, not superficial elements. The vision must connect team members to a clear real-world problem they have the capacity to solve.
5. Memorable: A memorable vision makes sense to readers and resonates enough to stay with them throughout the project. Direct, honest communication of core decisions is more memorable than complex ideas buried in weak writing.
Vision documents often tempt authors toward pretension as they try to showcase grand thinking, but this defeats their purpose by obscuring ideas rather than communicating them. The greatest challenge in writing visions is expressing sophisticated ideas simply. Committee-written visions typically fail-while committees can provide feedback, one primary author should have authority to drive a single voice into the document.
To keep the vision alive, core goals should be prominently displayed in high-traffic areas, discussed openly in meetings, and featured on team materials. Most team members should be able to name the project goals they contribute to.
6장
From Ideas to Solutions: Navigating the Creative Process
Ideas come from people, not processes or methodologies. While humans naturally use creativity to solve problems, the ability to find good ideas is crucial throughout a project's lifecycle-from planning to implementation.
Many project management books fail to address how teams move from requirements to good design. Schedules often mark dates for completing requirements and specifications without explaining the creative work that happens between. This gap becomes problematic for complex projects requiring evaluation of different approaches.
The phrase "There are no bad ideas" is fundamentally wrong, despite its noble goal of preventing premature filtering in creative processes. In reality, there are infinite numbers of awful, useless, and comically stupid ideas. The space of good solutions is much smaller than the space of nonsolutions-just as there are few routes to successfully climb Mount Everest but infinite ways to not climb it.
Ideas can only be evaluated relative to specific problems or alternatives, not in the abstract. Without alternatives for comparison or a clear problem to solve, judging an idea's value becomes nearly impossible.
As Picasso noted, "Computers are useless. They can only give you answers." Well-crafted questions are powerful tools for directing creative energy and focusing discussions. Good questions act like magnets, attracting clever people and their ideas. The most powerful question in project management is simply: "What problem are you trying to solve?"
Good ideas often require the remains of many bad ideas. Without making mistakes and exploring unsuccessful approaches, it's difficult to find the path that leads to success. As one designer explained, "I don't really know what the good ideas look like until I've seen the bad ones." Every sketch or prototype teaches something more about the problem, increasing the odds that the next attempt will be better.
Good problem solvers notice things others don't. They see more detail, make more associations, and have deeper perception to draw connections. As Steve Jobs observed, creativity is about connecting things-seeing relationships that become obvious only after making the connection.
7장
Managing the Flow of Ideas: From Exploration to Decision
Managing ideas is more challenging than generating them. The transition from creative exploration to definitive decisions is crucial for project success. If teams fail to make timely design decisions before programmers need specifications, the project will suffer from delays and poor quality work.
The design process cannot be treated like a light switch that's abruptly turned off when deadlines approach. Instead of suddenly announcing "we're done with ideas," good idea management requires a predictable, gradual transition like a dimmer switch. Project managers must guide teams through a natural progression from expanding the design space (generating alternatives) to narrowing it (refining the best designs).
Design decisions are interconnected, with one change potentially affecting many others in unpredictable ways. Creative work builds momentum that's often stronger than inexperienced managers expect. The challenge is that new questions and issues arise faster than old ones are resolved, creating a sense that schedules will slip.
The best way to manage ideas is to establish clear checkpoints before creative work begins at full speed. Rather than having just two points-requirements and spec writing-intermediate checkpoints help structure the process. Key checkpoints include: vision and proof-of-concept, idea groupings/lists, three alternatives, two alternatives, one design, and specification.
Once you have enough ideas, they need to be organized into useful groupings to understand different viable design directions. Affinity diagrams (where ideas are written on Post-it notes and arranged on a wall) allow the team to focus on relationships between ideas rather than keeping everything in their heads.
Prototypes are the natural next step in the design process, allowing teams to apply what they've learned without taking on the risks of full implementation. They fulfill the carpenter's maxim "Measure twice, cut once" by improving design thinking before committing to a plan. Prototypes don't need to be elaborate, expensive, or time-consuming to be valuable.
With the first prototype complete, many new ideas and questions will emerge. Early prototype iterations might focus on exploring big ideas or wide changes, while later iterations will refine specific details. The best framework for these discussions is a set of questions that evaluate the design and focus discussion productively.
8장
Creating Clear Specifications: Translating Vision into Action
Specifications, when used effectively, convey important information simply. When used poorly, they become tedious burdens. Successful specs can describe functionality, force designers to clarify decisions, enable review before implementation, communicate from one to many, create team-wide reference points, provide schedule milestones, protect against knowledge loss, accelerate discussions, enable leadership feedback, and add confidence.
Creating specifications should focus on expressing existing plans clearly, not simultaneously designing those plans. Trying to do both simultaneously diminishes the quality of both activities. Spec authors must shift mindsets between exploring/creating and explaining/expressing.
The toughest challenge for technical people is effectively choosing which details to exclude. Like good teachers who know when to skip nonessential elements, well-written specs prioritize essentials and help readers build refined mental models. Complexity is sometimes unavoidable, but it's often a cop-out hiding poor writing or mediocre thinking.
Like vision documents, specifications need one author who incorporates contributions from others. This ensures the document reads like it was written by a clear-thinking individual. The primary author should be whoever is most accountable for decisions at that level-typically the project manager, designer, or lead programmer.
The biggest mistake with specifications is waiting for formal reviews to get feedback. Reviews should refine, not make first and final decisions simultaneously. This is why the design process is important-it allows for multiple iterations and incorporation of suggestions.
Unresolved issues during spec writing must be properly managed to avoid mid-project disasters. Project managers must take initiative in collecting and reviewing these issues, pushing the team to acknowledge them early. When prioritizing issues, ask: When does this need resolution? Who should decide? Can it be isolated to a specific component? What alternatives remain? Can we cut this issue? Can it be divided into smaller issues?
9장
Building Trust: The Foundation of Effective Leadership
Leadership fundamentally depends on trust. While movies portray leadership as dramatic heroism, real leadership involves simple, practical behaviors: doing what you say, admitting mistakes, and including others in decisions that affect them. Good leaders don't need to excel at every skill-they simply need to cultivate trust with their team.
Trust is built through reliable commitment. When someone repeatedly breaks commitments, such as failing to show up at agreed times, trust diminishes. According to Watts Humphrey, effective commitments have specific elements: they must be made willingly, carefully considered, mutually agreed upon, publicly stated, followed through even if help is needed, and renegotiated with advance notice if circumstances change.
Trust fractures when people behave unpredictably. Someone who consistently disregards commitments creates waves of concern throughout the team, forcing others to waste energy calculating whether that person will follow through and devising contingency plans.
Good managers make trust explicit by clearly delegating authority. They identify specific concerns requiring check-ins but otherwise direct their reports to make decisions independently. This delegation of authority-giving someone the "green light"-imparts powerful trust.
Power comes in two forms: granted and earned. Granted power derives from hierarchy or job titles, while earned power must be cultivated through performance and action-people choose to listen because they believe someone is smart or helpful, not because of their position. Using granted power as your primary leadership approach limits relationships. It focuses on force rather than intelligence and excludes the exchange of ideas.
Making things happen through persuasion rather than dictation creates more powerful outcomes. When people are convinced to do something rather than ordered to do it, they rely on their own intelligence for motivation when questions arise later.
When projects inevitably face unexpected challenges, trust becomes crucial insurance. Teams with established trust and collaborative decision-making experience show remarkable resilience. Like soldiers in a foxhole, team members watch each other's backs, freeing energy for the tasks ahead. Trust allows leaders to focus on solving problems rather than calming panicked employees.
10장
Making Things Happen: The Art of Execution
Project management requires the ability to make things happen-a combination of being a catalyst in various situations and having the courage to act. Clear priorities form the backbone of project progress. Much of a project manager's work involves creating ordered lists-requirements, features, bugs-arranged by importance, then leading the team to follow this order.
The most critical division in any ordered list is between priority 1 items-things absolutely essential for success-and everything else. Priority 1 should be kept as small and tight as possible, representing only what's truly necessary. Establishing this line requires difficult debates about what customers can truly live without, but these discussions should happen early so the team can move forward with clear understanding.
Having rock-solid priorities gives you tremendous power in resolving conflicts. When teams are deadlocked in arguments, a leader who frames discussions around clear priorities can quickly bring resolution. Good priorities eliminate secondary variables from discussions, focusing everyone on what truly matters.
If you can't say no, you can't have priorities, and if you can't have priorities, you can't manage. Since your priority 1 list should be very small, most ideas-even good ones-won't make the cut for a particular project. Saying no starts at the top: senior managers determine whether people can actually reject requests.
In project management, the critical path is the shortest sequence of work that can complete the project. By analyzing dependencies between work items, you can identify bottlenecks where delays will seriously impact other components. Beyond engineering work, project managers should always understand the critical paths in human relationships, decision-making processes, and team workflows.
"The world responds to action, and not much else." Many smart people can identify problems, but few expend the energy to find solutions and summon the courage to implement them. Successful project managers refuse to give up easily on important issues. They aggressively pursue answers, sometimes asking uncomfortable questions or challenging assumptions others leave unchallenged.
Being savvy means adapting your approach to the environment you're working in. Smart project managers evaluate the social, political, and organizational terrain before choosing tactics. Like a Marine, assess the environment and find the smartest route to your goals, making adjustments with each new situation or person you encounter.
11장
Navigating the End Game: Bringing Projects to Completion
End-game strategy focuses on hitting dates and deadlines while understanding that team productivity is a zero-sum resource. Extraordinary efforts to meet one deadline steal productivity from the next phase, with recovery time exceeding the crunch effort. Good management should avoid big pushes when possible, control them carefully when necessary, and understand their true costs.
Projects have multiple interim dates corresponding to the crossover points between project phases. Each represents a shift in team focus and should have its own exit criteria. The three key crossover points are: design/spec complete (ready for production code), feature complete (focus shifts to refinement and quality assurance), and test/milestone complete (quality and refinement reach appropriate levels).
Exit criteria define what state the project must achieve to complete a milestone. They should be established early, kept simple, and used publicly to track progress. Without clear exit criteria, teams waste energy in subjective debates about what "good enough" means when stress and risks are highest.
Successfully hitting milestone dates means not just meeting a deadline but setting the team up well for the next phase. Like landing an airplane, the goal is to finish in a state that makes it easy to take off again. The sharper the angle of descent (crash landing approach), the higher the risk that the project won't be in good condition when completing the milestone.
People naturally avoid tasks they don't want to do, meaning that as schedules progress, remaining work items become the unwanted, difficult tasks. Teams under pressure tend to pick easier bugs to fix first, leaving the most complex problems for the end. Additionally, defects discovered later in the schedule are naturally more complicated, taking longer to find and fix.
As projects near completion, authority must centralize. The "war team"-a small group of team leaders-becomes an executive branch of power, raising the bar on decision-making and signaling that the project is ending. This team includes senior members from each staff (programming, test, PM) who must agree on issues (or use a defined voting system).
The closing period of an engineering project is a difficult, mind-numbing process. Jim McCarthy likens it to working with Jell-O-each bug fix causes ripples throughout the codebase, and it takes time for everything to settle down. When the final build is confirmed and released to the world, celebration is essential. Completing projects is rare in the tech sector, where most never reach the finish line.
12장
The Power of Project Management: Turning Vision into Reality
Scott Berkun's "Making Things Happen" provides a comprehensive framework for understanding and executing successful projects. From the initial planning stages through idea generation, specification writing, and execution to final delivery, Berkun offers practical wisdom drawn from his years in the trenches at Microsoft and beyond.
What makes this book particularly valuable is its focus on the human elements of project management-building trust, managing relationships, understanding power dynamics, and navigating the emotional landscape of teams under pressure. Berkun recognizes that technical skills alone aren't enough; successful project managers must also master the art of leadership.
By integrating business, technology, and customer perspectives, maintaining clear priorities, fostering trust-based leadership, and managing the creative process effectively, project managers can dramatically increase their chances of success. The book's emphasis on practical techniques-from writing effective vision documents to running productive meetings and managing the end-game-provides actionable guidance for both new and experienced project leaders.
In a world where most projects fail to meet their objectives, Berkun's approach offers a path to not just completing projects, but doing so in a way that delivers genuine value while preserving team morale and building organizational capability for future endeavors. The ultimate message is clear: making things happen isn't about heroic individual effort but about creating the conditions where teams can collaborate effectively toward shared goals.
