Job Shadowing for Career Changers: Plan a Useful Two-Hour Visit
Plan a focused job shadow visit before a career change, with a request template, observation worksheet, fictional example, and a clear follow-up decision.
A short workplace visit can help you investigate the daily tasks behind an appealing career title. Use this plan to ask for access, observe one workflow, and leave with evidence you can actually use.
Choose the question your visit needs to answer
Job shadowing means observing someone at work to understand what their role involves. Delgado Community College describes it as a way to see a workplace from the inside over a few hours. The BLS career-planning guide also suggests shadowing workers to learn about daily work. Those resources address students; the planning exercise below adapts the observation approach for adults considering a career change.
Start with one uncertainty about the work itself. For example: 'Would I enjoy coordinating changing schedules, or am I mainly attracted to the idea of organizing things?' A visit cannot establish whether an entire occupation suits you, but it can show how one person handles a particular workflow in one setting. Write your question before choosing a host so that a friendly conversation does not become your only result.
Choose a role and a setting together: project coordinator at a small agency is more specific than project management. List a task you hope to observe, one working condition you need to understand, and one thing you already believe about the role. Treat that belief as something to investigate rather than something the host needs to confirm.
Request a small, clearly bounded visit
Look for an introduction through a former colleague, an alumni network, or someone you already know in the field. Ask whether the organization permits visitors and who must approve the arrangement. The two-hour agenda here is a suggested planning limit, not a rule about how long shadowing should last or a promise that employers offer it. Let the host propose a shorter visit or decline.
Adapt this request: 'I am exploring a move from customer support into project coordination. I want to understand how a coordinator handles schedule changes and team handoffs. If your organization permits it, could I observe a suitable part of your workflow for up to two hours, at a time convenient for you? I would follow your visitor rules and avoid confidential material. A short conversation or a demonstration using a fictional example would also help if observation is not possible.'
Before agreeing, confirm the date, location or video link, host, visitor requirements, and tasks you may observe. Ask whether note-taking is permitted and which topics are off limits. Do not assume permission to record, photograph screens, contact customers, or access internal systems. Keep the arrangement focused on observation and questions; you do not need to offer productive work to make the request worthwhile.
Use a two-hour agenda and an observation worksheet
If the host agrees to two hours, propose this flexible agenda: 10 minutes for introductions and boundaries, 60 minutes observing a permitted workflow, 20 minutes discussing what happened, 20 minutes exploring work you could not observe, and 10 minutes to summarize and thank the host. Follow the host's work rather than forcing the schedule. If a sensitive task begins, step away and record only that part of the workflow as unobserved.
Make one worksheet row per event. Use these fields: task or trigger; action observed; output or handoff; interruption or constraint; my reaction; evidence type; unanswered question. Evidence type should be observed, described by the host, or my interpretation. Add the date and setting once at the top. Leave names, customer details, private messages, and proprietary figures out of your notes.
An observation might read: 'A delivery date changed; the coordinator checked dependencies, updated a schedule, and asked a team lead to approve a new deadline.' Your interpretation might be: 'The work seems to require frequent negotiation.' Keep those statements separate. Ask which parts of the sequence are typical and which were unusual today. A quiet hour does not prove that a job is quiet, and one busy incident does not establish its normal workload.
Worked example: an appealing task with an unexpected constraint
This example is fictional, not a report of an actual visit. Maya works in customer support and is exploring project coordination. She expects to enjoy making plans but wants to know how much of the role involves chasing updates. During a permitted visit, she observes a coordinator revise a task list after two team members report delays. The coordinator then asks another team for a revised handoff date.
Maya's worksheet separates three things. Observed: the plan changed after new information arrived. Described by the host: following up on missing updates is a recurring responsibility. Personal reaction: Maya enjoyed tracing the dependencies but found the repeated follow-up less appealing. She has evidence about one workflow, not a finding about all coordinator jobs or her ability to perform them.
Her next question is: 'How do responsibilities differ between coordinators who maintain schedules and those who investigate process problems?' Her next step is to speak with a coordinator in another setting and ask about that distinction. She does not need to enroll in training simply because the visit was enjoyable, or abandon the whole field because one part felt uncomfortable.
Debrief into one next action, including when access is limited
After the visit, complete three sentences: 'I saw evidence that ...'; 'I still do not know ...'; 'My next check will be ...'. Choose whether to investigate further, compare another setting, or set this version of the role aside for now. Tie the choice to a task or condition in your notes. Send a brief thank-you through the agreed contact method, and do not publish workplace notes or identify people without their permission.
If a workplace cannot host you, ask whether someone can walk through a sanitized example of a completed task. Mark it as a demonstration or explanation, not direct observation of a normal workday. An informational conversation can still clarify the workflow, but leave interruptions, pace, and working conditions unknown if you did not see them.
MyPathFit's assessment collects information about goals, experience, skills, and constraints, and its public sample report shows career, freelance, and business paths. Use a suggested role to choose what to investigate with this manual worksheet. Arrange the visit yourself; a report recommendation does not confirm an employer's duties or provide access to a workplace. Your useful result is one clearer question and a practical next check, rather than a final career verdict.
Quick checklist
- Choose one role in one setting and write a specific question about its daily work.
- Ask for a bounded visit, with approval and an alternative if observation is unavailable.
- Confirm visitor rules, note-taking permission, and tasks that are off limits.
- Record the task, action, output, constraint, reaction, evidence type, and unanswered question.
- Distinguish what you observed from what the host described and what you inferred.
- Use the debrief to choose one next check; avoid generalizing from one visit.