Marian Kamenistak · CTO · VP Engineering · Head of Engineering

CTO Board Deck: The Delivery Number You Owe by Friday

Three quarters of shipping 50 to 60% of the roadmap, a board deck due Friday, and no explanation that doesn't sound like an excuse. Half the team is quietly interviewing on top of that, so the honest fix has to move delivery and retention at once, which is exactly the kind of promise boards have stopped believing. The delivery number is the share of the roadmap that shipped against plan, and right now yours reads 50 to 60%.

You can get two of the three done by Friday. This is about which two, and how you say so without it reading as a retreat.

Marian Kamenistak speaking at an engineering leadership event.

Why both of the obvious answers are bad

The trap is that both available stories cost you something. The optimistic one commits you to a number you can't hit, and you're back in twelve weeks having spent the last of your credibility. The candid one hands a board that's already nervous a fresh reason to be nervous, and you spend the following quarter being managed rather than trusted.

There's a third version, and it's the one boards tend to reward. Split the story in two: leading indicators you commit to weekly, and lagging outcomes you forecast with a stated confidence. Sprint completion, ad-hoc ratio and cycle time are things you can move inside a month and show moving. Roadmap percentage is an outcome you predict, with a range, and boards are far more tolerant of an honest range than of a missed point estimate.

That shifts the question in the room from did you hit it to is the system improving, which you can answer truthfully every six weeks. It also spares you the death march, because nothing in it needs the team to work weekends to make a slide true.

So we build the deck line by line. Which three leading indicators you'll own in public, what your baseline genuinely is rather than the flattering read of it, and what you say when a board member asks why last quarter missed. They will ask, and it's a question with a good answer available to you if you've prepared one.

By the next board cycle you have a number that survives scrutiny, a written plan underneath it, and no further need to ask for another quarter.

Working it 1:1

Marian Kamenistak, mentor to CTOs and VPs of Engineering

Bi-weekly through an ordinary quarter, weekly in the fortnight before a board meeting. I have sat in the seat: helped build Mews into a $2bn+ unicorn from 8 to 80 teams, was an advisor to Manta (acquired by IBM), and spent 3 years in the Bay Area as Principal Software Architect at Databricks. The pattern data comes from 3,662 1:1 leadership sessions with engineering leaders in 17+ countries. Mentees rate every session from 0 to 10 right after it. Since 2024 the average is 9.79.

Pricing is public: 395 EUR per session, or 1,975 EUR per quarter (6 sessions over 3 months, 5 paid + 1 free). Same prices if you check fit and book with my AI tool: under 10 minutes to your first session, no discount. You only pay for a session you rate 8 out of 10 or higher. Full pricing.

Related reads

The other situations CTOs bring

All six, plus the questions CTOs ask most: CTO coaching & mentoring