Labhandler at work

I have stories.  And I love to share them.  I’ve gathered a collection of stories that illustrate my most impactful and transformation projects.

Featured Project

Lab Modernization:
How a programming project turned into a cultural transformation

When a client approached me to help bring his laboratory into the 21st century, it was supposed to be an easy fix.  Transfer all of their records from pen-to-paper logbooks to an electronic lab notebook (ELN)., I was up for the challenge.

I try to approach most projects like this with a period of discovery.  I take this as a chance to get to know the team.  I want to understand how they work, and what their biggest frustrations are.

I learned early on, if you need to transform the culture of a laboratory there are three things you have to do first:

  1. Gain their trust.
    2. Give them quick wins.
    3. Make the changes easier and more attractive than the current state.

Continue reading to find out how I did just that.

Success Stories and Lessons Learned

A Problem Well Stated Post 4: Evolution of a Problem Statement

A Problem Well Stated Post 4: Evolution of a Problem Statement

n small to mid-sized testing laboratories, a well-developed problem statement is the foundation of effective corrective action. This post explores how a problem statement evolves—from initial detection to a fully actionable plan—within the framework of ISO/IEC 17025. Rather than rushing to solutions, lab teams are encouraged to begin with a “concept statement,” a rough draft that helps focus investigation and align team understanding.

A Problem Well Stated Part 3: Building Problem Statements that Actually Works

A Problem Well Stated Part 3: Building Problem Statements that Actually Works

In the third post of the A Problem Well Stated series, we introduce a practical framework—the 7-Question Matrix—to help lab teams write clear, focused problem statements. These statements guide investigations, reduce noise, and improve root cause analysis.

You’ll learn the difference between metadata thinking and root cause thinking, and why starting with what you know now leads to better outcomes. We also emphasize a critical mindset shift: problem statements evolve—they’re living documents.

Plus, we tackle a common mistake: blaming people instead of fixing processes. Protecting psychological safety leads to stronger teams and smarter solutions.

Bonus: Download our worksheet to apply the matrix in real time.

Try it now: Use the 7 questions to reframe one current issue. See what clarity emerges

“To make changes stick, face them E.A.S.T.  It works every time.”

A Problem Well Stated Post 4: Evolution of a Problem Statement

A Problem Well Stated Post 4: Evolution of a Problem Statement

n small to mid-sized testing laboratories, a well-developed problem statement is the foundation of effective corrective action. This post explores how a problem statement evolves—from initial detection to a fully actionable plan—within the framework of ISO/IEC 17025. Rather than rushing to solutions, lab teams are encouraged to begin with a “concept statement,” a rough draft that helps focus investigation and align team understanding.

A Problem Well Stated Part 3: Building Problem Statements that Actually Works

A Problem Well Stated Part 3: Building Problem Statements that Actually Works

In the third post of the A Problem Well Stated series, we introduce a practical framework—the 7-Question Matrix—to help lab teams write clear, focused problem statements. These statements guide investigations, reduce noise, and improve root cause analysis.

You’ll learn the difference between metadata thinking and root cause thinking, and why starting with what you know now leads to better outcomes. We also emphasize a critical mindset shift: problem statements evolve—they’re living documents.

Plus, we tackle a common mistake: blaming people instead of fixing processes. Protecting psychological safety leads to stronger teams and smarter solutions.

Bonus: Download our worksheet to apply the matrix in real time.

Try it now: Use the 7 questions to reframe one current issue. See what clarity emerges

Let’s Start a Conversation