The first-week workplace map: people, places, and handoffs

A new employee can leave orientation with a notebook full of names and still be unsure whom to ask about a locked door, an unfamiliar instruction, or a task that needs approval. The answer is not a larger directory. It is a small workplace map that connects a situation to the person or process responsible for it. For Tennessee state employees, this complements Edison TN onboarding rather than competing with it.

The official HR description says onboarding includes meeting colleagues and learning the role and agency culture. What follows is an editorial method for making those introductions useful. It is not a claim that every agency assigns the same roles, provides the same facilities, or uses the same first-week schedule. Confirm your own arrangement with your supervisor.

Learn responsibilities before memorizing titles

When someone introduces a colleague, ask what kinds of questions that person handles. A title may describe a broad responsibility without showing how the person fits your daily work. Knowing who checks a draft, who coordinates an appointment, and who owns an equipment request helps you avoid sending every issue to the most senior person you met.

Record roles in plain language. “Checks this type of completed work” is often more useful during the first week than an unfamiliar acronym. Include a backup route if the person is away, but do not assume that any coworker can approve on their behalf. Delegated authority should be confirmed, not inferred from a shared office or friendly offer to help.

Give each new contact a reason to remain on your short list. You do not need to reproduce the agency directory in a personal notebook. Keep only what helps you act appropriately and store it in an approved place. If a contact changes, update the role as well as the name so that old notes do not steer a later request to the wrong team.

Walk the route of an ordinary workday

A useful orientation tour follows what you will actually do. Where do you enter? Where should visitors wait? Which areas require an escort or special permission? Where are the approved spaces for meetings and calls? Ask these questions without trying doors or entering restricted spaces to see what happens. Physical access rules remain rules even when the building feels welcoming.

Ask where emergency information is posted and how the agency communicates urgent instructions. Do not rely on an informal description of what a colleague did during an earlier incident. The current local procedure is the relevant one. If you need an accessible route or another arrangement, raise the practical need through the appropriate agency channel rather than assuming that the standard tour covers it.

For remote work, the map is less physical but still important. Identify the approved meeting channel, the place for current team instructions, and the method for reporting a connection problem. A chat room is not necessarily the official place to submit an absence notice or retain a work record. Ask which channel is intended for each purpose.

Watch one handoff from beginning to end

Many jobs become understandable at the handoff. Someone prepares an item, another person reviews it, and a third person acts on the result. Ask to observe an appropriate example or use an authorized training case. Focus on what changes hands, what information must accompany it, and what tells the sender that responsibility has moved.

Do not confuse sending with acceptance. If the receiving person needs a reference, attachment, or decision, an incomplete message may sit unresolved even though it left your outbox. Learn what a complete handoff looks like in your team. Then ask how exceptions are handled when the normal reviewer is unavailable or a deadline approaches.

Keep your notes free of real case details unless the agency permits them. You can often describe the sequence without retaining a person’s name, record number, or private information. A training note should explain the process. It should not become an unauthorized example library that outlives the reason you collected it.

Separate helpful customs from actual requirements

Teams develop useful habits: a preferred meeting time, a naming convention, or a quick verbal check before a formal submission. Learn those habits, but ask when they are customary rather than mandatory. This distinction matters when a local shortcut appears to conflict with written guidance or when someone says “we always do it this way” without explaining the underlying rule.

A respectful question can be direct: which current procedure should I use for this step? If there is a difference between the written instruction and the demonstration, describe the difference without assigning blame. Let the responsible person clarify it. Quietly choosing whichever version is easier can produce errors that are difficult to trace later.

The same principle applies to system access. A colleague may know a menu path that your role cannot use. That does not necessarily mean your account is broken. Ask whether the function belongs to your assignment before requesting access. Your workplace map should identify both the useful contact and the limit of your authority.

Turn the map into a first-week review

At the end of the week, test the map against a few ordinary scenarios. If you cannot attend a scheduled activity, who needs to know? If a task stops at a missing permission, where do you report it? If two instructions disagree, who resolves them? You should not need a perfect answer to every possible problem, but the common routes should be clear.

Bring remaining gaps to your supervisor in one short conversation. Explain what you understand and where you still need direction. Update the map after that conversation and discard superseded working copies according to agency practice. A good orientation map gets smaller as your understanding grows; it is a navigation aid, not a second administrative system.