Your Bottleneck Scores

Primary Bottleneck Identified

What Your Answers Reveal About Your Patterns

Talk soon,

Mara Whitener

Your Bottleneck Scores

Primary Bottleneck Identified

What Your Answers Reveal About Your Patterns

Talk soon,

Mara Whitener

Your Bottleneck Scores

Primary Bottleneck Identified

What Your Answers Reveal About Your Patterns

Talk soon,

Mara Whitener

Your Bottleneck Scores

Primary Bottleneck Identified

What Your Answers Reveal About Your Patterns

Talk soon,

Mara Whitener

Your Bottleneck Scores

Primary Bottleneck Identified

What Your Answers Reveal About Your Patterns

Talk soon,

Mara Whitener

Your Bottleneck Scores

Primary Bottleneck Identified

What Your Answers Reveal About Your Patterns

Talk soon,

Mara Whitener

Your Bottleneck Scores

Primary Bottleneck Identified

What Your Answers Reveal About Your Patterns

Talk soon,

Mara Whitener

Your Bottleneck Scores

Primary Bottleneck Identified

What Your Answers Reveal About Your Patterns

Talk soon,

Mara Whitener

Your Bottleneck Scores

Primary Bottleneck Identified

What Your Answers Reveal About Your Patterns

Talk soon,

Mara Whitener

Your Bottleneck Scores

Primary Bottleneck Identified

What Your Answers Reveal About Your Patterns

Talk soon,

Mara Whitener

Your Bottleneck Scores

Primary Bottleneck Identified

What Your Answers Reveal About Your Patterns

Talk soon,

Mara Whitener

Your Bottleneck Scores

Primary Bottleneck Identified

Your Revenue Is Too Dependent On You

Revenue is strong, but it’s personally tied to your involvement. Whether it’s sales conversations, client retention, or problem resolution—the business hasn’t developed the capacity to deliver your level of experience without you.

This shows up as:

• Clients expecting to deal with you personally
• Sales stalling without your involvement
• Being the “fixer” when client issues arise
• Revenue opportunities waiting for your attention

The Pattern: You’ve probably built your reputation on personal excellence—and your clients love working with you. But that strength has become a constraint. The business can’t grow beyond your personal capacity to show up.

The Risk: This bottleneck directly limits your growth ceiling and your ability to step back. Every vacation, every sick day, every attempt to work ON the business instead of IN it… your revenue feels the impact.

What Your Answers Reveal About Your Patterns

Your Results Are Unusually Low

You indicated that things are working well across most areas—your team handles things, your systems work, decisions happen without you.

What This Might Mean:

• Option 1: You’ve genuinely built a business that runs well without you. If this is true—congratulations. That’s rare and valuable. Your bottleneck might be somewhere we didn’t measure, or you might be ready for a different kind of challenge entirely.
• Option 2: There’s a gap between perception and reality. Sometimes founders believe things are working better than they actually are. This isn’t about being delusional—it’s about not having visibility into what happens when you’re not watching.
• Option 3: You answered aspirationally. Some people answer these questions based on how they want things to work, or how they work on a good day, rather than what typically happens.

The Question For You: If your team could see your answers, would they agree with your assessment?

Talk soon,

Mara Whitener

Your Bottleneck Scores

Primary Bottleneck Identified

Your Systems Haven’t Scaled With You

You’ve grown, but your operational infrastructure hasn’t kept pace. Things that used to work when you were smaller are now creating friction, delays, and dependencies on you personally.

This shows up as:

• Work stalling when you’re unavailable
• Being the only one who knows how everything connects
• Handoffs that require your involvement to actually happen
• Quality inconsistency when you’re not watching

The Pattern: You’ve likely added people and tools, but the underlying operational architecture still assumes you’re at the center of everything. The business runs through you instead of around you.

The Good News: This is often the most straightforward bottleneck to address once you can see exactly where the gaps are. It’s about building infrastructure, not changing people.

What Your Answers Reveal About Your Patterns

You’re Struggling To Let Go

Your answers consistently reflected distrust of outcomes: “I’d worry about the result,” “They might mess it up,” “I’d probably need to fix it later.”

