Technology Leadership

Attribution

The experience described here was gained by David Martin during prior employment, including technology leadership roles with McKesson and CoverMyMeds. It is professional experience brought to D W Martin, LLC rather than work performed by the company.

What kind of technology leader

The defining characteristic is range. Responsibility extended from representing technology during an acquisition, through leading the team supporting pharmacy operations, through architecture and program oversight — and then into writing the migration code personally.

That combination is unusual. Leadership-only advisors often cannot evaluate whether a plan is executable; engineers without leadership scope often cannot see why an executable plan is the wrong one.

Scope of responsibility

• Representing enterprise technology during acquisition and integration activities
• Overseeing application and technology migration out of legacy environments and data centers
• Leading the technology team supporting pharmacy operations, then expanding across additional pharmacy operations
• Overseeing multi-site pharmacy platform consolidation
• Coordinating technology work across multiple pharmacy environments
• Working directly with data analysts and data engineers
• Overseeing integration, reporting, analytics, and migration activities
• Coordinating commercial technology vendors and internal platforms
• Contributing software and data engineering directly

What this informs today

This experience shapes how the company approaches architecture and technology leadership engagements — including fractional and interim leadership, delivery oversight, and architecture-led execution.