How to Lead with Clarity
You know that feeling when your team seems to be working hard but nothing's really moving forward? When you're in back-to-back meetings, answering a million questions, and people still seem confused about what they're supposed to be doing?
Yeah, I know that feeling too!
After years of coaching leaders and working in organizations across industries, I've noticed a pattern. When teams are struggling, it's almost never because people aren't trying hard enough or don't care about the work. But that’s one of the first excuses that pops into a leaders mind.
Rather, these issues happen because they're missing one simple thing: clarity.
The problem? Clarity isn't just one thing. You can't just send a clear email and call it a day. Your team needs clarity in the right places to actually move the needle.
That's where the Get a GRIP™ framework comes in.
What is Get a GRIP™?
Get a GRIP™ is a framework I use with leaders to diagnose where their team is stuck and what kind of clarity they actually need. It stands for:
Goals – What are we trying to achieve?
Roles – Who's doing what?
Implementation – How do we get the work done?
People – How do we work together?
Think of these as the four layers of clarity. They build on each other, starting with the foundation of goals. When Goals and Roles are solid, everything else becomes easier. When Implementation and People are aligned, that's when you get real momentum.
But there is a hierarchy to this model. We don’t start with People, we end there. Let me break down each one.
Goals: What Are We Actually Trying to Achieve?
This one seems obvious, right? But here's what I see all the time: teams that have a vague sense of "we need to grow revenue" or "we're launching this product" without really understanding what success looks like or why it matters.
When you have tension in a meeting and can't figure things out, you actually need to take a step back and ask: what are we trying to achieve here and why? A lot of times we've lost sight of that along the way.
Your team needs clarity on:
What are we trying to achieve?
Why is this important?
What does success look like?
What are our priorities?
Without this clarity, people make assumptions. They prioritize the wrong work. They spend three weeks building something that wasn't actually what you needed. Or worse, different teams define success differently and end up working against each other.
Rather, when your team knows what you're trying to achieve, why it matters, and how you're measuring success, you don't need to micromanage them. They know you're heading to Grandmother's house. They know Grandmother's house is north. As a leader, you can let go and say, "Take whatever path you want, as long as you're at Grandma's house by Tuesday with that basket of chocolate chip cookies."
The test: Can every person on your team explain the goal in their own words and tell you why it matters? If not, you've got a Goals problem.
Roles: Who's Doing What?
Once you've clarified goals, you can tackle roles. This is where infighting or turf wars usually stems from, a lack of clarity around who needs to be involved and what each person's responsibility is.
Clarity on roles means people know:
Who's supposed to be doing what?
Who's responsible vs. accountable? (Think RACI chart)
What's each person's role in decision-making?
Who has actual decision-making authority?
You want to pay attention to the gaps, where nobody's taking ownership, and the overlap, where egos and friction can creep in.
This is also where you define what work you as the leader should be doing versus what your team should be doing. As leaders, especially when we've gotten promoted because we were so good at “the doing”, we need to do less doing and more enabling. You need to pass work on to your team. How do you set them up for success so they deliver what you have in mind? That goes back to goals.
The test: If I asked your team "who's responsible for X," would everyone give me the same answer? If there's confusion or finger-pointing when something doesn't get done, you've got a Roles problem.
Implementation: How Do We Get the Work Done?
Here's where things get specific. Once you're aligned on goals and roles, the biggest tension points start to recede. You can actually have true collaboration and momentum. This is where you've empowered your team to do their work without micromanaging. This is where you've freed up time for more strategic thinking.
Implementation is about the mechanics of how you work together. This is where the specifics of your company, department, and roles come into play:
How and when should decisions be made?
How are we going to communicate within the team and between teams?
What data do we need to collect so we can make decisions later?
What are the specific procedures, processes, and systems needed here?
How do we monitor progress?
All of this needs to be clear so you can work well, especially when you're working cross-functionally with other teams. When you aren't clear on implementation, it feels like a tug-of-war.
The test: Does your team feel coordinated or chaotic? If meetings feel like battles over process or you're constantly asking "wait, how are we doing this again?" then that's an Implementation problem.
People: How Do We Work Together?
Here's the thing: you can have crystal clear goals, perfectly defined roles, and solid implementation plans, and still have challenges. If you've tackled the first three layers and there's still friction, it might actually be about different people and personalities.
This is where you focus on:
Different communication styles
How information is processed differently
Differences in cultures, habits, and norms
Think Myers-Briggs. Think about when you have a sensing, details person talking to a big picture person. Or when you have a thinking person making decisions with a feeling person. These differences matter.
This is where DEI comes in too. What are people bringing with them? How are different cultures being perceived? How do you navigate all that?
The test: Are conflicts actually about the work, or are they about personality clashes and different working styles? That's a People problem.
When to Use This Framework
Here's the practical part. There are multiple situations when you can use this framework, but let’s talk about two common scenarios:
1. When kicking off new projects: Before you jump into the work, have one meeting with everyone involved. Walk through the framework:
Goals: Here's what we're trying to achieve, here's the problem we're solving, here's how we define success
Roles: Do a RACI chart or version of it—who's playing what role, who has decision-making authority over what
Implementation: When are we meeting? When will we review? How often should we check in?
People: Let me tell you how I like to work. This is how I communicate, how I like to be given feedback. Rather than making assumptions about my personality, let me just tell you what you'll find when you work with me.
I know you're thinking, "I don't have time for this, I just need to get started." This IS the most important work. Take one pause, one meeting, to do this. It will make everything easier.
2. When diagnosing conflict: When there's tension, things are falling apart, and you can't figure out what's wrong, go back to GRIP:
What are we trying to achieve here? Let's go back to basics.
What's everyone's role? Seems like there's a lack of clarity on who's supposed to be doing this piece.
How are we getting this done? Are we aligned on the process?
Is this actually a people issue?
This is how you diagnose conflict and get to the real root cause instead of just treating symptoms.
The Aha Moment
Here's what I want you to walk away with: when your team is struggling, it's almost never because people don't care or aren't trying hard enough. It's because they're missing clarity in one of these four areas.
The beauty of this framework is that it gives you a diagnosis tool. You don't have to guess where the breakdown is happening. You can systematically work through Goals, Roles, Implementation, and People to figure out exactly where you need to focus your energy.
And here's the real power move: when you start with goals and roles, when you nail those two foundational layers, everything else gets easier. Your team knows what they're working toward and who's responsible for what. That's when you stop micromanaging. That's when you free up time for strategic work. That's when your team can actually operate independently and make decisions without coming to you for everything.
So the next time you're feeling like your team is spinning its wheels, ask yourself: do we have a GRIP on this?
If the answer is no, you know exactly where to start.