What This Means: Even when your team might be capable, you’re not fully trusting them to deliver. This pattern keeps you involved even when you don’t technically need to be—and it’s exhausting for both you and your team.

The Uncomfortable Truth: This pattern often has less to do with your team’s actual capability and more to do with:

• Your own standards feeling impossible to transfer
• Difficulty tolerating imperfection
• A part of you that needs to be needed
• Past experiences where letting go went badly

The Watch-Out: Teams can sense when they’re not trusted. Over time, this can become a self-fulfilling prophecy—capable people stop trying because they know you’ll step in anyway, or they leave for environments where they have real autonomy.

The Question For You: What would need to be true for you to actually trust someone else with this?

Talk soon,

Mara Whitener

Your Bottleneck Scores

Primary Bottleneck Identified

Your Systems Haven’t Scaled With You

You’ve grown, but your operational infrastructure hasn’t kept pace. Things that used to work when you were smaller are now creating friction, delays, and dependencies on you personally.

This shows up as:

• Work stalling when you’re unavailable
• Being the only one who knows how everything connects
• Handoffs that require your involvement to actually happen
• Quality inconsistency when you’re not watching

The Pattern: You’ve likely added people and tools, but the underlying operational architecture still assumes you’re at the center of everything. The business runs through you instead of around you.

The Good News: This is often the most straightforward bottleneck to address once you can see exactly where the gaps are. It’s about building infrastructure, not changing people.

What Your Answers Reveal About Your Patterns

Your Results Are Unusually Low

You indicated that things are working well across most areas—your team handles things, your systems work, decisions happen without you.

What This Might Mean:

• Option 1: You’ve genuinely built a business that runs well without you. If this is true—congratulations. That’s rare and valuable. Your bottleneck might be somewhere we didn’t measure, or you might be ready for a different kind of challenge entirely.
• Option 2: There’s a gap between perception and reality. Sometimes founders believe things are working better than they actually are. This isn’t about being delusional—it’s about not having visibility into what happens when you’re not watching.
• Option 3: You answered aspirationally. Some people answer these questions based on how they want things to work, or how they work on a good day, rather than what typically happens.

The Question For You: If your team could see your answers, would they agree with your assessment?

Talk soon,

Mara Whitener

Your Bottleneck Scores

Primary Bottleneck Identified

Your Systems Haven’t Scaled With You

You’ve grown, but your operational infrastructure hasn’t kept pace. Things that used to work when you were smaller are now creating friction, delays, and dependencies on you personally.

This shows up as:

• Work stalling when you’re unavailable
• Being the only one who knows how everything connects
• Handoffs that require your involvement to actually happen
• Quality inconsistency when you’re not watching

The Pattern: You’ve likely added people and tools, but the underlying operational architecture still assumes you’re at the center of everything. The business runs through you instead of around you.

The Good News: This is often the most straightforward bottleneck to address once you can see exactly where the gaps are. It’s about building infrastructure, not changing people.

What Your Answers Reveal About Your Patterns

You See This As Your Gap To Fix

Your answers consistently reflected ownership: “I haven’t set this up well enough,” “I haven’t created the clarity they need,” “I haven’t built the infrastructure.”

What This Means: You tend to take responsibility for the bottleneck rather than blaming your team. This is actually a strength—it means you’re coachable, self-aware, and likely ready to do the work required to change things.

The Watch-Out: Sometimes founders with this pattern take too much ownership. They assume everything is their fault when sometimes the real issue is having the wrong people, or trying to build something that can’t be built with current resources.

The Question For You: Is the bottleneck really just about infrastructure and clarity you haven’t built? Or are there other factors—team capability, trust issues, or your own resistance to letting go—that are also at play?

Talk soon,

Mara Whitener

Your Bottleneck Scores

Primary Bottleneck Identified

You’re The Only One Thinking Strategically

Your team can execute, but they’re waiting for you to set direction, make decisions, and evaluate opportunities. Every strategic move requires your involvement, which means growth only happens at the pace you can personally drive it.

This shows up as:

• Projects pausing when they need direction and you’re unavailable
• Your team deferring decisions to you even when they could decide
• Opportunities waiting for your evaluation
• Growth feeling directly tied to your personal bandwidth

