Project Strategy
The Tradeoff Between Speed and Structure in Government Projects
Government projects don’t usually fail because they move too fast. They fail because structure either shows up too late… or never gets out of the way. The real challenge isn’t speed vs structure, it’s knowing when each one matters.
Systems Over Effort
The Reality: “Work smarter, not harder” is not just a saying. It’s a requirement. Effort alone does not scale. It might work in the short term, but over time it breaks down. The more something depends on manual steps, memory, or repeated effort, the more likely it is to fail.
Where People Get It Wrong: Too many people rely on effort instead of building systems. This shows up everywhere, especially in government. Teams would rather reinvent the wheel each time than invest in building a process that improves over time. The problem is not capability. It’s a reluctance to do the upfront work required to create something sustainable.
How Effort Fails: Manual processes often work at first because they are new and manageable. Over time, they become difficult to maintain. Steps get skipped, information becomes outdated, and consistency disappears. What started as a workable solution turns into friction. Manual processes don’t fail immediately. They fail quietly over time.
How Systems Win: A system is a consolidated group of tools and processes designed to produce consistent results. Systems remove the need to remember, reduce the number of decisions required, and create reliability over time. If something has more than a couple of manual steps or needs to be repeated, it should be systematized.
Real-World Application: Intranet System: The previous government intranet was manual, unused, and quickly became stale. By implementing a CMS with governance tracking, users are now presented with relevant, up-to-date information when they need it. Usage increased because the system supports the user instead of relying on them. External Website System: The prior external site was outdated and difficult to maintain. The new system uses a CMS, governance processes, and modern code standards. Content is easier to manage, stays current, and provides a better experience for the public. The system improved both internal workflows and external outcomes.
Why People Avoid Systems: Building systems requires upfront effort. Planning, designing, and refining takes time, and many people see that as a delay. In reality, that investment reduces effort over the life of the system. Skipping this step leads to more work, not less.
What Breaks Systems: Systems fail when they are not maintained or properly documented. Without clear documentation, consistency is lost. Without maintenance, systems degrade and eventually return to manual effort.
The Bottom Line: Effort works when it is supported by planning and structure. Systems become necessary when there are repeated steps, dependencies, or complexity. You don’t rise to your effort. You fall to your systems.