MELLORCATalk to Mellorca
Patterns

Knowledge, Documentation & Institutional Memory

When New Employees Spend Their First Week Chasing Basics

A new hire who spends the first week hunting for access, forms and the right person is showing you where the business depends on memory. Here is what to fix first.

Mellorca Patterns2026-10-11

Observable condition

A new colleague starts on a Monday. By Wednesday they still do not have a working login for the finance system. They have been told three different places to find the leave form, none of which is current. They do not know who approves a purchase, which template to use for a quote, or which of the two shared folders holds the real customer files. Each question is small. Together they consume the week.

Nobody is being negligent. The team is busy, the manager is in meetings and everyone answers questions kindly. But the newcomer spends most of the first five days asking, waiting and guessing, rather than doing the job they were hired to do. By Friday they are tired, slightly embarrassed and still not productive.

An illustrative example: a Pretoria engineering services firm hires a project coordinator. The offer letter is signed and the start date agreed, but the laptop is ordered the week she arrives. Her email account exists; her access to the project folders does not. A colleague forwards her six old emails as "the process". She spends Tuesday learning that two of them describe a method the firm stopped using last year.

Realisation

The realisation is that a poor first week is rarely about the new person. It is a measurement of how much of the business lives in people's memories rather than in the way work is set up. A newcomer is the one person who has no memory to lean on, so every undocumented step, unclear owner and missing permission shows up at once.

Experienced staff do not see these gaps because they have long since learned the workarounds. They know whom to phone, which folder is the real one and which form to ignore. The newcomer's questions are the first honest audit of the operation. Atlassian's guidance on documentation makes the same point in general terms: written, findable knowledge lets people get answers without interrupting a colleague, and it matters most to those who are new.

Realisation prompt: list everything a new starter would need in order to do one real piece of work on day one, from a working login to the template to the person who signs it off. How many of those items are written down in one place?

Identification

This is a pattern of onboarding that depends on tribal knowledge. The visible symptom is a slow ramp-up and a new employee who keeps interrupting others. The common assumption is that the person is not proactive enough or that the team needs a better buddy. The structural cause is that the information, access and decisions a role needs are scattered across people, inboxes and tools, with no single sequence that brings them together.

The related Discovery why new employees wait for system access looks at one specific blocker. This Pattern is wider: it covers the whole first week, including access, knowledge, introductions and expectations. The Pattern why teams keep asking the same internal questions describes the daily version of the same condition.

Diagnosis

  • Access is requested late. Accounts, licences, building passes and system permissions are raised on or after the start date, often by different people in different departments, so the newcomer cannot begin real work.
  • Nobody owns the first week. HR owns the contract, IT owns the laptop and the manager owns the role, but no one owns the experience from end to end, so gaps fall between them.
  • The knowledge is in heads and inboxes. The answer to "how do we do this here?" is a forwarded email chain or a colleague's recollection. The Pattern when business knowledge lives in inbox history shows why that is fragile.
  • Old and new instructions sit side by side. The newcomer cannot tell which document is current, so they ask a person, which pulls an experienced colleague away from their own work.
  • Expectations are unwritten. What good looks like in the first week, the first month and the first quarter is carried in the manager's head.
  • Each manager improvises. One team has a careful routine because its manager is organised; the next team has none, so the quality of the first week depends on luck.

Commercial impact

The commercial value at stake is time to productivity, staff retention, the capacity of experienced people and the quality of early work.

The most visible cost is paid-for time that produces little. In South Africa, where a hire may already have taken months to find and a notice period to release, every unproductive day is a day of salary and a day of delayed output. A week lost to chasing basics is also a week in which the newcomer forms their first impression of how the business really runs.

The second cost is borne by existing staff. Each question from a newcomer interrupts someone who is already carrying a full workload. The interruptions are small and unrecorded, which is why the cost is rarely counted. Across several hires in a year it adds up to a meaningful share of senior time.

The third cost is early attrition. People who feel lost, or who conclude that nobody expected them, are more likely to leave in the first months. Replacing them restarts the whole cycle. The fourth is error: a newcomer who guesses which template or approval route to use will sometimes guess wrong, and the correction lands on someone else.

Common misidentification

The usual response is to buy a buddy system or a one-off welcome presentation. A buddy helps, but if the buddy is the only source of answers, the business has simply moved the interruption from the manager to a colleague. A welcome presentation covers culture and policy, but it seldom covers the practical steps of doing the job.

Another common response is to hand over a thick induction pack. A pack that nobody maintains becomes another out-of-date document, and the newcomer returns to asking people. A third response is to blame the hire for not being self-directed. Self-direction depends on having something reliable to direct oneself by.

Possibility

In a better state, the first week is a designed sequence. Access is ready before the person arrives. A short list of real tasks, each with its template, owner and approver, takes them from the first morning to a first completed piece of work by the end of the week. Questions still arise, but they are about judgement rather than logistics, and the answers to the logistical ones live somewhere findable.

The Insight how to move operational knowledge out of people's heads describes how to capture what experienced staff already know, and what business processes need documentation first helps decide where to begin.

Intervention

  1. Interview the last three hires. Ask what they waited for, what they could not find and whom they had to ask. Their answers are a ready-made fault list.
  2. Raise access at offer stage. Make accounts, licences, equipment and permissions a checklist triggered by the signed offer, with a named owner for each item and a due date before day one.
  3. Write the first-week plan around real work. Choose three typical tasks for the role and write down the steps, templates, systems and approvers for each.
  4. Name one owner for the experience. This is usually the line manager, supported by HR and IT, who checks on day one, day three and day five that nothing is blocked.
  5. Put the answers in one findable place. Keep current guidance together, retire old versions and mark an owner and review date on each page.
  6. Ask the newcomer to fix what they hit. At the end of the first week, have them note every gap they encountered and update the plan, so that the next hire benefits.

Diagnostic questions

  • On a new starter's first morning, can they log in to every system their role needs?
  • Could they complete one real task by Friday without interrupting a colleague more than a handful of times?
  • Who is accountable for the first week, and how would you know it had gone badly?
  • When did you last ask a recent hire what slowed them down?
  • If your most experienced person were away, could a newcomer still find the current version of every template?

Bottom line

A newcomer's first week is a clear mirror. If it is spent chasing logins, templates and names, the business is relying on memory to hold its operations together. Preparing access in advance, writing down a small set of real tasks and giving someone ownership of the experience turns those lost days into useful ones, and the same preparation makes the business easier to run for everyone else.

Sources and further reading

Related Mellorca reading

Article summaryA new hire who spends the first week hunting for access, forms and the right person is showing you where the business depends on memory. Here is what to fix first.
Explore our solutionsStart a conversation