The first week at a new job usually comes with plenty to read. There are policies, organizational charts, employee handbooks, introductions, training materials, system guides, and perhaps an onboarding checklist covering everything from setting up accounts to meeting the right people. By the end of the week, a new employee may know where to find most of the information the company has formally documented.
What they probably don't know yet is how the company actually works. They don't know which meetings require preparation and which are mostly informal. They don't know whether a message from a manager saying “when you have time” really means this week or this afternoon. They may not know how comfortable people are disagreeing with someone senior, how much context colleagues expect before making a decision, or who actually needs to be involved when something gets stuck. Those things rarely fit neatly into an employee handbook, but they can shape the experience of joining a company just as much as the formal onboarding process.
Every company has a second set of instructions
Most organizations have two versions of how work happens. There is the official version: reporting lines, processes, responsibilities, policies, and tools. Then there is the version employees learn through experience. Maybe a particular approval technically belongs to one department, but everyone knows involving another colleague early makes the process much faster. Perhaps the company says decisions should happen asynchronously, but important decisions almost always end up in a meeting.
Long-term employees barely notice these patterns because they've become normal. A new employee notices them immediately because they don't yet know which parts of the formal process match reality and which require additional context. They may follow the written instructions perfectly and still feel as though everyone else knows something they don't. In many cases, everyone else does—they've simply accumulated knowledge that was never formally written down.
Small uncertainties can make simple work surprisingly difficult
Consider something as ordinary as sending a draft to a manager. A new employee may wonder whether the manager expects something rough enough to discuss or nearly finished. Should they send it as soon as they have a direction, or wait until they've checked every detail? If the manager doesn't reply, should they follow up tomorrow or assume silence means approval?
None of these questions is particularly complicated, but together they create friction. Experienced employees already know the answers because they've seen how their manager responds, watched colleagues handle similar situations, and learned from previous mistakes. A new employee has none of that context yet, so even straightforward work can require more mental effort than it appears to from the outside.
This is one reason onboarding isn't simply a matter of transferring information. New employees are also building a model of the organization: who knows what, how decisions happen, what good work looks like, where they have autonomy, and when they should ask for help.
Culture becomes visible in ordinary moments
Companies often explain culture through values. A new employee might hear that the organization values ownership, transparency, collaboration, or speed. Those words can be useful, but employees usually learn what the culture actually means through much smaller moments.
What happens when someone makes a mistake? Can a junior employee challenge a senior one in a meeting? Does asking for help demonstrate good judgment or lack of independence? When a deadline is unrealistic, are people expected to raise the issue or quietly work longer? When someone says they want feedback, what happens when the feedback is uncomfortable?
These situations teach people what behavior is genuinely accepted, rewarded, or discouraged. A company can describe itself as collaborative, but if decisions are consistently made before the meeting begins, employees will learn that quickly. It can say people should speak openly, but if disagreement is routinely dismissed, the unwritten lesson will be stronger than the written value.
Good onboarding shortens the guessing period
Companies probably can't document every unwritten rule, nor should they try. Workplaces change, different teams develop different habits, and some knowledge only makes sense once someone encounters the situation themselves. The goal of onboarding shouldn't be to produce a manual for every possible interaction.
What companies can do is make important expectations more explicit and give new employees safe ways to discover the rest. Managers can explain how they prefer to receive updates, what requires approval, how much autonomy the employee has, and what to do when priorities conflict. Teammates can provide context that wouldn't naturally appear in formal training. Regular check-ins can surface questions that employees may initially hesitate to ask because they don't yet know what is considered obvious.
That matters particularly in international teams, where employees may arrive not only from different companies but from different workplace cultures. Shared language doesn't guarantee shared assumptions about hierarchy, feedback, urgency, or disagreement. Making more of those expectations visible can help people spend less time interpreting the organization and more time contributing to it.
Starting a job means learning how a group of people works
A successful first week isn't one where a new employee has memorized every policy or completed every item on an onboarding checklist. Most of that information can be looked up later. The harder knowledge is understanding how the people around them turn those policies, processes, and responsibilities into actual work.
That understanding takes longer than a week. But companies can make the learning curve easier by recognizing that onboarding isn't only about telling someone what their job is. It's also about helping them understand the environment in which they're expected to do it.
The employee handbook explains the company. The first few weeks teach someone how the company really works.
Hirona helps hiring teams gather structured information before someone joins the team, while the people behind the process remain responsible for the decisions that follow. See how it works →