Knowledge
Problem Map
Common organisational, operational, data, cyber and legal signals — written in the language people actually use when something is not working.
Before the service, name the situation.
The Problem Map is not a list of services. It is a practical collection of situations, symptoms and warning signs that often appear before a clear decision can be made. Each item points toward the INGENS area that may help clarify the problem.
Shared signals
Universal Problems
Everything was supposed to work, and it does not.
If you have arrived here, you are probably not looking for another tool, report or presentation. You are looking for an answer. In many organisations, problems do not come from a lack of work. They come from a lack of clarity. The first step is to understand the situation and separate symptoms from causes.
I spent the money, and the problem stayed.
New systems, new machines, new processes or new services do not always solve the problem. Sometimes they remove only the symptoms. Before the next investment appears, it is worth checking whether the problem has been defined properly.
I know something is wrong, but I do not know what.
This is more common than it may seem. Organisations usually notice the effects of problems much earlier than their causes. The purpose of analysis is to find the place where the problem is actually being created.
I have run out of ideas.
Sometimes the greatest value is not another solution, but a fresh view of the situation. People who work with a problem every day often stop seeing things that are obvious to someone from outside.
Everyone says something different.
Different people see the same problem from different perspectives. That does not mean someone is wrong. It means there is no shared picture of the situation that would allow decisions to be made on facts rather than opinions.
The company is growing, and I have less and less control.
Company growth often increases complexity faster than revenue. This is a natural moment when the old ways of managing the business stop being enough and need to be structured.
I have more people than before and more problems.
A larger team does not always mean greater effectiveness. As an organisation grows, new dependencies, more communication and new risks appear. Sometimes the problem is not the number of people, but the way they work together.
We are constantly firefighting.
If the same problem returns regularly, there is a strong chance that the effects are being removed, not the causes. It is worth stopping for a moment and checking why the problem is being created.
Something is wrong, but I do not know where.
In many cases, the source of a problem is somewhere completely different from the place where its effects are visible. That is why analysis usually starts with questions, not proposed solutions.
It should not look like this.
Experience tells you that something is wrong, even if it is still difficult to name the exact cause. These signals should be treated seriously. They are often the first warning before a larger problem appears.
It was supposed to be easier.
New solutions are meant to help. If after implementation there is more work, more meetings or more complication, it is worth checking whether the right problem was solved.
Why is it getting harder?
Changing market conditions, company growth, new customer requirements or a growing number of systems can gradually increase organisational complexity. This does not always mean a crisis. Often it means the situation needs to be structured.
We have more tools than last year and less time.
Tools should support work, not complicate it. If each new system increases the load instead of reducing it, it is worth looking at the whole process, not only at individual applications.
The problem came back, even though we already solved it.
If the problem comes back, it was probably never fully solved. The symptom disappeared, but the cause stayed in place.
Fuck, nothing works the way it should.
If you have reached this point, the level of frustration is probably already high. The good news is that most organisational problems can be broken into smaller parts, understood and structured. It usually starts with a simple question: what exactly is not working, and since when?
Decision layer
Consulting
The company is growing, and the chaos is growing faster.
Growth should create more capability, but it can also create more dependencies, additional responsibilities and more things that require attention. Chaos does not always mean a lack of competence. It is often the result of growth that has moved faster than the organisation's existing ways of working.
Every important decision ends up on my desk.
Many owners and managers reach a point where the organisation formally delegates responsibility, but the most important decisions still return to one person. This is not always a people problem. Sometimes the problem is the absence of clear rules for making decisions.
I have managers, but everything still goes through me.
Job titles and responsibilities can look right on an organisation chart. In practice, many organisations operate differently from what the documents suggest. If most decisions return to the owner, it is worth checking not only the structure, but also the flow of responsibility.
Everyone is busy. The results are not visible.
High activity does not always mean progress. Meetings, reports, calls and current issues can fill the working day without moving the organisation closer to its goals. It is worth separating busyness from effectiveness.
Everyone says something different, and I do not know who to believe.
Different departments look at the company from different perspectives. Sales sees customers. Production sees constraints. Finance sees costs. Differences do not have to mean conflict. Often they mean there is no shared picture of the situation.
We meet more often than before, and there are more problems.
Additional meetings can improve communication, but they do not replace decisions or action. If the number of meetings grows faster than the number of solved problems, it is worth looking at how the organisation makes decisions.
I do not know which problem to solve first.
When there are many problems, all of them can feel urgent. In practice, some are causes and others are only effects. Setting priorities often creates results faster than fighting everything at the same time.
We keep coming back to the same topics.
If the same topic appears regularly, there is a strong chance that only its symptoms have been addressed. Durable solutions usually require understanding the cause of the problem, not only reacting to its effects.
When something does not work, the search for someone to blame begins.
In stressful situations, organisations often focus on personal responsibility instead of analysing causes. Many problems come from processes, communication or the way work is organised. Finding someone to blame does not always mean solving the problem.
The company works only when I personally keep an eye on everything.
If every important matter requires one person's presence, the organisation becomes dependent on that person. This is a common sign that knowledge, responsibility or processes are not distributed enough. A well-organised company should also work when the owner or director takes a few days off.
Operations
Industrial
I bought new machines and still do not have the results.
New machines can increase production capability, but they do not solve every problem on their own. If the constraints are in planning, work organisation, material flow or communication, even the best equipment will not deliver the expected results. Sometimes the problem is next to the machine, not inside it.
Production is stopped, and people are running around.
This is one of the most common signs of operational problems. High activity does not always mean progress. When people are constantly reacting to the next situation, the organisation can look very busy while the actual flow of work is disrupted.
One shift gets results, the other does not.
If the same process produces different results depending on the shift, it is worth looking not only at people, but also at work standards, training, workstation organisation and how information is handed over. Repeatability is one of the foundations of a stable process.
The warehouse is full, and we are still missing things.
Full shelves do not always mean the right materials are available. In many organisations, the problem is not the quantity of stock, but its structure, location or the way it is managed. Excess and shortages very often exist at the same time.
One failure stops half the company.
Some parts of a process matter much more than others. When a single failure stops a large part of the business, it is worth identifying the key dependencies and assessing the level of operational risk.
Everything works until the first problem appears.
Many processes look good under normal conditions. The real test comes when there is a breakdown, delay or unexpected situation. Process resilience often turns out to be more important than efficiency in ideal conditions.
Everyone works fast, and orders are still late.
Local efficiency does not always translate into the result of the whole process. If every department is working hard and the customer is still waiting, it is worth looking at the flow of work as a whole and finding the places that limit the pace of delivery.
We have more rework and more complaints.
A growing number of errors is often a signal that the process is losing stability. The cause may be organisational change, overloaded teams, missing standards or quality problems. The earlier the first symptoms are noticed, the easier it is to limit their effects.
Every week we fight the same fire.
If the same problem returns regularly, the organisation has probably learned to live with its effects instead of removing its cause. Long-term firefighting consumes time, energy and resources that could be used for development.
It was supposed to create order, and it turned into a fucking mess.
Implementing changes does not always go according to plan. New procedures, systems or ways of organising work can bring additional complexity instead of the expected simplification. Before more changes appear, it is worth checking exactly what stopped working and why.
Evidence
Data Analytics
I have data everywhere, but answers nowhere.
Many organisations collect huge amounts of data. The problem appears when it is difficult to turn that data into concrete decisions. Data does not solve problems by itself. Value appears only when it helps people understand what is really happening in the company.
Every report shows something different.
If different reports lead to different conclusions, the problem is often not in the numbers, but in how they are defined, collected or interpreted. It is worth making sure everyone is talking about the same data.
I do not know which numbers to trust.
Business decisions require trust in data. If the numbers change depending on the report, system or person preparing the summary, it is worth organising the sources of information first.
The KPIs are green, and the company still has problems.
Good indicators should help people understand reality, not replace it. If reports show success but daily work looks different, it is worth checking whether the right things are being measured.
Every department has its own Excel file.
This is a common sign of an organisation that grew faster than its information systems. Local solutions often help solve immediate problems, but over time they make it harder to build a shared picture of the situation.
The data exists, but nobody uses it.
Collecting data by itself does not create value. Information should support decisions, help identify problems and point toward action. Otherwise, it becomes just another administrative obligation.
We spend hours on reports and still guess.
If preparing reports takes more time than using them to make decisions, it is worth looking at the whole reporting process. The goal is not to produce reports. The goal is to understand the situation better.
We have dashboards, but we do not have decisions.
A dashboard can show what is happening. It cannot, by itself, answer what should be done. Data should support the decision-making process, not replace it.
The numbers are right, but reality is not.
Sometimes all reports are technically correct, and still they do not describe what is actually happening in the organisation. In these situations, it is worth checking the assumptions, definitions and method of measurement.
I do not know what really drives the company's results.
Revenue, costs, productivity, quality, customers and processes are connected. Understanding these relationships makes it possible to focus attention on the actions that truly matter for the organisation's results.
Exposure
Cyber Security
I do not know whether we are secure or just lucky.
The absence of incidents does not always mean security. Sometimes it only means the problem has not appeared yet. Risk assessment helps separate real protection from the hope that nothing will happen.
We have backups, but we have never tested them.
A backup is useful only if it can be restored effectively. Regular tests make sure the data will be available when it is truly needed.
The IT person says one thing, the supplier says another.
Different sides often look at the problem from different perspectives. In these situations, an independent view can help assess the risk and make an informed decision.
I am afraid of the day when something stops working.
Many organisations depend on systems whose failure can stop work for hours or days. Understanding dependencies and preparing fallback plans helps limit the effects of unexpected events.
Nobody knows who has access to what.
Over time, the number of accounts, permissions and systems grows. Without regular access reviews, an organisation can lose control over who actually has access to key resources.
Everyone uses their own tools and accounts.
Individual solutions often help solve immediate problems. At the same time, they increase risk around security, data availability and business continuity.
Only after an incident did we start thinking about security.
This is more common than it may seem. Many companies begin analysing security only when a real problem appears. Even then, it is worth treating the incident as an opportunity to put the situation in order.
I do not know where to start securing the company.
Cyber security does not have to start with complicated technology. The most important step is to understand the risk, define priorities and implement actions appropriate to the scale of the organisation.
We have systems, but we do not have certainty.
Having tools does not always mean having control of the situation. What matters is understanding which risks have been reduced and which still require attention.
One email can paralyse the whole working day.
Many incidents begin with a message that looks ordinary. Appropriate procedures, user awareness and organisational preparation help limit the effects of these situations.
Boundaries
Legal Filter
The contract looks good, but something does not feel right.
Experience often suggests that a document deserves a closer look. If doubts appear, it is better to clarify them before signing than after a problem has already been created.
Am I signing myself into a problem?
Not every unfavourable situation is visible immediately in the wording of a document. Sometimes the greatest risk hides in the consequences of clauses that seem unimportant at first glance.
Only after signing did the problems start to appear.
Many disputes begin with different interpretations of the same wording. The earlier potential ambiguities are identified, the easier it is to avoid problems later.
Everyone interprets this clause differently.
If several people draw different conclusions from the same document, it is worth checking whether its meaning is clear enough. Ambiguity often becomes the source of later conflict.
Nobody can clearly say what the risk is.
Making decisions requires understanding possible consequences. The purpose of analysis is not to predict the future, but to identify the areas that may require particular attention.
I do not know whether this is a legal problem or a business problem.
Some situations sit on the boundary between law, organisation and business. Before formal action appears, it is worth understanding the full context of the problem.
We went to the lawyer too late.
In many cases, legal help appears only when the problem already exists. Earlier analysis can help reduce risk and avoid costly consequences.
Everyone says it will be fine. Nobody wants to sign it.
If people involved in the matter avoid formally confirming their position, it is worth stopping and analysing the situation more carefully. Caution often has a reason.
The more I read, the less I understand.
Documents, regulations and contracts can be complicated. The purpose of analysis is not to add more pages of explanation, but to help understand the most important consequences and risks.
I want to know where I stand before I make a decision.
This is a sensible approach. A good decision does not require complete certainty. It requires enough understanding of the situation, possible consequences and available options for action.