In scientific and technical organizations, the path to laboratory leadership often follows a predictable yet perilous trajectory. A brilliant bench scientist or technician consistently demonstrates world-class problem-solving abilities and achieves exceptional experimental reproducibility. Consequently, they are promoted to laboratory manager. However, the exact trait that secured their advancement—the ability to immediately provide the "right" answer—frequently becomes their greatest liability as a leader.
At the 2026 Lab Manager Leadership Summit, Sean Grace, leadership consultant and founder of Peak Luma, diagnosed this phenomenon as the "expert trap." During his session, "The Many Faces of Laboratory Innovation: Unlocking Value Beyond the Lab Bench," Grace argued that when technical leaders rush to solve every problem for their personnel, they inadvertently stifle the autonomous, innovative thinking required for long-term operational success.
Key takeaways:
- Overcoming the expert trap: Transitioning from the primary problem solver to a facilitator of team-led innovation.
- The duct tape audit: Identifying temporary workarounds that signal underlying process bottlenecks and regulatory risks.
- The vocabulary of co-creation: Using strategic questioning frameworks to lower defensive barriers and encourage collaborative solutions.
- Managing up: Using data-driven storytelling to secure executive buy-in for operational improvements.
- Fostering psychological safety: Creating a culture that rewards experimentation and open dialogue around uncertainty.
- To transition from an operational bottleneck to a facilitator of continuous growth, lab leaders must master what Grace termed the art of the question—shifting their daily vocabulary from directives to discovery.
Dismantling the expert trap
Technical organizations are inherently built on expertise, which makes stepping away from the role of the primary problem solver incredibly difficult for new managers. "They are so anxious to solve the problem for their teams because that's what they're good at," Grace explained. "But it doesn't necessarily encourage their teams to solve their own problems."
When a manager immediately delivers a solution to an underling's technical frustration, they create a culture of tactical dependency. The team stops analyzing systemic flaws because they know the "expert" will fix it. This dependency blinds the lab to broader structural innovations.
Grace asserted that a leader’s primary responsibility is not to generate every solution, but to cultivate an environment where solutions bubble up organically from the bench. To do this, leaders must manage their own discomfort with uncertainty, recognizing that the friction of an unsolved problem is precisely where innovative workflows are born.
The duct tape audit: spotting hidden workarounds
To guide a team toward independent problem-solving, lab leaders must first learn where to look for friction. Grace shared an elegant diagnostic strategy called the duct tape audit, centered on a ubiquitous laboratory staple.
Recalling an insight from a favorite text, Grace described walking through New York City and noticing the creative, improvised ways everyday people used duct tape to bypass broken infrastructure. In a laboratory environment, "duct tape" takes the form of temporary workarounds—unvalidated software scripts to bridge incompatible data platforms, manual spreadsheet tracking to supplement an inefficient laboratory information management system (LIMS), or physical adjustments to aging instrumentation.
While these patches may solve immediate needs, they often bypass critical data integrity standards such as FDA 21 CFR Part 11, which governs electronic records and signatures. “When you see duct tape being used, it's often to try to solve a problem without having to go through the whole process of actually being too innovative about it,” Grace noted. “But those duct tape experiences are where the innovation could be.”
For lab managers, these temporary workarounds are the clearest indicators of an underlying process bottleneck. However, a creative workaround is merely an invention born of convenience; it does not become a true operational innovation until it is scaled, standardized, and measured. Grace challenged leaders to hunt for these "duct tape" moments and use them as collaborative starting points, asking their teams to define what long-term success looks like beyond the temporary patch.
The vocabulary of co-creation: disarming the ego
Transitioning a lab from workarounds to scalable solutions requires a delicate linguistic shift, particularly when dealing with entrenched personnel or institutional inertia. Laboratories are often populated by individuals with deeply entrenched habits and highly protective professional egos. Announcing a top-down solution to a workflow bottleneck often triggers immediate defensive reactions.
To counter this, Grace highlighted the psychological power of specific strategic questioning frameworks. Rather than presenting an innovative idea as a definitive mandate, he suggested leveraging the vocabulary of co-creation. One of his preferred strategies involves the phrasing: “Would it make sense if we looked at the process this way?”

Sean Grace, communication consultant, coach, speaker, and author.
“It has this strange effect on people where they say, 'That’s worth thinking about,'” Grace observed. “All of a sudden, you loosen up a bit of that armor, and now you get people to be part of the solution.”
By rephrasing an executive decision as an exploratory question, the manager disarms the reactive barriers often found in technical environments. It shifts the dynamic from a binary argument to an exercise in co-creation. Similarly, Grace advocated for the consistent deployment of "How might we . . . ?" questions. As explored in "Why vs. How: Which Question Drives Better Results?," asking a team "Why is sample intake always delayed?" fosters defensiveness. Asking, "How might we redesign the sample intake workflow to cut turnaround time by 20 percent?" reorients the collective intelligence of the lab toward a measurable, shared goal.
Managing up and fostering psychological safety
The challenge of driving innovation frequently requires managing up to navigate the expectations of upper management. When summit attendees raised concerns about securing budgetary buy-in for non-technical innovations, Grace emphasized a balanced strategy of data and narrative to overcome institutional inertia.
While data-driven justifications are essential for technical leadership, Grace cautioned that facts alone rarely dissolve resistance. True persuasion requires storytelling. Leaders must articulate how fixing a "duct tape" bottleneck directly influences human efficiency, mitigates diagnostic risk under standards like CLIA, and protects the lab’s broader brand reputation and ISO/IEC 17025 accreditation.
Ultimately, building an innovative laboratory requires leaders to foster psychological and emotional safety. This means explicitly rewarding experimentation, validating smart failures that yield critical data, and normalizing open dialogue around operational uncertainty.
“Look beyond the science,” Grace concluded. “Question how work is structured and delivered. Create the conditions for innovation to emerge.”
True laboratory leadership is not defined by possessing an answer for every operational breakdown. It is defined by the strategic curiosity to ask the precise questions that unlock the innovation already waiting in every corner of the lab.










