The (dreaded) weekly report

Every organization lives with the risk of someone being “hit by a bus.”

What happens if your development director, programs manager, or events coordinator suddenly disappears? For most orgs, the answer is chaos.

That’s because critical processes live in someone’s head, not in a shared place. There isn’t a playbook, a checklist, or documentation in sight.

A lack of process documentation isn’t just a risk for the worst-case scenarios, but also for common ones: someone quits, goes on leave, or changes roles. In those moments, you can be stuck scrambling to piece together how things worked, falling behind for months.

People leaving the organization is inevitable. It’s sad when they’re someone who does so much, but it doesn’t have to be devastating if you document the process.

Some tips for process documentation:

• Start with the recurring tasks: Anything that happens monthly, quarterly, or annually – think reports, events, renewals, or donor touchpoints efforts – is worth documenting.
• Use a format that fits: Paragraphs of text about how something is done is rarely the best approach. Whether it’s a checklist, timeline, screen recording, flowchart, or simple bullets, make the format fit the process.
• Record the who, what, and when: Ownership and timelines around each step are just as important as the step itself. Who do you work with to do that thing? When does it happen? Capture those details.
• Perfection isn’t the goal: When you start documenting, don’t focus on making it perfect – it can be messy and a little incomplete. Get a draft, then refine it over time.
• Store it somewhere central: For most process-related info, my org uses Confluence as a “wiki,” but any platform works as long as everyone has access and knows where to find it.
• Update regularly: Processes change from time to time. Set a reminder to take a look at your process documentation and update them as needed.

The biggest crisis facing young Americans today is a lack of purpose. They wander through life weighed down by hopelessness, convinced the future isn’t worth fighting for. They can’t afford basic necessities because of rising costs and stagnant wages. They’re told they’ll never have homes. Marriage and kids are, for many, out of the realm of possibilities. And to make it all worse, the climate doomers say they won’t have a future because climate change will suffocate us all.

The emptiness many young people feel today is profound, and originates from multiple sources, but one especially stands out: climate doomerism, the belief humanity is on an unstoppable march toward destruction, has become a defining feature of our generation.

The story told to millions of young people is the planet is dying, the system is rigged, and the future is lost. When that message becomes the moral framework for a generation, what hope is there?

If you dive into books or articles on building great organizations, you’ll find no shortage of frameworks, models, or operating systems. I’ve studied and used pieces of nearly all of them for about a decade now. But none quite fit the kind of organizations I’ve worked in: organizations created to solve big problems and create lasting impact.

After a decade of leading organizations, I’ve come to learn that every healthy and effective organization is built upon four foundations – Impact, Talent, Operations, and Ownership. And when these foundations are built well, they allow every corner of the organization to fire on all cylinders.

The world doesn’t need another podcast. But this post isn’t really about podcasts. It’s about the pressure to jump on what other organizations are doing – a newsletter, a blog, an influencer program, a local ambassador program, you name it.

These things could very well advance your organization. But “because everyone else is doing it” is not a strategy. And for us, these were intentional add-ons that pay returns.

Start with the problem you’re trying to solve or a specific audience you’re trying to reach. Then ask: Is this the best tool for that job?

Over the last few months, we’ve implemented something new across our leadership team: an organizational scorecard. It’s a simple idea, but it’s already changing how we operate.

Each week, our department VPs and I review and update a simple matrix of the organization’s most important metrics – the drivers that tell us whether we’re on track or not. We look at things like membership growth, events, fundraising, employee happiness, and a few other criteria. Nothing too complicated. Just a single, living scorecard that we update every week and apply an “on track” or “off track” label.

The purpose of a scorecard isn’t to add more reporting. It’s to keep the most vital indicators front and center. When you track these weekly, you can effectively predict the future. You start to see problems before they happen.

I’ve sometimes seen a desire to throw $100,000 in salary and benefits at a “bandwidth problem” when it’s really just a prioritization problem.

Sometimes, hiring is absolutely the right decision. But sometimes, the better solution isn’t hiring, it’s doing fewer things better.

Before you hire, ask these questions:

• Are we trying to do too much? The instinct to say yes to everything creates artificial capacity problems. What if the issue isn’t a lack of people, but a lack of focus?
• Can we cut or pause lower-priority projects? Every initiative competes for attention. Which ones could you shelve without meaningfully impacting your core objectives?
• Are we clear on what actually created results? If you can’t identify your highest-impact activities, adding more people just increases the confusion.
• Could we streamline operations or automate some work first? Process improvements and automation often free up more bandwidth than a new hire, without the ongoing cost.

Hiring should be a strategic growth move, not a reflex to wrangle chaos. Sometimes the real answer isn’t adding people, it’s tightening focus.