Get to the point

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.

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?

There’s probably something big you’re avoiding right now.

I’ve been there too: Staying in a job I no longer liked because starting a new one felt like a pain in the ass. Keeping a toxic employee around because I didn’t want to have the awkward 20-minute conversation to let them go. Waiting until the last minute to start a big project because I didn’t know how to get started.

In Traction, Gino Wickman calls this the “36 hours of pain.” He tells the story of a manager who knew one of his longtime employees was no longer the right fit for the role as the company grew. The thought of letting them go was agonizing. But after the 36 hours leading up to the termination, once he finally did it, the work environment changed overnight. His team even thanked him for making the tough decision.

We trade long-term peace for short-term comfort all the time. Over time, these constant tradeoffs deteriorate our motivation, mental state, confidence, and even our physical health.

A tough moment today – a decision, a conversation, a confrontation with reality – can save you from months or years of frustration.

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.

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 😉

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.