The Pattern: You’ve built a team that can follow instructions well, but they haven’t developed—or been empowered to develop—strategic thinking of their own. The vision lives in your head, and they’re dependent on you to translate it.

The Question: Is this because you haven’t communicated your vision clearly enough? Or because you haven’t trusted them to interpret it? Or because you actually enjoy being the strategic brain? The answer matters for what comes next.

What Your Answers Reveal About Your Patterns

You’re Questioning Your Team’s Capability

Your answers consistently reflected doubt about your team: “They can’t handle this,” “They don’t have the judgment,” “They won’t step up without me.”

What This Means: You’re not confident your team can operate without you—whether that’s about skill, judgment, motivation, or all three. This might be accurate. Or it might be a story you’re telling yourself.

The Real Question: Do you have a team problem or a trust problem? Sometimes it’s both. But they require very different solutions.

• If it’s a team problem: You may need different people, better training, or clearer role definitions
• If it’s a trust problem: Your team may be more capable than you’re giving them credit for

The Watch-Out: Founders who consistently blame team capability sometimes struggle to see their own role in creating that dynamic. Have you given them real authority? Clear expectations? Room to fail and learn?

Talk soon,

Mara Whitener

Your Bottleneck Scores

Primary Bottleneck Identified

Your Revenue Is Too Dependent On You

Revenue is strong, but it’s personally tied to your involvement. Whether it’s sales conversations, client retention, or problem resolution—the business hasn’t developed the capacity to deliver your level of experience without you.

This shows up as:

• Clients expecting to deal with you personally
• Sales stalling without your involvement
• Being the “fixer” when client issues arise
• Revenue opportunities waiting for your attention

The Pattern: You’ve probably built your reputation on personal excellence—and your clients love working with you. But that strength has become a constraint. The business can’t grow beyond your personal capacity to show up.

The Risk: This bottleneck directly limits your growth ceiling and your ability to step back. Every vacation, every sick day, every attempt to work ON the business instead of IN it… your revenue feels the impact.

What Your Answers Reveal About Your Patterns

You’re Questioning Your Team’s Capability

Your answers consistently reflected doubt about your team: “They can’t handle this,” “They don’t have the judgment,” “They won’t step up without me.”

What This Means: You’re not confident your team can operate without you—whether that’s about skill, judgment, motivation, or all three. This might be accurate. Or it might be a story you’re telling yourself.

The Real Question: Do you have a team problem or a trust problem? Sometimes it’s both. But they require very different solutions.

• If it’s a team problem: You may need different people, better training, or clearer role definitions
• If it’s a trust problem: Your team may be more capable than you’re giving them credit for

The Watch-Out: Founders who consistently blame team capability sometimes struggle to see their own role in creating that dynamic. Have you given them real authority? Clear expectations? Room to fail and learn?

Talk soon,

Mara Whitener

Your Bottleneck Scores

Primary Bottleneck Identified

Your Systems Haven’t Scaled With You

You’ve grown, but your operational infrastructure hasn’t kept pace. Things that used to work when you were smaller are now creating friction, delays, and dependencies on you personally.

This shows up as:

• Work stalling when you’re unavailable
• Being the only one who knows how everything connects
• Handoffs that require your involvement to actually happen
• Quality inconsistency when you’re not watching

The Pattern: You’ve likely added people and tools, but the underlying operational architecture still assumes you’re at the center of everything. The business runs through you instead of around you.

The Good News: This is often the most straightforward bottleneck to address once you can see exactly where the gaps are. It’s about building infrastructure, not changing people.

What Your Answers Reveal About Your Patterns

You See This As Your Gap To Fix

Your answers consistently reflected ownership: “I haven’t set this up well enough,” “I haven’t created the clarity they need,” “I haven’t built the infrastructure.”

What This Means: You tend to take responsibility for the bottleneck rather than blaming your team. This is actually a strength—it means you’re coachable, self-aware, and likely ready to do the work required to change things.

The Watch-Out: Sometimes founders with this pattern take too much ownership. They assume everything is their fault when sometimes the real issue is having the wrong people, or trying to build something that can’t be built with current resources.

