Monthly Team-Member Shadow
Watch real work side by side and turn friction into improvements
- Difficulty
- Easy
- Time to result
- ~days to results
- Steps
- 4
- Confidence
- 99%
UWM leaders regularly shadow a team member by sitting beside them, watching normal work, and asking questions for about an hour. Wilner uses the session to investigate specific details: why a screen is designed a certain way, why a phrase is used on a call, and what would make the job easier. Each shadow produces pages of observations because direct work reveals friction that leadership summaries miss. The mechanism links firsthand evidence to continuous improvement: schedule the observation, focus entirely on one person's task, question unexpected steps, capture notes, and translate them into better technology, process, or product. Wilner increased her personal goal from one shadow a month to two and planned the teams in advance, protecting the practice from a calendar full of competing priorities.
Origin
Wilner says UWM requires leaders to shadow a team member monthly and that every one of her sessions produces two to three pages of useful notes.
Core principles
- 01Leaders improve work by seeing it directly
- 02Focused observation reveals details reports miss
- 03Questions should connect behavior to process design
- 04Regular cadence prevents urgent priorities from displacing learning
How to run it
- 1
Protect the cadence
Schedule recurring shadows before daily priorities consume the time. Select teams in advance so the practice covers different parts of the operation.
Pro tip Wilner maps two teams per month across the year.
Watch out A vague intention to shadow more often will lose to urgent work.
- 2
Observe normal work
Sit one-on-one beside a team member and watch the actual job being performed. Keep the hour focused on their task rather than on a general status conversation.
Pro tip Ask the person to work as they ordinarily would.
Watch out Turning the session into an evaluation can hide real friction.
- 3
Question the details
Ask why screens, statements, and process steps work as they do. Invite the team member to identify what would make the job easier.
Pro tip Follow every surprising workaround until its cause is clear.
Watch out Do not assume an awkward step is pointless before hearing its purpose.
- 4
Capture and improve
Record observations during the session and convert the strongest findings into technology or process changes. Connect the improvement back to the eventual customer product.
Pro tip Leave with a short list of owners or next investigations.
Watch out Notes create no value if they never change the work.
In the wild
Wilner sits beside a team member, watches the job, and asks why a screen looks a certain way, why a particular phrase is used on a call, and what could make the work easier. She says she consistently leaves with two to three pages of notes.
→ Direct observation supplies concrete ideas for better processes, technology, and customer experience.
Common mistakes
Shadowing as surveillance
If the team member expects a performance judgment, the session is less likely to expose ordinary workarounds and friction.
Leaving notes unactioned
Observation is only the input; the value arrives when findings improve the operating system.
Is it for you?
Best for
It is best for operational leaders responsible for processes, tools, and customer outcomes across multiple teams.
Not ideal for
It is not ideal as a covert individual performance review that would distort normal work and suppress honest feedback.
From the transcript
“every month we have to shadow a team member. Shadow meaning sitting with them, watching them do the job, asking questions, sitting one-on-one, side-by-side”
“I come away with every one of those with two to three pages of notes”
“if you don't know what what your people are doing, it's hard to get them to think about the best way to do whatever um…”
From the episode
The Most Powerful Woman in Mortgage Melinda Wilner