First 90 Days as a CPTO
The conventional onboarding playbook fails CPTOs. Passive listening for 90 days reads as uncertainty. This framework gives the first three months a specific shape.
The one question that matters most
"Where does accountability go to die?"
Every org has a specific handoff — between product and engineering, between strategy and execution, between customer feedback and backlog — where ownership becomes genuinely unclear. That seam is what you were hired to close. Find it in the first 30 days, because everything else is downstream of it.
The three-phase shape
D1
Day 1–30
Diagnosis, not relationship-building
The goal is not coffees and intros. The goal is to understand where accountability breaks down. Build a reading list, not a social calendar.
Read the last 6 months of incident reports — look for action items that were never assigned
Pull the roadmap and ask when every item was last reprioritized and by whom
Sit in sprint reviews as an observer — watch what gets escalated and what gets silently dropped
Find the post-mortem that names a systemic problem that shows up again in a later incident
Ask each direct report: what decision has been waiting longest for an owner?
D30
Day 30–60
Build the shared frame — before you move
Resist the pull to fix the visible problem. The visible problem is almost never the real problem. Use this phase to understand whose version of reality will collide with yours when you start moving.
Watch out for
The person who seems most aligned in one-on-ones is often the first to sandbag a decision when it goes to a broader audience. Map the gap between private alignment and public behaviour before you present anything consequential.
D60
Day 60–90
Signal your actual model
By day 60, the org has already formed a view of you. The clearest signal you can send isn't a reorg or a strategy deck. It's how you navigate one difficult conversation that crosses the product-engineering seam.
Run one prioritization debate where a technical refactor competes with a customer-facing feature — hold both lenses in the same room
Make at least one staffing decision that reflects the integrated view, not a compromise
Be explicit about the tradeoff, not just the outcome — show your reasoning across both sides
The 90-day test
"By day 90, you should have made at least one decision that disappointed someone on each side. Not to prove balance — but because the integrated view genuinely produces different outcomes than optimizing for either side alone. If everyone is happy with you at 90 days, you haven't started doing the job yet."