United Kingdom · Technical roles · Mid-Level (2-5 years)

Technical Program Manager

Here is the whole job, in plain words. What it is, a real day, what you decide, how you're judged, how people get here and where they go next. Then the part no course gives you: twelve AI tutors who learn your work.

Experience bandMid-Level (2-5 years)
Direct reportsNo direct reports
Reports toSenior Technical Program Manager
UK framework levelUsually a coordinator, or early in a professional job

Also advertised as Project Delivery Lead (Technical) · Software Programme Coordinator · Engineering Project Manager

Built on an analysis of 43,079 real UK job descriptions · grounded in qualifications employers recognise

Start with a free Future Fluency check, tuned to Technical Program Manager

Ten quick questions, one per Future Fluency, asked against this role rather than a generic one. About five minutes, and no card.

Start the check, free

1What this role really is

You'll be the person who keeps our technical projects on the rails, making sure engineering teams are building the right thing, at the right time, and that everyone's on the same page. It’s a hands-on role where you'll get deep into the technical details without actually writing code. Think of yourself as the conductor of a complex orchestra, ensuring all sections play in harmony to deliver a brilliant performance.

2What you'd actually use

The tools this job runs on, and how well you'd need to know each one.

Jira & ConfluenceIntermediate

Creating and managing projects, building basic dashboards, writing clear project requirements and technical specifications. You'll understand workflows, link tickets, and use basic JQL to find information. You'll keep our Confluence pages tidy and up-to-date.

Miro / LucidchartIntermediate

Facilitating brainstorming sessions, creating basic system diagrams to explain technical flows, and documenting user journeys. You'll use these to visualise dependencies and explain complex ideas simply.

Slack / MS TeamsIntermediate

Proficiently using channels, threads, and basic integrations (like Jira bots) for daily communication. You'll run stand-ups and help triage incidents in dedicated channels, keeping comms clear and focused.

Tableau / LookerBasic

Navigating pre-built dashboards to understand project health, team velocity, or sprint progress. You'll apply filters and export data to answer specific questions about your project's performance.

GitHub / GitLabBasic

Navigating repositories to understand where code lives, following pull request (PR) workflows, reading release notes, and linking commits to Jira tickets. You won't be writing code, but you'll understand the development lifecycle.

3What you get to decide, and how that grows

Power in a job isn't your title. It's what you're allowed to decide. Here's how it grows as you move up.

The choice	Coming in	Where you are now	The step above
Project Scope Changes	Escalate all proposed changes to supervisor for approval. No independent decisions.	Can approve minor scope adjustments (e.g., swapping out a non-critical feature for another of similar effort) within a sprint, after consulting with Product. Major changes require manager and Product Lead approval.	Can recommend and drive approval for significant scope changes across multiple sprints or workstreams, in consultation with Product and Engineering Directors. Can approve minor scope changes for their own programs.
Dependency Resolution	Identify and flag dependencies to supervisor. Support supervisor in tracking resolution.	Independently identify and actively manage critical dependencies, escalating only when unblocked after 48 hours or if requiring senior intervention. Can propose workarounds.	Proactively identify and resolve complex, multi-team dependencies. Can negotiate resource allocation with peer leads to unblock critical path items. Defines and improves dependency management processes.
Technical Risk Mitigation	Identify potential risks and report to supervisor. Assist in documenting mitigation plans.	Identify and document technical risks in the RAID log. Work with engineering leads to propose and track mitigation strategies. Escalate high-impact, high-probability risks to manager.	Lead technical risk assessments, quantify potential impact, and design comprehensive mitigation plans. Present risk profiles and trade-offs to leadership. Own the overall technical risk posture for their programs.
Budget Allocation (Project Specific)	No budget authority. Inform supervisor of any potential costs.	Can track project spending against a pre-defined budget. Any expenditure over £2K (e.g., new tool licences, specific contractor hours) requires manager approval. Can provide input for team-level budget planning.	Manages project budgets up to £50K, including vendor selection and contractor engagement. Can make recommendations for larger budget allocations and contribute to annual planning cycles.

4How you'll be judged

The scoreboard, honestly: the hard targets, how often each one is actually looked at, and the quiet human signals that never make it onto a dashboard.

On-Time Milestone Completion

Percentage of critical project milestones delivered by their committed date.

Target · 90% of all major milestones met on schedule

