Clarity comes from systems

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 😉

Neither is your organization. I know that’s really hard to hear or accept.

You’re not so unique that the basics of leadership, systems, and clarity don’t apply to you.

You’re not so unique that you just happen to attract bad hires. Maybe you have weak management.

You’re not so unique that setting clear goals, building a healthy culture, and creating clarity somehow aren’t “your thing.”

Saying you’re unique is convenient. It’s a way to avoid change, sidestep responsibility, and ignore the hard truths every other leader eventually has to face.

The good news is, you’re not alone. But you’re not exempt either.

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.

Ever look up a recipe and find a short novel before the recipe itself?

Or maybe you received an email from someone, and after three paragraphs, you still don’t know what they want.

Maybe it’s a report or memo that buries the top line info in fluff and filler.

One of the best ways to get a response, earn respect, and win is by getting to the point.

It doesn’t mean being cold – you’re still a human communicating with another human, so respect is a must. It means being concise and clear.

Say what you mean and say it early.

Sometimes, “building the plane while you fly it” is unavoidable. You just have to take off, move fast, and figure it out on the way.

But here’s the real question: Are you building the plane with duct tape or rivets?

Too often, “building the plane as we fly it” becomes an excuse to cut corners. “Just get it done. We’ll fix it later.” But later rarely comes and temporary becomes permanent. And you’re left flying a patched-together machine at 30,000 feet.

Yes, getting thrown in the deep end can be a great way to grow. But what if you used the chaos to take a beat and build something that lasts?

Even in the rush, you usually have a choice.

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.