For a long time, I tried to understand what was happening inside this company as a collection of isolated cases. Decisions that were difficult to explain, uncomfortable situations, people who never quite fit in. Everything seemed to have a specific justification when viewed separately.
But after spending enough time inside, that interpretation starts to fall apart.
You begin to notice that these are not independent events, but repetitions of the same pattern. People with real capability (both in business and technical areas) arrive with the intention of contributing, identify clear problems, propose concrete improvements, and, in some cases, even develop solutions on their own.
And still, nothing happens.
There is no serious technical evaluation. No in-depth discussion. No explicit decision to move forward or reject ideas based on actual criteria. Instead, there is something much harder to point at: a kind of diffuse resistance, ambiguous responses, a constant feeling that things simply never move forward.
Meanwhile, the problems that had already been identified remain exactly where they were.
The most striking thing is not that this happens once. It is that it happens consistently, with different people, at different moments, with proposals that, at least on paper, make sense.
That is where the perspective changes.
Because at some point, it stops being reasonable to think the problem lies in each individual person or in each specific idea. When the same outcome repeats itself over and over again, with capable people and solid approaches, the explanation can no longer be circumstantial.
It has to be structural.
And that is the starting point of what I need to tell you.
When that pattern repeats itself for years, across different people and different departments, there comes a point where it no longer makes sense to search for individual explanations.
It cannot be that every person trying to push improvements is wrong.
It cannot be that every idea fails because of the way it is presented.
It cannot always be a matter of timing.
I have seen it in business, where generating results was not enough to sustain proposals for change.
I have seen it in technical areas, where identifying real problems ended up being more uncomfortable than useful.
And I also see it in how certain positions become consolidated, where alignment with the structure weighs more than the ability to create value.
When you put all of this together, it stops looking like a collection of isolated cases.
It starts to look like a system functioning exactly as it was designed to function.
And that is where the focus changes.
Because the problem is no longer whether an idea is good or bad.
Nor whether a person is right or wrong.
The problem is something else.
The problem is that this organization has no real mechanism to absorb those kinds of initiatives.
There is no clear process where a proposal can be evaluated outside of the established structure. There is no space where technical or business judgment weighs more than organizational inertia. There is no structure capable of turning a good idea into an executable decision.
What does exist is a system that favors predictability. A system designed to preserve stability, avoid deviations, and operate within what is already known. And everything that falls outside of that, even when it makes sense, generates friction.
And that friction rarely appears as a direct rejection.
It is more subtle than that.
Ideas are not openly dismissed. They simply do not move forward. They dissolve over time. They lose priority. They are left behind without any explicit decision.
And meanwhile, the organization reinforces itself. The people who create discomfort eventually leave or adapt. he people who fit the structure without friction become consolidated.
And the system continues operating… exactly the same way.
That is when the conclusion stops being uncomfortable and becomes obvious.
It is not a talent problem. It is not an initiative problem.
It is a design problem.
There is something difficult to accept, but necessary to say clearly: this company works.
The processes exist (inefficiently). The teams deliver (not at the required level). The day-to-day operation continues (the company survives).
And that is precisely where the problem begins.
Because everything is designed so that operations continue without disruption. So that what is already known can be repeated predictably. So that there are no deviations.
That kind of structure is efficient in the short term. But it has a side effect that is being ignored: any attempt to improve something that requires change automatically becomes an anomaly.
Not because the improvement does not make sense.
But because it does not fit the system.
When someone proposes a solution, whether technical or business-related, it does not enter an environment prepared to evaluate it. It enters a system that already has its priorities, its timelines, and its way of operating completely predefined.
And then something very characteristic happens.
The proposal is not rejected directly. Nobody says, “this makes no sense.”
But it is not integrated either. It gets postponed. Repositioned. Diluted among other urgencies.
There is always something more immediate. Something more aligned with what is already in motion. Something that does not force the organization to rethink anything.
And little by little, improvement loses momentum until it disappears.
Meanwhile, the operation continues. Incidents are resolved. Customers are attended to. Systems that already have known limitations continue being maintained.
And all of that consumes the organization’s capacity.
To the point where a very clear paradox appears.
There is no time to improve because all the time is spent sustaining what no longer works properly.
And this is not inevitable. It is a design decision.
It could be different. You could separate operations from improvement. You could create protected spaces where not everything competes against urgency. You could measure not only what gets solved, but what stops repeating itself.
But today, that does not happen.
And in this context, the people trying to introduce improvements are not competing against a single bad decision.
They are competing against an entire system designed to prioritize continuity over evolution.
And against that, a good idea alone is not enough.
There is another pattern that becomes evident over time, and it is harder to recognize because it is not explicit.
Not all ideas have the same path… regardless of their quality.
It is not only about what is being proposed.
It is about where the proposal comes from.
In this company, technical or business judgment is not always the deciding factor. What truly determines whether something moves forward or not is how well it fits within the hierarchical structure.
If an idea comes from below, from someone working in operations or in a technical role, it starts at a disadvantage. It does not matter whether it is well thought out or whether it solves a real problem. Its future depends on someone with more authority validating it.
And if that validation never comes, the idea simply stays there.
It is never discussed in depth.
It is never technically challenged or evaluated.
It is never brought into a space where it can compete against other priorities.
It gets excluded before it even has the chance to play.
And this is not accidental. It is design.
Because there is no real system where ideas can compete based on merit. Everything depends on intermediaries, hierarchy, and alignment.
At the same time, something else happens that you should pay close attention to.
Similar ideas, or even less developed ones, do move forward when they come from positions of greater authority or when they align more closely with what leadership already has in mind.
Not necessarily because they are better. But because they are safer within the system. They do not force the organization to rethink itself. They do not challenge too much. They do not generate friction.
And within this structure, that weighs more than the actual value of the proposal.
Over time, this completely changes the rules of the game.
Decisions stop being based on the best available judgment and begin depending on who proposes the idea, who supports it, and how well it fits within what is already established.
And when that happens, the system stops optimizing for quality.
It starts optimizing for stability.
This has a direct consequence that is already becoming visible.
The people trying to contribute through real knowledge, the ones who understand the problem and propose solutions, begin colliding with the system constantly.
Not because they are wrong.
But because they operate under a different logic: they are trying to solve problems, not navigate structures.
And this is where you have to make a choice.
Either you maintain a system where ideas need permission to exist.
Or you build one where ideas compete based on their value.
That means creating formal spaces where proposals can be evaluated regardless of who brings them forward. It means defining clear decision-making criteria. It means allowing knowledge to carry more weight than position.
Because right now, that balance is broken.
And when hierarchy weighs more than judgment, what becomes impossible is not making decisions.
It becomes impossible to improve.
There is another factor that ultimately explains why ideas do not move forward in this company, even when they make sense.
It is not only a matter of communication or alignment.
It is a matter of how decisions are made.
In practice, there is a single real point of decision-making.
Everything goes through you.
And the rest of the figures who, in theory, should contribute judgment, directors, managers, middle leadership, do not truly act in that capacity. They are not there to evaluate, challenge, or enrich proposals. They are there to ensure that what has already been decided gets executed.
That has an immediate consequence: there is no real space where an idea can be analyzed independently.
There is no debate. There is no contrast of perspectives. There is no real discussion between different points of view.
And without that, there are no high-quality decisions.
Everything gets filtered through a single vision.
Yours.
And this is not a personal issue. It is a structural limitation. No organization can scale if everything depends on a single analytical capacity, a single interpretation, a single way of understanding reality.
This already has several consequences.
The first one is obvious: the company’s ability to process ideas is extremely limited. It does not matter how many proposals exist or how well they are developed. Everything depends on whether you understand them, value them, and decide to push them forward.
That creates a bottleneck.
And that bottleneck is slowing down the entire organization.
The second consequence is quieter, but just as serious: distributed responsibility disappears.
No one defends an idea. No one pushes it forward. No one makes it move inside the system.
Because deep down, everyone knows the decision is not really theirs to make.
And once people understand they have no real ability to influence outcomes, they stop trying.
They limit themselves to execution.
And this can also be changed.
It is not about losing control. It is about redesigning how decisions are made.
About creating spaces where different profiles can evaluate proposals with real judgment.
About assigning real responsibility to middle-management roles.
About allowing decisions to be built collaboratively, instead of being validated only from the top.
Because right now, the organization is not only wasting the talent it already has.
It is giving up its ability to question itself and improve.
Everything gets reduced to execution.
And execution, without real distributed decision-making capacity, eventually becomes nothing more than repeating the same thing over and over again.
There is another element that ultimately reinforces everything described so far, and it is probably the hardest one to detect from the inside.
The culture of risk.
No one here explicitly says that people should not propose ideas, innovate, or try to improve things. There is no written rule prohibiting it.
But in practice, the system sends a much clearer message.
Trying to change something comes with a cost.
It means exposing yourself. It means questioning how things are being done. And many times, it means pointing out problems that already exist and that others have chosen to ignore.
And within this organization, that is not neutral.
The people who push for change generate friction. Not because they are doing something wrong, but because they force the system out of its comfort zone.
And that friction accumulates.
Over time, those people start being perceived as uncomfortable, difficult to fit in, not fully aligned.
Not because of what they contribute. But because of what they disrupt.
Meanwhile, the people who remain inside the established framework, without questioning anything, without pushing for change, operate with much greater stability.
Not necessarily because they provide more value. But because they do not create problems.
And in that balance, the company sends a very clear message, even if it is never said out loud.
It is safer not to try changing anything than to try improving something.
And eventually, people internalize that message.
People stop proposing ideas. They stop insisting. They stop pushing.
Not because they do not see the problems, but because they understand how the system works.
And that is how the cycle closes.
Ideas do not disappear because they do not exist.
They disappear because no one is willing to assume the cost of pushing them forward in this environment.
And once that happens, there is no longer any need to block change explicitly.
The system itself takes care of preventing it from appearing.
But this, too, is a design decision.
And it can be changed.
It is possible to build an environment where proposing ideas is not punished, where questioning things is not a personal risk, where improving something does not mean exposing yourself alone.
That requires something very concrete: aligning incentives.
Recognizing the people who improve things.
Protecting those who challenge the system with judgment and criteria.
Valuing the attempt, even when it does not succeed.
Because right now, the opposite is happening.
And while the opposite continues happening, the rational behavior inside this company will always be the same.
Do not move.
And a company where the safest option is not to move… is a company that has already started falling behind.
There is one final element that reinforces everything described so far and makes it even harder to break.
The company never leaves operational mode.
The day-to-day operation is completely consumed by incidents, emergencies, support tasks, and problems that require immediate solutions. And by itself, that would not be a problem. Every company has operations.
The problem begins when operations consume everything. For example, a local trade fair can paralyze every department. Nothing else moves forward. Any external demand has to wait.
Inside this company, there is no real space to build for the medium or long term. There is no protected time to improve the product, redesign processes, or attack structural problems. Everything becomes subordinated to urgency.
And urgency always wins.
There is always something more immediate. There is always something that “cannot wait.” There is always a reason not to stop and rethink anything.
And little by little, without realizing it, the company enters into a self-reinforcing dynamic.
The same problems repeat themselves over and over again because they are never addressed at the root level. They are solved superficially, just enough to keep operating, but never enough to truly disappear.
And that feeds the system itself.
More problems generate more operational work.
More operational work eliminates any space for improvement.
Less improvement ensures that the problems continue to exist.
A perfect loop.
A loop that keeps the company functioning, but increasingly limited.
In that environment, any initiative that is not directly tied to putting out a fire is automatically pushed aside. Not because it lacks importance, but because it cannot compete against immediate urgency.
And that has a very clear consequence.
The company becomes highly skilled at sustaining itself… but not at evolving.
It works. But it does not improve. And the most delicate part is that, from the inside, this gradually starts to feel normal. Even inevitable.
But it is not.
It is not a problem of lacking time.
It is a design problem.
You could create protected spaces where improvement does not compete against operations.
You could dedicate specific resources to eliminating root problems.
You could measure success not only by what gets solved today, but by what stops happening tomorrow.
But today, none of that is happening.
And as long as that does not change, the company will remain trapped in this cycle.
Constantly solving what is urgent, while what is important never truly gets addressed.
And an organization that lives permanently in reaction mode eventually loses its ability to anticipate.
And once that happens, it loses real control over its own future.
Everything I have described to you so far is not just a way of working. It is not a theoretical issue or a subjective interpretation.
It has very concrete consequences.
And the most concerning part is that many of those consequences are not openly recognized. They become normalized. They integrate into the daily routine until they stop looking like problems.
Inside the company, the effect is not immediate. There is no visible collapse. No sudden fall that forces a reaction.
What exists is a progressive deterioration.
The company continues generating revenue, but sustaining it becomes increasingly difficult.
Opportunities continue being closed, but the foundation they are built on becomes increasingly fragile.
Decisions continue being made, but they become increasingly disconnected from technical reality and from what is actually happening with customers.
And that kind of deterioration is especially dangerous because it is not perceived as an emergency.
It is perceived as normality.
A growing dependence on external solutions also begins to appear, even for problems that, in another context, could have been developed internally.
More money gets invested.
More time gets consumed.
And even then, the results are not always better.
Not because it would have been impossible to build internally.
But because the system does not allow it.
Meanwhile, the structural problems remain there, silently accumulating.
But where the impact becomes most visible, and hardest to reverse, is in people.
The individuals who have real judgment, both technical and business-related, tend to go through a very clear process.
First, they try to contribute. Then they try to adapt. Eventually, they begin to feel frustrated.
And finally, they make a decision.
Either they disconnect… or they leave.
Some reduce their level of involvement and limit themselves to simply fulfilling expectations. They do what is required, but they stop trying to improve what they already know will never change.
Others look for environments where their capabilities actually have room to grow.
In both cases, the company loses something valuable.
Not only talent.
It loses its ability to question itself. It loses its ability to improve. It loses its ability to evolve.
And that is not something easily recovered.
The most paradoxical part is that, from the inside, this is not always perceived as a real problem.
Because the system continues functioning. Operations continue. The results, although weaker, still exist.
But beneath that apparent stability, something far more difficult to measure is being lost.
The ability to do things better is disappearing.
And when a company loses that, it does not fail all at once.
It slowly falls behind.
Until one day, it becomes too late to fix anything without breaking everything apart.
There is something else that has gradually established itself and further reinforces everything described so far.
Control has stopped being a means and has become an end in itself.
Not as a tool for improvement, but as a way to preserve order, hierarchy, and predictability.
And inside this company, that can be seen in many details of everyday work.
In the constant need to limit access. In the obsession with controlling information. In the centralization of decisions, even the smallest ones. In the appearance of barriers around tasks that should be simple.
Sharing information stops being something natural and becomes mediated.
Accessing tools becomes a process.
Even basic actions require validation.
Everything has to go through someone.
In theory, all of this is justified as security, control, or governance.
But in practice, the effect is something very different.
It slows everything down.
Every step requires permission.
Every advance depends on validation.
Every initiative loses momentum before it even begins.
But something deeper also happens, and it is even more concerning.
It changes the organization’s focus.
People stop thinking about how to do things better.
And they start thinking about who is allowed to do what, who has permission, who validates.
Work stops flowing naturally.
Responsibility becomes diluted.
Initiative decreases.
And what should be a system oriented toward results turns into a system oriented toward control.
And there is a key idea here that you should seriously consider.
More control does not equal more strength.
When control weighs more than execution, the company does not become more robust.
It becomes slower.
And in an environment where the ability to adapt and execute quickly makes the difference, becoming slow is not just an operational detail.
It is a structural disadvantage.
There is another pattern that ultimately closes the system and explains why, even when there is real capability inside the company, it never translates into real improvement.
It has to do with how positions of responsibility are assigned.
In theory, key positions should be occupied by people with judgment, experience, and the ability to make decisions that bring value to the organization.
But in practice, what often gets prioritized is something else.
Alignment with the structure.
People become consolidated because they do not question, do not generate friction, and execute without deviating. Profiles that fit well into the system as it already exists, even if they are not necessarily the people capable of taking it to a higher level.
This is never said openly.
No one openly says they are looking for people who do not think or do not question things.
But the decisions being made consistently point in that direction.
And over time, the effect becomes obvious.
Positions with influence stop being spaces where the organization improves.
They become spaces where the organization maintains itself.
Where the priority is no longer moving forward, but ensuring that everything continues functioning exactly as it always has.
And that creates a structural consequence that is very difficult to reverse.
A gap begins to form.
On one side, the people with the greatest real capability,the ones who understand the problems, who can propose solutions, who could elevate the organization, are not in decision-making positions.
On the other side, the decision-making positions are not designed to leverage that capability, nor to incorporate it.
And once that disconnect becomes consolidated, the company stops evolving from within.
Not because it lacks talent.
But because it has built a system where that talent has no access to the spaces where decisions are actually made.
And until that changes, every attempt at improvement will continue colliding with the same limit.
Not the limit of capability.
The limit of organizational design.
For all of this to sustain itself over time, something else is required.
A story is needed to explain it.
And inside this company, that story exists, even if it is not always spoken explicitly. It is the way things are interpreted whenever something does not fit.
When someone capable leaves, the context is never deeply analyzed. People simply say they “could not adapt.”
When an initiative does not move forward, the system itself is never questioned. People say “it was not the right moment.”
When someone points out real problems, no real investigation happens. People say “they are too negative.”
These are explanations that fit comfortably within the structure.
They are comfortable explanations.
But they serve a very specific function.
They prevent the system itself from being questioned.
Because questioning it would mean recognizing that there are things that are not functioning as they should. It would mean accepting that the problem is not isolated, but structural.
And that would open the door to changes that the organization, as it is currently designed, is not prepared to face.
So instead of reviewing the model, the narrative gets adjusted.
And that narrative allows everything to continue exactly the same. Without apparent conflict. Without visible rupture.
But also without real improvement.
And within this context, something else also happens to the people inside the system.
It becomes very easy to fall into a trap.
To think that the problem is yourself.
That you are not explaining ideas correctly. That you lack context. That you need more support or more validation.
And that leads you to insist harder. To improve the form, polish the message, search for the right moment.
But over time, if you observe honestly, you eventually realize something even more uncomfortable.
The problem is not how you are doing it.
It is where you are doing it.
You are trying to introduce a logic of improvement into a system designed to preserve stability. You are operating with judgment inside an environment where judgment is not the main driver of decision-making.
And in that context, doing things better does not always produce better outcomes.
Sometimes, it only creates more friction.
And yet, the company continues functioning.
It operates.
It generates business.
It sustains itself.
But that does not mean it is healthy.
Because beneath that apparent stability, there is something that is either not being seen, or not being acknowledged.
Talent that cannot find space.
Ideas that never even get evaluated.
Problems that repeat themselves without ever being solved at the root.
And none of that happens by accident.
It happens because the system was designed this way.
Not to grow through the capabilities it already has inside.
But to preserve itself exactly as it is.
And that leaves us with a question that can no longer be avoided.
If an organization is not capable of taking advantage of the people it already has,
if it is not capable of listening to, evaluating, and executing improvements that emerge from within…
what real possibility does it have of improving?
I do not know if there is still time to change it.
But to do so, you would first have to accept something difficult:
that the main limitation of this company is no longer the market.
It is the way the company is being led.
— An employee who still sees what this company could become