⏳ “Why
Haven’t You Started?” — Nobody Gave Me My Computer Login

I arrive
early because I am new and I want to make a good impression. I know the
name of the place, I know roughly what I am supposed to do, and I know that
somebody is meant to introduce me to the routine. Then twenty minutes pass.
Nobody comes. I do not have access to the system, I do not know which room
I should use, and I am not sure whether I am allowed to begin the task
alone.

Eventually someone appears and asks a frustrating question:
“Why haven’t you started yet?” Suddenly the situation sounds as if I have
been lazy, even though I was waiting for the instruction I thought I
needed.

This is a different kind of newcomer conflict. The problem
is not that I broke a rule. The problem is that expectations were never
synchronized. One person expected me to act independently. I expected
someone to show me the first step. Both assumptions remained invisible
until the delay created tension.

The first useful sentence is
simple

At beginner level, I need very little German to explain the
situation. I can say, “Ich bin neu,” “Ich warte auf Frau Klein,” or “Was
soll ich machen?” I can ask where the room is, who can help me, or whether
I should start now.

These phrases are useful because newcomers often
spend surprising amounts of time waiting for information that experienced
people assume is obvious. A short question can prevent a long
misunderstanding.

Waiting can be reasonable, but silence creates
ambiguity

If I am told that somebody will meet me at nine o’clock,
waiting is reasonable. If that person does not arrive, however, there is a
point at which I should ask someone else. This creates a useful
distinction: the organization may have failed to provide the expected
introduction, while I may also have had an opportunity to escalate the
uncertainty sooner.

A constructive conflict conversation can
acknowledge both sides. I can explain why I waited and also say what I will
do differently next time. This is much stronger than simply saying, “It
wasn’t my fault.”

Access problems are not motivation problems

Newcomers frequently depend on practical prerequisites. I may need a
badge, login, key, safety briefing, software permission, equipment,
timetable, or supervisor approval. If one of those is missing, telling me
to “just start” may not be realistic.

As my German becomes more
advanced, I can explain exactly what blocked me. I can distinguish between
not knowing how to do a task and being technically unable to begin it. I
can also document what I requested, when I requested it, and whom I
contacted.

Different people may expect different levels of
independence

One supervisor may say, “Wait until I show you.”
Another may later say, “You should have started by yourself.” This is not
necessarily dishonesty. Teams often have informal expectations that have
never been made explicit.

A useful response is to ask for a clear
boundary. Which tasks can I begin independently? Which ones require
approval? Who should I contact if my assigned person is unavailable? How
long should I wait before escalating a missing introduction or access
request?

Defending yourself without refusing responsibility

At intermediate levels, the learner must handle stronger accusations.
Perhaps someone says that I showed no initiative. I can disagree with that
interpretation without becoming hostile. I can explain that I arrived on
time, contacted the person named in my welcome email, and did not have the
credentials required for the task.

At the same time, I can admit
that I could have asked another colleague sooner. This combination is
powerful: I do not accept an inaccurate description of my behavior, but I
remain open to improving my response.

Advanced conflicts require
separating facts from expectations

At higher levels, the discussion
may involve a manager, coordinator, tutor, or supervisor. The question is
no longer simply whether I waited too long. We may need to reconstruct what
the onboarding plan actually promised, which dependencies were ready, what
the newcomer was told, and what level of initiative was reasonably
expected.

This is where precise German becomes useful. I can
distinguish between an explicit instruction and an assumed convention. I
can say that I accept responsibility for not escalating sooner while
rejecting the claim that I ignored an available task. I can propose a
concrete improvement rather than arguing indefinitely about blame.

A good newcomer process defines the first move

A surprisingly
effective onboarding improvement is to tell a new person exactly what to do
if the normal plan fails. If your supervisor is absent, contact this
person. If your account is not active, open this request. If nobody meets
you after fifteen minutes, go to this desk. If the task requires
authorization, do not proceed alone.

These fallback instructions
reduce anxiety for newcomers and interruptions for experienced colleagues.
They also make accountability fairer because the expected response is
visible before a problem occurs.

The goal of this lesson

The German conversations below begin with very easy situations: waiting
for a person, finding a room, asking what to do, and requesting help. Later
scenes introduce missing logins, unclear schedules, absent supervisors,
contradictory instructions, incomplete training, accusations about
initiative, and disagreements about responsibility.

At the most
advanced levels, the learner discusses onboarding as a system of
dependencies, expectations, escalation paths, and feedback. The central
lesson remains practical: when I am new, I should not pretend to know what
I do not know. But I also should not remain silently blocked forever. I can
ask, clarify, escalate appropriately, and defend myself with facts when
expectations were never made clear.