The Question For You: Is the bottleneck really just about infrastructure and clarity you haven’t built? Or are there other factors—team capability, trust issues, or your own resistance to letting go—that are also at play?

Talk soon,

Mara Whitener

Your Bottleneck Scores

Primary Bottleneck Identified

Your Systems Haven’t Scaled With You

You’ve grown, but your operational infrastructure hasn’t kept pace. Things that used to work when you were smaller are now creating friction, delays, and dependencies on you personally.

This shows up as:

• Work stalling when you’re unavailable
• Being the only one who knows how everything connects
• Handoffs that require your involvement to actually happen
• Quality inconsistency when you’re not watching

The Pattern: You’ve likely added people and tools, but the underlying operational architecture still assumes you’re at the center of everything. The business runs through you instead of around you.

The Good News: This is often the most straightforward bottleneck to address once you can see exactly where the gaps are. It’s about building infrastructure, not changing people.

What Your Answers Reveal About Your Patterns

You See This As Your Gap To Fix

Your answers consistently reflected ownership: “I haven’t set this up well enough,” “I haven’t created the clarity they need,” “I haven’t built the infrastructure.”

What This Means: You tend to take responsibility for the bottleneck rather than blaming your team. This is actually a strength—it means you’re coachable, self-aware, and likely ready to do the work required to change things.

The Watch-Out: Sometimes founders with this pattern take too much ownership. They assume everything is their fault when sometimes the real issue is having the wrong people, or trying to build something that can’t be built with current resources.

The Question For You: Is the bottleneck really just about infrastructure and clarity you haven’t built? Or are there other factors—team capability, trust issues, or your own resistance to letting go—that are also at play?

Talk soon,

Mara Whitener

Your Bottleneck Scores

Primary Bottleneck Identified

Your Systems Haven’t Scaled With You

You’ve grown, but your operational infrastructure hasn’t kept pace. Things that used to work when you were smaller are now creating friction, delays, and dependencies on you personally.

This shows up as:

• Work stalling when you’re unavailable
• Being the only one who knows how everything connects
• Handoffs that require your involvement to actually happen
• Quality inconsistency when you’re not watching

The Pattern: You’ve likely added people and tools, but the underlying operational architecture still assumes you’re at the center of everything. The business runs through you instead of around you.

The Good News: This is often the most straightforward bottleneck to address once you can see exactly where the gaps are. It’s about building infrastructure, not changing people.

What Your Answers Reveal About Your Patterns

Your Results Are Unusually Low

You indicated that things are working well across most areas—your team handles things, your systems work, decisions happen without you.

What This Might Mean:

• Option 1: You’ve genuinely built a business that runs well without you. If this is true—congratulations. That’s rare and valuable. Your bottleneck might be somewhere we didn’t measure, or you might be ready for a different kind of challenge entirely.
• Option 2: There’s a gap between perception and reality. Sometimes founders believe things are working better than they actually are. This isn’t about being delusional—it’s about not having visibility into what happens when you’re not watching.
• Option 3: You answered aspirationally. Some people answer these questions based on how they want things to work, or how they work on a good day, rather than what typically happens.

The Question For You: If your team could see your answers, would they agree with your assessment?

Talk soon,

Mara Whitener

Your Bottleneck Scores

Primary Bottleneck Identified

Your Team Isn’t Fully Stepping Up

You have people, but they’re not operating as empowered leaders. Whether it’s decision-making, conflict resolution, or self-direction—there’s a gap between the team you have and the team you need.

This shows up as:

• Team members waiting for your input instead of acting
• Conflicts or issues festering until you address them
• Productivity dropping when you’re not present
• Decisions defaulting to you even when they shouldn’t

The Pattern: This is often the most complex bottleneck because it’s not just about systems or processes—it’s about people. And the root cause isn’t always obvious. It could be:

• A hiring issue: You don’t have the right people
• A development issue: You haven’t grown them into the roles you need
• A trust issue: They’re more capable than you’re allowing them to be
• A clarity issue: They don’t know what “stepping up” actually looks like

