In 2015, mscripts was facing serious challenges—customers were frustrated, many hadn’t received a product update in over two years, and the technology was fragmented and difficult to support. Code management was inconsistent, and the company’s focus had skewed heavily toward sales, leaving engineering in a reactive and constrained state.

When I joined, I took swift action to assess and address both the organizational and technical issues. Culturally, the team operated in a fear-based environment with limited autonomy. I restructured the team, which involved making tough but necessary staffing changes, and worked to build a culture of ownership, accountability, and open communication—where team members felt empowered to speak up, make decisions, and take responsibility for outcomes.
‍
On the technical side, I led the consolidation of a fragmented product landscape into a single, configurable platform. We established a well-defined API boundary between the client and server, enabling parallel development: some teams focused on building modern, API-driven front-end applications, while others rebuilt and unified the back-end systems to support the same API. This approach brought all customers onto a single codebase and enabled us to deliver new features regularly, restoring customer trust and setting the stage for sustainable growth.

mscripts thrived and was acquired by Cardinal Health in 2019. Later, it spun off to a PE controlled combination of TDS and the Cardinal pharmacy platforms to form Outcomes Operating systems.