Framework, model and method – this is really a question of different levels of governance and implementation. Many organizations use the words sloppy or trendy, which makes them seem interchangeable. But the concepts often describe completely different things: from vision and direction to concrete work instructions.
Summary of the knowledge area:
Frameworks, methods and models
Brief
If one views an organization as a journey from the current state to the desired state, one can see the concepts as different layers:
| Question | Typical tool |
| Where are we going? | Vision, strategy, business plan |
| How are we going to get there? | Roadmap, framework, methodology |
| How should we work along the way? | Methodology, regulations |
| How exactly do we do it? | Process, routine, checklist, instruction |
| How does it look good in practice? | Role model, best practice |
Many misunderstandings arise because one expects a high-level tool to provide answers at a low level.
Examples:
- One business plan says that the company will grow by 30 %.
- One roadmap shows which initiatives are to be implemented.
- One framework describes the areas that need to be addressed.
- One method describes how to work.
- One checklist describes exactly what needs to be checked.
The problem is that many organizations stick with a roadmap, framework, or methodology and believe that they have thereby created operational capability. It’s almost like giving someone a map of Sweden when they really need GPS navigation to a specific address. That’s why many employees feel that they are told: ”We’re going to follow our transformation framework,” but never: ”On Monday you do step 1, on Tuesday step 2, and on Wednesday step 3.”
To understand why, one needs to distinguish between:
- Description tools (explain)
- Management tools (control)
- Implementation tools (to perform)
That is the last category that creates real behavior.
History
During industrialization, the following dominated:
- Instructions
- procedures
- standards
Taylorism and continuous lines required that work be described in great detail. As work became more knowledge-intensive in the later part of the 20th century, organizations began to use:
- models
- framework
- management system
The idea was that people would no longer simply follow instructions but make their own decisions. However, the result was that the amount of abstract concepts increased significantly.
Business plan
A business plan answers the following questions: What do we want to achieve and why?
Often contains:
- goals
- economic forecasts
- market
- strategy
- Priorities
Examples:
- Sales are expected to increase by 20% %
- establishment in a new country
- launching a new service
The business plan usually does not contain detailed work instructions. It is a management document.
Roadmap
A roadmap is a time-bound roadmap. It answers the following questions: When should different things happen?
Examples:
- Q1: preliminary study
- Q2: development
- Q3: pilot
- Q4: launch
A roadmap rarely says exactly how the work is carried out. It rather describes the order of things.
Framework
A framework describes the building blocks that are needed. It answers the following questions: Which areas need to be addressed? Examples:
ITIL
- Incident Management
- Change Management
- Problem Management
COBIT
- Governance
- Risk
- Control
SAFe
- Portfolio
- Program
- Team
Frameworks are almost never step-by-step. They describe what should be there - not exactly how.
Model
A model is a simplified representation of reality. Examples:
- SWOT
- Porter Five Forces
- Kotter's change model
Models are used for analysis and understanding. They are not work instructions.
Method
A method describes how to work to achieve a specific result. Example: Design Thinking
- Understanding the user
- Define the problem
- Generating ideas
- Test
- Improve
A methodology is significantly more operational than a framework.
Methodology
A lot of confusion arises here. Methodology is basically: The science of methods or The principles behind the choice of methods. Example: Agile methodology says:
- Iterative development
- customer focus
- tight feedback loops
But it does not exactly describe how each work step should be performed. The methodology provides the mindset – the methods provide the working methods.
Rules Book
A regulatory framework answers: What are we allowed to do and what are we not allowed to do? Examples:
- Information security
- economy
- compliance
- Quality requirements
Rules create boundaries. They rarely describe the process.
Role Model
A role model is not a method. It is: a living example. People often learn faster by observing behavior than by documents. Examples:
- Senior consultant
- successful manager
- Experienced project manager
Therefore, mentoring is often more effective than another framework.
Checklist
The checklist is the most concrete tool. It answers the following questions: Have we done everything required? Examples before production setup:
- Test conducted
- Backup verified
- Documentation updated
- Approval obtained
Checklists are extremely underrated. The airline industry, healthcare, and the nuclear power industry use them because they actually influence behavior.
Level of abstraction
A simple way to think about it:
| Strategy ↓ Business plan ↓ Roadmap ↓ Frameworks ↓ Method ↓ Process ↓ Routine ↓ Checklist |
The further down the list goes, the more concrete it gets. The higher up the list goes, the more freedom there is.
Common misunderstandings
Organizations often buy:
- SAFe
- ITIL
- COBIT
- TOGAF
and believe that they bought a ready-made solution. In reality, they often bought:
- structure
- concept
- principles
but not a finished way of working. They have to translate this themselves into:
- processes
- routines
- Checklists
Ecosystem
The concepts live together. A realistic example:
- Business plan: Become the market leader.
- Roadmap: Three-year change program.
- Framework: SAFe.
- Method: Scrum.
- Regulations: Information security.
- Role model: Experienced product owners.
- Checklist: Definition of Done.
When everything works properly, the levels are connected to each other. When it doesn’t work properly, only documents are available at the higher levels.
Practical example 1
Many companies are introducing ”agile work”. They create:
- vision
- roadmap
- framework
But never:
- daily instructions
- Checklists
- coaching
Results: No one knows what should actually be done.
Practical example 2
In the aviation industry there are:
- framework
- methods
- Rules
but also very detailed checklists. That is an important explanation for the high level of security. One does not rely solely on abstract models.
Summary
The most important insight is that these concepts operate at different levels.
| Concepts | Question |
| Business plan | What do we want to achieve? |
| Roadmap | When will it happen? |
| Frameworks | What parts are needed? |
| Model | How can we understand the situation? |
| Methodology | What principles govern the work? |
| Method | How do we work? |
| Rules book | What rules apply? |
| Role model | What does successful behavior look like? |
| Checklist | What concrete steps must be implemented? |
Advantages
When the concepts are used correctly:
- better governance
- clearer responsibilities
- easier priorities
- Scalability
- more consistent working methods
Disadvantages, risks and limitations
When the concepts are mixed up:
- Unclear expectations
- documents without practical value
- Many meetings but few results
- shifting the responsibility
- ”management theater”
The most common risk is that the organization produces more models than behavioral changes.
Why is there so little ”do-this-this-way”?
This question goes to the heart of the matter. There are at least five reasons:
1. Reality varies
A general method must work in many environments. Therefore, it becomes abstract.
2. Responsibility is transferred
Consultants, standardization bodies and framework owners often want to provide direction, not take responsibility for implementation.
3. Knowledge work cannot be fully controlled in detail
Programmers, researchers, sales people and managers often have to make their own decisions.
4. Organizations underestimate operationalization
You invest in strategy but not in the translation into everyday work.
5. Practical knowledge is expensive to document
Creating a useful checklist is often much more difficult than creating a neat framework.
Five readiness questions
- Do we know what result we are trying to achieve?
- Do we have a method that leads to the result?
- Are there clear rules and responsibilities?
- Has the method been translated into processes, routines and checklists?
- Can a new employee understand the work without asking an expert?
If the answer to question 5 is no, the organization likely has too much methodology and too little operationalization.
Recommendation
If you encounter a new framework or a new model, always ask three questions:
- What does this help me understand?
- How does this help me to make a decision?
- How does this help me do anything at 8:00 AM on Monday morning?
Only when the third question can be answered have the ideas been transformed into real organizational capability.
Read more about the framework->