The Truth: Most founders with this bottleneck have some combination of all four. Untangling which is which—and in what proportion—is where real progress starts.

What Your Answers Reveal About Your Patterns

You’re Questioning Your Team’s Capability

Your answers consistently reflected doubt about your team: “They can’t handle this,” “They don’t have the judgment,” “They won’t step up without me.”

What This Means: You’re not confident your team can operate without you—whether that’s about skill, judgment, motivation, or all three. This might be accurate. Or it might be a story you’re telling yourself.

The Real Question: Do you have a team problem or a trust problem? Sometimes it’s both. But they require very different solutions.

• If it’s a team problem: You may need different people, better training, or clearer role definitions
• If it’s a trust problem: Your team may be more capable than you’re giving them credit for

The Watch-Out: Founders who consistently blame team capability sometimes struggle to see their own role in creating that dynamic. Have you given them real authority? Clear expectations? Room to fail and learn?

Talk soon,

Mara Whitener

Your Bottleneck Scores

Primary Bottleneck Identified

Your Team Isn’t Fully Stepping Up

You have people, but they’re not operating as empowered leaders. Whether it’s decision-making, conflict resolution, or self-direction—there’s a gap between the team you have and the team you need.

This shows up as:

• Team members waiting for your input instead of acting
• Conflicts or issues festering until you address them
• Productivity dropping when you’re not present
• Decisions defaulting to you even when they shouldn’t

The Pattern: This is often the most complex bottleneck because it’s not just about systems or processes—it’s about people. And the root cause isn’t always obvious. It could be:

• A hiring issue: You don’t have the right people
• A development issue: You haven’t grown them into the roles you need
• A trust issue: They’re more capable than you’re allowing them to be
• A clarity issue: They don’t know what “stepping up” actually looks like

The Truth: Most founders with this bottleneck have some combination of all four. Untangling which is which—and in what proportion—is where real progress starts.

What Your Answers Reveal About Your Patterns

Your Results Are Unusually Low

You indicated that things are working well across most areas—your team handles things, your systems work, decisions happen without you.

What This Might Mean:

• Option 1: You’ve genuinely built a business that runs well without you. If this is true—congratulations. That’s rare and valuable. Your bottleneck might be somewhere we didn’t measure, or you might be ready for a different kind of challenge entirely.
• Option 2: There’s a gap between perception and reality. Sometimes founders believe things are working better than they actually are. This isn’t about being delusional—it’s about not having visibility into what happens when you’re not watching.
• Option 3: You answered aspirationally. Some people answer these questions based on how they want things to work, or how they work on a good day, rather than what typically happens.

The Question For You: If your team could see your answers, would they agree with your assessment?

Talk soon,

Mara Whitener

Your Bottleneck Scores

Primary Bottleneck Identified

Your Systems Haven’t Scaled With You

You’ve grown, but your operational infrastructure hasn’t kept pace. Things that used to work when you were smaller are now creating friction, delays, and dependencies on you personally.

This shows up as:

• Work stalling when you’re unavailable
• Being the only one who knows how everything connects
• Handoffs that require your involvement to actually happen
• Quality inconsistency when you’re not watching

The Pattern: You’ve likely added people and tools, but the underlying operational architecture still assumes you’re at the center of everything. The business runs through you instead of around you.

The Good News: This is often the most straightforward bottleneck to address once you can see exactly where the gaps are. It’s about building infrastructure, not changing people.

What Your Answers Reveal About Your Patterns

You See This As Your Gap To Fix

Your answers consistently reflected ownership: “I haven’t set this up well enough,” “I haven’t created the clarity they need,” “I haven’t built the infrastructure.”

What This Means: You tend to take responsibility for the bottleneck rather than blaming your team. This is actually a strength—it means you’re coachable, self-aware, and likely ready to do the work required to change things.

The Watch-Out: Sometimes founders with this pattern take too much ownership. They assume everything is their fault when sometimes the real issue is having the wrong people, or trying to build something that can’t be built with current resources.

The Question For You: Is the bottleneck really just about infrastructure and clarity you haven’t built? Or are there other factors—team capability, trust issues, or your own resistance to letting go—that are also at play?

