Over the course of my career, I’ve accumulated certifications and experience across project management, Agile delivery, change management, and continuous improvement among others. Each discipline has taught me valuable lessons. Each provides principles, tools, and frameworks that help organizations solve difficult problems, improve performance, and deliver results.
But one lesson has become clearer with experience:
Organizations achieve better outcomes when they focus first on the problem they are trying to solve and the results they are trying to achieve, rather than the methodology they have chosen to follow.
That may sound obvious, but in practice, it is surprisingly easy to lose sight of.
I’ve sat in meetings where considerable energy was spent debating whether an initiative was “Agile enough.”
I’ve seen organizations launch major process improvement efforts without first reaching agreement on the business outcome they hoped to improve.
I’ve watched project teams work diligently to preserve a plan even as changing circumstances made parts of that plan increasingly disconnected from reality.
In each case, intelligent and capable people were trying to do the right thing. They were applying methods they had learned, methods that had worked before, or methods their organizations had formally adopted.
The problem was not competence.
The problem was that the methodology had gradually become the focal point instead of the outcome.
The longer I work in transformation, delivery, and operational excellence, the more convinced I become that methodologies are not destinations. Methodologies are tools, and like any tool, their usefulness depends on the problem, the environment, and the objective.
- Agile can be highly effective when teams are navigating uncertainty, learning quickly, and iterating toward a solution.
- Lean Six Sigma can be exceptionally valuable when an organization needs to improve quality, reduce variation, eliminate waste, or increase predictability.
- Traditional project management disciplines can provide essential structure when commitments, budgets, dependencies, schedules, and governance require careful coordination.
- Change management practices can help ensure that even the best solution is understood, adopted, and sustained by the people affected by it.
Each approach brings value, but each is also (or can be) incomplete on its own.
Agile will not solve every delivery challenge. Lean Six Sigma does not determine strategic direction. A highly predictive project approach can struggle when conditions change faster than the plan. Change management cannot compensate for a flawed solution or an unclear strategy.
That is not a criticism of these disciplines.
It is simply recognition that no framework was designed to answer every organizational challenge.
Start With Context
If methodologies are tools, then context should determine which tools we use.
The more useful question is not: “Which methodology should we use?”
The more useful question is: “What does this situation require?”
Answering that question requires understanding context before selecting an approach.
For example:
- What outcome are we trying to achieve?
- What problem are we actually solving?
- How does this work support the organization’s strategy?
- What constraints and risks matter most?
- How much uncertainty are we dealing with?
- What stakeholders need from the outcome?
- What capabilities does the organization already possess?
- These questions should come before the methodology discussion.
A company pursuing aggressive growth may require a very different operating model than one focused on profitability and operational efficiency.
A team facing a regulatory deadline may need greater structure, documentation, and traceability than a team exploring a new product concept.
An organization integrating an acquisition may require a combination of governance, process redesign, change management, and iterative problem-solving practices.
A mature team operating in a stable environment may benefit from standardization and predictability. A team confronting significant uncertainty may need experimentation, rapid feedback loops, and frequent reassessment.
The frameworks available to these organizations may be the same, but the appropriate combination of practices likely is not.
That is why I increasingly view methodology as something that should be downstream of strategy and context.
Strategy determines what the organization is trying to accomplish.
Context shapes what is possible.
Methodology provides tools for getting there.
Discipline Without Dogma
Being methodology-agnostic does not mean being undisciplined, nor does it mean ignoring proven practices, inventing processes arbitrarily, or changing direction whenever circumstances become difficult. In many situations, following a framework closely is exactly the right decision. The difference is intentionality.
Effective leaders understand which principles are essential, which practices can be adapted, and which constraints cannot be ignored. They do not begin with a predetermined answer. They begin with the outcome they are trying to achieve and then select the practices most likely to support it.
Sometimes that means applying a methodology largely as designed.
Sometimes it means blending disciplines.
A project may use traditional governance for financial management, risk oversight, executive reporting, and dependency management while delivery teams work iteratively.
A process improvement initiative may use Lean techniques to identify waste, Six Sigma tools to understand variation, project management practices to coordinate implementation, and change management disciplines to support adoption.
These approaches are not contradictions.
They are responses to different dimensions of the same problem.
Adapting a framework does not mean abandoning discipline.
In fact, thoughtful adaptation often requires more discipline because it demands an understanding of both the principles behind the methodology and the realities of the environment in which it is being applied.
Following a framework is relatively straightforward. Knowing when to follow it, when to adapt it, and when another approach is more appropriate requires judgment. That judgment develops through experience.
The Organization Is the System
One of the reasons methodology-first thinking falls short is that organizations are not collections of isolated projects, processes, or teams: They are interconnected systems.
Systems composed of people, processes, technologies, incentives, constraints, customers, suppliers, regulators, and competing priorities. They also operate within environments that continually change:
- Economic conditions change.
- Customer expectations change.
- Technology changes.
- Regulations change.
- Competitors change.
- Leadership priorities change.
No methodology can eliminate that complexity. At its best, a methodology provides a structured way to navigate part of it. But a framework should never become a substitute for understanding the system itself. The objective should not be methodological purity.
The objective should be creating an operating approach that fits the organization, supports its strategy, responds to its environment, and increases the probability of achieving meaningful outcomes.
Sometimes that approach may look Agile.
Sometimes it may look Lean.
Sometimes it may look like traditional project management.
Most often, it will look like a thoughtful combination of several disciplines.
And it may evolve as circumstances change.
That is not inconsistency.
It is adaptation.
Better Organizations, Not Better Framework Implementations
This brings me back to the central point: Organizations are best served by an outcome-focused, methodology-agnostic approach that considers the challenge at hand, the environment in which they operate, and the long-term strategy they are trying to achieve.
- Frameworks matter.
- Experience matters.
- Process matters.
- Discipline matters.
But none of them should become more important than the results they are intended to support.
The goal is not Agile maturity.
The goal is not Lean maturity.
The goal is not project management maturity.
The goal is organizational effectiveness.
The organizations that consistently succeed are not those that demonstrate the purest implementation of a framework. They are the ones that understand their objectives, understand their environment, and apply the right combination of practices to achieve meaningful results.
Ultimately, methodologies should serve the organization; the organization should never serve the methodology.