Publications

Success Requires Stability and Agility

Deliver Projects Reliably with a Hybrid Approach

Success Requires Stability and Agility

Agility creates value when it sharpens direction and accelerates
execution. For executives, the leverage comes not from adding more methods, but from clearly separating traditional planning for the stable core from adaptive approaches where learning matters most. This improves effectiveness across sales, development, engineering, and project management.

Define What Must Remain Fixed

Agility was not created as a universal doctrine for every organization. It emerged as a response to work characterized by high uncertainty and short learning cycles. The 2001 Agile Manifesto emphasized faster feedback, greater ownership, and closer customer collaboration.

The principle still applies: agility is a means of solving problems more effectively, not an end in itself. Organizations that mirror every market shift immediately may gain speed but often lose strategic focus.

Agility becomes strategically robust when management first defines what is non-negotiable: customer value, the quality promise, the profit model, regulatory requirements, and core technological capabilities.

Match Project Methods to Uncertainty and Value

Practice has already moved in this direction. The Project Management Institute reports a significant increase in hybrid approaches. The key insight is not that one method has prevailed, but that methods must fit the task and environment.

Organizations with broader learning and development offerings also achieve measurably better project performance. This is particularly relevant in sales management, marketing campaigns, information technology (IT) management, software development, and research, where teams must test hypotheses quickly and frequently refine priorities.

In medical technology, plant engineering, engineering, product lifecycle management, and cost-reduction projects, clear approvals, reliable documentation, and disciplined handoffs create greater value. Hybrid management is therefore not a compromise. It is a deliberate operating model for mixed requirements.

Anchor Leadership in Clear Roles and Guardrails

As projects grow, performance depends less on the number of agile rituals and more on the overall management architecture. International Organization for Standardization (ISO) 21502 therefore defines project management broadly enough to support predictive, iterative, adaptive, and hybrid approaches.

This matters in practice. Early product development, value engineering, and hydrogen or circular-economy initiatives require room for alternatives, testing, and rapid learning cycles.

As initiatives move closer to industrialization, regulatory approval, commissioning, quality assurance, or serial operations, clear roles, decision rights, change-control logic, and schedule management become increasingly important.

This is where leadership creates value: not through micromanagement, but through a precisely defined framework that allows teams to move quickly without losing direction.

Use Market Pressure as a Design Requirement

The need for differentiation is increasing across industries. The
Organisation for Economic Co-operation and Development (OECD) describes how digitalization, Artificial Intelligence (AI), and data-driven value creation are changing business models, capability profiles, and ways of working at the same time.

As a result, operating speed, transparency requirements, and investment risk are increasing in parallel. Sales and marketing must learn faster from data. Development and research must reduce uncertainty earlier. Engineering functions must combine innovation with reliability.

In product development, engineering, and plant construction, neither planning alone nor improvisation alone is sufficient. Competitive organizations protect their stable core while deliberately keeping variable elements adaptable.

Implement Three Leadership Rules Now

Three steps apply across most project environments:

  1. Document the strategic constants. Define customer value, target costs, quality levels, regulatory boundaries, and core technologies.
  2. Segment the project methodology and governance portfolio by uncertainty. Determine where learning needs are high, where reliability becomes critical, and how to manage the transition between the two.
  3. Redesign roles, decisions, and escalation paths. Create short decision paths for teams, clear intervention points for leaders, and a Project Management Office (PMO) that provides direction rather than adding bureaucracy.

This turns agility from a buzzword into a leadership capability: a clear direction combined with deliberately adaptive execution.

Back to Publications