If a project has 10 key milestones, you'd aim to hit 9 of them on the original date. Missing a critical API freeze date would count against this.

Dependency Resolution Time

The average time it takes to unblock a critical dependency once it's identified.

Target · Critical dependencies unblocked within 48 hours

Team A needs an API from Team B. If Team B is delayed, you're expected to get the right people talking and find a solution (or a workaround) within two days, not let it fester for a week.

Status Report Accuracy

How often your project status reports lead to unexpected escalations or surprises for leadership.

Target · Zero escalations due to inaccurate or delayed status reporting per quarter

If the Head of Engineering finds out about a major blocker from an engineer in the hallway, not from your weekly report, that's a miss. You should be ahead of the news.

Scope Creep Management

The percentage of agreed-upon scope that changes or expands without formal approval.

Target · Less than 10% unapproved scope changes per project

If the initial project was to build X, Y, Z, and we end up with X, Y, Z, A, B without a formal change request, that's scope creep. You're the gatekeeper.

Proactive Risk Identification

How well you spot potential problems before they become actual blockers or delays.

You're regularly flagging risks in RAID logs, bringing up 'what if' scenarios in planning meetings, and suggesting mitigation strategies. Engineers and product managers often say, 'Good shout, I hadn't thought of that.'

Cross-Functional Collaboration

Your ability to get different teams (Engineering, Product, QA) working together smoothly on your project.

Teams are openly communicating, sharing information without prompting, and resolving minor conflicts amongst themselves because you've fostered a collaborative environment. You're seen as a neutral, helpful party by all involved.

Clarity of Communication

How effectively you translate complex technical details into understandable updates for non-technical audiences, and vice-versa.

Product managers understand the engineering constraints, and engineers grasp the business 'why' for their tasks. There are fewer misunderstandings in meetings, and your written updates are consistently clear and concise.

Team Morale & Engagement (Project Specific)

The overall sentiment and engagement of the engineering team working on your program.

Engineers feel heard, supported, and understand their role in the bigger picture. They come to you with problems, not just their manager. Project retrospectives are productive, not just gripe sessions.

5Would you like it

The honest version. What people enjoy, and what grinds them down.

What people enjoy

Solving Complex Puzzles

You'll spend your days untangling technical dependencies, figuring out how to sequence work across different teams, and diagnosing why a project is stuck. It's a constant stream of 'how do we get this done?'

Figuring out how to integrate a new third-party service that impacts five different internal teams, each with their own priorities and technical stacks.

Driving Visible Impact

You'll see your projects go from an idea on a whiteboard to a live feature used by customers. Your work directly contributes to shipping new products and improving our platform.

Launching a major new platform capability that significantly reduces customer onboarding time, knowing you orchestrated its delivery.

Orchestrating Collaboration

You'll be the glue between engineering, product, and other teams, making sure everyone's talking, aligned, and working towards a common goal. It's about bringing people together to achieve something bigger.

Successfully running an 'interlock' meeting where three different engineering teams agree on a shared API contract and commit to a delivery timeline.

What frustrates people

Herding Cats: Being accountable for success without direct authority over the people doing the work.
The Translation Tax: Constantly translating between deep technical details and high-level business impact.
Accountability without Control: Taking the blame for delays caused by teams outside your direct influence.
Roadmap Tetris: The endless challenge of fitting immovable deadlines and under-estimated work into finite timelines.
Chasing Status Updates: Having to constantly ping people for progress because they don't proactively communicate.

What this role does not give you

