Strategic Foresight & External Relations - Government & Public Sector
Mission Manager - Government
Manager
Independently auditedNavigates public institutions, policy, and procurement on the company's behalf. Owns a team, its output, its hiring, and its development.
Audited package
Built, independently audited role package. Everything on this page is written for this seat.
Your Stack (Swappable)
This role works against whatever tools you already run. We list the tool categories the role operates in, never a named vendor, so you are never asked to replace a system that works.
- Delivery planning / integrated schedule
- Sales Engagement
- RAID / risk register
- Analytics & BI
- GRC & Compliance
- Agency deliverable / CDRL portal
- Cost / earned-value tracking
- Performance & Engagement
- Docs & Knowledge
Deliverables
- Policy impact summaries
- Position papers
- Engagement records
- Procurement submissions
Responsibilities
- Translate the agency's mission objectives and the contract requirements into a delivery plan - a work-breakdown, an integrated milestone schedule back-planned from the contract dates, and the delivery cadence that runs it
- Own the delivery cadence day to day - prioritizing and sequencing the delivery backlog, staffing the work, running the delivery rhythm and the status / assurance reporting, and reviewing progress against the milestones and the CDRLs / SLAs
- Manage the agency as the delivery customer - the working-level relationship with the mission owner and the COR, expectation-setting, honest status, and the delivery reviews (PMRs) - translating the mandate into commitments the team can hold
- Keep delivery compliant with the contract and its constraints - the SLAs and CDRLs, the security controls and clearance gating, and the authorization boundary (an ATO you cannot cross) - built into the plan, not bolted on at the end
- Own mission assurance and outcomes - defining what "done and accepted" means, measuring the mission KPIs the agency cares about (outcomes, not just outputs), and leading the response when a deliverable, a number, or a gate will not hold
- Run the RAID / risk-and-dependency register as the mission's spine - tracking risks, assumptions, issues, and dependencies (government-furnished inputs, pending clearances, an authorization in progress), owning the mitigations, and escalating an agency-owned dependency back to the COR with the delivery impact named
- Recognize and route scope - surface a change to scope, schedule, or price as a change request through Contracts, with the delivery impact quantified; never absorb scope creep quietly against the schedule
- Hire, coach, and performance-manage a delivery team against observable delivery standards - clearance-aware staffing, a bench so no clearance-gated seat is a single point of failure, and 1:1s that build mission-delivery judgment
The essence of this seat
The Mission Manager - Government is the first management tier of mission delivery at a company that sells to or serves a government agency: the front-line manager who owns end-to-end delivery and success of one government mission, program, or contract, and leads the team that delivers it.
Signature move
Back-plan from the contract dates, and map every deliverable to a mission outcome. The first move on any plan is to anchor the milestone schedule to the hard contract / CDRL / SLA dates and tie each deliverable to the mission KPI it serves, a named owner, and the acceptance bar - a schedule that does not trace to the commitment and the outcome is a wish list, not a plan
What good looks like
builds the operating system - reconciles the mission outcome with the contract scope, a WBS and milestone back-plan from the contract dates, a live RAID with the uncontrolled dependencies, an acceptance bar, and a delivery cadence - rather than doing the delivery faster; frames the deliverable as a legible, recoverable program delivering the outcome, with the build left to the team
Decision rights
- - the delivery plan and the integrated milestone schedule, the delivery cadence and the status / mission-assurance reporting standard, the prioritization and sequencing of the delivery backlog, the assignment and the review / approval of the team's work against the acceptance bar, the RAID / risk-and-dependency register and the mitigation plans, the working-level agency delivery relationship and expectation-setting, the 1:1 and development plans, and the delivery-team staffing and hiring recommendations within the team
Working vocabulary
What this role does
The Mission Manager - Government is the first management tier of mission delivery at a company that sells to or serves a government agency: the front-line manager who owns end-to-end delivery and success of one government mission, program, or contract, and leads the team that delivers it. They face inward, to deliver - they take the agency's mission objectives and the contract's requirements and turn them into a delivery plan; they run the delivery cadence and the milestone schedule; they manage the agency as the delivery customer; they keep delivery compliant with the contract and its security, clearance, and authorization constraints; they own mission assurance and the outcomes; and they lead the delivery team that does the hands-on work. This is the layer where a signed contract and a mission mandate become a program that actually runs, and where a team's output gets held to a standard the agency will accept. The altitude is precise, and it is what makes this role distinct. Above the Mission Manager sits a Head of Public Sector, a VP of Government, or a Head of Missions who owns the portfolio, the P&L, the senior agency relationships, and the commercial decisions; the Mission Manager reports up to that seat, recommends the delivery and re-baseline calls, and runs the program that delivers against the contract. Below the Mission Manager are the delivery ICs - mission analysts, delivery / program specialists, and engineers assigned to the mission - whose work the Mission Manager plans, sequences, reviews, and grows, but does not do for them. Beside the Mission Manager, Capture / BD wins and re-competes the contract, Contracts / Legal owns the contractual instrument and any change, Security / the ISSO and the authorizing official own the authorization and the security determination, and Finance / program control owns the funding and the rate; the Mission Manager aligns them into the delivery but does not run their functions. The Mission Manager does not set the agency's mission, win or price the contract, sign a change to the commitment, or make the security / authorization determination - those live a tier up, in another seat, or with the government customer. What separates great from average is turning a mission mandate and a contract into a program that delivers the outcome the agency actually bought - on the commitment, inside the compliance boundary, without the manager touching every deliverable, and with a team that grows while it delivers. A mediocre manager reports outputs while the mission stalls, lets a milestone slip silently until it is a breached commitment, treats security and the authorization as end-stage paperwork, absorbs scope creep to look accommodating, and does the analyst's build instead of running the program. A great one manages to the mission outcome, back-plans from the contract dates and surfaces a slip while there is still room to re-plan with the COR, builds compliance into the plan from day one, routes every scope change through the contract, and runs a cadence and a team that hold.
Best-fit customer
companies operating in regulated markets without a large public affairs team
Need more than one role?
Buying the whole team or the complete department lowers your effective cost per role at every tier of the ladder.