When you start a new job, it is inevitable to experience a flood of emotions that can be somewhat difficult to manage: from a huge excitement to prove your ability to do things well, and the pressure and uncertainty of facing a new challenge, to the feeling that, with an outsider's perspective, it is possible to quickly detect what is not working.
During the first few weeks, you begin to observe patterns that seem obvious: processes that could be simplified, teams that seem lacking in motivation, managers who feel stuck, or professionals with great potential who, nevertheless, are not being recognized as they should be.
Following this assessment, the phrase "There is a lot to fix here" will immediately pop into your head. However, let us tell you that experience shows that the initial analyses of a newly appointed leader are not always as objective as they seem. The urge to act, the limited information available, and the human tendency to look for quick explanations can turn an initial perception into a false certainty.
The urge to change before understanding
One of the greatest risks for a newly arrived leader is confusing speed in decision-making with the actual impact that those new ideas or measures might have. There is an implicit expectation that a new hire must identify opportunities for improvement and quickly demonstrate that their arrival generates value. In executive positions, this pressure increases because the organization expects a different perspective and decisions that mark a new chapter.
This phenomenon is related to what psychology calls action bias: the tendency to prefer doing something over waiting around, even when there is not yet enough information to intervene correctly.
In business contexts, this bias can translate into premature changes in performance appraisal processes, organizational structures, or talent management models. Not because those initiatives are necessarily wrong, but because they may respond more to the new leader's need to act rather than a real need of the organization.
Before transforming a system, it is necessary to understand how it works. A performance appraisal with low participation, for example, can be interpreted as a commitment issue. However, it could also be related to a lack of communication, a lack of trust in the process, a poor prior experience, or a negative perception regarding how results are used. The exact same signal can have completely different root causes.
The first stories you hear can distort the diagnosis
When you are new to a company, the initial conversations carry enormous weight. It is your first reality check, which may or may not align with what you imagined about your role or position in the new company.
You listen to other colleagues explaining their experiences, gather concrete examples, and begin to build an initial mental picture of the organization. The problem arises when those individual experiences begin to represent a collective reality without being verified.
This mechanism is related to the availability bias, described by Kahneman and Amos Tversky, which explains how we give more importance to information that is most present or easiest to recall. To put it simply, consider the following case: A team with a bad experience with their manager can create the perception that there is a widespread leadership problem. A leader failing to recognize the talent of the team or a specific person at a particular moment can quickly lead us to the idea that "the company does not recognize talent." But... is that actually true?
An organization cannot be diagnosed solely through the individual experiences of employees, let alone generalized. It is necessary to analyze patterns. Therefore, the question we must ask ourselves is not whether a problem exists, but rather understanding how it came to be:
-
Does it affect all teams, or is it concentrated in specific areas?
-
Is it a cultural issue, or does it depend on specific managers?
-
Is it a historical trend or a recent situation?
Without this information, the risk is turning a specific experience into a global explanation.
The desire to demonstrate value can lead to intervening in the wrong places
When there is pressure to justify the hiring decision, the newly onboarded person may make the mistake of implementing changes in aspects of the organization where they were not needed. Modifying a process, launching a new survey, or redesigning a talent model can generate activity, but it won't necessarily solve a real need.
In change management, this distinction is fundamental. John Kotter, a professor at Harvard Business School and author of Leading Change, has highlighted the importance of creating a sense of urgency based on a true understanding of the problem before driving transformations. Effective change does not start with a solution. It starts with a shared diagnosis.
The first step is not to transform, it is to segment
Before reaching the decision-making stage, you need to gain perspective, analyze the facts presented, and figure out what might be an objective fact versus an isolated case. An organization is not a homogeneous reality. Within it, different teams, experiences, performance levels, and leadership styles coexist. Therefore, speaking of "cultural problems" without analyzing where they surface can lead to overbroad interventions.
A more accurate approach consists of crossing different dimensions of organizational functioning:
-
The results achieved by the teams.
-
The behaviors observed in the way people work.
-
People's perception of their experience within the organization.
Instead of making broad generalizations like "we have a leadership problem," it is much more useful to propose hypotheses that can be tested.
For example:
"The perceived low performance in department X is related to lower scores in leadership, engagement, and 360-degree feedback."
The difference is significant. The first statement presents a conclusion. The second seeks to find the underlying reason that brought us there. And a testable hypothesis allows for better decisions.
From intuition to analysis: how to reduce the margin of error
A talent diagnosis needs to compare equivalent demographics and observe where the differences actually show up. Analyzing an entire department, a professional category, or a specific group allows you to identify whether you are facing a general trend or specific points for intervention.
For instance, cross-referencing information from 360-degree feedback appraisals, organizational climate indicators, and metrics such as eNPS can help answer questions that intuition alone cannot resolve:
-
Do teams with lower leadership ratings also show lower engagement?
-
Is the problem concentrated around specific managers?
-
Does the negative perception appear across the entire organization or only within specific groups?
Technology applied to People Analytics has precisely this goal: transforming large volumes of scattered data into patterns that enable better decision-making. It is not about measuring more. It is about knowing how to interpret it better.
A leader's maturity lies in knowing when not to intervene
The first few months in a company should not be a race to prove you have all the answers. In reality, it should be a period dedicated to building better questions. A newcomer often starts from the urge to fix everything, when before reaching that point, one must analyze what has been happening before launching any kind of transformation.
Conversely, those who dedicate time to analyzing, segmenting, and validating hypotheses achieve something far more valuable: intervening precisely where a real opportunity for improvement exists. Because in talent management, the most expensive mistake is rarely failing to act. Often, it is acting too soon on a problem that was never truly understood.