Direct people management responsibilities (that comes at higher levels).
Deep, hands-on coding (you'll understand it, but not write it day-to-day).
A perfectly predictable, unchanging work environment (expect curveballs).
The ability to make unilateral decisions about technical architecture or product features.

6Who you work with

This role directly impacts our technical delivery cadence and the quality of our product releases. Get it right, and we're faster, more reliable, and build better software. Get it wrong, and we're looking at missed deadlines, unhappy engineers, and frustrated customers. You're a critical cog in the machine that turns ideas into reality.

Inside the business

Engineering Leads and Teams
Product Managers
Designers
QA Engineers
Operations Teams

Outside the business

Key Vendors (occasionally, for integrations)
Early Adopter Customers (for feedback gathering)

7What you need before you start

Not a wish list. The things you would be expected to already have.

At least 2 years of experience in a technical project coordinator, scrum master, or junior TPM role, or equivalent experience in a software engineering role with strong project leadership.
A proven track record of successfully delivering small to medium-sized technical projects.
Experience working in an Agile environment (Scrum or Kanban is fine).
Demonstrable ability to communicate effectively with both technical and non-technical audiences.
A foundational understanding of software development processes and technical concepts.

8What to practise next

Where the job is going, and what to do about it starting this week.

Advanced Cloud Infrastructure Concepts

Our infrastructure is constantly evolving. A deeper understanding of cloud services means you can better anticipate technical risks, understand architectural trade-offs, and communicate more effectively with platform engineering teams.

Serverless Architectures (e.g., AWS Lambda) · Containerisation (e.g., Docker, Kubernetes) · Infrastructure as Code (IaC) · Cloud Security Fundamentals

This week: Read a few introductory articles or watch some YouTube videos on Docker and Kubernetes.
This month: Ask a platform engineer to walk you through our core cloud architecture for your project's services.
Month 2: Take a free online course or tutorial on AWS or GCP fundamentals (focus on compute, storage, networking basics).
Month 3: Start attending relevant internal tech talks or brown bag sessions on cloud infrastructure. Ask questions!

Quick win: When discussing technical requirements, ask engineers about the specific cloud services they plan to use and why. It shows you're engaged and learning.

9Staying current once you are in

What people here do to keep up

Regularly read industry blogs and publications focused on technical project management, Agile best practices, and software development trends.
Attend webinars or online conferences on topics like dependency management, technical risk assessment, or stakeholder communication.
Participate in internal 'Lunch & Learn' sessions or brown bag talks on new technologies or engineering practices.
Seek out mentorship from more experienced TPMs or engineering leads within the organisation.

10How the AI economy is changing work like this

Before we ask anything of you, here's what we can already say about AI and work of this kind:

The new skill this role is being asked for: Prompt Engineering & LLM Integration

Honestly, competitors are already using AI to draft reports in 10 minutes that used to take 2 hours. TPMs who figure this out will outproduce their peers significantly. This isn't future-gazing; it's happening now.

We'll only ever tell you what we can actually back up. No hype, no scare tactics.

The rising capability

Zavmo analysis

What's rising in its place

This is where the work is heading, and the higher pay with it. Get fluent here and the shift stops being a threat and starts being your edge.

Prompt Engineering & LLM Integration

Honestly, competitors are already using AI to draft reports in 10 minutes that used to take 2 hours. TPMs who figure this out will outproduce their peers significantly. This isn't future-gazing; it's happening now.

Context windows and token limits
Temperature settings for different tasks
RAG architectures for proprietary data
Output validation and hallucination detection
Prompt chaining for complex analysis

Data-Driven Decision Making (Advanced)

As projects grow more complex, 'gut feeling' isn't enough. TPMs will need to use data to justify resource allocation, predict project health, and prove impact. This moves beyond just reading dashboards to actively interpreting and presenting data.

Basic Statistical Analysis
Data Visualisation Best Practices
A/B Testing Principles
Predictive Analytics Fundamentals

What you’ll use

Skills this role draws on

Technical

Agile & Lean Methodologies
System Design & Architecture Concepts
Cross-Functional Dependency Management
Technical Risk Management
Roadmap & Release Planning
Stakeholder Communication & Influence

The pathway

How you actually get there, here

How you become one varies far more by country than what one does. This is the UK route. Most people take one of these ways in; the right one depends on where you're starting from.

1
Junior Technical Program Manager / Project Coordinator
1-2 years
Skills to master
- Mastering project tracking tools (Jira), basic Agile ceremonies, clear status reporting, and identifying simple dependencies.
You're ready to move on when
- Consistently delivers assigned tasks on time and to a good standard.
- Proactively flags issues and asks for help when stuck.
- Can run a basic sprint stand-up or retrospective effectively.
- Demonstrates a good grasp of the software development lifecycle.
2
Software Engineer (with project leadership aspirations)
2-4 years
Skills to master
- Understanding the full software development lifecycle, effective communication across teams, basic project planning, and a desire to move into a non-coding role.
You're ready to move on when
- Has led small technical initiatives or features within their team.
- Is often the 'go-to' person for coordinating work between engineers.
- Shows strong organisational skills and a knack for problem-solving beyond just code.
- Expresses a clear interest in driving project outcomes rather than just writing code.
3
QA Lead / Test Manager
2-3 years
Skills to master
- Deep understanding of quality gates, release processes, risk assessment, and cross-team coordination for testing efforts.
You're ready to move on when
- Has owned the test strategy and execution for complex features or projects.
- Is adept at identifying and managing risks related to quality and release readiness.
- Demonstrates excellent communication with engineering and product teams.
- Has experience coordinating work across multiple QA or engineering teams.

11Where this role leads

The long view:Your journey as a Technical Program Manager here at Zavmo is just the beginning. We're committed to your growth, and there are clear pathways for you to become a leader in technical delivery, whether that's through managing people or becoming an indispensable individual contributor shaping our most critical programmes.

Pay & demand

Pay and demand for this role will appear here, each figure traced to a named authoritative source (e.g. the ONS Annual Survey of Hours and Earnings, under the Open Government Licence). We don’t show numbers we can’t attribute.

The ten Future Fluencies

Zavmo analysis

The credential is what you can do today. These are what keep you valuable.

A qualification proves you can do the job as it's defined today. These ten are what decide whether you're still the obvious person for it in five years. They're the capabilities employers are now writing into senior roles faster than people are learning them. Zavmo weaves them through whatever you study, so you come out with both: the credential and the fluency.

The highlighted ones are the Fluencies your role leans on hardest, from how Technical Program Manager is actually changing. In about two minutes, the free confidence check asks where you stand on each of the ten. That's the whole check, and it's what makes the plan yours rather than generic.

12The team that's yours

No two people are taught the same way. This is one-to-one, not one-to-many.

Zavmo is a hyper-personalised AI learning platform. Twelve virtual tutors, each with a different way of teaching, and one orchestration agent that picks the right one for the moment. So every single lesson is shaped around you, your role, and the way you learn. Not a course everyone sits through. A conversation built for you, and no one else.

…and nine more, matched to you after your first chat. Meet all twelve

Start free and meet yours

13What it feels like

A conversation, not a course

Because your tutor knows your role, your projects and your last session, learning sounds like this. And it's different for every single person:

IT & Telecoms System ManagementLevel 4

Applied to your work in Technical Program Manager

This unit aims to provide learners with the skills to effectively manage IT and telecoms systems. Learners will understand system management components, including monitoring, maintenance, and troubleshooting, and review system functionality to identify areas for improvement. They will then manage systems by implementing changes and ensuring optimal performance, following best practises.

How the thinking builds

Remember
Understand
Apply
Analyse
Evaluate
Create

An illustration of a Zavmo lesson, built from this role’s own route. The unit, its objective and every criterion above are the awarding body’s own words, not an example.

One to one, not one to many

No two people run this the same way

A course is written once and handed to everyone. This is assembled around you, and keeps changing as it learns you. Five things it reads, and what each one changes.

Your actual work Every lesson is taught against a live piece of your own work, not a worked example from a textbook.
What you already know The first conversation finds your starting point, so you skip what you can already do and spend the time on what you cannot.
The conditions you learn under Not a learning-styles quiz. The evidence does not support those. The dimensions the research does back, read once and used to shape the plan.
How far you got last time It picks up mid-thought. The tutor knows what you said, what you struggled with, and what it asked you to try.
Which tutor suits the moment Twelve of them, each for a different kind of thinking. The one who walks you through a first idea is not the one who stress-tests it.

See how you learn, free. Eight questions, no sign-up. A directional taster; the diagnostic inside Zavmo goes deeper and keeps adapting.

DemonstrateIllustration

Evidenced on your work in Technical Program Manager

You do not finish by watching something. You finish by showing it on the work you already do, against the measures this job is judged on.

On-Time Milestone CompletionPercentage of critical project milestones delivered by their committed date.If a project has 10 key milestones, you'd aim to hit 9 of them on the original date. Missing a critical API freeze date would count against this.90% of all major milestones met on schedule
Dependency Resolution TimeThe average time it takes to unblock a critical dependency once it's identified.Team A needs an API from Team B. If Team B is delayed, you're expected to get the right people talking and find a solution (or a workaround) within two days, not let it fester for a week.Critical dependencies unblocked within 48 hours
Status Report AccuracyHow often your project status reports lead to unexpected escalations or surprises for leadership.If the Head of Engineering finds out about a major blocker from an engineer in the hallway, not from your weekly report, that's a miss. You should be ahead of the news.Zero escalations due to inaccurate or delayed status reporting per quarter
Scope Creep ManagementThe percentage of agreed-upon scope that changes or expands without formal approval.If the initial project was to build X, Y, Z, and we end up with X, Y, Z, A, B without a formal change request, that's scope creep. You're the gatekeeper.Less than 10% unapproved scope changes per project

These are this job's own measures, with its own targets. Nothing is marked evidenced, because nobody has started this yet. Yours would fill in from the work you bring.

Your passport

This isn't a certificate you file away. It's a passport to the life you're designing.

Every credit you earn and every fluency you build adds up: evidence where it counts, carried with you. Zavmo keeps the map: where you are, where you're heading, and the next step, at your pace, around your life. From Technical Program Manager to Senior Technical Program Manager (L3), and whatever you decide comes after.

Level 3 · in progressAI Fluency→ Senior Technical Program Manager (L3)→ your design

Where this takes you

Your journey as a Technical Program Manager here at Zavmo is just the beginning. We're committed to your growth, and there are clear pathways for you to become a leader in technical delivery, whether that's through managing people or becoming an indispensable individual contributor shaping our most critical programmes.

See Your Progress GrowIllustration

Technical Program Manager

Agile & Lean Methodologies
System Design & Architecture Concepts
Cross-Functional Dependency Management
Technical Risk Management
Roadmap & Release Planning
Stakeholder Communication & Influence

This is your Mind Palace on learn.zavmo.ai. Every skill above comes from this role's own record, not an example borrowed from another job. A node lights up when you evidence it, and what you build stays yours between jobs. That is the part a course cannot do.

14The detail, folded away

Everything else the record holds

The career branches in full, how AI is already showing up in the day-to-day, and the questions people ask about this job. Here when you want them, out of the way while you decide.

Where it leads next, rung by rung

Where it leads

The career path, and where it branches

Technical Program Manager is a start, not a ceiling. Each step below asks for new skills and hands back more autonomy.

Senior Technical Program Manager (L3)
3-5 years
Leading complex, ambiguous programs with multiple workstreams. Mentoring junior TPMs. Making technical decisions within scope.
- Mastery of programme-level risk management.
- Designing and implementing new process improvements.
- Deep understanding of architectural trade-offs.
- Leading technical discovery and design sessions.

Working with AI on the job

Working with AI

Where AI is starting to help

Let's be real, a lot of a Technical Program Manager's job involves wrangling information, chasing updates, and drafting communications. Good news: AI can take a big chunk of that off your plate, freeing you up to do the actual problem-solving and influencing that truly matters.

We're not talking about replacing your job; we're talking about giving you a superpower. Imagine having a personal assistant that never sleeps, helping you stay on top of everything. Our internal AI Hub is packed with tools and guides specifically for TPMs, designed to make your day-to-day work smoother and more impactful.

Automated Scribe & Summariser

Use AI meeting assistants (like Fathom or Otter.ai) to automatically transcribe your meetings, pull out action items, and generate concise summaries. No more frantic note-taking; just focus on the conversation. You'll then get a neat summary to drop into Slack or Confluence.

Risk & Dependency Forecaster

Imagine an AI scanning our Jira backlogs, Confluence pages, and Slack channels, flagging potential dependencies or risks that haven't been explicitly linked. It might ping you, 'AI detected similar keywords in Team A's API spec and Team B's feature brief. Is there an un-tracked dependency?' This tool helps you spot problems before they blow up.

First-Draft Factory

Need a project brief, a communication plan, or a stakeholder update? Feed a few bullet points and key data into an LLM (like ChatGPT or Claude) and get a solid first draft in minutes. You'll spend your time refining, not staring at a blank page. Great for those tricky 'we need this by end of day' requests.

Stakeholder Comms Customiser

Got a detailed technical status update? Drop it into an AI model and ask it to generate tailored summaries for different audiences. A high-level business impact summary for the CEO, a financial update for the CFO, and a resource-focused summary for engineering leads – all from one input. Seriously powerful stuff.

Common questions

How do you become a Technical Program Manager?

Common routes in include Junior Technical Program Manager / Project Coordinator (1-2 years), Software Engineer (with project leadership aspirations) (2-4 years) and QA Lead / Test Manager (2-3 years). Times vary with prior experience.

Where can a Technical Program Manager progress to?

This role can lead on to Senior Technical Program Manager (L3) (3-5 years), depending on the skills you build.

What level is a Technical Program Manager in the UK?

This role aligns to RQF Level 3 on the UK framework, a guide to the depth of qualification it maps to, not a hard entry bar.

What new skills matter most for a Technical Program Manager?

Increasingly, Prompt Engineering & LLM Integration and Data-Driven Decision Making (Advanced). These are the areas where the higher-paid, future-proof work is heading.

The honest bit

You’ve started things before

Most of them were built for a room full of people who aren’t you. A cohort moves on whether or not your week allowed it, and by the third week the thing you’re behind on becomes the reason you stop opening it.

There’s no cohort here, and no timetable to fall behind. Before anything starts, Zavmo asks when you’re sharpest and how long you can realistically sit down for, then builds the sessions around those answers. A bad fortnight changes your pace. It doesn’t put you behind.

And you only pay once you start learning. Searching and planning are free, and you can cancel any time — so the cost of finding out is an afternoon, not a year.

What it costs

Less than one coaching session. Every month.

A single career-coaching hour costs more than a month of this, and it ends when the hour does. Zavmo doesn't. It's £70 a month, about £2.30 a day, for a companion that knows a Technical Program Manager, works on the job you actually do, and keeps going at your pace rather than a timetable's.

Searching and planning stay free. You only pay when you start learning.
Your credits are yours. Regulated, and they don't vanish when a subscription ends.
Cancel any time and billing stops. No notice period, no minimum term.

Your path, personalised

You have the map. Walking it is the part we do together.

This route runs to 9 national skill standards. That is a real journey.

Zavmo shapes a learning experience as unique as you are. It fits how you learn, your pace and the work you already do. Every step stays benchmarked to recognised national standards. That’s the plan for becoming a Technical Program Manager: personal to you, and it still counts. The first steps are free.

Independent research finds well-designed intelligent tutoring performs nearly as well as one-to-one human tutoring: VanLehn (2011), Educational Psychologist.

A private tutor in the UK averages £35–40 an hour . Zavmo is £70/month.

A Zavmo curriculum screen: a three-month plan of nine units, ninety credits, each one an Ofqual-regulated unit the learner can tick or untick before starting. — A real plan on learn.zavmo.ai: Ofqual-regulated units, credits, and a three-month run at your own pace.

Start free No commitment. See your first steps free.

15Where to go from here

Other roles at Level 3

Same depth of qualification, different job. Useful if the work appeals but this particular role does not.

Other roles in Technical roles

Stay in the field you know and move sideways rather than up.

If you leave this industry

The skills you'll build as a Technical Program Manager are highly transferable. You could move into broader Programme Management roles in other technical industries (e.g., FinTech, HealthTech, Gaming), or even transition into Product Management if you develop a strong product sense. Your ability to orchestrate complex technical work is valuable everywhere.

Not sure this is the right direction?

Work out what you actually want from work first, then come back and see which roles fit it. Takes about ten minutes.

You're not behind. You're right on time. The shift is only just beginning. Your role won't look the same in two years. Be the one who leads the change, not the one it happens to. Build my plan, free Here's the first ten minutes: a 2-minute confidence check → your personalised roadmap → meet the tutors matched to you. No card, cancel any time. No card. Build your plan, see your roadmap and meet the twelve tutors matched to you. All free. When you're ready to start learning, it's £70 a month, billed monthly. Cancel any time and billing stops.

Technical Program Manager

What's rising in its place

Prompt Engineering & LLM Integration

Data-Driven Decision Making (Advanced)

Skills this role draws on

Technical

How you actually get there, here

Junior Technical Program Manager / Project Coordinator

Software Engineer (with project leadership aspirations)

QA Lead / Test Manager

The credential is what you can do today. These are what keep you valuable.

Roles this leads to

No two people are taught the same way. This is one-to-one, not one-to-many.

A conversation, not a course

No two people run this the same way

This isn't a certificate you file away. It's a passport to the life you're designing.

Everything else the record holds

The career path, and where it branches

Senior Technical Program Manager (L3)

Where AI is starting to help

Automated Scribe & Summariser

Risk & Dependency Forecaster

First-Draft Factory

Stakeholder Comms Customiser

Common questions

You’ve started things before

Less than one coaching session. Every month.

You have the map. Walking it is the part we do together.