Talk soon,

Mara Whitener

Your Bottleneck Scores

Primary Bottleneck Identified

Your Systems Haven’t Scaled With You

You’ve grown, but your operational infrastructure hasn’t kept pace. Things that used to work when you were smaller are now creating friction, delays, and dependencies on you personally.

This shows up as:

• Work stalling when you’re unavailable
• Being the only one who knows how everything connects
• Handoffs that require your involvement to actually happen
• Quality inconsistency when you’re not watching

The Pattern: You’ve likely added people and tools, but the underlying operational architecture still assumes you’re at the center of everything. The business runs through you instead of around you.

The Good News: This is often the most straightforward bottleneck to address once you can see exactly where the gaps are. It’s about building infrastructure, not changing people.

What Your Answers Reveal About Your Patterns

You See This As Your Gap To Fix

Your answers consistently reflected ownership: “I haven’t set this up well enough,” “I haven’t created the clarity they need,” “I haven’t built the infrastructure.”

What This Means: You tend to take responsibility for the bottleneck rather than blaming your team. This is actually a strength—it means you’re coachable, self-aware, and likely ready to do the work required to change things.

The Watch-Out: Sometimes founders with this pattern take too much ownership. They assume everything is their fault when sometimes the real issue is having the wrong people, or trying to build something that can’t be built with current resources.

The Question For You: Is the bottleneck really just about infrastructure and clarity you haven’t built? Or are there other factors—team capability, trust issues, or your own resistance to letting go—that are also at play?

Talk soon,

Mara Whitener

Your Bottleneck Scores

Primary Bottleneck Identified

You’re The Only One Thinking Strategically

Your team can execute, but they’re waiting for you to set direction, make decisions, and evaluate opportunities. Every strategic move requires your involvement, which means growth only happens at the pace you can personally drive it.

This shows up as:

• Projects pausing when they need direction and you’re unavailable
• Your team deferring decisions to you even when they could decide
• Opportunities waiting for your evaluation
• Growth feeling directly tied to your personal bandwidth

The Pattern: You’ve built a team that can follow instructions well, but they haven’t developed—or been empowered to develop—strategic thinking of their own. The vision lives in your head, and they’re dependent on you to translate it.

The Question: Is this because you haven’t communicated your vision clearly enough? Or because you haven’t trusted them to interpret it? Or because you actually enjoy being the strategic brain? The answer matters for what comes next.

What Your Answers Reveal About Your Patterns

You See This As Your Gap To Fix

Your answers consistently reflected ownership: “I haven’t set this up well enough,” “I haven’t created the clarity they need,” “I haven’t built the infrastructure.”

What This Means: You tend to take responsibility for the bottleneck rather than blaming your team. This is actually a strength—it means you’re coachable, self-aware, and likely ready to do the work required to change things.

The Watch-Out: Sometimes founders with this pattern take too much ownership. They assume everything is their fault when sometimes the real issue is having the wrong people, or trying to build something that can’t be built with current resources.

The Question For You: Is the bottleneck really just about infrastructure and clarity you haven’t built? Or are there other factors—team capability, trust issues, or your own resistance to letting go—that are also at play?

Talk soon,

Mara Whitener

Your Bottleneck Scores

Primary Bottleneck Identified

Your Team Isn’t Fully Stepping Up

You have people, but they’re not operating as empowered leaders. Whether it’s decision-making, conflict resolution, or self-direction—there’s a gap between the team you have and the team you need.

This shows up as:

• Team members waiting for your input instead of acting
• Conflicts or issues festering until you address them
• Productivity dropping when you’re not present
• Decisions defaulting to you even when they shouldn’t

The Pattern: This is often the most complex bottleneck because it’s not just about systems or processes—it’s about people. And the root cause isn’t always obvious. It could be:

• A hiring issue: You don’t have the right people
• A development issue: You haven’t grown them into the roles you need
• A trust issue: They’re more capable than you’re allowing them to be
• A clarity issue: They don’t know what “stepping up” actually looks like

The Truth: Most founders with this bottleneck have some combination of all four. Untangling which is which—and in what proportion—is where real progress starts.

