Decoding “How Big Things Get Done”: Key Takeaways for Nonprofit Tech Projects

In the whirlwind of nonprofit technology projects, the ambition is often grand. We aim to implement systems that transform operations, scale impact, and ultimately, better serve our missions. But as many of us know, "big things" come with big challenges. That's why I've found invaluable insights in Bent Flyvbjerg's book, "How to Get Big Things Done." It's not specifically about tech, but its core tenets resonate deeply with the complexities we face in the nonprofit technology landscape.

I've recommended this book to many colleagues, and today, I want to share some key takeaways that can help us all navigate those ambitious "big things" in our nonprofit tech initiatives:

1. The Iron Law of Megaprojects: Beware of Optimism Bias.

Flyvbjerg highlights the "iron law" of megaprojects: they are over budget, over time, and under benefits over and over again. While our nonprofit tech projects might not be on the scale of the Olympics, we're certainly not immune to optimism bias. We might underestimate the time needed for data migration, the complexity of integrations, or the resistance to change. Flyvbjerg's work reminds us to be rigorously realistic about the cost, schedule and benefits.

2. Get Real About Reference Class Forecasting:

Instead of relying solely on internal estimates (which can be prone to bias), Flyvbjerg advocates for "reference class forecasting." This involves looking at the actual outcomes of similar projects to get a more realistic sense of potential timelines and costs. For nonprofits, this could mean researching the implementation timelines and budgets of similar organizations that have adopted the same CRM or launched a comparable digital platform.

3. Embrace the Power of "Slow Thinking":

In our fast-paced world, there's often pressure to rush into solutions. However, Flyvbjerg emphasizes the importance of "slow thinking" – taking the time for thorough analysis, careful planning, and robust stakeholder engagement. This is particularly crucial in the nonprofit sector, where understanding the nuances of organizational culture and user needs is paramount. Rushing can lead to costly mistakes and solutions that don't truly fit.

4. Focus on the "Why" (Again, but Deeper): Articulating Benefits and Engaging Stakeholders.

Flyvbjerg stresses the importance of clearly articulating the benefits of a "big thing" and engaging stakeholders throughout the process. For nonprofit tech projects, this means continuously communicating how the new system or platform will ultimately help the organization better serve its mission and its beneficiaries. When people understand the "why" and feel involved, they are more likely to support the project and contribute to its success.

5. Plan for the Unexpected: The Importance of Contingency and Flexibility.

"Big things" rarely go exactly as planned. Flyvbjerg's research underscores the need for robust contingency plans and a flexible approach. In the nonprofit tech world, this might mean having backup plans for data migration, allocating buffer time in the schedule, and being prepared to adapt to unforeseen challenges.

Applying Flyvbjerg's Wisdom to Our Missions:

While "How to Get Big Things Done" isn't a nonprofit tech manual, its principles offer profound insights for navigating our ambitious technology initiatives. By being aware of optimism bias, leveraging reference class data, prioritizing thoughtful planning, clearly articulating benefits, and building in flexibility, we can increase our chances of successfully delivering those "big things" that ultimately drive greater impact for our organizations and the communities we serve.

Ready to get your big thing done? Let’s chat! Contact Clearly Consulting for a no-pressure discussion about your project.