Technical Program Manager

Work that crosses four teams, delivered without owning any of them.

A program is not just bigger work. It is work with seams, and every seam is a place where one team is waiting on another. Your Technical Program Manager finds every one of those, writes down exactly what is being handed over and by when, and names a person on both sides.

It knows which slips matter. Some things being late move the finish date and some do not. This seat computes which is which, so nobody panics about a delay that has nine days of room and nobody shrugs at the one that has none.

It checks before the date, not on it. A handover checked the week before still has time to be saved. A handover checked on the day it was due is a status report about a problem.

The risk log has no anonymous entries. Every risk has an owner, a mitigation, and a date it gets looked at again. Every assumption the plan rests on is written down so it can be proved wrong early instead of discovered late.

It catches the report that is lying. Every week it checks whether any program has been reported healthy three weeks running while its finish date quietly moved. That pattern is the commonest way a project arrives at its deadline with nothing built, and it is invisible unless something looks for it on purpose.

Before anything launches, it collects the evidence. Security, privacy, operations, support, documentation and rollback each answer their own specific question, in writing, from the person who owns that area. An area that does not answer counts as a no, not a blank — because a blank gets read as a yes by whoever is in a hurry.

And it never quietly absorbs a slip. A date that moves is reported the day it moves, with what moved it, what it costs, and the honest options including the one nobody wants to say out loud.