Groove Management

08/13/2026

A real Team Timeout gives a team space to get out of the day-to-day, look honestly at how they’re working together, reset what isn’t working, and build a shared experience they can actually use when they get back to work.

08/06/2026

07/28/2026

Facilitating vs leading. Is facilitating your hiding space?

07/21/2026

Have you ever asked an AI to review a document and had it simply reply, "This is good to go. No edits needed"?

Probably not.

AI models are people-pleasers. They are programmed to take action, meaning they will drag your team into an endless loop of minor redlines and synonym swaps if you let them. They can draft brilliantly, but they lack the human confidence and contextual awareness to know when a project is truly finished.

(Though, to be fair, my wife Brita is just as good at finding that one missing comma… maybe I’m married to a bot? 😉)

This isn't a technology flaw; it’s a leadership challenge. In my latest Groove Management blog post, I explore why defining the threshold for "good enough" is the new leadership imperative, and I share three specific prompts to get your AI to finally put the red pen down.

Read the full article here: https://www.groovemanagement.com/blog/ai-doesnt-know-when-to-say-done

06/11/2026

A risk surfaces. The leader takes it. Tension builds. The leader smooths it over. A ball drops. The leader picks it up before anyone names it.

Each move looks like ownership. Together they teach one lesson: wait.
The pattern feeds itself. The team waits, so the leader absorbs more. The leader absorbs more, so the team waits longer. From the inside it feels like being needed. From the outside it’s a team that stopped moving on its own.

It’s hard to catch because absorbing gets rewarded. It reads as care. Nobody tells a leader “you’re carrying too much.” They say thank you.

One thing to try: next time something drops in a meeting, leave it on the floor. Thirty seconds. See who reaches for it.

The leader is the last to see this pattern. The team saw it months ago.

04/16/2026

04/06/2026

𝗦𝘁𝗼𝗽 𝗺𝗮𝗸𝗶𝗻𝗴 𝘆𝗼𝘂𝗿 𝘁𝗲𝗮𝗺𝘀 𝘀𝘂𝗳𝗳𝗲𝗿 𝘁𝗵𝗿𝗼𝘂𝗴𝗵 "𝗳𝗼𝗿𝗰𝗲𝗱 𝗳𝘂𝗻." 🛑
At Groove Management, one of our core values is the Peter Pan Principle: we take our work seriously, but not ourselves. When we design Team Timeouts, the goal is never to force engagement. The goal is to earn it.

I just published a new article breaking down the secret to a successful executive offsite. It covers:
🔹 How to pivot when a room is dreading an agenda.
🔹 The real purpose behind team-building activities (hint: it's about trust and alignment, not just games).
🔹 Why the magic doesn't happen during the activity, but during the debrief.
Check out the full story and learn how to earn your team's trust, respect, and laughter at your next offsite: https://www.groovemanagement.com/blog/forced-fun

03/17/2026

At Groove, we usually think of management and leadership as distinct. Different skills, different mindsets, different outcomes.

It can be useful to question even our most familiar assumptions. So here is one worth testing: what if management and leadership are not separate categories? What if they two aspects of the same function operating inside the same team at the same time?

Management creates enough stability to execute: alignment, consistency, and predictable rhythm. Leadership helps a team recognize when its assumptions, structures, or priorities no longer fit and need to evolve.

Every team needs both. Over-stabilizing reduces adaptability. Pushing change without enough structure burns people out.

Once you stop treating management and leadership as separate categories and start seeing them as an ongoing tension, a different question emerges:
𝗪𝗵𝗲𝗿𝗲 𝗶𝘀 𝘁𝗵𝗲 𝗳𝗿𝗶𝗰𝘁𝗶𝗼𝗻 𝘆𝗼𝘂𝗿 𝘁𝗲𝗮𝗺 𝗸𝗲𝗲𝗽𝘀 𝘀𝗺𝗼𝗼𝘁𝗵𝗶𝗻𝗴 𝗼𝘃𝗲𝗿 𝘁𝗵𝗮𝘁 𝗺𝗶𝗴𝗵𝘁 𝗮𝗰𝘁𝘂𝗮𝗹𝗹𝘆 𝗯𝗲 𝘁𝗵𝗲 𝘀𝗶𝗴𝗻𝗮𝗹?

03/10/2026

𝗪𝗵𝗮𝘁 𝗬𝗼𝘂𝗿 𝟯𝟲𝟬 𝗙𝗲𝗲𝗱𝗯𝗮𝗰𝗸 𝗜𝘀𝗻’𝘁 𝗧𝗲𝗹𝗹𝗶𝗻𝗴 𝗬𝗼𝘂

360 feedback tells you how people experience you. It doesn’t tell you what’s producing that experience.

A leader scores low on “empowers the team.” The standard move is predictable: delegate more. Step back.

But sometimes the team doesn’t trust each other, decisions don’t hold, and the leader is acting as the glue. In that system, “empowerment” isn’t a behavior tweak. It’s a structural issue. Backing off doesn’t fix it. It exposes it.

Most 360s turn signals into to-dos. Low score → action item → behavior theater. It looks like growth while the underlying pattern stays intact.

Before you build a development plan, ask a better question:
𝗪𝗵𝗮𝘁 𝗽𝗿𝗼𝗯𝗹𝗲𝗺 𝗶𝘀 𝘁𝗵𝗶𝘀 𝗯𝗲𝗵𝗮𝘃𝗶𝗼𝗿 𝘀𝗼𝗹𝘃𝗶𝗻𝗴 𝗳𝗼𝗿 𝘁𝗵𝗲 𝘀𝘆𝘀𝘁𝗲𝗺?

A 360 tells you what the room sees. It doesn’t tell you what the room needs. #360