Ever wondered how major corporations tackle project delays and budget overruns? Are you curious about how professors bring real-world business solutions into the classroom? How does an academic concept like the Theory of Constraints revolutionize project management in practice? Dive into this fictional story that weaves together corporate challenges, academic insights, and personal struggles in an exploration of innovative project management tactics.

Critical Chain

Daniel Pullman, the assertive CEO of Genemodem, adjourned the board meeting. It had been another successful quarter, the norm for the past six years. Pullman approached Isaac Levy, the executive VP of engineering, to discuss the final report from McAllen's consulting firm. Levy had hired them to analyze Genemodem’s product development process, but despite their thorough work, the solutions proposed would only marginally reduce development time.

Pullman decided to launch a think tank, composed of three young managers: Mark Kowalski, Ruth Emerson, and Fred Romero. Mark, from engineering, was chosen as the group leader despite Levy's reservations about his rebelliousness. Ruth, a marketing brand manager, was selected for her integrity and questioning nature. Fred, a finance project auditor, was known as the rebel of finance.

Levy explained the company's urgent problem: their products had a short lifespan of about six months, but development took two years. This mismatch meant they were bound to miss a launch eventually, which would be disastrous for their market share and stock value. The think tank's mission was to find a drastic way to cut development time, using the A226 project as their test ground, with no budget constraints and direct reporting to Levy.

Meanwhile, Rick Silver, a newly promoted associate professor, received a memo inviting him to teach a course in the Executive MBA program. This opportunity signaled a potential tenure recommendation, a coveted security in academia. Rick met with Jim Wilson, head of the program, who chose him for his unique teaching style—encouraging open debate and discussion.

Rick was nervous about teaching experienced managers, fearing his theoretical knowledge might not match their practical expertise. However, Jim reassured him that honesty and openness were key. They discussed which course Rick should teach, considering his desire to make a significant contribution to a field in need. Jim suggested project management, aligning with Rick's aspirations and Jim's own research interests.

In another scene, university presidents, including B.J. vonBraun, discussed the potential oversupply of MBA graduates and the declining number of applicants. Bernard Goldsmith and Alistair Franklin shared their concerns about the sustainability of business school growth. They debated solutions, including legislative requirements for managers to hold MBAs, but acknowledged the difficulty of enforcing such measures.

B.J., analytical and ambitious, pondered ways to enhance her university’s reputation and attract more applicants. She considered supporting and cultivating existing talent within her business school, though the likelihood of finding unrecognized brilliance was uncertain.

The narrative intertwines the challenges faced by Genemodem in reducing development time and the academic pursuits of Rick Silver and university presidents in maintaining the relevance and reputation of their programs amidst changing market demands.

Can Genemodem's Think Tank Solve the Development Time Crisis and Save Their Market Share?

As Rick Silver entered the MBA classroom, he was taken aback by the number of students—nearly thirty, but he was ready. With a summer spent diving deep into project management literature and interviewing veterans in the field, Rick felt prepared for anything. The room quieted down, but the back row remained restless. 

Rick pointed to a burly man lingering in the back. "What's your name?" Rick asked. "Mark Kowalski," the man responded loudly. Mark was a project leader at a modem company, grappling with unrealistic promises made by his predecessor. His grin faded as he admitted to having issues managing his project due to these wild promises about performance and delivery time.

Wanting to engage the class, Rick proposed two paths: a semester of intense lectures on optimization techniques or a collaborative effort drawing from their real-world experiences to improve project management. Mark raised a hand, curious about what he should expect from the course. Rick promised that the course would equip him to better handle his project's challenges.

They dove into discussing the infamous Channel Tunnel project, which ran over budget and was delayed, and the North Sea oil rigs with their notorious overruns. But Rick also shared the success story of the U-2 spy plane, developed in just eight months—a stark contrast to typical ten-year timelines. This prompted Fred, an accountant, to question the rarity of such successful projects.

Fred's assignment on a new production facility in Malaysia revealed typical project issues: budget overruns, delays, and quality complaints. The official reasons blamed external factors—weather, vendors, government negotiations—while unofficial reasons pointed to internal issues like unrealistic schedules and poor supervision. The class recognized a pattern: higher-level managers blamed external factors while lower-level managers identified internal problems.

The discussion turned to the role of uncertainty in projects. They acknowledged that every step in a project involves uncertainty, leading people to build in substantial safety buffers to cover unforeseen issues. Mark admitted that his time estimates included significant safety margins, often 200% of the median time required. They realized that while uncertainties are inherent in projects, the way they manage these uncertainties can drastically affect outcomes.

