There is a moment that does not appear in any onboarding plan, is never mentioned in HR guidelines, and yet almost every IT professional experiences it within the first two to three weeks after starting at a system integrator. It is quiet, unspectacular, and it does not happen in a meeting room. It happens internally. Somewhere between day five and day twenty, when the first excitement has faded, when the first tickets have been seen, when internal communication patterns become visible, when presales and delivery interactions can be observed, when it becomes clear how knowledge is transferred — or not transferred at all.
During this exact phase, we conduct what we internally call PREP conversations. PREP is what happens before and after interviews and again shortly after a candidate has started in their new role: preparation, reflection, debrief. We speak with candidates before interviews, directly after interviews, after their first day, and again after two to three weeks inside the company. Not out of curiosity. Not as a formality. But because this is the phase in which people say things they would never say to their employer.
Across hundreds of these conversations, a very consistent pattern has emerged.
The first question IT professionals ask themselves after joining an integrator is not, “Is this technically interesting?” It is not, “Are the colleagues nice?” It is not even, “Is the salary right?”
The real question is:
“Is this integrator structurally healthy — or are certain people compensating for a system problem every single day?”
This question is never spoken aloud. But it is always there.
IT professionals are exceptional pattern recognizers. They do not need months to understand an organization. Ten working days are enough. In those ten days they see how escalations are handled, how many exceptions exist, how often someone says “That’s just how we do it here,” how much knowledge lives in people’s heads instead of in systems, and whether processes truly exist — or whether individuals are replacing processes.
In these PREP conversations, we hear statements like:
“Officially this is not my job, but without me this would not run.”
“The colleagues are good, but the system is heavy.”
“There are a few people here holding the whole place together.”
“I understand now why this role was open.”
None of these sentences are said inside the company. But they are said to us regularly.
Many integrators are initially described as “very nice.” That sounds positive, but it is not a quality indicator. Often it is a warning signal. Because what candidates feel in week two is not culture — it is structural load. They notice whether colleagues are permanently operating at their limits, whether handovers work, whether account managers and engineers are aligned, whether projects are planned or constantly rescued.
Then comes a sentence that sounds harmless: “You can tell that people here are very committed.” What it really means is: If two or three of these key performers leave, this organization has a serious problem.
These are not complaints. They are precise organizational analyses made after only a few days of observation.
What IT professionals tell us in these conversations is remarkably direct:
“I know now why they are always hiring.”
“This feels grown, but never really built.”
“A lot of know-how, but little order.”
“There are heroes here, but no systems.”
“I don’t think they realize how dependent they are on certain individuals.”
These observations lead to a silent internal evaluation that has nothing to do with salary, title, or technology. The real evaluation is: “Can I work well here long term — or will I permanently have to compensate, improvise, rescue, step in, explain, and replace missing structure?”
Integrators often do not see this themselves because they live inside this structure every day. For them, it is normal. For a new employee, it is contrast. And that contrast is brutally honest. This is why the first twenty days are so revealing.
There is one sentence that appears in almost every second PREP conversation and reveals everything:
“The company is good. But…”
After this “but,” the truth comes out. Too many exceptions. Too many dependencies. Too little clarity. Too little structure. Too much implicit knowledge.
This is also the fundamental difference between integrators that rarely need to hire and those that seem to have permanent open positions. In the first case, people can simply do their jobs. In the second case, people become part of the system that needs to be stabilized every day.
This explains why professionals leave after 18 months even when salary, colleagues, and technology are perfectly fine. Not because of money. Not because of tasks. But because of structure.
The unspoken core question is:
“Do I have to carry this system long term — or can I simply do my job here?”
This question is never asked out loud. But it determines whether someone stays mentally — or mentally starts looking elsewhere after only a few weeks.
In well-organized integrators, we hear very different statements:
“Incredibly well structured.”
“Everyone knows exactly what they are doing.”
“Hardly any friction between departments.”
“Knowledge is properly documented.”
“I haven’t had to rescue anything yet.”
That last sentence is perhaps the highest compliment an integrator can receive.
In the end, the first question IT professionals ask themselves after joining an integrator can be reduced to a single thought:
“Is this organization built in a healthy way — or is it being held together by people every single day?”
They know the answer after two weeks.
Even though they will never say it out loud.
