Executive Perspectives
Ask Better Questions.
Make Stronger Decisions.
Explore the questions I use to help leaders make decisions, integrate acquisitions, and prepare complex programs for delivery.
Program Management · M&A · Transformation
These are the questions and principles I use to help executive teams move from program activity to accountable execution.
Program Governance Should Move Decisions.
A program can have a full calendar of status meetings and still struggle to make the decisions that control delivery. I look for governance that connects an organizational objective to an accountable owner, a clear decision, and a date when that decision is needed.
Four Questions For Executive Sponsors
- What outcome are we protecting? Define the outcome and the measure of success before debating workstream status.
- Who owns each consequential decision? Separate recommendation, approval, and execution. A committee should clarify ownership.
- Which dependencies can change the delivery date? Expose cross-functional decisions, resource constraints, and vendor commitments in one integrated view.
- What requires executive intervention now? Present the options, consequence, recommendation, and latest responsible decision date.
A useful steering discussion ends with decisions, named owners, and explicit consequences. Reporting supports that discussion; it should not consume it.
Acquisition Integration Extends Beyond Day One.
Day One creates a transition point. Integration creates a functioning organization. I approach the work by connecting continuity, the future operating model, and the sequence of changes needed to get there.
Organize The Integration Around Operations
- Protect continuity. Identify what must work for payroll, finance, customer service, suppliers, and access on the first operating day.
- Define the target model. Agree on which processes, roles, controls, data standards, and platforms will become common, and which must remain distinct.
- Build one dependency plan. Connect functional workstreams and system changes to transition commitments and organizational milestones.
- Validate readiness with evidence. Test end-to-end scenarios, reconciliation, ownership, and support before approving a transition.
My acquisition-integration experience at AXIS Capital, Ingredion, Boehringer Ingelheim, and The Aspen Group reinforces the same principle: the integration plan must reflect how the acquired business will actually operate.
Transformation Needs An Accountable Owner.
An implementation partner can design and deliver a platform. The organization must own the operating decisions, readiness, and results that make the transformation useful.
Connect Delivery To The Future Operation
- Describe the future operation. Define how Finance, HR, Operations, and technology will work together after the change.
- Make operating decisions visible. Resolve process ownership, controls, policy, data, and organizational questions alongside technical delivery.
- Treat adoption as operating readiness. Validate whether people can execute the new process, rather than counting training attendance alone.
- Carry accountability into stabilization. Agree on support ownership, operating measures, issue escalation, and the path to normal operations.
The executive sponsor needs a client-side leader who can challenge assumptions, align functions, and coordinate implementation partners around the organizational objective. That is the role I bring to transformation programs.
Readiness Is A Decision Supported By Evidence.
A scheduled go-live is a planning assumption. Readiness is an executive decision. On a complex cutover, I want that decision to be grounded in the evidence needed to protect operations.
Five Areas To Validate Before Transition
- Data: conversion results, reconciliation, exception ownership, and the timing of final loads.
- Integrations: critical operating flows, downstream dependencies, and recovery paths.
- People and processes: operating procedures, role access, training, and ownership.
- Cutover execution: sequenced activities, dependencies, accountable resources, and clear go/no-go checkpoints.
- Stabilization: support coverage, issue prioritization, communications, and operational handoff.
Programs at Disney and Bentley illustrate why orchestration matters: hundreds of systems and thousands of transition activities require shared visibility and explicit decisions. A green status label is useful only when the underlying evidence supports it.
Put The Perspective To Work.
Discuss your program, integration, or transformation challenge directly with me.