The first 90 days in a new job are not the time for demonstrating initiatives, quick wins, or attempting to impress management. This approach, often promoted in onboarding programs, can lead to unforeseen conflicts and long-term stagnation. The author's experience, spanning 20 years in IT and over 10 years in leadership positions, shows that employees who hold strong positions after a year focus their first three months on an invisible but critically important task—building an organizational map.

Three Layers of the Company Map

This map consists of three key layers:

1. The Real Power Structure

The formal organizational structure often differs from the real one. A new employee only sees the official hierarchy, but real power may belong to people in different positions. For example, a CTO may formally lead, but actual decisions might be made by a long-standing architect with influence on the board. Similarly, product advancement might be driven not by a Product Director, but by a Senior Product Owner with a direct line to senior management. In HR, real hiring decisions might depend on a specific HR manager who has strong ties with lead recruiters.

Gathering this information involves observation: who is listened to in meetings, who can interrupt without consequence, who has direct access to leadership, and who is approached for specific problem-solving. The goal within the first 90 days is to understand the real influence of the three to five key individuals you will be working with. An initiative directed at the wrong person may go unanswered, while approaching the right person can resolve an issue in a single day.

2. Boundaries and Taboos

Every company has unspoken topics whose discussion can provoke a disproportionately negative reaction. This is often due to past conflicts, grievances, or failures. A new employee, by accidentally touching upon such a "taboo," may encounter misunderstanding and problems.

Examples of such taboos include:

• Reasons for reorganization or team disbandment if the decision was controversial.
• Criticism of past product launch failures, especially if current employees were involved.
• Mentioning specific vendors with whom the company has poor relations.

This information is conveyed verbally and is not available to newcomers. Identifying these taboos requires careful observation: how people react to certain topics, which phrases cause abrupt silence. Any comparison to previous work experience without understanding these nuances can lead to conflict.

3. Working and Mimic Processes

Every company has formal processes: planning, retrospectives, code reviews, technical committees, etc. However, not all of them function equally. Some processes are real decision-making mechanisms, while others are merely formalities.

It is critically important to understand this difference within the first 90 days. Planning can be either a real decision-making process or a ritual for voicing decisions already made behind closed doors. Retrospectives can serve for genuine reflection or be a formal hour where only positive aspects are discussed. Technical committees can genuinely define architecture or merely approve decisions made in advance by key individuals.

An employee who does not understand this difference risks wasting time preparing for "theatrical" meetings or missing opportunities to influence real processes by not preparing for them adequately. The task within the first 90 days is to test key processes, assessing where real decision-making occurs and where it is merely imitation. This will allow you to determine which processes are worth investing effort in and where formal participation is sufficient.

Strategy for the First 90 Days

Activity in the first 90 days without understanding the company's internal map is a "shot in the dark." Even a brilliant idea, proposed to the wrong person or within a non-functional process, will not be implemented and can create enemies. Externally, such behavior appears dull: completing assigned tasks, listening attentively in meetings, asking clarifying questions without judgmental opinions, and refraining from criticizing existing processes or suggesting their overhaul.

Internally, however, active information gathering is taking place: every meeting, every conversation, every comment on a neighboring team's code review is data for building a model of the organization. By the end of the 90 days, such an employee will have developed a comprehensive model, allowing them to act consciously.

Managers observing this behavior might consider the employee "normal, but not yet shining." This is the correct impression. Those who "shine" in the first few months have often already stepped on "mines" and will be dealing with the consequences. An employee who gathers information accumulates capital for a future breakthrough.

Managing Manager Expectations

Tasks assigned by a manager should be executed excellently – this is visible activity. It is better to postpone initiatives and strategic proposals until the fourth or fifth month. By this time, the employee will have formed a map that allows them to propose a solution that will be implemented through the right processes and with the right people. An initiative proposed in the second week might create enemies and not be accepted. The same initiative in the fifth month, fitting into the right structure, will become the first major success.

In the case of a strict 90-day probationary period, demonstrating results should consist of excellent execution of assigned tasks and active participation in meetings by asking intelligent questions. Companies expecting a revolution from a newcomer on probation have a poor hiring culture. A good company, in the first 90 days, tests the employee's ability to work within the existing context, rather than redesigning it.

Key Question for a Manager

In the first week of a new job, instead of asking about 90-day goals, ask your manager: "Is there anything I should absolutely avoid doing in the first 3 months?" This question can reveal two or three specific mistakes that previous new hires made, providing a valuable part of the organizational map for free.

Often, people who didn't pass their probation period or struggled through it were active in the first 30-60 days, got into unforeseen conflicts, and then spent time resolving them, despite their technical competence. The problem lay in "acting in the dark" with high activity.

Conclusion

Those who do nothing outwardly in the first 90 days but actively map the organization find themselves in the strongest position after a year. This invisible work allows them to act consciously, avoiding pitfalls and conflicts. The first 90 days are a unique window for information gathering that should be used to build a foundation for the next 3-5 years, rather than for attempts to impress others. Observing the real power structure, identifying taboos, and understanding work processes will allow one to reach a position after a year that may seem inexplicable to more "active" colleagues.