Use an organizational scorecard to predict the future

Today’s post is simple – please help the victims and communities affected by the devastating flooding in Texas over the Fourth of July weekend. As of this post, the death toll is now over 80 people, and 10 young campers remain missing.

You can donate here.

Every dollar helps.

I remember in college when I was a state officer for DECA. We had to generate a fifth-of-the-month report (FOMR) for our coach outlining the projects, wins, and challenges we worked through that month.

I hated them.

Then I got into the professional world and had to do more reports – some internal, some client-facing.

I still hated them.

I get it – writing a report is a big lift. Whether it’s weekly, monthly, or quarterly, they not only can take a lot of time to complete but there is always the fear of leaving something out or getting called out for something you include.

Despite their reputation, I am a big believer in weekly reports. They can be a powerful thing if done well. But most of the time they’re not. They become a formality or a Friday afternoon chore. A waste of time. The problem? No one ever explains why they’re important, or what a good one looks like. They should be seen as an opportunity to tell the story of the week.

Here’s how I approach weekly reports as a manager:

• They’re not a task list. They should tell the story of the week: progress, wins, challenges, and lessons learned. If it was a great week, the report should clearly communicate why. If it was a bad week… same thing.
• Provide a guide: If you want to avoid reports being phoned in, set clear expectations for what reports should communicate. I literally created a “good report / bad report” side-by-side comparison for my team when I noticed a pattern of unhelpful reports, and it worked.
• Good reports create better one-on-ones. The weekly report should be your pre-read for check-ins. That way, they can focus on coaching, providing context, working through challenges, and professional development – not just a project status that can be communicated another way.

When done correctly, weekly reports help leaders stay connected to what’s really happening on the team and help employees feel seen, supported, and celebrated.

Oh, by the way, managers: make sure you actually read them 😉

That $5 donor can become one of your biggest donors.

That new follower can become your future business partner.

The shy intern may run the organization one day.

I’ve been amazed in my career at what the small moments can turn into with some cultivation and patience.

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?

For the first five years, our organization operated without written values.

At first, it didn’t seem to matter. We were small, close-knit, and aligned by instinct. But as we grew, the cracks began to show. Departments started working in silos, communication broke down, turnover climbed, and morale slipped.

Our culture wasn’t toxic; it was just undefined. In many ways, it was accidental instead of intentional.

That tension finally pushed us to sit down as a team and define who we wanted to be, and how we wanted to work together.

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.