Rick assigned the class to investigate the embedded safety in their project time estimates, emphasizing the importance of understanding this aspect to improve project management. Despite initial resistance due to the workload, the class agreed to delve deeper into their projects.

Later, Mark, Ruth, and Fred discussed their findings. They noticed that estimates often matched actual completion times, suggesting a self-fulfilling prophecy—adding safety time without changing outcomes. Ruth argued that this pattern mirrored production issues, where extended delivery promises didn't improve performance. They debated whether gathering more data or deeper analysis was needed, but Ruth was adamant that understanding the safety embedded in projects was crucial for reaching their goal of better management practices.

In the end, they all agreed that uncovering the root causes of project overruns and delays, and learning to manage uncertainty effectively, could lead to significantly better project outcomes.

Mastering Project Management: Lessons from Channel Tunnel, North Sea Oil, and U-2 Spy Plane

Chris walked into B.J.'s office with frustration bubbling under the surface. He dropped a memo onto her desk, declaring it "totally unacceptable." B.J., steadfast and unyielding, challenged him on the need to trim the budget due to fewer student registrations. The argument escalated, with B.J. suggesting course reductions and merging classes, while Chris insisted on a long-term strategy, feeling defeated by her logic.

B.J. knew she had only won a battle, with more challenges ahead. Seeking advice, she asked her trusted colleague Bernard for help. Driving away from town, B.J. expressed her concern about the declining business school enrollments. Bernard listened patiently as she revealed her findings from a recent survey—business schools were failing to deliver valuable education, unlike law schools, which had simply over-supplied the market.

The stark reality hit hard—MBA programs were seen as increasingly irrelevant. B.J. and Bernard realized the dire need to address the issue before the business schools collapsed, potentially dragging other university departments down with them. B.J., overwhelmed by the responsibility, contemplated resigning, unable to bring herself to slash and reform the very institution she fought to build. Bernard, however, urged her to act now to minimize the trauma.

Meanwhile, Rick was grappling with his own academic pressures. His colleague Jim had dropped a stack of papers on his desk, excited about their potential for a good article. They discussed categorizing reasons for project snafus and the importance of focusing on the critical path in project management. Rick noticed a pattern: companies often saved a small percentage on costs but incurred significant delays, turning profitable projects into losers. Jim saw potential for further research and articles.

Rick's anxiety about tenure and budget cuts led him to seek reassurance from Jim, who assured him that his tenure was safe despite high-level political games at the university.

In class, Rick faced a lively discussion on project management techniques. Ruth and other students debated the importance of focusing on the critical path versus starting every path early or late. They concluded that existing progress measurements overlooked the critical path, leading to delayed project completions. The session ended with Rick feeling triumphant about the passionate and practical learning that took place.

At home, Rick found a surprise—a brand new Chevy Blazer, a gift from his wife Judith. Despite her excitement, Rick was concerned about their financial situation. Judith's frustration with their constant need to wait and budget boiled over, leading to a heartfelt confrontation. Rick's attempts to calm her only highlighted the sacrifices and losses they had endured together.

Are MBA Programs Becoming Irrelevant in Today's Education Landscape?

Jim dropped Rick's article on his desk with a comment, "Not bad for a first draft." The pages were covered in red marks, a testament to Jim's meticulous nature. He encouraged Rick, saying it would be publishable soon, but stressed the importance of producing more articles. He mentioned Johnny's lack of interest in modeling the financial impact of project delays, surprising given Johnny's usual enthusiasm for mathematical models.

In an attempt to find alternatives, Rick suggested generating new ideas. Jim was skeptical but listened as Rick explained his brainstorming with students. Rick proposed tackling the optimization problem of early versus late project start. Jim was initially dismissive but eventually agreed that Rick's focus on project managers' ability to concentrate was a significant insight, albeit impractical without a mathematical solution.

During a faculty colloquium, Johnny Fisher shared his experiences at UniCo, introducing the Theory of Constraints (TOC). He explained TOC's management philosophy, research methods, and applications, emphasizing the conflict between controlling cost and protecting throughput in organizations.

Johnny illustrated the concept using a chain analogy, highlighting the need to focus on the weakest link to improve overall performance. He presented a five-step focusing process: 
1. Identify constraints, 
2. Exploit them, 
3. Subordinate other efforts, 
4. Elevate constraints, and 
5. Avoid inertia.

Johnny demonstrated the impracticality of compromising between cost and throughput, revealing that local efficiencies often lead to increased costs. He challenged the assumption that good cost performance requires good local performance everywhere, advocating for a focus on system constraints instead.

