A new government affairs leader’s first 90 days should produce three things: a reliable view of the landscape, explicit choices about priorities and ownership, and an operating cadence the team can sustain. Days 1–30 are for auditing and listening. Days 31–60 are for prioritizing and designing. Days 61–90 are for institutionalizing the work.
Use the Government Affairs 30/60/90-Day Plan Template to manage interviews, findings, decisions, risks, and deliverables inside the wider Government Affairs Operating System. If you are building the function rather than inheriting it, pair this plan with How to Build a Government Affairs Function From Scratch.
Four principles for the first 90 days
Do not confuse access with understanding. A full calendar can hide weak issue strategy. Do not announce metrics before defining objectives. Measurement follows strategy. Do not reorganize around the loudest anecdote. Test patterns across leaders, staff, records, and external evidence. Do not wait until day 90 to improve obvious controls. Assign urgent commitments, deadlines, and uncovered relationships immediately.
Days 1–30: Audit and listen
Start with business priorities and the external decisions that could change them. Interview the CEO or business president, legal, regulatory, finance, communications, operating leaders, and the government affairs team. Ask what leadership expects, which outcomes matter, where surprises have occurred, which relationships are concentrated, and what decisions the function should enable.
| Audit area | Questions | Day-30 output |
|---|---|---|
| Business and policy priorities | What decisions could change revenue, cost, permission, reputation, or timing? | Ranked external-decision landscape |
| Team and consultants | Who owns what, where is capacity constrained, what is outsourced? | Responsibility and dependency map |
| Stakeholders and issues | Who matters to each priority and what evidence supports the current read? | Initial stakeholder and issue portfolio |
| Systems and memory | Where do interactions, commitments, rationale, and reporting come from? | Institutional-memory risk baseline |
| Leadership reporting | What cadence exists and what decisions does it support? | Reporting expectations and immediate fixes |
By day 30, publish a short diagnostic—not a grand strategy. Name the five to seven priority external decisions, critical deadlines, top relationship gaps, overdue commitments, consultant dependencies, data limitations, and decisions leadership must make. Use the existing Institutional Memory Risk Assessment to test continuity without fake precision.
Days 31–60: Prioritize and design
Turn the audit into choices. Define the objective, desired outcome, minimum acceptable outcome, accountable issue owner, executive sponsor, priority stakeholders, engagement logic, next milestone, and escalation trigger for each major issue. Tier stakeholders based on their relevance to the objective—not status alone. Assign operating owners and backups for critical relationships.
| Design decision | What good looks like |
|---|---|
| Issue portfolio | A bounded set with explicit outcomes, owners, milestones, and stop/defer choices |
| Stakeholder coverage | Priority tiers, evidence, operating owners, principals, backups, and next actions |
| Team and consultant roles | Clear scope, decision rights, deliverables, and knowledge-retention expectations |
| Operating cadence | Weekly review, commitment control, briefing rhythm, and escalation path |
| Measurement | Leading and lagging indicators tied to objectives and evidence |
Days 61–90: Institutionalize
Install the habits that make the strategy durable: a weekly intelligence and priority review; issue owners who maintain status and next milestones; relationship owners who coordinate engagement; commitments with owners and due dates; a decision-oriented leadership update; monthly portfolio review; and quarterly revalidation of objectives, risks, KPIs, and relationship coverage.
A practical week-by-week sequence
| Weeks | Primary focus | Evidence of progress |
|---|---|---|
| 1–2 | Leadership, team, business, and issue interviews | Interview log; immediate risks and commitments assigned |
| 3–4 | Portfolio and system audit | Day-30 diagnostic; memory-risk baseline |
| 5–6 | Priorities, outcomes, stakeholder tiers | Draft issue charters and coverage map |
| 7–8 | Ownership, roles, cadence, reporting | Operating model reviewed with team and leadership |
| 9–10 | Run the new rhythm | Two complete weekly cycles; escalations resolved |
| 11–12 | Validate, adjust, publish next-quarter plan | 90-day review, annual-plan bridge, KPI baseline |
Common first-90-day mistakes
Avoid promising outcomes before understanding decision paths; treating every legacy issue as a priority; replacing consultants before capturing their knowledge; importing bad spreadsheets into a new system without governance; measuring meetings before defining value; and making yourself the owner of every executive relationship. The goal is organizational capability, not personal indispensability.
Adapt the first 90 days for individual contributors, managers, and leaders
| Role level | Primary first-90-days objective | Evidence by day 90 |
|---|---|---|
| Individual contributor | Learn institutions, business context, sources, workflow, stakeholders, controls, and quality standards | Reliable analysis, preparation, records, commitments, and an owned workstream |
| Manager | Understand the portfolio and assume issue, stakeholder, and workflow ownership | Prioritized work, clear owners, useful briefs, coordinated execution, and surfaced risks |
| Director / VP | Diagnose and design the function’s mandate, choices, resources, cadence, leadership interface, and continuity | Approved operating model, portfolio, responsibilities, reporting, and development priorities |
A new individual contributor should not imitate a VP reorganization plan, and a new leader should not spend 90 days proving personal monitoring skill. The progression moves from learning and doing the work, to owning the work, to designing the system in which the work occurs. Use the career guide and professional capability model to set level-appropriate development expectations.
What should exist at day 90
Leadership should see a prioritized issue portfolio, stakeholder coverage and ownership, a clear risk register, defined team and consultant roles, a working weekly rhythm, an executive reporting format, a KPI baseline, a knowledge-retention standard, and the next-quarter or annual plan. Continue with the ROI framework, executive and board reporting guide, and weekly operating rhythm.
Michael-Christopher Warren is a government affairs practitioner and the founder of StatecraftCRM. He writes practical frameworks for how government affairs work actually gets done — from stakeholder relationships and institutional memory to executive briefings, strategy, and team operations.
Start Statecraft without a sales process.
Choose your plan and users, see the exact price, and start online.