Why Founder Boundaries Backfire (And What to Set Instead)
Most founders confuse boundaries with rules — and that confusion drives away good employees, protects bad ones, and keeps the founder trapped as the bottleneck.
Most founders who struggle with boundaries are not struggling because they lack assertiveness. They are struggling because they are using the wrong framework entirely. Annie Carbonneau, who specializes in relationship coaching for entrepreneurs, identifies one distinction as the root of most relational breakdown in founder-led businesses: the difference between a boundary and a rule. Getting this wrong does not just create awkward conversations. It drives away the people founders most need to keep.
The Distinction That Changes Everything: Boundaries vs. Rules
A boundary is not something you set for another person. It is a declaration of what you will and will not accept for yourself, and what you will do when that line is crossed. No one else has to agree to it. No one else has to sign off on it. It is yours.
A rule is different. Rules are mutual agreements between two people, or across a team, about how a group will operate together. Rules require buy-in. Rules need enforcement. Rules are negotiated, even when the negotiation is implicit.
Most founders conflate the two. They announce "boundaries" that are actually demands: stop pinging me after 7pm, don't bring me problems without solutions, I need two weeks' notice for time-off requests. These are rules. They may be reasonable rules. But when they are framed as personal boundaries, two things go wrong: the founder feels violated when they are not followed (because it feels personal), and employees feel controlled rather than guided (because no one agreed to the demand).
Boundary | Rule | |
|---|---|---|
Belongs to | The individual | The group or relationship |
Requires agreement | No | Yes |
Example | "I don't take calls after 7pm" | "The team doesn't ping leadership after 7pm" |
Consequence of crossing | You act (leave, stop, disengage) | Enforcement, accountability conversation |
Can be imposed on others | No | Yes, with mutual agreement |
Failure mode | Not holding it yourself | Not enforcing it consistently |
The Authentic Connection Blueprint, Annie Carbonneau's six-month framework for founders rebuilding their relational capacity to beat emotional exhaustion, treats this distinction as foundational. Founders cannot build real support, cannot trust, delegate, or stop carrying the weight alone, until they understand what belongs to them and what belongs to the group.
How Founders Violate Their Employees' Boundaries Without Realizing It
The boundary conversation in most leadership content focuses on founders protecting themselves. Far less attention goes to the ways founders routinely cross the boundaries of the people who work for them.
Three patterns show up most consistently.
Implicit participation requirements
A team leader builds a culture where after-work drinks, holiday parties, and team dinners are treated as expressions of loyalty. No one says attendance is mandatory. But employees who skip are quietly marked as "not team players." The implicit message: your time outside work hours belongs to us too. This is a boundary violation. An employee's personal time, social choices, and energy outside contracted hours are theirs. A culture that treats those as organizational assets has overstepped.
Working on days off
Sending messages on weekends, expecting fast replies during vacations, looping employees into decisions on their days off -- each of these individually may feel minor. Collectively, they communicate that there is no boundary between the employee's personal life and the job. The founder often does not notice because they have long since dissolved that boundary for themselves. But what founders accept for themselves, they do not get to expect from others by default.
The "we're family here" culture
Of all the relational frameworks founders apply to their teams, this one causes the most structural damage. When a founder positions the team as family, they import a relational structure that is fundamentally incompatible with employment. In a family, roles are unconditional and permanent. Accountability is softened by love. The difficult conversation gets postponed indefinitely because you do not fire your brother.
In a functional team, roles are earned and conditional. Accountability is the baseline, not the exception. Difficult conversations are the mechanism by which the team stays healthy.
When founders blur this line, employees unconsciously shift dynamics. Some wait to be told what to do rather than taking initiative. Others leverage the emotional closeness to avoid accountability. And everyone struggles when the founder has to make a hard decision, because the family frame makes it feel like a betrayal rather than a business necessity.
How Founders Fail to Hold the Line for Their Teams
The second pattern is the inverse: founders who do not enforce the rules that exist to protect their people.
The most damaging version of this is the protected employee. The boss's friend who is abrasive to the team. The high-performer whose results are used to excuse their treatment of colleagues. The early hire whose tenure makes them feel untouchable. When founders tolerate this behaviour, because the conversation is uncomfortable, because the relationship is complicated, because they do not want to look like the bad guy, they leave the rest of the team to absorb it alone.
Here is what that costs. Every employee who witnesses a boundary violation being ignored learns two things: their discomfort does not matter enough to address, and the rules apply to some people but not others. The trust in the founder's leadership erodes. The team's willingness to flag problems decreases. The best employees, the ones with options, start looking elsewhere.
The slacker who gets covered for creates the same dynamic. When one person consistently underdelivers and others quietly absorb the extra load, the unspoken message is that the founder values harmony over fairness. Over time, the team's capacity and morale both degrade.
Annie Carbonneau's framework names this clearly: failing to enforce a rule that protects employees is not neutrality. It is a choice, and employees register it as one.
Why Founders Struggle to Hold Either Kind of Line
Understanding the distinction between boundaries and rules does not automatically make them easier to hold. For most founders, especially those who have built their businesses through sheer self-reliance, the real obstacle is internal.
Holding a boundary requires being willing to act on it, and that action often means disappointing someone, losing their approval, or triggering conflict. For a nervous system wired toward hypervigilance and self-reliance, conflict does not read as a neutral event. It reads as a threat to belonging.
This is the pattern Annie Carbonneau works with directly in The Authentic Connection Blueprint: the founder whose identity is built around being capable, competent, and needed, and who therefore experiences setting a limit as a form of weakness, or enforcing accountability as a form of cruelty. The "family" framing makes both worse, because families are not supposed to have performance reviews.
The identity wound underneath is often some version of: if I hold this line, I will lose this person, and I cannot afford to lose people. So the founder absorbs the violation, works the extra hours, tolerates the protected employee, and covers for the slacker. The result is emotional exhaustion and a growing sense of isolation that most founders never name out loud.
The nervous system piece matters here too. When founders are chronically dysregulated, running on stress, adrenaline, and the low-grade hypervigilance of doing everything alone, their capacity for the kind of calm, clear conversation that boundary-holding requires is genuinely compromised. This is not a willpower problem. It is a biology problem. Regulation has to come first1.
What It Actually Looks Like When It Works
A founder with real relational clarity does a few things differently.
They hold their own boundaries quietly and consistently. "I don't take calls after 7pm" is not an announcement. It is simply what they do. When someone calls, they do not answer. When someone apologizes for a late message, they respond in the morning without drama. The boundary holds because the founder holds it, not because everyone else agreed to respect it.
They establish rules explicitly and enforce them evenly. If the expectation is that everyone is reachable during core hours, that applies to the boss's friend and the newest hire alike. If the standard is that team members treat each other with basic respect, that is enforced regardless of performance or tenure.
They name the frame they are using. Teams that hear "we're a family" from their founder need to hear something different: "we're a team that genuinely cares about each other, and that means I will hold everyone, including myself, to the same standard." That is not colder. That is safer.
And when someone crosses a line, theirs or a colleague's, they address it. Not dramatically, not punitively, but clearly. The conversation that feels hardest in the moment is almost always the one that prevents the exodus three months later.
Frequently Asked Questions
What is the difference between a boundary and a rule at work?
A boundary belongs to one person: it describes what that individual will and will not accept, and what they will do if that line is crossed. A rule is a mutual agreement between two people or a group about how they will operate together. Rules require buy-in and consistent enforcement. Boundaries require only that the person holding them actually acts on them.
Is it a boundary violation when a boss expects employees to work on their days off?
Yes, when the expectation is implicit rather than agreed upon. An employee's personal time is theirs. A founder who sends weekend messages and expects fast responses is communicating, without agreement, that personal time is a shared resource. This crosses a boundary that most employees have not consented to dissolve.
Why does "treating employees like family" backfire?
The family model imports unconditional loyalty, tolerance for underperformance, and conflict avoidance into a context that requires accountability, clarity, and fair standards. When a founder uses family language, employees unconsciously shift into relational dynamics that are not designed for professional environments, and accountability conversations become nearly impossible without feeling like a betrayal.
What happens when a founder doesn't enforce a rule protecting employees?
The team registers the inaction as a choice. Trust in the founder's leadership erodes. The employees absorbing the bad behavior, covering for a slacker or tolerating a colleague who is abrasive, begin to question whether their wellbeing matters. Over time, the best employees leave, and the ones who stay do so because they have fewer options, not because they are invested.
Why do founders with good intentions still struggle to hold boundaries?
Holding a boundary often means disappointing someone or triggering conflict, and for founders wired toward self-reliance and belonging, conflict can feel like a threat rather than a neutral event. This is a nervous system and identity pattern, not a knowledge gap. Relationship coaching for entrepreneurs addresses exactly this layer: not just the concept of boundaries, but the relational capacity to act on them consistently, without emotional exhaustion or guilt.
Founders who recognize themselves in these patterns, who know they are the bottleneck, who sense that the culture they have built is costing them their best people, and who are exhausted from carrying it alone, are not dealing with a strategy problem. They are dealing with a relational capacity problem. Coaching for entrepreneurs who want to rebuild that capacity is what Annie Carbonneau does. You can find her profile on Coaching Intelligence Hub to learn more about how the work is structured.
1: Porges, S., PMC, NIH, “The Polyvagal Perspective”, 2008