Johnny's story about UniCo's turnaround of a steel company emphasized the power of TOC. By questioning the industry's reliance on tons-per-hour as a prime measurement, they identified and addressed the core issue, leading to significant improvements without additional investments.

The experience showcased the transformative potential of TOC's thinking processes, encouraging the pursuit of solutions beyond traditional optimization models.

Johnny Fisher Unveils Theory of Constraints at UniCo

The classroom was filled with a palpable tension. Rick Silver had given the class an assignment to interview people about the safety margins added to project time estimates, but the desks were mostly bare. Only one report had been submitted. 

Frustration bubbled up as he questioned the students, who looked everywhere but at him. Ted revealed that people were reluctant to discuss their safety margins, and Charlie added that even his attempts at probing were met with laughter or vague answers.

Rick realized he had erred in his instructions. People always believe their estimates are realistic, not padded with safety as the class was meant to uncover. Explaining that safety translates to a high probability of completion, he hoped to recalibrate their approach. Charlie shared a discovery: time estimates are heavily influenced by the last overrun experienced. This revelation lightened the mood, bringing laughter.

Ted, still bitter from his failed attempts, added that foremen typically claimed over 90% certainty in their estimates, provided all conditions were ideal. Mark and Ruth chimed in with insights from their questionnaire, showing that while most believed they had a high chance of finishing on time, their confidence was contingent on external factors not delaying them.

Rick summarized: the class had confirmed the expected overconfidence in estimates and the hidden safety margins. Fred then shared a surprising finding: in his company, time estimates often ballooned because each management level added its own safety factor, and top management routinely cut project time by a percentage, leading everyone to inflate their estimates initially.

Rick noted three mechanisms for safety insertion: pessimistic experiences, multiple management levels, and protection against global cuts. However, projects often still ran late. Ted offered an example of a mall construction delayed by weather and rework, despite the original 14-month estimate.

A discussion ensued about the inefficiencies in safety usage. Delays from one step accumulated, while advances were wasted. Multi-tasking inflated lead times as workers juggled multiple tasks, each step taking longer overall. This self-fulfilling prophecy was recognized as a major issue.

Rick then gave the class a new assignment: identify examples of each mechanism that adds and wastes safety, numerically. The session ended, but the quest for better project management continued.

Are Hidden Safety Margins Sabotaging Your Project Deadlines?

Mark, Ruth, and Fred had become fervent believers in a new project management method after their last class session. Their zeal was evident as they persuaded their professor, Rick Silver, to speak to Mark's team at Genemodem, who were developing the A226 modem. The professor didn't know much about modems but was adept at identifying project management pitfalls. He had spent three hours with the team, guiding them to understand the issues and solutions.

The team recognized that padding each step with safety time was counterproductive, leading to wasted time through mechanisms like student syndrome, multitasking, and accumulated delays. They agreed to strip away the safety time from individual steps and instead protect the critical path with a project buffer.

Despite initial resistance, the team saw the logic in focusing on the critical path and adding buffers to protect it from delays in non-critical paths. The professor also introduced the concept of the resource buffer, ensuring that resources would be available when needed.

Mark's team implemented these changes, and within three weeks, they saw significant improvements. The pressure to compromise on quality or specifications had diminished, and the team was working more efficiently without false alarms and procrastination. The reduction in multitasking led to a calmer work environment, and the resource buffers ensured that critical path steps were not delayed due to unavailable resources.

The class discussed the challenges of implementing these ideas with vendors and subcontractors, who often focused solely on price. Roger, a student skeptical about vendor collaboration, invited the professor to join a meeting with a subcontractor. The professor managed to persuade the vendor to offer options trading price for lead time, proving that vendors could be flexible when approached correctly.

Roger, impressed by the professor's success, admitted he had already secured approval from his company's top management to pay for shorter lead times, understanding the financial impact of delays. The professor's methods were proving effective, and even the most cynical students were starting to see their value.

Transforming Project Management: A Lesson from the Professor

Isaac Levy is thrilled with the progress of the project, which is set to be delivered two months ahead of schedule without compromising any specifications. Despite the good mood, Levy reminds the team that the final tests have just begun, and anything could still happen. Ruth is uncertain about marketing, but Levy agrees it's better to keep them informed to avoid wasting gains.

Levy contemplates the team's success, acknowledging their method's potential but expressing concerns about its scalability across multiple projects. He questions the criteria for their promised ten thousand shares, emphasizing the need for their method to become the company norm. The team agrees to hire Professor Silver for consulting, ensuring they continue to refine and prove their approach.

