The setting
's keep code in Git repositories and run automated pipelines, written in YAML, that build, test, and deploy software. Teams run it as a hosted service, on their own servers, or as a managed service for one customer.
Completed prerequisites are waiting on a shared review while rehearsal reservations expire.
Separate acceptance protects the reserved dates, while a shared discussion protects against mismatched assumptions.
Who you’d be doing this for
“I’ve cleared tomorrow morning for three engineers, and I’m still being asked to keep the slot tentative.”
Enrico Navarro · Enterprise DevOps Lead · a character in this brief
Has reserved engineers’ time for one of the six onboarding rehearsals.
What is at stake
Six enterprise customers could lose tomorrow’s onboarding rehearsals despite completed prerequisites. You must weigh separate acceptance against the assumptions a shared review might catch.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- independent acceptance vs shared understanding
- customer reservations vs engineering preparation
- immediate closure vs repeatable handoffs
Why Gitlab
GitLab Duo Agent Platform onboarding connects engineering readiness with enterprise customers’ existing source control and CI/CD workflows.
Written with these in mind
Not your kind of problem? 30 more at Gitlab, or browse every organization.
Where the organization context comes fromThe postings this brief was written from, and the reporting read before it.
The organization context comes from public information. The situation and characters are written for the brief.
Job postings it was written from
Public descriptions of the work at Gitlab. They are listed as sources, not as openings. The lines under a posting are its own words, where it meets this brief.
- Principal Technical Program Manager (opens in a new tab)
- Leading the GitLab Duo Agent Platform from GA through enterprise adoption, including customer onboarding, support models, and billing integration for AI-driven capabilities
- We own the end-to-end delivery of complex, cross-functional programs including AI platform capabilities, enterprise customer initiatives, and strategic technology transformations.
- Technical Program Manager (opens in a new tab)
- Facilitate working group meetings and async discussions to support decision-making, surface tradeoffs, and keep programs on track.
- As a Technical Program Manager in GitLab’s R&D organization, you’ll lead cross functional initiatives that help teams deliver reliably, efficiently, and at scale.
- Senior Manager, Technical Program Management (opens in a new tab)
- Staff Program Manager, CCO Programs (opens in a new tab)
- You'll be the first Program Manager supporting CX Executive initiatives and the founding hire in a Programs function that will grow as the CCO's highest-priority cross-functional initiatives outgrow ad hoc ownership.
- You'll be the Staff Program Manager, CCO Programs, running the cross-functional initiatives on the Chief Customer Officer's (CCO) priority list.
- Customer Experience Enablement Lead (opens in a new tab)
- The team partners across Sales, Customer Success, Solutions Architecture, Partnerships, Product, Marketing, and Operations to turn business priorities—including product launches, new GTM motions, and AI adoption—into scalable programs, practical content, training, onboarding, and accreditations.
- It’s a high-impact, cross-functional team focused on improving field productivity, strengthening customer-facing capabilities, and measuring enablement’s contribution to business growth.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.
Where similar work appears
Other live briefs connected to this one, and what connects them.
Similar problems at other organizations
Like this one, each of these turns on moving faster inside a system others depend on.
Four departments still request manual extracts despite having working reports.
You must weigh departmental ownership against a centralized service that needs less customer preparation.
Incorrect confirmations are sending patients into clinic callbacks and invalid appointment slots.
You have to weigh rapid restoration against the proof needed before changing a live scheduling workflow.
Refund-policy changes are approaching review while Jira, Salesforce, and Slack disagree about unresolved work.
You must decide what AI can reconcile and what Program Managers must verify before acting.
The same setting, from another role
Each is set around Gitlab’s Integrated source control and CI/CD, written for a different role. They’re separate briefs, not the same scenario.
Repository investigations are consuming critical release time because the first plausible cause is hard to verify.
You must decide what AI assembles, what engineers confirm, and how the pilot proves the difference.
Required approvals are appearing after merge requests enter review, creating avoidable rework.
You have to weigh a clear preview against the performance and fidelity of repository rule evaluation.
Agent-written CI/CD changes are creating unexpected runner demand after they merge.
You must weigh early cost guidance against estimates that could overstate risk and slow useful changes.
Other problems with a similar purpose
In each of these, as in this one, the aim is to turn a complicated, unpredictable operation into something customers can count on to arrive on time.
Northern Mexico fleet installs are being booked with vehicle lists that do not match the installer’s assignment.
You must protect appointment speed without sending partners incomplete work.
Incomplete first shipments are entering the receiving exception queue and delaying brand activation.
You have to weigh a tighter readiness check against the need to get qualified brands live quickly.
Only 68% of invited employees make a first card purchase within 48 hours.
You have to weigh faster activation against keeping entity assignment and spend controls accurate.
