The romance of a laboratory lives at the bench. There is the question, the experiment, the result, and perhaps a pleasingly complicated machine making serious noises. Ted Palashis built his career around what happens just outside that frame. Someone has to know where the machine will sit, whether the new room has the right power and gases, who will service it, how much downtime it can tolerate, and what happens when the whole operation moves across town.
That work rarely makes the celebratory photograph. It becomes conspicuous only when it is late, missing, broken, or plugged into the wrong wall. Palashis saw a company in those details. He founded Overbrook in Massachusetts in 2001 and developed it into a specialist in laboratory relocation, asset management, instrument maintenance and qualification, equipment planning, and procurement. The proposition was steady: manage the operational machinery so laboratory teams could stay focused on their own work.
Twenty-five years later, the idea looks less like a collection of technical services and more like an operating philosophy. Palashis writes about data before decisions, inventories before moves, diagnosis before repair, and follow-up after delivery. He has presented for the International Institute for Sustainable Laboratories and the Association for Facilities Engineering, spoken at Lab Manager summits, and contributed to Lab Manager and Lab Design News. His favorite subject is not equipment alone. It is the web of decisions around equipment.
The business between the boxes
A laboratory move sounds, from a comfortable distance, like a moving job. Palashis describes a living system. An instrument has a weight and footprint, but it also has service clearances, environmental requirements, electrical demand, connections, vendor dependencies, and a place in a workflow that may already be under deadline. The object can arrive intact while the operation arrives broken.
He once compared a lab relocation to changing the wheels of a car while it is moving. The image is dramatic; his remedy is painstakingly ordinary. Build a detailed, accurate asset list. Identify weak links in accountability. Put the right resources where they belong. Check the utilities. Start early enough that the drawing can still change. Palashis has warned that instruments cannot be installed if gases were not plumbed correctly or power receptacles are in the wrong places. The expensive calamity may begin as a tiny mark omitted from a plan.
“It can’t be overstated how important a detailed and accurate asset list is.”Ted Palashis, on laboratory lifecycle management
This is why he argues for instrumentation specialists to join a project while the space is still being designed. Architects, engineers, project managers, scientists, and equipment experts see different slices of the same room. The test fit is where those perspectives must meet. To skip it because it looks like an added expense is to buy certainty later at construction prices.
Five acts, no intermission
Palashis organizes the laboratory lifecycle into five phases: start-up, operation, expansion or relocation, maturity, and exit. It is a neat framework for an untidy reality. Each phase changes the risk. A start-up may depend on a single instrument with no backup. An operating lab must distinguish the equipment central to production from tools used occasionally for research. Expansion puts pressure on space and workflow. Maturity brings a larger service and compliance burden. An exit raises questions of redeployment, resale, and disposal.
Palashis’s laboratory lifecycle
The framework has a dry wit in retrospect. In November 2025, Overbrook entered its own fifth phase when Innovative Lab Services acquired the company. The deal expanded ILS into Boston and New England and added Overbrook’s relocation, asset-management, and multi-vendor maintenance capabilities. Palashis and his team joined the combined organization, with Palashis continuing to lead laboratory lifecycle and technical services.
His statement about the deal sounded like the original thesis with a larger map. Overbrook, he said, had been founded to help laboratories through their lifecycle so they could focus on their work. Joining ILS would extend that mission nationally and give customers broader technical resources. The founder did not abandon the niche. He attached it to a bigger engine.
Overbrook is founded as a laboratory services and instrumentation company.
Palashis speaks at Lab Manager’s asset summit and records a customer-service interview.
Innovative Lab Services acquires Overbrook; the team joins the national organization.
He publishes on early equipment planning in laboratory design and relocation.
Service, with the friction removed
Palashis’s most portable idea has almost nothing to do with instruments. In a 2022 Leadership in Action interview, he drew a line between customer service and customer compliance. Service means caring enough to work in the way the client wants to work. Compliance means forcing the client through the provider’s preferred machinery. Plenty of companies call the second experience service because the ticket eventually closes.
He made the principle concrete with the smallest possible office ritual: answering the phone. Do not announce that the person a client wants is in a meeting. Try to find them. If they cannot be reached, say they are unavailable and ask what you can do. The words are not magic. The posture is. An employee is either acting as an advocate or explaining the company’s inconvenience.
“The real test of customer service is how the customer feels after the interaction.”Ted Palashis, Leadership in Action, 2022
His emphasis on follow-up is just as practical. Check in after the deliverable. That conversation demonstrates attention, but it also moves the provider closer to the real conditions of the work. You learn whether the promised outcome survived contact with Tuesday. For a company managing complex physical assets, that feedback is not courtesy added to the service. It is operating data.
A LinkedIn recommendation describes Palashis as energetic, disciplined, focused, comfortable in negotiation, and capable of running an innovation-based professional services firm. His own public material supports the picture of a founder who likes structure but measures it by human consequences. Records matter because they shorten downtime. Training matters because it helps an employee show empathy competently. A process earns its keep when the customer feels the difference.
The funnel and the hunch
When an instrument fails, urgency invites improvisation. Palashis recommends a funnel. Start broadly: is the problem related to method, operation, or mechanics? Ask what happened immediately before it appeared. Check software and instrument logs. Reproduce the problem. Confirm that parameters have not changed. Then isolate sections of the system until the field of possible causes narrows.
A calm path to the root cause
The rule that gives the funnel its power is simple: resist trying several fixes at once. Multiple changes create motion but destroy evidence. If the machine begins working, nobody knows why. The team has repaired the morning and impoverished the record.
That lesson travels well beyond a lab. Palashis’s work repeatedly favors legibility over intuition. His Asset Integration Assessment framework treats an instrument as more than a purchase price. It asks about workflow, utilization, adoption, service, integration, and long-term value. His writing on data-driven labs makes the same case at fleet scale: a manager needs accurate information and the authority to use it, not merely a dashboard with attractive colors.
Three forms of value recur in his newer work: intellectual property, people, and instrumentation. Ideas define the mission. People carry it out. Instruments make the work possible. The third category is his chosen territory, but his point is interdependence. A room full of expensive equipment is not an operating laboratory any more than a meticulously wired theater is a play.
A founder’s quiet advantage
Overbrook’s story is a reminder that founder insight need not arrive as a novel technology. Sometimes it is a better description of work everyone already performs badly. Palashis named the lifecycle, mapped the dependencies, and built services around moments when clients have more complexity than time. He then published enough of the method for laboratory managers to see their own operations more clearly.
There is an appealing lack of mystery to his advice. Inventory the assets. Look at the logs. Plan the utilities. Train the employee. Follow up with the client. Change one variable. Each instruction is almost too obvious to admire, which is exactly why organizations skip it. The difficulty is not understanding one step. It is preserving the discipline across hundreds of steps while the wheels are still turning.
A quarter-century after Overbrook began, Palashis is working inside a larger laboratory-services organization, still arguing for the plan before the plan. Science gets the discovery. He has made a career from the conditions that let the work continue tomorrow.