The title looks simple on paper. Chief Product and Technology Officer. Engineering, product, operations, tech support, infrastructure, data ops, implementations. all reporting up. One person responsible for the entire technology organization, post-merger, at a healthcare company backed by a serious private equity firm with serious expectations. Clean. Crisp. Legible.
It is none of those things in practice.
What you actually inherit is six functions that have never operated as a single unit, two sets of processes built by two teams who each believed their way was correct (and were each right, in their original context), and a company that has been in integration mode long enough that everyone is a little exhausted and a little territorial and a little uncertain about where they stand. You're not stepping into a clean org. You're stepping into a structure that is still figuring out what it is.
I've been through this. Here's what I wish someone had told me before day one.
The Org Chart Is a Fiction
I don't mean that disrespectfully. Org charts serve a real purpose. they describe formal reporting relationships, they clarify accountability on paper, they're a necessary artifact of how large organizations function. But they do not describe how decisions actually get made, who people actually listen to, or where the informal authority sits.
In a post-merger environment, the gap between the org chart and reality is especially wide. The formal structure was often drawn before the integration was complete, sometimes before it had really begun. Titles were assigned to manage the transition, not to reflect the actual power dynamics of the combined company. There are people on that chart who will have enormous influence over whether your agenda succeeds, and they are not in the boxes you'd expect.
The org chart tells you who reports to whom. It tells you almost nothing about who shapes what gets done, who surfaces problems early, and who the organization actually trusts under pressure.
You will not understand the real power structure in 30 days. This is not a failure. it is the honest timeline. In the first month, you're still learning the language. The vocabulary of each legacy team, the shorthand that signals belonging, the specific anxieties people are carrying about their futures. You can't read the informal power map until you've been in enough rooms to see who people look to when a hard question gets asked.
What you can do in 30 days: listen aggressively. Specifically, pay attention to who gets cited when decisions are defended. "We talked to so-and-so and she said..." is a signal. Who is that person? Are they in a senior box on the org chart or are they three levels down and running something critical? Either way, find them.
The Two Traps That Get New CPTOs Killed
The first trap is proving you're smart by having answers before you understand the questions. This one is seductive. You came in with experience. You've seen this movie before, maybe at a different company, a different merger, a different technology context. You have a view. And you have a board and a CEO who brought you in because they want a view. The temptation to deliver it immediately is real.
Don't. The experience that makes you valuable is the experience that helps you ask better questions, not the experience that lets you skip asking them. The specific context of this company, this merger, this team, this customer base. you don't have it yet. And the person who shows up on day two with a transformation roadmap has told every legacy leader in the room that what they built doesn't matter. You've earned enemies before you've made a single ally.
The second trap is the mirror image: trying to be liked by not making any decisions. This one is subtler. You tell yourself you're still in listening mode. You're being collaborative. You're not being rash. But the organization is watching, and what it sees is someone who won't make a call. In a post-merger environment where everyone is tired and uncertain, a leader who won't decide is more destabilizing than one who decides too fast. At least decisiveness is a known quantity.
You have to find the narrow path: demonstrate that you understand the situation before you propose solutions, but don't use understanding as a substitute for leadership.
What You Actually Need to Accomplish
By the end of 90 days, you need four things. Not a hundred-day plan. Not a new operating model. Not a reorg. Four specific things.
Know where the revenue is. Which products, which customer segments, which contracts are generating the actual cash the business runs on. This sounds obvious. It is not obvious in a merged company where two revenue streams are still being reconciled and the sales organization is still figuring out how to position the combined product. Get into the data yourself. Don't wait for someone to brief you.
Know where the risk is. Technical debt that threatens a customer commitment. A system that two integrations depend on and one engineer understands. A compliance gap that nobody has escalated because it's not yet a crisis. Post-merger companies have inherited risk from both sides, and it accumulates quietly. You need to find it before it surfaces publicly.
Identify the three people who actually make things happen. In every organization, there are people whose absence would cause things to stop working. They are not always in senior roles. Find them. Learn what they care about. Understand what would make them stay, and what would make them leave. These people are not replaceable on a short timeline, and losing one in your first 90 days is a recoverable problem. Losing one in month six because you didn't see it coming is not.
Make one visible decision that shows you understand what the business needs. Not a transformation initiative. Not a platform announcement. One specific thing. a prioritization call, a resource shift, a "we're stopping this". that demonstrates you have a view on what the business needs to succeed and you're willing to act on it. This is the moment people decide whether they trust you. It does not have to be large. It has to be real.
The Tension You Can't Resolve
There is a persistent tension in every post-merger tech leadership role between transformation and time-to-revenue. The board has a thesis. probably something about platform consolidation, operational leverage, the combined capabilities unlocking a market that neither company could address alone. That thesis requires change, and change requires investment and time.
The business has immediate needs. A customer renewal that depends on a feature. An implementation that's running late. A support escalation that's threatening a relationship. These things don't pause for transformation timelines.
Most playbooks frame this as a sequencing problem: stabilize first, then transform. That's useful, but it's incomplete. It implies that transformation is a mode you enter after the immediate work is done. In practice, the immediate work never ends. If you wait for stability before beginning transformation, you wait forever.
The better frame: manage both in parallel, be explicit about the tradeoffs, and don't let either consume the other. The transformation work cannot be sacrificed entirely to the immediate because then you've delivered no lasting value. The immediate work cannot be sacrificed to transformation because then you've delivered no near-term value either. Neither extreme is survivable. The job is to hold the tension and make the tradeoffs visible to the people who need to make them.