As companies scale, many leadership problems that appear to be attitude problems are actually clarity problems. A founder says an executive is not owning an area. The executive says they were never given real authority. A team misses a deadline. The manager says priorities changed twice. Two functions argue over a customer issue. Each function believed the other one owned the handoff. In a small company, ambiguity can be overcome through proximity and heroic effort. In a scaling company, ambiguity becomes a tax on speed, trust, and execution.
Clarity, accountability, and decision rights are deeply connected. People cannot be held accountable for work they do not understand, decisions they do not control, or trade-offs that were never made explicit. At the same time, clarity without accountability becomes documentation that no one uses. Accountability without clear decision rights becomes blame. Decision rights without behavioral discipline become theory.
15.1 Diagnosing Unclear Expectations and Duplicated Ownership
Expectation clarity: shared understanding of what outcome is required, who owns it, what standard applies, what constraints matter, what authority is granted, and how progress will be reviewed. Many founders believe expectations are clear because they have stated the goal repeatedly. But a goal is not the same as an expectation. “Improve retention,” “make the launch excellent,” or “own customer experience” may be directionally useful, but each phrase leaves room for interpretation.
Unclear expectations show up first as friction. A founder is disappointed by the quality of a deliverable. The executive is surprised by the founder’s reaction because the standard was never defined. A project slips because several people assumed someone else was driving the final decision. A leader believes they were asked to recommend a path, while the founder believed they were asked to execute one. The work may be moving, but the meaning of ownership is not shared.
Scaling companies are vulnerable to this because early success rewards flexible ownership. In the first stage, everyone does what must be done. People overlap, improvise, jump in, and solve problems without asking whether the task belongs to them. That flexibility is often a strength. But as the company grows, the same overlap creates confusion. Two executives may both believe they own pricing. Product may believe customer success owns implementation quality, while customer success believes product owns the customer experience created by product gaps. Marketing may believe sales owns pipeline conversion, while sales believes marketing owns lead quality. Each function can make a reasonable case.
Duplicated ownership: a situation in which two or more leaders believe they own the same decision, outcome, relationship, or workstream, or where each assumes another person owns it. The first version creates conflict. The second creates neglect. Both become expensive because people spend energy negotiating authority instead of delivering outcomes.
A coach will often diagnose unclear expectations by listening for repeated phrases. Leaders say, “I thought we had aligned,” “I did not know that was mine,” “I was waiting for input,” “I assumed the founder wanted to decide,” or “I did not realize this was the priority.” These phrases are not excuses to dismiss. They are clues. They reveal where the system has forced people to infer rather than know.
Founders can unintentionally create unclear expectations through casual intensity. A founder may say in a meeting, “We need to fix onboarding,” and assume the responsible executive will translate that concern into a plan. The executive may hear a concern, not a mandate. Another leader may hear an implied priority shift. A manager may hear criticism of their team. Without explicit ownership, the comment generates motion but not clarity.
The founder’s historical involvement can also blur ownership. If the founder has always approved product details, pricing exceptions, messaging, or senior hires, people may continue to treat those areas as founder-owned even after the founder says they want executives to own more. Formal delegation does not immediately erase learned behavior. The organization remembers what has actually happened, not only what was recently announced.
Diagnosing unclear expectations requires looking at several dimensions:
- Outcome: What result is expected, and how will success be recognized?
- Owner: Who is directly accountable for delivering the result?
- Authority: What decisions can the owner make without further approval?
- Constraints: What budget, timing, customer, compliance, quality, or strategic boundaries apply?
- Interfaces: Which other functions must advise, support, or execute parts of the work?
- Review: When will progress be discussed, and what will trigger escalation?
A coach may use these questions in interviews or leadership-team sessions to reveal different interpretations. The founder may believe the chief revenue officer owns revenue retention. The chief revenue officer may believe customer success owns it. Customer success may believe product quality is the real driver. Product may believe the target customer segment is unclear. The point is not to declare one person wrong. The point is to expose the chain of assumptions that has been operating beneath the surface.
Clear expectations reduce emotional friction because disappointment becomes less mysterious. If a leader misses a commitment that was explicit, the conversation can focus on execution, resources, judgment, or capability. If the commitment was ambiguous, the conversation must begin with the system that created ambiguity. Founders often want accountability, but accountability becomes credible only when expectations are explicit enough to be fairly tested.
15.2 Defining Who Decides, Who Advises, and Who Executes
Decision rights: explicit agreements about who has authority to make a decision, who should provide input, who must be informed, who executes, and how unresolved disagreement escalates. Decision rights are one of the most important upgrades in a scaling company because they reduce founder dependency and prevent slow, political, or circular decision-making.
In founder-led companies, decision rights often begin as founder rights. The founder decides because the founder has the most context, conviction, and risk exposure. As the company scales, this model becomes insufficient. Executives are hired to own functions, but they cannot fully own them if important decisions keep returning to the founder by default. The founder becomes overloaded, executives become hesitant, and the organization learns that decisions are provisional until the founder reacts.
Defining decision rights does not mean removing the founder from important choices. Some decisions should remain with the founder or CEO, especially those involving company strategy, executive hiring, capital allocation, board-sensitive commitments, major cultural principles, or existential risk. But many decisions should move closer to the person with the best information and direct accountability. The work is to define the difference.
A practical decision-rights system begins with three questions. Who decides: the person with final authority to choose the path. Who advises: the people whose input is required or useful before the decision is made. Who executes: the people or teams responsible for carrying out the decision once made. Many companies get stuck because advising is confused with deciding. A leader gives input and later behaves as if their agreement was required. Or a founder offers advice and the team treats it as a decision.
The distinction between advice and decision is especially important for founders. Founder input carries weight even when the founder intends it casually. If the founder says, “I wonder whether we should delay the launch,” some teams will treat the launch as delayed. If the founder asks, “Why are we not targeting larger customers?” someone may build a new enterprise-growth plan. The founder must learn to label the mode: “I am raising a question, not making a decision,” or “This is my advice, but the decision owner should make the call.”
Decision rights should be mapped around recurring decisions, not only dramatic ones. The most painful ambiguity often lives in ordinary repeat decisions: discount approvals, customer exceptions, roadmap changes, headcount requests, executive hiring steps, budget reallocations, customer escalations, compensation exceptions, policy changes, and launch readiness. If the same decision type keeps returning with confusion, it needs a decision-rights agreement.
Escalation rule: a pre-agreed condition under which a decision moves from one owner or forum to another. Escalation should not mean “bring it to the founder whenever someone is uncomfortable.” It should be tied to clear thresholds: budget impact, customer risk, strategic conflict, legal exposure, unresolved cross-functional disagreement, or a decision that affects company-level priorities. Without escalation rules, executives may escalate too early to avoid risk or too late to avoid conflict.
A coach can help the executive team build a decision map by choosing the ten or fifteen decision types that most often create friction. For each one, the team names the decision owner, required advisers, execution owner, escalation trigger, and communication path. The output does not need to be complex. It needs to be used. A one-page decision map that leaders actually follow is better than a comprehensive matrix that becomes shelfware.
Decision rights also require commitment after the decision. Once a decision owner has made a call using the agreed process, others should support execution even if they preferred another path. This is where founders must be disciplined. If the founder allows executives to relitigate decisions privately after losing the debate publicly, the decision-rights system loses credibility. The founder should ask, “Was the decision made through the agreed process?” If yes, the founder should be cautious about reopening it without a clear reason.
Some decisions are reversible, and some are not. Reversible decisions should be made faster and closer to the work. Irreversible or high-consequence decisions deserve broader input and more deliberate review. A coach may help the team distinguish decision types before deciding the process. Not every decision needs executive-team debate. Overprocessing small decisions creates bureaucracy. Underprocessing major decisions creates risk.
The founder’s role is to model respect for the system. If the founder believes a decision owner made a poor call, the founder can address the decision quality, the criteria used, or the escalation threshold. But repeatedly overriding decisions without clarifying why teaches the organization that decision rights are ceremonial. The better response is, “This decision should have been escalated because it crossed our strategic-risk threshold. Let’s update the decision rule.” That preserves both standards and system integrity.
15.3 Making Accountability Feel Constructive Rather Than Punitive
Accountability: the practice of making ownership, commitments, progress, results, and consequences visible in a way that improves performance and trust. Accountability is often misunderstood in founder-led companies. Some people hear it as code for blame. Some founders use it when they are frustrated that people are not moving fast enough. Some executives avoid it because they associate it with public embarrassment or political exposure.
Constructive accountability starts with the premise that capable adults want to do meaningful work well. When performance misses occur, the first question should not always be, “Who failed?” It should be, “What commitment was made, what happened, what did we learn, and what must change?” Sometimes the answer is individual performance. Sometimes it is unclear ownership, unrealistic planning, insufficient resources, shifting priorities, weak cross-functional support, or founder interference. A healthy accountability system can tell the difference.
Constructive accountability: accountability that combines clear standards with fair context, timely feedback, problem-solving, and appropriate consequences. It is not soft. It does not avoid hard truths. It simply avoids turning every miss into a character judgment. In scaling companies, this distinction matters because public blame reduces candor. If leaders believe misses will be punished before they are understood, they will hide risks, polish updates, and delay bad news.
Founders often create accountability problems through inconsistency. They may ignore missed commitments for months because they are busy or conflict avoidant, then react sharply when frustration accumulates. They may tolerate underperformance from early loyalists while holding newer executives to a different standard. They may demand ownership but intervene in the work. The result is a culture where accountability feels unpredictable rather than fair.
Fair accountability requires four conditions. First, the expectation must be clear. Second, the owner must have sufficient authority and resources. Third, progress must be reviewed at appropriate intervals. Fourth, consequences must be proportionate and timely. If any condition is missing, accountability may feel like blame for a system failure.
The coach can help founders use accountability language that improves ownership rather than defensiveness. Instead of saying, “Why did you let this happen?” the founder might ask, “What commitment did we make, where did execution break down, and what decision is needed now?” Instead of saying, “You need to be more accountable,” the founder might say, “I need you to own the full customer-onboarding outcome, including cross-functional escalations. Let’s clarify what authority you need to do that.”
Accountability also depends on visible commitments. Leadership teams often discuss issues without converting them into commitments. People leave with a sense of direction but not a named owner, deadline, or next step. When work does not happen, everyone is frustrated, but no one can point to the actual commitment. A simple commitment discipline at the end of meetings can change this: what was decided, who owns it, by when, what support is needed, and when it will be reviewed.
Performance conversation: a direct discussion about whether a leader is meeting the requirements of the role, with enough specificity to support improvement or make a role decision. Coaching can help prepare these conversations, but founders should not use coaching language to avoid clear performance feedback. If an executive is not scaling, the founder owes them directness. “I want to explore your leadership edge” may sound kind, but it is unclear. “The role now requires building a management team, not personally solving every escalation, and that shift has not happened yet” is clearer.
Constructive accountability also includes consequences. Without consequences, accountability becomes theater. Consequences do not always mean termination or punishment. They may include changed scope, closer review, additional support, role redesign, coaching, missed bonus, or eventually replacement. The key is that consequences are connected to explicit expectations, not emotional surprise.
The founder should also invite accountability for themselves. In a founder-led company, accountability cannot only flow downward. If the founder changes priorities without acknowledgment, reopens decisions casually, reacts harshly to bad news, or bypasses executives, the team should have a way to name that impact. A coach can help establish safe mechanisms for upward feedback. Founder accountability does not reduce founder authority. It increases trust in founder authority.
When accountability is constructive, people do not fear truth as much. They know that problems will be taken seriously, not personalized prematurely. They know that commitments matter. They know that support and consequences both exist. This kind of accountability creates maturity. It allows a scaling company to move beyond heroics and excuses into a culture where ownership is clear, performance is discussed directly, and learning happens fast.
15.4 Using the Coach to Identify Where Structure and Behavior Are Misaligned
Structure-behavior alignment: the match between the company’s formal design and the way leaders actually behave. Many scaling companies change structure before behavior changes, or ask for behavior change while keeping structures that make the new behavior difficult. A founder announces that executives should own decisions, but continues to approve details through back channels. The company says it values cross-functional collaboration, but incentives reward functional wins. The leadership team says bad news should surface early, but meetings punish uncertainty.
Structure includes roles, reporting lines, decision rights, goals, incentives, meetings, planning cycles, metrics, escalation paths, and communication forums. Behavior includes how leaders actually make decisions, raise concerns, share information, respond to mistakes, challenge peers, use authority, and protect their teams. When structure and behavior are aligned, the company’s operating model reinforces the culture it wants. When they are misaligned, people believe the behavior they experience more than the structure written down.
A coach is useful because misalignment is often invisible to those living inside it. The founder may believe the executive team is empowered because the org chart says so. Executives may still feel that the founder’s informal preferences determine what is safe. The people leader may believe feedback channels exist, while managers know that certain truths are dangerous to raise. Finance may believe budget ownership is clear, while functions know that exceptions can be won through private founder access.
One common misalignment is between delegated ownership and founder intervention. The founder tells a leader they own an area, but continues to jump into their team’s work, comment on details, or make decisions through direct relationships with employees. The founder may intend helpfulness or quality control. The behavior tells the organization that the leader’s authority is conditional. A coach can help the founder see where involvement is helpful, where it is undermining, and what inspection mechanism could preserve standards without bypassing ownership.
Another misalignment appears between accountability and authority. A leader is held responsible for a metric they cannot influence without decisions owned by other functions. Customer success is accountable for retention, but product decides roadmap, sales decides customer fit, finance decides service capacity, and the founder approves exceptions. The leader may look weak when the real issue is fragmented authority. A coach can help map the system so accountability is attached to actual levers.
A third misalignment is between candor and reaction. The founder says they want bad news early, but reacts with visible frustration, interrogation, or sarcasm when bad news appears. The company has the structural channel for candor, such as executive meetings or risk reviews, but the behavioral experience teaches people to soften the truth. A coach can observe the meeting, interview leaders, and bring the founder the gap between stated value and lived signal.
A fourth misalignment is between enterprise leadership and functional incentives. Executives are told to act as one team, but goals, bonuses, recognition, and meeting agendas reinforce functional optimization. Sales is celebrated for bookings regardless of implementation burden. Product is celebrated for velocity regardless of customer impact. Finance is celebrated for discipline regardless of strategic opportunity. The executive team cannot consistently behave as an enterprise team if the system rewards them primarily for defending their function.
The coach identifies misalignment through pattern recognition. Interviews reveal where people are confused, cautious, or duplicating effort. Meeting observation reveals who really decides. Feedback themes reveal whether stated norms are credible. The coach should not simply report that people are frustrated. They should help the founder and team locate the friction: role design, decision rights, founder behavior, incentives, communication, or capability.
The coach can then help translate insight into a small number of operating changes. That may mean clarifying a role, redesigning a meeting, creating a decision-rights map, changing escalation rules, adjusting metrics, coaching the founder to stop bypassing executives, or helping the executive team agree on how to raise peer accountability. The work should be practical. Misalignment improves when leaders change what people experience.
A useful coach will also guard against overstructuring. Founders sometimes respond to ambiguity by adding processes everywhere. But too much process can slow the company and drain entrepreneurial energy. The goal is not maximal structure. It is a sufficient structure for the company’s current complexity. A coach with good judgment helps founders add clarity where ambiguity is costly and preserve flexibility where speed and creativity matter.
The founder should expect some discomfort. Structure-behavior misalignment often reveals that the founder’s stated intentions are not fully matched by their habits. It may reveal that an executive role is poorly designed, an early leader is miscast, or an accountability problem has been tolerated too long. The coach’s value is not in making these discoveries painless. It is in helping the founder and team address them without blame, denial, or unnecessary drama.
Clarity, accountability, and decision rights are the management backbone of a scaling company. They allow leaders to act without constant founder interpretation. They allow teams to understand what matters and who owns what. They make accountability fairer because expectations and authority are visible. They reduce politics because decisions have homes. A coach helps the founder see where the backbone is weak, where behavior is contradicting structure, and where a few disciplined changes can restore speed, trust, and ownership.
