In laboratory leadership, the quality of a decision often depends on the quality of the questions that precede it. Lab managers routinely troubleshoot technical problems, assess staffing constraints, justify resource needs, guide change, and mediate competing priorities across departments. In each situation, the wrong question can narrow the discussion too early, send the team toward the wrong problem, or leave important concerns unspoken.
During her 2026 Lab Manager Leadership Summit presentation, Melissa Duong, MS, PA(ASCP), emphasized that question framing is a practical communication skill for lab leaders. While much of leadership communication focuses on word choice and audience awareness, Duong noted that how leaders frame questions also matters because “a poorly framed question is counterproductive” and may mislead the team. Framed well, questions can help teams focus their thinking, surface useful information, and move from discussion to action.
This skill has direct operational value for lab managers. Different situations call for different types of questions. A question that works well during a root cause investigation may not help during a brainstorming session. A question that engages frontline staff may not answer an executive’s concern about strategic alignment. By matching the question to the situation, lab leaders can improve clarity, reduce rework, and make better use of staff expertise.
Use investigative questions to identify root causes
Investigative questions are among the most familiar to laboratorians. They help leaders drill down into what happened, why it happened, and what underlying conditions allowed it to occur. These questions are especially useful during root cause analysis, quality investigations, safety reviews, failed audits, corrective and preventive action planning, or recurring workflow problems.
Duong describes investigative questions as the type that supports the “five whys” approach. In a lab, that might mean asking: Why did this specimen miss its turnaround time target? Why was the instrument unavailable? Why was maintenance delayed? Why was the backup workflow not used? Why was the team unaware of the downtime plan?
The value of investigative questions is that they prevent the team from stopping at the most visible symptom. For example, a delayed result may first appear to be a staffing problem. Further questioning may reveal that the issue stems from unclear escalation criteria, an outdated procedure, insufficient cross-training, or a communication gap between shifts.
Lab managers should take care to use investigative questions without making staff feel blamed. “Why did this happen?” can sound accusatory if the tone suggests fault-finding. A more useful version might be: “What conditions contributed to this?” or “Where did the process break down?” The goal is to understand the system, not corner an individual.
Use speculative questions to generate options
Speculative questions help teams think beyond the current process. They work well when a manager needs ideas, alternatives, or staff input before making a change. These questions are useful for process improvement, workflow redesign, new technology implementation, staffing models, scheduling changes, and space planning.
Duong describes speculative questions as open-ended questions that promote brainstorming. Examples include: What do you suggest to improve this process? How might we reduce handoff errors between shifts? What would make this workflow easier to sustain? What options have we not considered?
These questions matter because frontline staff often see problems that leaders may miss. A supervisor may know that a process fails, but the technologist performing the work may know where the bottleneck occurs, which workaround staff use, and which step creates the greatest risk for error.
Speculative questions also help build ownership. When staff contribute to a solution, they are more likely to understand the reasoning behind it and support the change. This does not mean every suggestion can be adopted. But the manager can use staff insight to make the final decision stronger.
Use interpretive questions to connect details to the bigger picture
Interpretive questions help leaders make meaning from information. These questions are useful when lab managers need to connect data, trends, or events to broader implications. They often matter most when communicating with senior leaders or when translating lab-level issues into organizational priorities.
During Duong’s presentation, interpretive questions included examples such as: What does this mean in terms of scaling up? How does this affect the strategic vision? What lessons can we take from this?
Interpretive questions can help move a discussion from isolated facts to decision-ready insight. For example, a lab may know that test volume has increased by 18 percent, overtime has risen, and turnaround time has slipped. An interpretive question asks: What does this pattern tell us about capacity? What does it mean for patient care, client service, compliance, or revenue? What risk does the organization accept if no action is taken?
These questions are especially useful when advocating for resources. Executives may not need every operational detail, but they do need to understand the business, quality, safety, or service impact. Interpretive questions help lab managers frame data in terms of consequences and priorities.
Use productive questions to move from discussion to action
Productive questions focus on next steps. They help define what must happen, who needs to be involved, what barrier needs to be removed, and how progress will continue. These questions are useful in project management, change implementation, corrective action planning, and team meetings that risk becoming circular.
Duong describes productive questions as action-based. Examples include: What steps will keep the project on track? Who needs to be involved next? What decision do we need before we can move forward?
In a lab environment, productive questions can prevent meetings from ending with broad agreement but no clear ownership. A team may agree that sample handoffs need improvement, but a productive question turns that agreement into action: What information must be included in every handoff? Who will revise the huddle checklist? When will the team trial the new process? How will we know whether it worked?
These questions also help managers support staff through change. If an employee resists a new process, a productive question can shift the conversation from frustration to support: What training would help you feel ready to use this system? What obstacle is preventing you from following the new workflow? What can we adjust without compromising quality or compliance?
Use subjective questions to surface concerns and sentiment
Subjective questions address the human side of lab operations. They help managers understand what staff think and feel, including concerns that may not appear in metrics. These questions are useful during change management, conflict resolution, burnout assessment, team check-ins, and post-implementation reviews.
Duong describes subjective questions as those that assess “the unsaid or the underlying sentiment.” Examples include: How do you feel about this change? What concerns do you have about this process? What part of this transition feels unclear? What feedback have you heard from the team?
These questions can be easy to overlook in technical environments where leaders focus on data, procedures, and deadlines. But ignoring sentiment can create hidden resistance. A team may understand a new workflow but still feel anxious about workload, competence, staffing levels, or the pace of change.
Subjective questions also help leaders identify the real source of resistance. In one example from Duong’s presentation, an employee who seemed resistant to a new instrument was concerned about her ability to learn the technology. Once that concern surfaced, the leader could provide retraining, practice opportunities, and peer support. The issue was not unwillingness; it was uncertainty.
Match the question to the leadership task
No single question type works in every situation. Lab managers need to choose the question that fits the task at hand.
Used together, these question types give lab leaders a more complete view of a problem. Consider a recurring turnaround time issue. An investigative question identifies where the delay occurs. A speculative question invites staff to suggest improvements. An interpretive question connects the delay to service, compliance, or patient care. A productive question defines the next step. A subjective question reveals whether staff believe the proposed fix is realistic.
This approach helps managers avoid two common communication traps: asking only technical questions when the issue also involves people, or asking broad questions when the team needs direction. Better questions create better conversations. Better conversations lead to stronger decisions.
Question framing is not a soft add-on to technical leadership. It is a decision-making tool. The right question can uncover risk, clarify priorities, build staff ownership, and keep work moving. Asking better questions is one of the most practical ways lab leaders can improve team performance.












