Key Takeaways
Run projects with plans for delivery and adaptation for uncertainty
Two kinds of control. Project Management Second Order, or PM-2, combines conventional planning with complexity management. The first control cycle compares progress with a plan and corrects deviations. The second treats managers as participants inside a changing system, where communication, observation, and experimentation help the project respond. Neither replaces the other: a project still has a deadline and a defined result, but its route may be unpredictable.
Four connected lenses. PM-2 also asks managers to consider technical delivery, complexity, human behavior, and the assumptions or rules shaping decisions. A familiar construction project may need mostly conventional controls. Research involving new technology, multiple cultures, or changing stakeholders may require all four lenses.
The model's strength is its refusal to choose between control and flexibility as universal virtues. It resembles a useful principle from control theory: a system needs both a target and feedback about changing conditions. The caution is practical. Broad ideas such as self-organization can sound profound while leaving teams unsure what to do on Monday. PM-2 is most useful when translated into explicit decisions about who can change scope, how often plans are revisited, and what evidence triggers a response.
Map complexity across mission, organization, delivery, stakeholders, and team
Five sources of difficulty. The MODeST model organizes managerial complexity into mission, organization, delivery, stakeholders, and team. It was developed from workshops and responses involving 128 project managers, who generated 160 concepts about what makes projects difficult to manage. Examples include unclear goals, organizational restructuring, unfamiliar methods, changing stakeholder needs, and shifting team motivation.
Track change and interaction. Complexity is not just a snapshot of how many elements a project contains. Each category can change, and changes can interact. A restructuring, for example, may alter staffing, decisions, and stakeholder relationships at once. The researchers also suggest that too much or too little of a factor, such as senior-management involvement, can create difficulty.
MODeST is valuable because it makes complexity discussable without pretending that a single score captures it. Its emphasis on changing relationships echoes ecological models, where effects arise from interactions rather than isolated components. The model also places the project manager inside the system: choices about decomposition or stakeholder engagement can change the difficulty being assessed. Because the findings reflect managers' perceptions, the framework is a diagnostic map, not proof that every listed factor causes failure.
Make owners examine strategic exposure alongside operational risks
A skewed risk picture. Researchers examined about 1,550 risk entries across seven large projects. Roughly 91 percent concerned operational delivery, about 9 percent concerned short-term strategic effects, and none were classified as long-term strategic risks. Even among the projects' highest-priority risks, 82 percent were operational. Examples included site stoppages and installation productivity, while strategic risks included an undefined operating strategy or disagreement among partners.
Different success horizons. Project managers are often judged on delivery, while owners bear the cost and future value of the investment. Yet the studied owners and project teams both tended to focus on operational problems. The authors suggest clarifying whether an owner's representative acts as a strategic manager or mainly as an additional project manager.
This finding exposes a governance problem hidden by a tidy risk register: what gets counted often reflects the people closest to the work, not the organization's largest exposure. In principal-agent terms, owners and delivery teams have different information and incentives, so regular dialogue matters. A strategic-risk review should not displace practical controls, though. Long-horizon risks are harder to quantify and can become vague speculation unless tied to explicit benefits, assumptions, and decision owners.
Plan in short feedback cycles when scope keeps moving
Let evidence set the detail. Research on dynamic environments supports starting with a high-level plan, then elaborating work as information arrives. Useful methods include prototypes, pilots, staged releases, and parallel experiments. The right balance depends on the cost of change: a safety-critical construction job may benefit from resisting change, while rapidly evolving software may lose value if it waits for a perfect plan.
Sense portfolio changes early. In four project portfolios studied at two companies, scope changes were a more important source of uncertainty than shifts in corporate strategy. One software group found that only about half of early requirements reached the market. It separated early requirement investigation from project execution and shortened the planning horizon for content to roughly one or two months.
This is a strong argument for matching planning cadence to the rate at which knowledge changes. It also makes experimentation an investment in information, not merely a concession to poor planning. The trade-off is that iterative work can multiply coordination demands, especially across dependent teams. Short cycles need clear authority to select, defer, or cancel work, plus a stable view of what must remain reliable. Otherwise, flexibility becomes churn with better branding.
Reduce complexity before integrating what cannot be separated
Three practices for complex systems. An Ericsson case study describes a practical approach to large telecom projects. First, lagomizing means reducing ambitious specifications to functionality the team can reliably deliver and test. Second, organic integration builds and tests system capabilities in increments, using a shared picture of how functions depend on one another. Third, the Systems Emergency Ward is a highly visible daily meeting where managers and specialists review defects and make rapid decisions.
Make errors useful quickly. Complex systems can contain layered defects: correcting one problem may expose another. Frequent integration and public problem-solving help reveal these interactions sooner. The system anatomy used in the case maps functional dependencies, rather than assuming that every component can be cleanly isolated.
The case adds needed specificity to the abstract advice to be agile: reduce scope, integrate real capabilities, and give experts a place to resolve failures quickly. It also resembles reliability engineering, where early testing reveals interactions that component-level checks miss. Scope reduction is not automatically customer value, however. If managers narrow requirements without transparent agreement about what matters, a reliable delivery can still be the wrong product.
Tie every deliverable to value, measures, risks, and accountable owners
A project brief that connects the dots. The Logical Framework Approach-Millennium, or LFA-M, updates the older logical framework so it fits contemporary project management. Its Logframe-Millennium matrix connects four commitments, organizational value, scope or deliverables, activities, and resources, with success measures, verification methods, risk events, and responsible authorities. Stakeholders also rank measures as essential, flexible, or adjustable.
Build it through dialogue. The seven-step process moves through context, problem, stakeholders, options, activities and resources, risks, and a validated matrix. The steps can be revisited as information changes. At Canada's nuclear safety regulator, the approach helped frame a research project on predicting steam-generator tube failures and leak rates, connecting technical work to its safety purpose and ways to assess results.
The matrix is useful because it forces a project to explain not only what it will produce, but why the result matters and who remains accountable. That structure can prevent a technically successful project from drifting away from its organizational purpose. A limitation is that matrices reward what can be specified early. For discovery work, measures should be treated as revisable hypotheses, not promises that suppress learning.
Design collaboration to move expertise across organizational boundaries
More than goodwill. In multipartner projects, collaboration quality describes how well partners communicate, coordinate, support one another, align effort, and maintain a shared commitment. A literature-based model identifies trust, clear roles, compatible goals, aligned incentives, conflict resolution, and fulfilled expectations as conditions that can support this quality. Good collaboration helps partners combine specialist knowledge into decisions and usable work.
Make practice shareable. A health-care case describes a national committee of regional project-management offices that developed methods, templates, and a shared language. Experienced members passed on know-how while newer members tested and refined common tools. This learning depended on interaction, not simply storing lessons in a database; tacit expertise is difficult to transfer as a document alone.
The insight links social structure to technical performance: partners cannot integrate knowledge they do not trust one another enough to reveal. Communities of practice and project forums help turn individual know-how into collective capability. Still, collaboration has costs, and more communication is not always better. The useful question is whether a meeting or network resolves a dependency, shares a needed skill, or improves a decision. Without that purpose, collaboration becomes overhead.
Build team morale before free-riding weakens shared understanding
Morale shapes participation. In a study of 279 students working in software-development teams, higher team morale was strongly associated with less free-riding. Free-riding means taking the benefits of team membership while contributing less than a fair share. It harmed performance partly by preventing members from building shared knowledge of the task and of one another's expertise. Larger teams showed a smaller, marginal association with more free-riding.
Set the social conditions early. The study suggests using a project kickoff to establish why the work matters, what members owe the group, and how their skills fit together. A separate study of 52 project managers in one UK financial-services company found links between several leadership dimensions, including resource management and empowering colleagues, and aspects of project delivery or usability.
The mechanism matters: weak contribution does not merely reduce labor; it also deprives the team of conversations through which members learn who knows what. That makes morale a coordination resource, not just a pleasant atmosphere. The evidence is suggestive rather than universal, since the free-riding experiment used student teams and the leadership study sampled one company. In professional settings, clear task ownership and visible contribution can complement morale without turning every interaction into surveillance.
Judge public projects by public value, not cost control alone
Governance must earn trust. Four Australian public-sector cases found that project management helped organizations improve accountability, transparency, risk reporting, and consistency of delivery. These features matter when projects spend public funds under scrutiny from taxpayers, media, politicians, service users, and auditors. Political requests can also change priorities during delivery.
Value has several dimensions. The cases show that value for money matters, but it is not the only test. Housing, disability services, and infrastructure projects must also deliver benefits to users and communities. Project methods can provide evidence and coordination, but they cannot fix shortages of skilled staff or eliminate the need to adapt processes to different public-service settings.
The public-sector cases distinguish efficient administration from legitimate outcomes. A project can meet its budget and still fail the people it was meant to serve. This fits public-value approaches that treat citizen needs and participation as part of performance, not external decoration. The counterpressure is real: flexible consultation can blur accountability or invite political interference. Good governance therefore needs both traceable decisions and a credible route for affected communities to influence them.
Use project controls as scaffolding, not a cage, for new products
Innovation resists complete definition. A new-product project, such as developing a dishwasher, spans concept design, feasibility, engineering, testing, production, marketing, and eventually product withdrawal. Standard project tools help organize tasks, resources, and schedules, but innovative work has interdependent activities and uncertain solution paths. The complete scope may not be knowable at the start.
Track income as well as cost. Unlike a conventional delivery project, product development is an investment expected to generate sales over a product life cycle. A narrow focus on budget can discourage features that create customer value. The paper also finds gaps in standard guidance on team dynamics, innovation-supporting leadership, organizational learning, and the effects of output-based controls. Stage gates and lean methods may help in some settings, but the article calls for stronger evidence about when they work.
The distinction between delivering a product and developing a business opportunity is essential. A schedule can track engineering progress, but it cannot by itself establish that customers will want the result or that sales justify the investment. This resembles portfolio thinking, where the value of a bet includes both downside and future returns. Controls still matter: uncertainty is not a license for endless scope growth. The challenge is to preserve financial discipline while allowing evidence to reshape the design.
Switch leadership modes when conditions invalidate the plan
Four modes, no universal winner. A study compared two polar expeditions and examined whether leaders explored or used existing expertise, and whether they followed a plan or adapted to events. In the Arctic expedition, a leader's chosen dogs escaped, and he failed to respond effectively; another team member improvised a protective alarm system from equipment already available. In the Antarctic expedition, storms broke the ship's moorings, forcing its leader to evacuate the site and navigate through danger.
Authority depends on judgment. The comparison found no single mode that guarantees success. What mattered was the ability to change modes as the situation changed. The collection's superyacht study makes a related point: when bespoke requirements shift late in a build, experienced managers often improvise to meet delivery constraints.
The expeditions make a powerful case that expertise includes knowing when a familiar procedure no longer fits. This connects to adaptive leadership: leaders preserve direction while changing the method, and they sometimes need to let a team member's knowledge correct their own judgment. Switching modes is not automatically wise, however. In high-risk environments, teams need shared thresholds for when to stop, escalate, or depart from the plan, so improvisation is informed rather than impulsive.
Analysis
This collection does not present one unified agile method. It assembles research papers that approach projects through complexity theory, risk governance, team behavior, innovation, public administration, and field cases. Their common argument is narrower and more useful: conventional plans remain necessary, but they cannot be treated as complete descriptions of a project whose goals, stakeholders, technologies, or surrounding conditions continue to change.
The strongest practical synthesis is a layered management approach. Establish an explicit purpose and delivery commitments. Distinguish risks to immediate outputs from risks to long-term benefits. Use short feedback cycles where uncertainty is high, while retaining firmer controls where safety, regulation, or stable requirements demand them. Make collaboration and authority visible, because information and decision rights are distributed across owners, project teams, users, suppliers, and specialists. The cases show that adaptation is not simply a softer version of control. It requires structures: prototypes, integration routines, risk reviews, accountable owners, and forums where problems can be surfaced quickly.
The evidence is uneven, which is typical of a journal anthology. Some claims arise from interviews or conceptual models, some from case studies, and the free-riding article uses student teams. These sources illuminate mechanisms, but they do not establish that one approach works everywhere. The collection is strongest when it offers concrete practices and weakest when broad scientific paradigms are presented as universal future doctrine. Its enduring contribution is therefore not a replacement for project standards, but a disciplined challenge to apply them contingently. Managers should ask what is stable enough to plan, what must be learned through action, and who is authorized to revise the route without losing sight of the intended value.
Glossary
Project Management Second Order (PM-2)
dual-cycle project managementA reference model that combines traditional project planning and control with methods for managing complexity, such as observation, communication, experimentation, and adaptation. It treats projects as goal-directed endeavors that still need defined outcomes, while recognizing that nonlinear conditions and human systems can make the route to those outcomes unpredictable.
MODeST
five-part complexity mapA grounded model of managerial complexity in projects. Its five dimensions are mission, organization, delivery, stakeholders, and team. The model includes both relatively stable conditions and changes over time, as well as interactions among those conditions, offering managers a structured way to describe what makes a project difficult to manage.
Logical Framework Approach-Millennium (LFA-M)
iterative project-design processAn updated, seven-step approach for clarifying a project's organizational context, problem, stakeholders, options, activities, resources, and risks. It leads to a high-level matrix that connects organizational value to deliverables and execution. The process is intended to involve stakeholders and integrate with project approval, planning, and evaluation tools.
Logframe-Millennium (LF-M)
project commitments matrixThe matrix produced through the LFA-M. It organizes four commitments, organizational value, scope or deliverables, activities, and resources, alongside success measures, means of verification, risk events, and responsible authorities. It is designed to connect a project's purpose with what it will produce and how progress and risks will be assessed.
lagomizing
top-down scope reductionA practice described in complex systems development in which project leaders reduce or reinterpret ambitious specifications so the team can deliver functionality it understands and can test reliably. It aims to contain scope growth and complexity. Because it changes expectations, it requires care to ensure that reduced scope still meets the customer's meaningful needs.
organic integration
incremental capability integrationA method for developing complex systems by assembling and testing basic system capabilities before adding more advanced ones. It uses a shared representation of functional dependencies, sometimes called a system anatomy, to coordinate integration. The approach assumes components may not work correctly at first and seeks to expose errors early.
Systemakut
daily systems problem forumAn Ericsson practice, translated as Systems Emergency Ward, in which project managers and relevant specialists meet frequently, often daily, to examine reported defects and make rapid decisions. Its visibility signals management attention, while its hands-on discussions help integrate expertise and control the effects of changes in complex systems.
project-collaboration quality
quality of partner interactionA way of assessing how well organizations or groups work together, based on the fluency of their interactions rather than only on eventual results. Its elements are communication, coordination, mutual support, aligned effort, and cohesion. The concept is used to explain how collaboration can help partners integrate knowledge and pursue shared project outcomes.
ambidexterity
ability to change action modesIn the project-leadership discussion, ambidexterity is the capacity to move between complementary modes of action. Leaders may rely on existing knowledge or explore new possibilities, and may follow a plan or adapt to events. The polar-expedition cases suggest that effectiveness depends less on one favored mode than on recognizing when a different mode is needed.
team morale
shared commitment to team workThe collective attitudes and shared commitment of team members toward their assignments. In the student software-team study, stronger morale was associated with less free-riding. The concept captures how members' shared expectations that the work matters and deserves effort can shape participation and support the development of common task understanding.
Download PDF
Download EPUB
.epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.