What Your Answers Reveal About Your Patterns

You See This As Your Gap To Fix

Your answers consistently reflected ownership: “I haven’t set this up well enough,” “I haven’t created the clarity they need,” “I haven’t built the infrastructure.”

What This Means: You tend to take responsibility for the bottleneck rather than blaming your team. This is actually a strength—it means you’re coachable, self-aware, and likely ready to do the work required to change things.

The Watch-Out: Sometimes founders with this pattern take too much ownership. They assume everything is their fault when sometimes the real issue is having the wrong people, or trying to build something that can’t be built with current resources.

The Question For You: Is the bottleneck really just about infrastructure and clarity you haven’t built? Or are there other factors—team capability, trust issues, or your own resistance to letting go—that are also at play?

Talk soon,

Mara Whitener

Your Bottleneck Scores

Primary Bottleneck Identified

You’re The Only One Thinking Strategically

Your team can execute, but they’re waiting for you to set direction, make decisions, and evaluate opportunities. Every strategic move requires your involvement, which means growth only happens at the pace you can personally drive it.

This shows up as:

• Projects pausing when they need direction and you’re unavailable
• Your team deferring decisions to you even when they could decide
• Opportunities waiting for your evaluation
• Growth feeling directly tied to your personal bandwidth

The Pattern: You’ve built a team that can follow instructions well, but they haven’t developed—or been empowered to develop—strategic thinking of their own. The vision lives in your head, and they’re dependent on you to translate it.

The Question: Is this because you haven’t communicated your vision clearly enough? Or because you haven’t trusted them to interpret it? Or because you actually enjoy being the strategic brain? The answer matters for what comes next.

What Your Answers Reveal About Your Patterns

You See This As Your Gap To Fix

Your answers consistently reflected ownership: “I haven’t set this up well enough,” “I haven’t created the clarity they need,” “I haven’t built the infrastructure.”

What This Means: You tend to take responsibility for the bottleneck rather than blaming your team. This is actually a strength—it means you’re coachable, self-aware, and likely ready to do the work required to change things.

The Watch-Out: Sometimes founders with this pattern take too much ownership. They assume everything is their fault when sometimes the real issue is having the wrong people, or trying to build something that can’t be built with current resources.

The Question For You: Is the bottleneck really just about infrastructure and clarity you haven’t built? Or are there other factors—team capability, trust issues, or your own resistance to letting go—that are also at play?

Talk soon,

Mara Whitener

Your Bottleneck Scores

Primary Bottleneck Identified

Your Team Isn’t Fully Stepping Up

You have people, but they’re not operating as empowered leaders. Whether it’s decision-making, conflict resolution, or self-direction—there’s a gap between the team you have and the team you need.

This shows up as:

• Team members waiting for your input instead of acting
• Conflicts or issues festering until you address them
• Productivity dropping when you’re not present
• Decisions defaulting to you even when they shouldn’t

The Pattern: This is often the most complex bottleneck because it’s not just about systems or processes—it’s about people. And the root cause isn’t always obvious. It could be:

• A hiring issue: You don’t have the right people
• A development issue: You haven’t grown them into the roles you need
• A trust issue: They’re more capable than you’re allowing them to be
• A clarity issue: They don’t know what “stepping up” actually looks like

The Truth: Most founders with this bottleneck have some combination of all four. Untangling which is which—and in what proportion—is where real progress starts.

What Your Answers Reveal About Your Patterns

You See This As Your Gap To Fix

Your answers consistently reflected ownership: “I haven’t set this up well enough,” “I haven’t created the clarity they need,” “I haven’t built the infrastructure.”

What This Means: You tend to take responsibility for the bottleneck rather than blaming your team. This is actually a strength—it means you’re coachable, self-aware, and likely ready to do the work required to change things.

The Watch-Out: Sometimes founders with this pattern take too much ownership. They assume everything is their fault when sometimes the real issue is having the wrong people, or trying to build something that can’t be built with current resources.

The Question For You: Is the bottleneck really just about infrastructure and clarity you haven’t built? Or are there other factors—team capability, trust issues, or your own resistance to letting go—that are also at play?

Talk soon,

Mara Whitener