Setting a Clear Boundary for a Workflow Observation

A unit manager invites you to watch a shift of procedures and report back on who used the device correctly. That request feels reasonable, but saying yes without qualification puts you in the position of judging staff competency, which is not your role and not your facility's expectation of you. The example below shows how to redirect that request while still giving the team something useful, and what to do before, during, and after the visit so the boundary holds.

Why This Conversation Goes Wrong

A workflow observation sounds like a small favor. A manager is short staffed, wants a second set of eyes, and asks the visiting specialist to watch a shift and flag who is struggling. The specialist wants to be useful and does not want the visit to feel like a wasted trip, so the request slides from observation into evaluation before anyone notices.

The problem is that competency assessment belongs to the facility, not to the device company. Once a specialist starts rating individual clinicians, that feedback can end up in a personnel file, a performance conversation, or a disciplinary record the specialist never intended to influence. It also puts the specialist in the middle of employment decisions they have no authority over and no full context for. A single rushed case, a busy day, or an unfamiliar room setup can make a competent clinician look unsure, and a specialist watching one shift has no way to tell the difference between a bad day and a real skill gap.

There is a second problem hiding in the same request. An unstructured observation often puts the specialist near patient specific information, conversations, charts, monitors, that has nothing to do with the device topic they are there to support. Without a clear boundary on what the observation covers, the specialist can end up holding information they should never have collected in the first place.

How To Prepare Before You Arrive

The preparation work happens before you set foot on the unit, and it is what makes the boundary easy to hold in the moment instead of something you improvise under pressure.

Contact the unit leader ahead of time and confirm three things. Confirm who has approved the observation and for what purpose, confirm which part of the workflow they want reviewed, and confirm where you should capture any questions that come up. Ask directly whether the observation is meant to inform staff assessment. If the answer is yes, say plainly that assessment sits with the facility and that your visit works best as an education focused review instead.

Write a short observation brief before you go. Include the permission contact, the approved device topic, the documents you plan to reference, and a simple method for logging questions, a shared note, a form, or a quick email to the unit educator after the visit. This document gives you something concrete to point to if the scope drifts once you are on site, and it keeps the visit anchored to what was actually approved rather than what feels convenient in the moment.

If the visit connects to a broader education plan tied to a procedure schedule, the approach described in Coordinating Device Education Around a Procedure Schedule is worth reviewing, since the same authorization habits apply when you are lining up education around scheduled cases.

What To Say During The Observation

A unit manager says, "Watch tomorrow's cases and tell me which clinicians are handling the device correctly and which ones need work." This is the moment the conversation either stays useful or turns into something you will regret documenting.

You answer, "I can support a permitted workflow observation focused on the approved device topic your team wants reviewed. Staff assessment and competency sign off stay with your facility, that is not something I am positioned to judge from a single shift. If you send me a few process questions ahead of time, I will use the current approved materials to answer them and note anything that should go to your unit educator or policy owner instead."

The manager pushes back. "I do not have time to write up questions, I just need to know who is falling behind." You reply, "I understand the time pressure. What I can do is watch the workflow steps tied to the device and flag any pattern I see across the group, not individual performance, and hand that pattern back to you and the unit educator to decide what it means for your team."

The manager accepts this. "Fine, just tell me if the group is missing something in general." You confirm, "That works well. I will note anything that comes up across the group and follow up with you and the educator after the observation."

Notice what happened. The manager still gets something they can act on, a general pattern worth reviewing, but the specialist never assigns a competency rating to a named person. That distinction is the entire boundary, and it holds even when the manager keeps pushing.

Mistakes That Blur The Boundary

A few habits turn a clean observation into a compliance problem.

1. Agreeing to rate or rank individual clinicians, even informally or in a private conversation after the shift, because a spoken rating still functions as an assessment the facility did not authorize you to make.
2. Skipping the upfront call with the unit leader and assuming the invitation itself counts as authorization, when the actual scope, topic, and access were never confirmed.
3. Writing down or discussing anything specific to a patient encountered during the observation, since the visit is about the device workflow, not the case in front of you.
4. Letting the visit expand past the approved topic because the day is slow and the manager asks you to also look at something unrelated, which stretches your access beyond what was granted.
5. Leaving without a clear next step for the questions you gathered, so the useful part of the visit disappears the moment you walk out the door.

If a session runs long and you cannot get through every question on the unit's list, the method described in Using a Question List When Device Education Runs Out of Time gives you a way to capture what is left over instead of rushing through it or promising more than you can deliver on site.

How To Practice And Score It

This conversation is easy to agree with in principle and hard to hold in the moment, especially when a manager is direct and clearly under pressure. Practicing it out loud, with someone pushing back the way a real manager would, is what makes the boundary automatic instead of something you have to think through live.

Ask a peer or your manager to play the unit leader and push for individual performance ratings at least twice, once directly and once after appearing to accept your first answer. Your job is to redirect toward local assessment every time without becoming defensive or vague, and to still leave the manager with something concrete, a process focused observation, a set of questions answered, a pattern flagged for the group.

Score the exchange on three points. Did you confirm authorization and scope before agreeing to observe. Did you decline to rate individual staff while still offering a useful alternative. Did you close with a clear next step for the questions or patterns you found. If you can hit all three under real pushback, you are ready for the actual visit. DealSpeak's Medical Devices practice conversations include this scenario with a counterpart that pushes back the way a real unit manager does, so you can run it more than once before the stakes are real.

Holding this boundary well is not about refusing to help. It is about being clear on what you can offer, a device focused, permission bounded observation, and what belongs to the facility, staff assessment and competency decisions. Get that distinction right and the visit stays useful to everyone in the room.