Key Findings
Download (PDF)
Table of Contents
How Legislative Intent Shapes Daily Work
Barriers to Effective Implementation
Outdated Language, Technological Burden, and Structural Lock-In
How Congress Could Learn Better
An important note: The recommendations compiled here reflect the individual views and experiences of interview participants. They are not endorsed by POPVOX Foundation, the Partnership for Public Service, the Niskanen Center, the Foundation for American Innovation, Civil Service Strong, or any other organization involved in the Departure Dialogues project.
Introduction
The companion methods paper to this report describes how and why POPVOX Foundation and a coalition of nonpartisan partner organizations launched the Departure Dialogues project: a proof of concept for capturing qualitative stakeholder input at scale in a format useful to Congress. That paper documents the process — the tools, the partnerships, the design decisions, and the operational lessons. This paper presents what we heard.
There is far more richness in these interviews and testimonies than any single paper can capture. Consider this paper a road map to the archive and the themes that emerged. We encourage you to explore the interactive reports and then dive deeper into the full contributions, where the texture and specificity of individual voices can speak for themselves.
Addressing the information pacing problem
Congress faces what scholars and practitioners call the “pacing problem” — the widening gap between the speed of technological, economic, and social change and the capacity of legislatures to understand and respond to it. But the dimension of the pacing problem that most directly motivated this project is informational. Effective legislation and oversight require Congress to process large amounts of qualitative, ground-level knowledge — what might in other contexts be called intelligence — from the people who actually implement programs and experience their consequences. That knowledge rarely reaches Capitol Hill through existing channels.
POPVOX Foundation’s work over several years — with Congressional caseworkers, agency liaison staff, and through the Interbranch Exchange partnership with Georgetown University’s Massive Data Institute — has built a detailed picture of why. So too has the work of our project partners, the Niskanen Center, Civil Service Strong, the Partnership for Public Service, and the Foundation for American Innovation, each bringing their own lens to the challenge of more effective Congressional oversight and increased state capacity. The formal mechanisms for interbranch communication have significant structural limitations. Committee hearings are performative as often as they are informative. CRS and GAO produce rigorous work, but it is frequently retrospective and constrained by the questions members think to ask. Congressionally mandated reports have too often become compliance exercises rather than genuine feedback mechanisms or methods to identify and test proactive policy solutions. And constituent engagement — casework, town halls, correspondence — generates enormous volume that Congress has invested little in its capacity to actually learn from.
The Legislative Affairs Bottleneck
One of the clearest findings from the Interbranch Exchange was that Legislative Affairs offices structurally function as bottlenecks in the flow of information between agencies and Congress. This is not a failing of the dedicated professionals in those roles, nor is it an institutional design flaw in isolation. Federal agencies are large and complex, and the challenge of managing them is compounded by the significant realignment of priorities, personnel, and operations that accompanies each change in administration. In that context, it is entirely appropriate that Legislative Affairs offices focus communications on presidential priorities and political sensitivities. The challenge is that this filtering function, while serving a legitimate purpose, comes at a cost to Congressional oversight. Program-level, operational oversights— what’s working, what’s breaking, what statutory language creates unnecessary friction — rarely make it through the Legislative Affairs channel. The result is a persistent information gap: the federal employees closest to implementation are among those with the least access to the legislative process, and Congress is left without the ground-level perspective it needs to write better laws and conduct effective oversight.
Departure Dialogues participants confirmed this pattern with striking consistency:
“If there had been stronger and more intentional connections between delivery teams and congressional staff, I believe many programs could have achieved their goals more effectively.”
“The one time I asked my direct supervisor about why we operated a program in a way that seemed quite different from the legislation authorizing them, I was told that interpretation of Congressional/legislative intent was only in the purview of agency leadership, and I should not question how programs operate. I was asked not to raise the issue further. Later, I was told offhand by another staff member that the decision on how to handle this program was made from an Assistant Secretary from a prior administration. I was confused why the decision stuck even though administrations had changed.”
“Congress could create stronger feedback loops by systematically reviewing how legislative requirements perform in practice.”
The Departure Dialogues Questions
The Departure Dialogues interview protocol centered on ten questions, developed through multiple rounds of discussion and feedback among coalition partners. These questions were, in a sense, leading: we asked what the challenges were to effective feedback loops and program administration, and where Congress placed burdens to efficiency — not whether they existed at all. They were leading because we knew already that these problems caused major challenges; the aim of the project was to surface them at a granular level.
Years of work at the intersections between Congress and the Executive branch — engaging caseworkers who navigate the collision between legislation and implementation daily, hearing from agency staff who carry deep programmatic knowledge but lack structured channels to share it, and studying the institutional dynamics that prevent good information from reaching the people who need it — had given the POPVOX Foundation team a clear sense of where the fault lines were. Career civil servants carry specific, actionable knowledge about how Congressional language functions once it enters the world of implementation. That knowledge has enormous value for legislative effectiveness, and it is systematically underweighted in how Congress learns. The pressures and capacity constraints on legislative staff — small teams, compressed timelines, enormous portfolios — do not usually allow the luxury of figuring out how a program will actually be implemented before a bill leaves committee.
The questions were designed to meet that reality. They asked participants to do what Congress often cannot: slow down, reflect on operational experience, identify specific friction points, and articulate what would make the programs they knew intimately work better. The responses confirmed what we expected in some areas and surprised us in others. What follows is organized around those ten questions, drawing out the themes that emerged most clearly across contributions.
Five main takeaways for a Congressional audience:
1. Congress has a structural intelligence problem.
The people closest to implementation at federal agencies have specific, actionable knowledge about what’s working and what isn’t. They want to share it. The Legislative Affairs structure at federal agencies filters it out. Congress is flying blind on implementation not because employees won’t talk but because no direct, timely channels exist for them to do so.
2. Laws are accumulating faster than they’re being maintained.
The most consistent finding across agencies: individually reasonable requirements have stacked into a cumulative burden that actively undermines program delivery. The Paperwork Reduction Act creates more paperwork. Build America Buy America adds 10-24% to construction costs. Reporting requirements generate compliance artifacts rather than useful information. Nobody is cleaning up the interaction effects of decades of layered mandates.
3. The contracting and technology model is backwards.
Agencies are required to outsource capabilities they should own, then locked into outdated systems by procurement timelines that can’t keep pace with technology cycles. FITARA centralized decisions away from the people who understand the work. The result: agencies that can’t build, can’t adapt, and can’t control their own technical infrastructure. Multiple participants independently pointed to in-house capacity as the fix.
4. Statutory language written for one era is governing programs in another.
Two-year political cycles can’t support ten-year economic development outcomes. Annual appropriations contradict multi-year program goals. Laws assume paper-based processes. The attorney general personally approves Diplomatic Security use-of-force guidance updates, creating years-long backlogs. The gap between what the law says and what the work requires is where mission effectiveness goes to die.
5. This kind of feedback mechanism should be permanent, not only possible in an emergency.
The proof of concept worked. Fifty experienced professionals produced hundreds of specific, granular, actionable observations — the kind of input Congress needs for reauthorizations and oversight but currently has no systematic way to collect. The project happened because of a workforce disruption. The need it addressed is structural and ongoing. Committees could build this into reauthorization cycles tomorrow.
This paper highlights selected quotes that illustrate key themes. The full archive of contributions — with far more richness, specificity, and nuance than any summary can capture — is available in the interactive reports at popvox.org/departure. We encourage readers to explore them:
Who We Heard From
Fifty individuals participated in Departure Dialogues through a mix of formats: 27 submitted responses via Google Form, eleven took part in small group interviews, nine contributed self-directed video interviews, and three participated in one-on-one interviews. Participants represented fifteen agencies across the Executive branch, with the heaviest concentration from USAID (9 participants) and HHS and its sub-agencies — including FDA, NIH, HRSA, and SAMHSA — (9 participants combined), followed by EPA (6) and the State Department (3). Other agencies represented included GSA, DHS, the Department of Education, USDA, IRS, and several others, reflecting meaningful breadth across both domestic and foreign policy functions.
Among those who listed their roles, participants held positions spanning a wide range of seniority and function — from program analysts and specialists to directors, deputy directors, senior advisors, and a vice chairman. Roles included technical and scientific positions (Physical Scientist, NEPA Specialist, Clinical Reviewer), operational and administrative functions (Grants Management Specialist, Transportation Specialist, HR Supervisor), and senior leadership (Assistant Administrator, Chief Well-being Officer). Many participants held Foreign Service or internationally-focused roles, consistent with the strong USAID and State Department representation.
The participant pool skewed toward experience. Total government service ranged from under one year to 40 years, with an average of 15 years overall and 14.3 years at participants’ most recent agency. Participants fell into four broad seniority tiers: 10 were early-career (0–5 years), 16 were mid-career (6–15 years), 15 were senior (16–29 years), and 9 had served 30 or more years. Nearly half of all participants had 16 or more years of service, and the 9 longest-serving participants each brought three decades or more of institutional experience. This seniority profile suggests that while the proof of concept drew a relatively small sample, it reached people with deep firsthand knowledge of how federal agencies function — and, in many cases, how they have changed over time.
The participants in Departure Dialogues were not a cross-section of discontented employees. They were experienced professionals — program managers, policy analysts, scientists, acquisition specialists, regional directors, foreign service officers — many with decades of service across multiple agencies and administrations. What they shared was not grievance but expertise.
“My career reinforced the profound impact that committed civil servants can have — both at home and abroad — and that work matters, even when institutions falter.”
“Regional office staff are hired from the regions. We don’t just work in our regions, we live in our regions and have cultural and regional history that we have lived ourselves.”
“I got to meet some of the smartest, most intelligent and dedicated people in the world. It was great because at every step in the level, I was blessed to work for people who truly believed in their job and career and that they were making a difference.”
“It’s painful for me to hear the insulting caricatures of federal employees that have become especially prevalent in recent times. The vast majority of federal colleagues I’ve known were hard-working and dedicated to achieving their missions in support of the American public.”
The interactive reports include the biographical context that each participant opted to share. The range of agencies, roles, and career trajectories represented in this project is itself a finding worth exploring:
How Legislative Intent Shapes Daily Work
How frequently did Congressional or legislative intent/language come up in your work, and in what contexts?
When we asked participants how frequently Congressional or legislative intent was a factor in their work, the overwhelming response: constantly. But the way participants described that presence split into two distinct patterns.
For some, legislative intent was a reliable compass — a reference point that gave direction and purpose to their work. For others, it was a source of persistent friction — language that collided with operational reality, created ambiguity, or imposed requirements that undermined the programs it was meant to support. Both groups took legislative intent seriously. The difference was in how well the intent had been translated into workable law.
Legislative Intent as Reference Point
Many participants described legislative intent as the foundation of their work — the thing that gave their programs direction and legitimacy. For these employees, Congressional language was not an obstacle but an anchor.
“Our team often used legislative intent as the benchmark, where agency actions stayed true to what Congress meant to accomplish.”
“So it’s almost as if we had a chance to operate, you know, inside the collective mind of Congress as certain provisions were written, and a lot of the Hill staff that had participated in the enactment of the IRA were either still on the Hill and on our motion or their motion engaged with us in how we interpreted the statute.”
Legislative Intent as Source of Friction
For other participants, the experience was markedly different. Legislative intent was present — but as a source of confusion, rigidity, or outright contradiction with what programs needed to accomplish.
“Because the statutory language was vague, agencies were left to define key regulatory concepts, such as ‘minimal risk,’ ‘informed consent,’ and ‘adequate provisions’, through expert opinion rather than empirical evidence, creating vulnerabilities in current policy.”
“Many times, we saw that while laws were well-intentioned, the implementation drifted away from that original purpose, creating friction for both the agency and the public.”
“I think that the lack of that general understanding has wreaked havoc as more and more legislation is enacted that doesn’t even understand what it is enacting...”
The distinction between these two groups is not simply a matter of attitude. For participants like Edgar and the EPN small group, legislative intent was navigable — in part because they had proximity to the people who shaped it, with Hill staff who had participated in drafting remaining engaged through implementation. That access allowed intent to function as a guide rather than a constraint.
For others, the experience was starkly different. Legislative language arrived without the operational context needed to apply it, guidance shifted constantly, and the people with the knowledge to clarify had not been in the room when the law was written. The further from the drafting process an employee was, the more opaque Congressional intent became — something to be inferred under pressure rather than understood and applied.
Barriers to Effective Implementation
What specific policy, procedure, or legislative requirement most hindered your ability to implement programs effectively?
This question produced the most passionate and specific responses in the entire project. Participants named actual programs, actual requirements, and actual consequences with the granularity that only comes from direct operational experience. Several themes recurred across agencies and policy domains.
The Cumulative Weight of Overlapping Requirements
No single reporting requirement is unreasonable. But federal employees described a landscape where individually sensible requirements have accumulated into a compliance burden so heavy that it actively undermines the programs it was designed to protect.
“One recurring challenge I encountered was the cumulative burden imposed by overlapping and sometimes conflicting legislative and reporting requirements associated with different funding streams. While each requirement was reasonable in itself, together they created inefficiencies that reduced our ability to focus on program effectiveness. This led to significant duplication of effort, diverting staff time and resources away from program monitoring, learning, and adaptation.”
“There is so much redundancy and cross-functional information that updates were never complete in all locations.”
“Reduce the inclination to create earmarks leading to overlapping initiatives and duplicative reporting.”
When the Law Prevents the Mission
Some of the most striking examples came from participants who described statutory language that directly prevented them from achieving the goals Congress intended. The gap between what a law was meant to accomplish and what its text actually allows can be enormous — and the people who fall into that gap are the constituents the law was written to help.
“Research shows that flexible financial assistance (FFA) is effective in helping victims gain safety and independence. Unfortunately, grant funds are so constrained that up until 2024, we were not able to even try to make FFA programs a possibility. In 2024 we released a NOFO for two FFA programs, one Tribal-specific and one with broad eligibility. Over 600 applications were submitted and we could only make a handful of awards. Application after application discussed the incredible need for this type of program. Think about a DV victim fleeing her abuser. She’s living in a shelter with her children, trying to find an apartment, and her car breaks down. Grantees cannot use grant funds to help her repair her car. Under FFA programs, they could. That car repair means she keeps her job, she earns enough to rent an apartment, she gets her kids to school, etc. It’s one step closer to her leaving her abuser for good.”
“This was particularly complex in fragile and conflict-affected environments, where rigid legislative requirements sometimes conflicted with rapidly changing conditions on the ground.”
The Price Tag of Inefficiency
Several participants went beyond describing frustration to quantifying it. Inefficiency is not just an inconvenience — it has a measurable cost, borne by taxpayers, by program beneficiaries, and by the federal employees who spend their time on compliance rather than mission.
“The statute that has resulted in the greatest increase in grant costs... is the Build America, Buy America Act... The cost of many construction projects is therefore typically 10–24% higher than they would be without the law... For a single construction project, this will likely require thousands of hours of additional work across the contractor, recipient, subrecipient, and federal agency.”
Systems Not Built for the Work Congress Mandated
A recurring theme: Congress authorizes programs without understanding the operational infrastructure required to deliver them. The result is mandates that collide with the systems, staffing, and authorities agencies actually have.
“One of the challenges that we encountered trying to implement this program through the USAID system is that our systems were not built to handle what we consider to be small grants.”
“We should not be making decisions that impact millions of lives without using quality data. Without quality data, objectivity is virtually impossible.”
The interactive reports contain dozens of additional examples across agencies and policy domains. The specificity of these contributions — naming actual programs, actual requirements, and actual consequences — is precisely the kind of ground-level intelligence that Congress needs but rarely receives. We encourage readers to explore the full archive:
Outdated Language, Technological Burden, and Structural Lock-In
Can you describe a situation where outdated legislative language or technological limitations created unnecessary administrative burden, on program staff or on constituents?
This is where the pacing problem becomes most visible. Participants described statutory language written for a pre-digital world, compliance frameworks that assume paper-based processes, and a contracting ecosystem that systematically locks agencies into outdated technology. The burden falls on both federal employees and the public they serve.
Statutory Language That Can’t Keep Up
When Congress doesn’t contemplate how a requirement will interact with operational reality, including the overlapping operational realities of multiple intersecting requirements, agencies are left to navigate the gap between what the law says and what the work requires.
“The fact that NEPA applied to these funding actions and how it applied and what that meant was never contemplated by Congress or the DOE or OSED leadership until after, in my case, the Hydrogen Hubs awardees were actually already selected.”
“The State Department must have the attorney general personally approve any updates to the use of force policies [for Diplomatic Security officers]. This requirement cannot be delegated. No other federal law enforcement agency faces this burden...The consequence of this hurdle is that updating policies takes years... agents were operating under outdated guidance that did not reflect best practices, creating significant legal and diplomatic risk... and reviews of security incidents overseas are hampered by timelines that do not reflect reality.”
Contracting and the Technology Trap
Contractor requirements and outsourcing practices are not, strictly speaking, outdated technology. But they create the conditions that lock agencies into it. When agencies are required to procure technology through cumbersome contracting processes rather than building and maintaining capacity in-house, the result is often systems that are outdated before they’re deployed — and nearly impossible to update once they are.
“FITARA is a good example of legislature that had the right intent but was implemented in a way that made delivery harder. By centralizing technology decision-making with CIOs, FITARA pulled authority away from the people closest to the work. That created bottlenecks, slowed down projects, and pushed agencies toward commercial off-the-shelf solutions that often didn’t fit their real needs. What was meant to create oversight ended up creating distance between decisions and delivery.”
“Most importantly, Congress needs to understand that agencies should retain ownership of their missions. Technology should be something agencies control and understand, not something they outsource blindly.”
“Realized approximately $10M in cost avoidance by working with team and stakeholders to create workflows and systems on our intranet using SharePoint instead of purchasing expensive applications.”
“While we must still be the authority on taxes, sea changes in the technology landscape make effective administration and records management dramatically easier and more efficient. Taxpayer expectations have also changed, as the private sector financial services industry continues to innovate and provide more convenient, even delightful customer experiences.”
A Note on the Paperwork Reduction Act
Across multiple participants and agencies, a striking pattern emerged around a single law:
“Complying with the Paperwork Reduction Act was overly burdensome and delayed projects, making us less effective than we could be.”
“If Congress wants effective federal programs, it needs better data to verify that effectiveness. It will not get that data with the Paperwork Reduction Act as it currently is.”
“It’s now the Paperwork Enhancement Act, especially reduces the ability to provide our program information in a way that is much more universally accessible.”
A law designed to reduce paperwork creating more paperwork is not just an irony — it is a microcosm of the broader pattern. Well-intentioned requirements accumulate. Each one makes sense on its own terms. And over time, the cumulative effect is a system that works against its own purposes. This is what the pacing problem looks like from the inside.
The full archive contains many more examples of statutory and technological mismatches, with specificity that goes well beyond what this summary can convey. We encourage readers to explore the interactive reports.
How Congress Could Learn Better
How could Congress do a better job of learning about programs in your area of expertise, with the goal of legislating more effectively?
This question elicited some of the most directly actionable responses in the entire project. A clear pattern emerged across agencies, policy domains, and career stages: create structured, regular opportunities for Congress to hear directly from the people implementing programs, at the working level, outside the filter of political appointees and Legislative Affairs offices. These participants want to be heard. They have specific, practical knowledge that would make legislation better. They lack a channel to communicate it.
This finding speaks to a clear appetite for more projects exactly like Departure Dialogues itself — and for institutionalizing them into the habits and expected workflows of Congress. What this project demonstrated as a one-time proof of concept, participants are asking to see become routine.
“Congress could strengthen its ability to legislate more effectively by creating more consistent, structured opportunities to learn directly from those implementing and affected by programs...Congress could also benefit from deeper, sustained engagement with mid-level technical experts within agencies, who have the most direct knowledge of what works, what does not, and why.”
“Talk to social workers, nurses, and caregivers on the front lines. Learn more about services and the gaps in affordable housing, senior housing, and Veteran housing.”
“Ask the front-line workers and subject matter experts what they need from Congress.”
“More elected officials need to be trained in the sciences. I’m not suggesting that they can’t be elected unless they have a background in science, but I am suggesting that they need a base-line level of knowledge and experience. Like a freshman orientation, if they don’t come in with a Bachelors in Science, or at least some AP classes. And regardless of that wishful thinking, they should get out on the ground more with civil servants doing the work. Every time we had a Congressional field trip with electeds and staff, the resulting conversations and policies seemed to come out better for the land and people that depend on the Forests. Showing up on the ground to see a project really makes things better.”
“Structured listening sessions, operational site visits, and independent reviews could give Congress a much clearer picture.”
“Create a mechanism to get feedback and suggestions from rank-and-file civil servants, but in a way that ensures anonymity and confidentiality.”
“Wild assumptions and accusations may generate headlines, but that kind of showmanship shuts communication and transparency down very quickly.”
Reporting Requirements Inform Rather than Obscure
Specifically under the umbrella of how Congress learns, one theme participants highlighted were the burdens of outdated or overly prescriptive reporting requirements. This represents a clearly open and promising area of potential improvement that could strengthen the quality of the information Congress receives and uses to make decisions while cutting down on mission-eroding administrative burden within agencies.
“At GSA — the quarterly reporting dynamics, while well-intentioned, was at times burdensome. Our framework of ‘quarterly updates’ created awkward situations — some quarters would have a glut of information that made us cut interesting content, while others had very little information of note.”
“Importantly, streamlining reporting to Congress would not compromise the quality or rigor of the data available.”
Participants offered dozens of specific, actionable ideas for how Congress could build better information channels. The interactive reports organize these by theme and agency. For committees and offices considering how to strengthen their connection to implementation reality, the archive is a practical resource.
Rebuilding from the Ground Up
If you could rebuild your program/agency from the ground up, without changing its overall scope and mission, how would it look different when you were done?
This question gave participants permission to think big. What’s striking is how consistently the answers converged: invest in people first; integrate programs that currently operate in silos; build technology in-house; reduce layers that create distance between decisions and delivery. Many participants were careful to note that the missions themselves are sound — it’s the organizational structures and procedural accumulations that need reimagining. Others tackled civil service reform with a scope that goes beyond what this paper can address in depth; a separate appendix of specific reform recommendations is forthcoming.
“USAID’s greatest asset is its workforce. A rebuilt agency would prioritize staff development...”
“At GSA — build the program exclusively in-house, or with minimal contractor support. There were usually 3 — at times 5 — different contracting teams. This was not a recipe for success.”
“It would look like a Veteran-centered healthcare system again, operating under clinical healthcare leaders who understand that healthcare is relational...”
“Administration transitions should require a 6–12 month moratorium for complete and thorough review and auditing before effecting any significant program changes or agency disbursements.”
If You Had Five Minutes
If you had 5 minutes to brief a Congressional committee about fixing bureaucratic inefficiency in your area, what specific legislative change would you recommend?
If you had 5 minutes to pitch agency leadership about changes they should make within the agency, what specific changes would you recommend?
These questions produced the most concise and targeted responses in the project. Participants took the time constraint seriously and focused their recommendations with impressive precision. A separate appendix compiling these specific recommendations is forthcoming; what follows is a selection that illustrates the range and specificity of what participants offered.
To Congress
“Congress needs to build and invest in its own digital service capability. It can’t rely entirely on outside vendors... there’s already the beginning of a digital service function in Congress, but it should be bigger, better resourced...”
“Allowing the Agency to partner with countries for development outcomes, which are impossible to achieve in 2-year political cycles...”
“I would advise them to weigh the true effect of their legislative changes... look at the effects of similar legislation at different levels of government, look at international law...”
To Agency Leadership
“Insist on a new standard of employee performance that is overseen by specialized leadership who have earned their leadership roles by demonstrating exceptional performance in their relevant disciplines.”
“If Congress wants better access, safer care, and a stable healthcare workforce, we must stop asking clinicians to carry the cost of inefficiency with their health and well-being.”
“Federal HR rules and regulations were designed with a myriad of laudable goals in mind... One thing they were not designed for? Empowering hiring managers...”
Life After Government Service
What are your plans post government service?
This question was lighter in tone than the others, but it revealed something important about the second-order effects of creating structured opportunities for public contribution. Many departing employees aren’t walking away from public service — they’re looking for new ways to continue it. The loss of this workforce is not just an institutional loss for the agencies they left; it represents an enormous reservoir of expertise and commitment that remains available if channels exist to engage it.
As documented in the companion methods paper, two participants who connected through Departure Dialogues went on to form “We the Doers,” a nonprofit organization of former senior civil servants focused on improving government effectiveness. The project had been designed as a data collection mechanism, but it became, in practice, a catalyst for community formation and sustained civic engagement. People who had recently lost their professional community found, through the act of contributing to a shared project, the beginnings of a new one.
This was not an isolated finding. Throughout the project, participants expressed gratitude for being asked — not because the questions were novel, but because the asking itself was. The simple act of creating a structured space for expertise to be shared and valued generated goodwill, connection, and ongoing engagement that extended well beyond the dataset.
“If these programs still exist in a few years and they are being rebuilt so they can continue to do good, I would love to be called to facilitate a discussion.”
“Throwing the expertise and decades of experience out the door and into the wood chipper was egregiously irresponsible and inhumane...”
“The public didn’t care that it was being destroyed because they thought that we were just giving away money to poor people...”
The willingness of departing employees to contribute their knowledge — even in the midst of significant personal and professional disruption — is itself a finding. The bottleneck is not willingness. It is infrastructure. And the value of building that infrastructure extends beyond any single project.
Cross-Cutting Themes
The preceding sections are organized around the questions we asked. But the archive itself — processed through Talk to the City’s AI-assisted qualitative analysis — surfaced patterns that cut across those questions and across agency boundaries. When hundreds of open-ended responses are analyzed for thematic clusters rather than mapped to predetermined categories, the picture that emerges is both confirming and surprising.
While we encourage readers to explore the full interactive Talk to the City archive, we highlight three of the most consistent cross-agency themes to emerge here:
Employment and workplace dynamics
Interagency and intra-agency communication, and
Contracting efficiency.
The first two, in particular, revealed dimensions of the implementation challenge that the interview questions alone might not have foregrounded — and that deserve attention from Congress, agency leadership, and anyone working to strengthen the operational capacity of the federal government.
The Workforce Behind the Work
The most voluminous cluster of responses across the entire archive concerned not legislation or programs but people — the federal employees who implement them. Participants consistently described a workplace ecosystem under strain: excessive bureaucratic processes around hiring, outdated assessment methods, rigid return-to-office mandates imposed without regard for mission needs, and a pervasive sense that the systems designed to manage the federal workforce were actively working against it.
This is not a new complaint. But the specificity and consistency with which it surfaced — across agencies, career stages, and policy domains — suggests something more than the usual frustrations of large-organization life. Participants described a workforce management apparatus that has not kept pace with either the nature of federal work or the expectations of the people doing it.
“VA federal hiring freeze created disruptions in hiring and onboarding new staff including critical clinical roles.”
“Every pay-raise or law required system changes... administrative leave changes... had a major impact on how things such as settlement agreements were processed.”
“A typical hiring process takes 6 months or more...few hiring managers are willing to persevere...[The] default is that hiring managers are only able to interview applicants that make the ‘HR cert’ based on the applicants’ own self-assessment...”
“There are today 120 pathways or hiring authorities in which somebody can become a federal employee [...] this proliferation of hiring.”
“I would require under this, like this to be under a statute, that agencies are required monthly to post on its public website, the hiring that they’ve done that month for which positions, as well as some basic demographic information...”
“Performance evaluations need to happen on the basis of performance, not of adherence to existing process. [...] The reason that adherence to existing process is not a good way to evaluate performance. It means that... that’s what counts rather than really improving things...”
“It would do a great deal for Federal employee morale if electeds would stop using them as political pawns.”
“But right now under this administration, they really want them to be staffed by politicals [...], that’s not going to garner trust within the workforce.”
“We need to redesign the way we structure that workforce, the way we hire, the way we supervise to address the trauma that current employees are experiencing.”
“The federal workforce has been damaged by the swift and dramatic personnel actions that took place in early 2025.”
“Do not treat public servants as interchangeable parts [...]. The government loses when it discards experienced public servants.”
“Listen to longtime career leaders, employees, and supervisors [...]. They are most likely there because they believe in the mission and want it to succeed.”
“Program resilience depends on institutionalizing better practices, not just good people.”
Several participants described leaving not because of pay or working conditions but because the agencies they served had, in their view, stopped adhering to the standards those agencies were created to uphold. When mission-driven employees leave because they believe the mission has been abandoned, the loss compounds — because these are precisely the people whose commitment and expertise are hardest to replace.
The analysis surfaced a strong consensus around the need for empathy in leadership, meaningful inclusion of employees in decision-making, and recognition that federal workers are motivated by purpose more than compensation. Participants were not asking for less accountability — they were asking for accountability structures that distinguish between compliance theater and genuine performance, and for leadership that understands the difference.
Breaking Down Silos: Communication Within and Between Agencies
The earlier sections of this paper focused primarily on the communication gap between Congress and the Executive branch — the broken feedback loops, the Legislative Affairs bottleneck, the program-level insights that never reach Capitol Hill. But the archive revealed that the communication problem runs deeper. Agencies are often siloed internally in ways that compound the external information gap.
The thematic analysis surfaced a clear pattern: siloed operations and bureaucratic hurdles within agencies hinder timely responses, adaptive policymaking, and effective service delivery. When divisions within the same agency operate on different timelines, with different data systems, and without structured mechanisms for coordination, the result is not just inefficiency — it is a degradation of the agency’s ability to fulfill its own mission.
“VBA and VHA were in two separate silos. Always 9 months or more out of sync and behind the 8 ball.”
“I was not allowed to send surveys to my colleagues because of the Paperwork Reduction Act... it was clear that our colleagues did not like the way it was going.”
“Well, if I could rebuild the department that I was involved in, OCED, in the beginning, I would have had NEPA in the room at the table. And if you had the correct people in the room in the beginning to design a process, an organization that made sense for what the goal was, and all of the different hoops, for lack of a better term, to jump through boxes you needed to check in order to achieve that goal, that just was never taken into consideration because the right people and experience and knowledge were not in the room.”
Participants consistently called for standardized metrics across agencies, better mechanisms for sharing lessons learned, and — perhaps most importantly — a culture that treats cross-agency coordination as a core competency rather than an afterthought. The absence of these structures means that when one agency solves a problem, the solution rarely travels to the agency next door facing the same challenge.
A Note on Contracting
The third thematic cluster — contracting efficiency — is addressed in earlier sections of this paper (particularly Sections V and VIII), but the thematic analysis underscored its scale and pervasiveness. Across the archive, participants described a procurement ecosystem where outdated regulations, excessive bureaucratic process, and poor coordination among multiple contractors actively work against the goals those contracts are meant to serve.
“Single audits should be conducted by audit firms hired and paid by the Federal government, so that they are accountable to the Federal government.”
“The whole [initiative I supported] should have been done by one contractor or an in-house team.”
The contracting theme reinforces a broader finding that runs through this entire report: systems designed for accountability and oversight have, over time, become systems that impede the very outcomes they were created to protect. The challenge for Congress is not to eliminate oversight but to modernize it — to build procurement frameworks that are flexible enough to adapt to changing needs, that incentivize in-house capacity where appropriate, and that hold contractors accountable to the government rather than the reverse.
These three cross-cutting themes — workforce dynamics, internal communication, and contracting — emerged organically from the data, cutting across the structured questions we asked and across agency boundaries. They represent the architecture of implementation: the people, the information flows, and the resource allocation structures that determine whether Congressional intent actually translates into effective programs. The interactive reports organize all of this material in explorable detail.
Conclusion
Across ten questions, three datasets, and hundreds of individual contributions, a set of patterns emerged with striking consistency.
The pacing problem is real and getting worse.
Legislative language written for one era is governing programs in another. Two-year political cycles cannot support ten-year development outcomes. Annual appropriations contradict multi-year programmatic goals. Statutory language assumes paper-based processes in a digital world. And the contracting structures meant to provide oversight are locking agencies into outdated technology rather than enabling them to keep pace with the missions Congress has assigned.
The feedback loops are broken.
The people with the most direct knowledge of how laws function in practice — program managers, frontline staff, technical experts — are the people with the least access to the legislative process. Legislative Affairs offices filter for presidential priorities. Reporting requirements generate compliance, not insight. Congressional hearings are structured around prepared testimony, not open-ended inquiry. And the pressures on legislative staff — small teams, compressed timelines, enormous portfolios — leave little room for the kind of sustained engagement with implementation reality that effective oversight requires.
The demand is real.
Participants did not need to be persuaded to share their knowledge. They came ready, specific, passionate, and constructive. The bottleneck was never willingness — it was infrastructure. The simple act of asking produced an outpouring of actionable intelligence that Congress could use tomorrow if it had the channels to receive it.
The Departure Dialogues project was made possible by a once-in-a-generation workforce disruption. The question now is how to ensure we are not waiting for the next extraordinary circumstance to solicit this kind of knowledge. Several directions deserve serious attention:
Standing mechanisms for implementation feedback.
Committees should consider building structured input processes into reauthorization cycles — creating regular, low-friction channels for program implementers to share what’s working and what isn’t before problems become entrenched.
Direct engagement with working-level staff.
Participants consistently asked for deeper, sustained engagement with mid-level technical experts — the people who have the most direct knowledge of what works and why, but who are rarely invited to share it with Congress directly. Structured listening sessions, operational site visits, and shadowing programs were among the specific models suggested.
Investment in Congress’s own analytical capacity.
AI-assisted analysis tools made this project viable for a small team with no dedicated research staff. Congressional offices and committees could leverage the same tools to process qualitative input at a scale that would have been impossible even a few years ago. Building that capacity is an investment in Congress’s ability to learn.
Reform of interbranch communication channels.
The Legislative Affairs bottleneck is structural, not personal. Creating alternative channels — ones that allow program-level insights to reach Congress without being filtered through political priorities — would require institutional innovation, but the need is clear and the participants in this project have articulated it with precision.
Support for communities of practice.
The network of participants that formed around this project — including new organizations like We the Doers — represents an ongoing resource for Congress and for the broader project of government effectiveness. Future implementations should design for community, not just contribution.
This paper has surfaced themes and highlighted voices. But there is far more richness in the interactive reports and the full archive of contributions than any summary can capture. We built this paper as a road map. The destination is the archive itself — the hundreds of specific, concrete, actionable observations from people who dedicated their careers to making government work, and who took the time to share what they learned.
We encourage you to explore it.
Acknowledgments
This project reflects a shared belief — across organizations that don’t always agree — that preserving institutional knowledge from departing federal employees is work that transcends any singular political moment. Capturing that knowledge and strengthening the feedback loop between the Executive branch and Congress requires a collaborative, nonpartisan effort, and we are grateful to the partners who brought that commitment to this work.
We are grateful to our coalition partners — the Partnership for Public Service, the Niskanen Center, the Foundation for American Innovation, and Civil Service Strong — for their early support, organizational expertise, dedication to a better federal government, and shared conviction that this moment called for new approaches to old problems.
The Departure Dialogues methodology depended on technology that made large-scale qualitative listening possible. The AI Objectives Institute and the Talk to the City (T3C) team brought both technical sophistication and genuine care for the integrity of participant voices to the work of synthesizing responses at scale. TheirStory provided the platform through which participants shared their experiences, offering an accessible and thoughtful interface for what was, for many contributors, a meaningful act of reflection.
Outreach for this project was only possible because organizations with deep roots in the federal workforce community opened their networks and lent their trust to this effort. We thank the Environmental Protection Network, the 18F alumni community, the American Federation of Government Employees (AFGE), the National Treasury Employees Union (NTEU), the National Association of Retired Federal Employees (NARFE), the Federal Legal Defense Fund, FedFam, Humans of Public Service, and WellFed for helping us reach the people whose voices are at the heart of this report.
We are grateful to the journalists who helped bring Departure Dialogues to a wider audience. Jason Briefel of FedManager was among the first to cover the project, and his early write-up helped us reach participants we might not otherwise have found. Sean Newhouse of Federal News Network provided thoughtful coverage of the project’s goals and methodology, and Terry Gerton of Federal Drive gave us the opportunity to share the work with the Federal Drive’s audience at a critical moment in our recruitment. Their interest in — and enthusiasm for — the work of departing federal employees made a real difference.
Above all, we are grateful to the federal employees who took the time to participate. This project exists because of them.
