The 7 Relationship Roles: A Definitive Guide to Setting Boundaries in Every Part of Your Life
1. The Tuesday Morning That Broke Me
Tuesday morning. I'm sitting in a coffee shop in Da'an District, Taipei. The kind of place where the music is quiet and nobody asks why you've been nursing the same Americano for two hours. My laptop is open. A spreadsheet is on the screen. I'm staring at numbers that I've already looked at four times, hoping they'll be different.
They're not different.
I'm 48 years old, and I'm trying to understand how I ended up here — financially depleted, emotionally exhausted, in a business partnership that had somehow become something I didn't recognize. I'm not angry. I'm past anger. I'm in the strange, quiet place you get to when you've finally run out of ways to pretend that things are okay.
I'd been in B2B sales for more than two decades. I knew how to build relationships. I knew how to read people. I had co-founded an accelerator — iiinno — with someone I genuinely cared about. And somewhere in the middle of all that genuine caring, something had gone catastrophically wrong.
As I sat there trying to figure out what had happened, I started making a list. Not of grievances — of mismatches. Moments when I had treated a professional relationship as if it were a friendship, when I had absorbed things that weren't mine to absorb, when I had stayed quiet because I didn't want to seem difficult — in a context where staying quiet was profoundly unhelpful.
The pattern that emerged from that list became the foundation of everything I've built since. I call it the 7 Roles framework. It's Pillar 1 of everything Coastline teaches. And I'm sharing the complete version here because I think it might save you from learning this the way I did — slowly, painfully, at significant cost.
The thesis is simple: every significant relationship in your life falls into one of seven roles. Each role has different natural expectations, different healthy limits, and different forms of legitimate exchange. When you mix up the rules — when you apply one role's logic to a different role's relationship — you create confusion, hurt, and eventual collapse. The confusion isn't malicious. It's almost never intentional. But it is predictable, and it is preventable.
2. The Framework: Why Roles Are the Foundation
Before we go through each role, I want to explain why I start here — why, when I'm helping someone think through their relationships or their business, the first question I ask is always: "Which role are you playing in this relationship, and which role is the other person playing?"
It's because almost every relational problem I've ever seen — in my own life or in the lives of people I've worked with — comes down to a role mismatch. Not bad intentions. Not incompatible personalities. Not fundamental value differences. Role mismatch.
You can't set a healthy boundary in a relationship until you know what the relationship is supposed to be. The boundary that's appropriate between co-founders is completely different from the boundary appropriate between friends. The accountability that's healthy between a leader and their team would be inappropriate between soulmates. The unconditional quality of parental love would be dangerous as a framework for a business partnership.
Every role has its own operating system. The software that works on one machine won't necessarily run on another. When you try to install friend-OS on a co-founder relationship, the whole system crashes.
Let's go through each one.
A coworker is someone you're connected to through shared professional goals. The relationship exists because of the work. It doesn't need to extend beyond the work — and it's often better when it doesn't. Coworker relationships are time-bounded (by the project or the job), outcome-oriented (you're here to accomplish something together), and role-defined (each person has a function in the shared endeavor).
The natural boundary in a coworker relationship is: professional collaboration, without the expectation of personal loyalty. You owe each other good work, professional respect, and honest communication about work matters. You don't owe each other friendship, emotional support, or personal confidences. These things can develop — and it's wonderful when they do — but they're not the default expectation of the role.
Early in my career, I treated almost every colleague as a potential friend. I thought building warmth and personal connection was always the right strategy — that the more people liked me, the better we'd work together. That's partially true. But I conflated "warm professional relationship" with "genuine friendship," and they are not the same thing.
I once shared something personal with a colleague — a genuine vulnerability about a difficult decision I was navigating at the time. They were kind in the moment. Three weeks later, during a performance review conversation, that information showed up in a way I hadn't anticipated. Not weaponized exactly — but used as context in a way that made me realize: this person and I were coworkers. The personal confidence I had offered them belonged to the friendship role, not the coworker role. I had given them something from the wrong operating system.
Expecting friendship-level loyalty from coworkers. When a colleague prioritizes their own career or their own team over your interests, it can feel like betrayal. It's not. They're operating correctly in the coworker role. The betrayal feeling comes from you having applied friendship expectations to a coworker relationship.
Before sharing anything personal at work, ask: "Would I be comfortable if this person used this information to serve their own interests?" If not, it belongs in a friendship — not in this room.
A friend is someone you've chosen to be close to — not because of shared work or shared biology, but because of genuine affinity and mutual care. Friendships are voluntary, which is what makes them meaningful. They're also — and this is the part people underestimate — inherently reciprocal. Not transactional, but balanced over time. Both people give, both people receive, both people matter to the other.
The natural boundary in friendship is reciprocity. A friendship where one person always gives and one person always takes is not a friendship — it's an arrangement. Genuine friendship allows for temporary imbalance (your friend is going through something hard, you carry more for a while) but not permanent imbalance. Real friends are also honest with each other — even when honesty is uncomfortable — because care without honesty is just niceness, and niceness isn't the same as friendship.
I had a friendship that lasted for years — someone I genuinely cared about, someone I would have called a close friend without hesitation. But looking back, I can see that the friendship had become unbalanced in a way I never named or addressed. I was consistently the one who reached out. I was consistently the one who adjusted my schedule. I was consistently the one who absorbed when things went sideways. I told myself this was fine — that's what friends do, that's what being a good person looks like.
What I didn't realize was that by never naming the imbalance, I was denying both of us the chance to actually recalibrate. My silence — which I experienced as patience and generosity — was actually a failure of honesty. Eventually, the friendship faded. Not dramatically. Just quietly, the way friendships do when neither person is getting what they actually need.
Real friendship can survive an honest conversation about imbalance. What it can't survive is two people pretending the imbalance doesn't exist until there's nothing left to save.
Treating every warm acquaintance as a close friend. The word "friend" covers enormous range — from someone you genuinely confide in to someone you enjoy having lunch with occasionally. Most relationship pain in the "friendship" category comes from conflating these levels: treating a lunch-level connection as a soul-level confidant, then feeling hurt when they don't show up accordingly.
Make a private list of your "friends." For each, honestly assess: is the give-and-take balanced over the last six months? If not, ask yourself — am I waiting for them to change, or am I willing to have an honest conversation? The first choice preserves the status quo. The second choice might save the friendship.
The leader/subordinate relationship is defined by an acknowledged power differential. One person sets direction; the other person executes. One person evaluates; the other person is evaluated. This isn't a moral hierarchy — it's a functional one. And it requires explicit structure to work well: clear expectations, clear accountability, and honest feedback in both directions.
The natural boundary here is role clarity. A good leader cares about their team, but the relationship has professional structure. A good leader doesn't parent their team — they set clear expectations and hold the team accountable to them. A good subordinate doesn't treat their leader as a peer — they understand the accountability structure and work within it while advocating for themselves clearly and professionally. Confusion about who has authority over what is the most common source of dysfunction in this role.
After 23 years in B2B sales, I've been in both seats many times. The hardest lesson I learned as a leader was this: caring about your team and avoiding difficult conversations with your team are not the same thing. For a long time, I thought they were. I thought that if I cared enough, if I was warm enough, if I created a safe enough environment, people would naturally perform at their best and problems would resolve themselves.
They don't. What happens is the problems persist, and the person who needed feedback six months ago is now entrenched in habits that are hard to change. What looks like kindness in the short term is actually a failure of the leader's core responsibility — to help their team member grow. I wasn't being kind when I avoided hard feedback. I was being conflict-avoidant. Dressing it up as care didn't change what it actually was.
Leaders becoming friends with their direct reports in a way that undermines accountability. This is not about being cold — it's about maintaining the structural clarity that makes the relationship useful. When a leader and their subordinate are such close friends that the leader can't give honest feedback without it damaging the friendship, both people are worse off. The leader is hobbled; the subordinate doesn't get the input they need to grow.
For leaders: write down the three pieces of feedback you've been avoiding giving someone on your team. Pick the most important one. Schedule a conversation this week. The kindest thing you can do for someone is tell them the truth about what's holding them back — before it's too late to fix it.
A co-founder is someone who is in the boat with you — financially, strategically, reputationally. You share the upside and the downside. You are both building this thing, both accountable for it, both affected by its success or failure. The First Follower variant (from Derek Sivers' famous TED talk) applies when one person leads a movement and another person joins early, publicly, and fully — making the difference between one person dancing alone and a real movement. Both require an explicit, honest agreement about what you're each contributing and what you each expect.
This is the role where most people get into the most serious trouble — because co-founder partnerships almost always form from either friendship or professional admiration, and those roles have entirely different rules. The co-founder role requires explicit agreements about decision-making authority, financial responsibilities, ownership, and exit conditions. It requires honesty even when honesty is uncomfortable. It requires treating your partner as an equal who can handle difficult truths. Friendship rules — forgive easily, avoid conflict, assume good faith indefinitely — are dangerous when applied to a co-founder relationship. They allow small misalignments to compound into catastrophic ones.
This is the role that cost me the most. When I co-founded iiinno, I brought my warmest, most loyal self to the relationship. I assumed good faith. I absorbed overruns without naming them. I avoided certain conversations because they felt like they might damage the friendship underneath the partnership. I applied friend-rules to a co-founder relationship — and when things went wrong, the friend-rules had no tools to fix what needed fixing.
Co-founder relationships require something that friendship culture actively discourages: early, explicit, potentially awkward conversations about the hard stuff. What happens if we disagree and we can't resolve it? What happens if one of us wants to stop and the other doesn't? What are we each actually committing to do, and how will we know if we're not living up to it? These conversations feel wrong in a friendship context — like you're preparing for failure, like you don't trust the other person. In a co-founder context, they are the foundation. Without them, you're building on sand.
I never had those conversations with my co-founder at iiinno. I thought our mutual care and shared vision would be enough to navigate whatever came up. It wasn't. Not because the care wasn't real — it was — but because care without structure breaks under pressure.
Choosing a co-founder because they're a good friend rather than because they're the right partner for this specific venture. These are different questions. A good friend may have completely different skills, risk tolerance, work style, and vision than what this particular business needs. Friendship is a wonderful foundation for trust — but trust alone doesn't make someone the right co-founder.
If you're already in a co-founder relationship, write down the three questions you've been afraid to ask your partner. Schedule a "founder conversation" — a formal, agenda-driven meeting, separate from your normal working sessions — and ask them. The conversation you're afraid to have now will be ten times harder to have in a year when the stakes are higher.
The parent role is unique in the 7 Roles framework because it's the only one where the love is truly unconditional — or should be. The parent doesn't love the child because the child is performing well, or because the child has been kind lately, or because the relationship is reciprocal. The love comes first and it stays regardless. But unconditional love does not mean unconditional enabling. The parent's responsibility includes structure, honest feedback, and — crucially — preparing the child to eventually not need them.
The boundary in parenting is perhaps the most counter-intuitive: loving your child means not absorbing everything for them. A parent who shields their child from all difficulty, all failure, all consequence, is not expressing love — they're expressing anxiety. Real parental love includes the courage to let your child experience appropriate consequences, to disagree with them honestly, and to maintain your own personhood rather than disappearing entirely into the parental role.
My son Ethan is 15, living with his mother in Canada. My daughter Tiana is 22, living in Taipei. I have a different relationship with each of them — not because I love one more, but because they're at different developmental moments and need different things from me.
The hardest shift I've had to make as a father is moving from protector to advisor. When Tiana was 15, my job was largely to keep her safe — to make the environment as sturdy as possible. At 22, my job is to share perspective and then get out of the way. If she makes a decision I disagree with, I can say so once, clearly, with my reasoning. But then it's her life to navigate. Holding on past that point — continuing to advise, continuing to worry audibly, continuing to suggest alternatives — isn't parenting anymore. It's anxiety transfer. And it doesn't help her; it just passes my discomfort to her while signaling that I don't trust her judgment.
Letting go in a healthy way is probably the hardest thing a parent does. And it's also, I've come to believe, the most loving thing.
Applying the parent role to relationships that don't call for it. This is the mistake I made most consistently in my co-founder and professional relationships — absorbing things, covering for people, protecting them from consequences that were actually theirs to face. When you parent an adult, you disrespect their capacity to handle their own life. You also exhaust yourself carrying their weight.
Ask yourself: in which non-parental relationships am I playing the parent role? Who am I protecting from consequences that are actually theirs to experience? Identify one such relationship and decide: what would it look like to step back into the correct role with this person?
A soulmate or partner is the relationship of greatest intimacy — where you are fully known and fully chosen, including the difficult parts. This relationship allows for more vulnerability, more honesty, and more mutual dependence than any other. But the most important word in the definition of partnership is also the most easily forgotten: two. A partnership requires two whole people. Not one person who has found someone to complete them — but two people who are each enough on their own, choosing to build something together.
The paradox of intimacy: the closer the relationship, the more important it is that each person remains a fully distinct individual. Couples who merge entirely — who have no separate interests, separate friendships, or separate inner life — don't become more intimate; they become enmeshed. Enmeshment is not closeness. It's the dissolution of the self, which makes genuine intimacy impossible because there's no longer a separate person to be intimate with. Healthy partners bring themselves fully to the relationship and protect the space for both selves to exist.
I won't write in detail about my marriage here — that's not my story alone to tell. But I will say this: one of the patterns I've had to work the hardest to understand is the difference between being present for someone and being responsible for their emotional state. My natural instinct, when someone I love is in pain, is to fix it. To absorb their difficulty. To do whatever I can to make the pain stop.
That instinct, in a partnership, can actually be harmful. When I make it my project to manage my partner's emotions, I'm doing two problematic things: I'm depriving them of the experience of processing their own feelings (which is where growth comes from), and I'm placing myself in an impossible position — responsible for something I can't actually control. The most respectful thing I can do for someone I love is be genuinely present with them in their difficulty, without trying to take the difficulty away.
This is, of course, much easier to articulate than to live. I'm still working on it at 51.
Expecting your partner to be all seven roles simultaneously — your best friend, your co-founder, your counselor, your parent figure, your greatest adventure companion, and your own mirror. This is an impossible and unfair expectation. Partners are partners. They're not meant to be everything. Having separate friendships, mentors, and communities isn't a threat to a strong partnership — it's part of what makes a strong partnership possible.
Identify one need you're currently trying to have met exclusively by your partner that might be better served through a friendship, a mentor, or your own inner resources. Taking that pressure off your partner — and finding the right role for that need — often creates more room for genuine intimacy in the partnership itself.
The relationship with yourself is the only one that is literally always present and never optional. It's also the relationship most people spend the least time intentionally tending. Your relationship with yourself — your own needs, values, limits, and inner voice — is the foundation every other relationship rests on. When it's unstable or neglected, everything built on top of it is shaky, regardless of how much work you put into the other six roles.
The boundary rule for Role 7 is this: treat your own needs as legitimate inputs, not as afterthoughts. This is profoundly counter-cultural in most of East Asia — and honestly, in most of human culture. We are taught that putting yourself first is selfishness. Adler's philosophy (The Courage to Be Disliked, which I've read three times) argues the opposite: when you genuinely tend to yourself, you have more to give, more sustainably, over a longer time. Self-neglect disguised as generosity is still self-neglect — and it eventually collapses.
Here's what I know now that I wish I had understood at 30: I cannot sustainably give to others from a place of depletion. Every time I have tried to do this — and I have tried many times — I have eventually hit a wall. Not immediately. Sometimes it takes months, sometimes years. But the wall always arrives. And the person who hits it isn't the warm, generous person I want to be — it's someone who is exhausted and resentful and quietly furious at themselves for letting it happen again.
The relationship with myself — asking what I actually need, what my actual limits are, what my genuine values require of me — is not a luxury I get to attend to after everyone else is okay. It's a prerequisite. It's the thing that makes every other role sustainable.
I started a daily practice — just 15 minutes, in the morning, before I open anything — of asking three questions: What do I actually need today? What am I most afraid of right now? What matters most? The answers are often uncomfortable. But they're honest. And they let me move through the rest of the day from a place of self-knowledge rather than blind momentum.
At 51, the relationship with myself is the one I'm working on most actively. And it's the one that's changed every other relationship for the better.
Treating "taking care of yourself" as something you'll do once everyone else is okay. That moment never arrives. The people around you will always have needs. The work will always have demands. The time you're waiting for — the quiet space to finally attend to yourself — will not appear on its own. You have to create it deliberately, and protect it even when it feels selfish, because the alternative is running on empty until you break.
This week, identify one thing you need that you've been denying yourself — not because you can't have it, but because you've been prioritizing everyone else first. It could be an hour alone. A conversation you've been avoiding because you're afraid of what you'll hear. Permission to stop doing something that costs you more than it should. Take one concrete step toward that need this week.
10. Putting It All Together
I want to leave you with the exercise that started all of this for me — the one I did in that coffee shop in Da'an District on a Tuesday morning when the numbers on my screen weren't getting any better.
I took every significant relationship in my life and I labeled it. Not with a name — with a role. And then, for each one, I asked: am I applying this role's rules to this relationship? Or am I using a different role's rules and creating confusion?
What I found was that I had been applying the Parent role to almost everything — absorbing, covering, protecting — because that's where I felt safest and most needed. The cost was enormous. In my co-founder relationship. In my professional relationships. In friendships that had become one-directional because I never named the imbalance. Even, in some ways, in my marriage.
The roles themselves aren't complicated. The work is in noticing which role you're actually in, and then having the courage to apply its rules honestly — even when applying those rules means having an uncomfortable conversation, or disappointing someone, or giving up a dynamic that feels familiar even though it's hurting you.
"The chaos in your relationships isn't because people are complicated. It's because you've been using the same approach for all of them — and it doesn't work for most of them."
Each role has its own operating system. Once you know which OS you're supposed to be running, everything gets clearer. The decisions get simpler. The limits feel less like walls and more like definitions — honest descriptions of what this relationship actually is, and what it's capable of sustaining.
I am, at 51, finally learning to hold all seven roles with some degree of consciousness. Not perfectly. Not without mistakes. But with more clarity than I've ever had before. And that clarity — that ability to walk into a relationship knowing which role I'm in and what it requires of me — is the single most valuable thing I've built in the last three years.
Start with the mapping exercise. Fifteen minutes. Every significant relationship in your life, labeled with one of the seven roles. Then ask yourself the hard question for each one: am I applying the right rules? The answer will tell you where the work is.
📋 Download the 7 Roles Worksheet
The full guided worksheet walks you through the role-mapping exercise — with prompts for each role, boundary-setting scripts, and the questions to ask in each relationship. Free for newsletter subscribers.
Get the Free Worksheet → Free E-Book Chapter🎓 Go Deeper with the Coastline Workshop
The 7 Roles framework is Pillar 1 of the Coastline E-book and the foundation of the Coastline Workshop. If you're ready to apply this systematically — to every relationship in your life — the workshop gives you the structure, the community, and the accountability to actually make it stick.
Join the Workshop → Start with the Newsletter11. Frequently Asked Questions
Q: What are the 7 relationship roles in the Coastline framework?
The 7 roles are: 1) Coworker — shared professional goal, time-bounded collaboration. 2) Friend — mutual care and reciprocity. 3) Leader/Subordinate — structured power differential with clear accountability. 4) Co-founder/First Follower — shared equity, shared risk, requires explicit agreements. 5) Parent — unconditional love with healthy developmental structure. 6) Soulmate/Partner — deep intimacy between two whole, separate people. 7) Self — the relationship with yourself, which all other relationships rest on. Each role has different natural expectations and different healthy limits.
Q: Why do relationship roles matter for setting boundaries?
Each role has different natural expectations and healthy limits. When you apply the wrong role's rules — treating a coworker like a best friend, or applying parent-logic to a co-founder relationship — you create confusion, resentment, and eventually collapse. Most boundary failures aren't caused by bad intentions; they're caused by role confusion. Once you name the role correctly, the appropriate boundaries become much clearer to define and to communicate.
Q: What is the most common role people get wrong?
Co-founder. Especially in Chinese and Taiwanese culture, business partnerships often form from friendship. When you become co-founders with a close friend, both roles are active and their rules conflict. Friend-rules say: be forgiving, be loyal, avoid conflict. Co-founder-rules say: be explicit, hold each other accountable, have hard conversations early. Most people apply friend-rules to co-founder dynamics — and discover too late that those rules have no tools to fix a structural disagreement under pressure.
Q: What does 'the relationship with yourself' (Role 7) mean practically?
It means treating your own needs, energy, values, and limits as legitimate inputs — not afterthoughts. Most people who are struggling with all their other relationships are actually struggling with Role 7 first: they don't feel entitled to their own needs, so they can't protect them. A simple practice: each morning, ask three questions before opening anything external — "What do I actually need today? What am I most afraid of right now? What matters most?" The answers create self-knowledge that makes every other role clearer and more sustainable.
Q: How do I set boundaries in a relationship without damaging it?
Name the role first. Then state the limit from the role's logic, not from personal emotion. "As your co-founder, I need us to agree on our decision-making process" is cleaner than "I feel like you're not respecting me." Boundaries stated from role clarity are easier to hear — they're not about you versus them; they're about the rules of the relationship both of you are in. And a relationship that can't survive a clearly stated, role-appropriate boundary probably wasn't healthy to begin with.
Q: Is the 7 Roles framework part of the Coastline E-book?
Yes. The 7 Roles framework is Pillar 1 of the Coastline E-book — the foundation because nothing else works without it. Not your decision-making system, not your business strategy, not your personal growth. Once you know which role you're in and which role the other person is in, you have the context for every other question. The worksheet (free for newsletter subscribers) is the starting point for applying it.