Gaining consensus in a large government agency can be harder than building the product itself. The IRS Direct File team smartly launched their e-filing system to IRS employees first, using the product as a tool to build internal support before a public rollout.

True innovation requires leaders to adopt a venture capital mindset, accepting that roughly nine out of ten initiatives will fail. This high tolerance for failure, mirroring professional investment odds, is a prerequisite for the psychological safety needed for breakthrough results.

Projects fail not from lack of tools, but from a lack of executive sponsorship. Success hinges on leaders dedicating significant weekly time (e.g., half a day) to a few key projects, rather than passively sponsoring many with monthly check-ins. This deep engagement is a primary driver of success.

Treat government programs as experiments. Define success metrics upfront and set a firm deadline. If the program fails to achieve its stated goals by that date, it should be automatically disbanded rather than being given more funding. This enforces accountability.

In siloed government environments, pushing for change fails. The effective strategy is to involve agency leaders directly in the process. By presenting data, establishing a common goal (serving the citizen), and giving them a voice in what gets built, they transition from roadblocks to champions.

When executing a large-scale government technology project, physically separating the technology team (e.g., in Bangalore) from the political and bureaucratic hub (e.g., in Delhi) is a crucial tactic. This creates a shield, allowing engineers to focus on deep work without constant interference.

In a high-agency environment, action trumps bureaucracy. Instead of asking for permission via a proposal, building a functional prototype demonstrates initiative and delivers immediate value, short-circuiting endless meetings and discussions.

A pilot program for a new product or service that runs perfectly is a failure because it has not uncovered the real-world vulnerabilities that need fixing before a full-scale launch. The goal of a pilot should be to actively seek out and document these "intelligent failures" to ensure the final launch is a success.

Owning a project launch means being accountable for its success, requiring more than execution. It involves proactively identifying all possible failure modes (technical, infrastructural, etc.) and systematically working backward to prevent them. This active risk mitigation is the essence of strong ownership.