In this guide
Turn a new role into a manageable sequence of people, decisions and supervised practice.
Learn how work moves
Tufts’ first-week guidance includes orientation, required acknowledgements and role-related training. Those official steps are important, but a new employee also needs to learn how work actually moves through a department. This article proposes an independent first-month planning exercise, not a substitute for the university’s onboarding requirements. Ask your supervisor which tasks are urgent, which require training before you begin and which can wait. A long personal checklist is less useful than an agreed sequence that matches the work you are expected to perform.
Begin with a service map on one page. Put your role in the middle and add the people who send you work, the people who rely on your output and the people who authorize exceptions. For each connection, write one practical question: what information must arrive, what a complete handover looks like or when a decision needs escalation. Keep it to working relationships rather than collecting everyone’s biography. Understanding a few important dependencies will help you ask better questions than memorizing an organizational chart alone.
Observe before optimizing
During the first week, ask to see one ordinary task from request to completion. Notice where information is checked, where a second person reviews it and where the process pauses. Do not assume that an unfamiliar step is unnecessary. It may exist for a reason you have not yet encountered. Equally, write down confusing points while they are fresh. A question such as “What problem does this check prevent?” invites explanation and can later support a thoughtful improvement proposal.
In a hypothetical department, a new coordinator notices that requests are returned when a field is missing. Instead of redesigning the form immediately, they ask which fields are essential and why people omit them. They practice recognizing a complete request with a colleague, then propose a small instruction change if appropriate. The result is learning anchored in an actual problem. It avoids making changes before understanding who owns the process and whether the suggested fix creates a problem elsewhere.
Define supervised practice
Agree on one or two tasks you can practice with review. For each, specify the expected output, the person who checks it and the conditions under which you should stop and ask. This is particularly important when work involves confidential information, specialized equipment, financial approvals or safety-sensitive activity. Confidence is not authorization. A clear boundary lets you learn actively without guessing at powers that belong to someone else or assuming that access to a system permits every action within it.
At the end of each week, bring three short notes to your supervisor: something you can now do reliably, something that remains unclear and one dependency blocking progress. Ask whether your priorities still match the team’s needs. Keep a question list, but distinguish urgent barriers from ideas that can wait for a scheduled conversation. This respects colleagues’ concentration while ensuring that a time-sensitive uncertainty does not sit quietly in a notebook until it causes avoidable rework.
Finish with a shared picture
By the end of the month, aim for a shared picture of your core duties, decision boundaries, recurring deadlines and next learning priorities. The aim is not complete independence in every task. Some roles reasonably require a longer period of training and supervised work. Summarize what is established and ask your supervisor to correct misunderstandings. Then use Turn a training course into a useful development plan to turn the next capability gap into a small, reviewable learning goal rather than an open-ended promise to “get up to speed.”
Continue reading: Turn a training course into a useful development plan, Make a flexible-work conversation concrete, Considering laboratory support? Examine the work behind the science.