Rick faces a dilemma at Genemodem with several projects sharing a bottleneck skill. He consults Jim and Johnny, who brainstorm solutions. Johnny suggests focusing on the constraint and critical path, but they realize it’s complicated when multiple projects are involved. Rick’s student Ted brings up the issue of lead times and penalties in the construction industry, revealing how contractors benefit from delays through change orders.

Johnny proposes a solution: developers should incentivize contractors with bonuses for early completion and penalties for delays, transforming the competitive landscape. Rick agrees, recognizing the potential for contractors to gain a competitive edge by shortening lead times.

Later, Rick is invited to speak at the Young President's Organization (YPO) dinner. Despite initial nerves, he delivers a successful presentation on project management. The presidents, including Pullman from Genemodem, acknowledge the benefits of his methods. Rick's boss, B.J., seizes the opportunity to advocate for more support for the Executive MBA program, suggesting a special track tailored to their needs.

Rick reflects on the possibility of creating a valuable, full two-year program based on the new knowledge he's developed, feeling optimistic about the future. As he walks to his car, the star-filled sky mirrors his hopeful outlook.

Is Rick's Revolutionary Project Management Strategy the Key to Genemodem's Success?

It's Saturday morning, and Rick is grappling with what to teach his class. His original plan was to discuss "projects' bottleneck," but Jim, who is evaluating the students’ knowledge, will be present. Rick decides to focus on buffers instead, hoping it will be enough to stimulate discussion.

Rick starts the class by reviewing the concepts of project-buffer, feeding-buffer, and resource-buffer. Ruth raises a question about what happens when delays in noncritical paths exhaust feeding buffers and penetrate the project buffer, suggesting the critical path changes. This sparks a lively debate. The students realize that the critical path might indeed change due to severe delays in noncritical paths, complicating project management.

Charlie shares a real-world issue where resource contention causes delays. Rick then introduces the concept of a "critical chain," emphasizing the importance of considering resource dependencies alongside path dependencies. The class learns to identify and manage the critical chain, acknowledging that sometimes resource limitations dictate project timelines more than task sequences do.

Rick's class ends with the students eager to apply the new insights to their projects. Jim praises Rick’s teaching style, noting how it fosters the creation of new knowledge right in front of the students.

In another part of the story, B.J., Chris, and Jim discuss tailoring the Executive MBA program to meet local companies' needs. They realize that while the subjects covered are standard, the content and delivery must bring tangible value to companies. They agree on using real-life scenarios and teaching problem-solving skills systematically. Jim suggests a radical idea: companies should pay for the program only after students deliver substantial benefits to their organizations. Despite initial hesitation, B.J. sees the potential and decides to explore it further.

Later, Rick and his team impress Don Pederson from UniCo with their project management insights, but he raises concerns about investment justification. Charlene proposes a new way to evaluate investments, using the concept of "dollar-days" rather than traditional methods. This approach considers the true impact of time and money constraints, offering a more accurate measure for investment decisions.

The narrative concludes with Rick's university poised to offer a groundbreaking MBA program centered around Theory of Constraints, promising real-world benefits and national acclaim.

Revolutionizing MBA Programs: Rick's Insightful Lessons & Bold Innovations

Reflecting on the challenges faced by Genemodem and the academic pursuits at the university, a few key insights emerge. Pullman's strategy to confront the development time mismatch by launching a think tank underscores the importance of innovative thinking in addressing urgent business problems. The chosen managers' diverse backgrounds highlight the value of interdisciplinary approaches in problem-solving.

Rick Silver's journey reveals the anxieties and opportunities within academia, emphasizing the significance of practical engagement and honest communication in teaching. His approach to project management, particularly focusing on the critical path and buffers, offers practical solutions to common project issues like delays and inefficiencies.

The university presidents' discussions on the oversupply of MBA graduates and the declining applicant numbers stress the need for business schools to adapt and demonstrate their value in a changing market. B.J.'s contemplation on enhancing her university's reputation reflects the broader challenge of maintaining relevance in education.

Rick’s classroom experiences, especially uncovering safety margins in project time estimates, illustrate the pervasive issue of overconfidence and inefficiency in project management. The insights gained from managing uncertainties and focusing on the critical path can lead to significant improvements in project outcomes.

The integration of Theory of Constraints into business practices, as demonstrated by Johnny Fisher, showcases a powerful approach to improving organizational performance by addressing system constraints rather than local efficiencies.

Overall, these insights emphasize the importance of innovative thinking, practical engagement, interdisciplinary collaboration, and adaptive strategies in both business and academia to navigate and overcome complex challenges.

Home

Trending Books

News & Mags

Relax

Curated

Collections

Key Ideas & Notes

Insights

Highlights & Bookmarks

Listening History

Key Ideas

#1