Roles

A role is something one of you takes on. It bundles a set of responsibilities, agreements, and checks into one package so you can talk about who handles what without listing a dozen things every time.

Every role has a name and a purpose. The name is what you call it. The purpose is why it exists.

The name

The name should tell you — and your partner — what the role is about at a glance. It doesn't need to be flashy. It just needs to be clear.

Some roles use descriptive names:

• Budget Steward

• Logistics Lead

• Meal Planner

Others use more playful names:

• Sidekick

• Connection Keeper

• Rest Advocate

Both styles work. The name catches attention, but the purpose is what tells you whether the role fits.

The purpose

The purpose explains why this role exists in one sentence. It's what you read to decide: is this for us?

A good purpose is concrete:

"Stay ahead of home repairs and upkeep"

You can picture what that means. You know if you need it.

A weak purpose is vague or corporate:

"Ensure household operational efficiency"

This doesn't sound like real life. It doesn't help you decide.

Examples

Each of these says something specific about what the role is for. They're grounded, not abstract.

What a role bundles

When you create a role, it becomes a container for three things:

1. Responsibilities — what the person in this role does

2. Agreements — the boundaries around this role

3. Checks — what gets tracked to see how it's going

A role without responsibilities has nothing to do. A role without agreements has no guardrails. A role without checks has no way to know if it's working.

Things to avoid

• Roles that feel like job titles. You're not hiring for this. It's a way to divide shared life, not a corporate structure.

• Roles that overlap. If two roles in the same area sound like they do the same thing, merge them or clarify the difference.

• Purposes that repeat the name. If the role is "Home Manager" and the purpose is "Manages the home," you haven't added anything.