tessia

The Method

Plan ahead. Organize what's there. Distribute what one person carries.

TESSIA designs care systems on three fronts over one foundation of design principles. A family can start on any front, depending on the moment.

OutcomeLess care concentrated in one person
Two empty chairs at a small wooden table with two mugs and a closed folder
01 · PLAN

Before care is needed

How do we prepare before a crisis organizes care for us?

  • Transitions you can see coming: a parent who starts to need help, a new child
  • Decisions still open: wishes, housing, money, who decides
  • A map of the real network
An entryway console with keys in a ceramic tray, storage boxes and a notebook
02 · ORGANIZE

What care runs on

How does care run day to day without living in one head?

  • Information, documents and contacts
  • Routines and workflows
  • The hard conversations between family members
Two identical house keys, one with a blue tag, next to a sealed envelope
03 · DISTRIBUTE

Not on one person alone

How does care keep working when one person steps away?

  • Continuity and backup
  • Handoffs that carry authority
  • Ownership of each thread

Review runs through all three · triggered by transitions, not by the calendar

FOUNDATIONCare ethicsPrivacy by designAgency of the person cared forReduce before redistribute

Diagnosis

Three questions. Three different moves.

Every care system can be read through three properties, and each one asks for something different.

Concentration

How much of your care runs through one person?

DISTRIBUTE

Distribute

Move threads, with authority

Volume

How much work does your care system create in total?

FOUNDATION

Reduce

Cut before you share

Fragility

What breaks if that person isn't there?

DISTRIBUTE

Create continuity

Care Continuity Method

Handoffs don't fix volume. When the problem is how much work there is, start by cutting it.

Your network

Your network tells you where to begin.

The same tool doesn't fit every family. Three questions sort the four situations we see most.

Is there anyone else who could take part?
NO →
TYPE 1 · FOUNDATION

No network

An only child, a single parent, family far away. Reduce, automate and hire. The ways out beyond family are the whole plan.

YES ↓
Do they see the work it takes?
NO →
TYPE 2 · FOUNDATION

A network that doesn't see it

The capacity exists, the intention doesn't. Reduce what only you carry and make the imbalance visible in facts, without turning you into a negotiator.

YES ↓
Is there a system they can run without you?
NO →
TYPE 3 · DISTRIBUTE

Willing, but no system

Good will, no structure. The Care Continuity Method works here almost as it is.

YES, STILL TOO MUCH ↓
TYPE 4 · FOUNDATION

Everyone helps, still overwhelmed

Everyone takes part and the system still crushes. Cut volume: remove rework, automate, outsource.

03 · DISTRIBUTE

The Care Continuity Method

The method behind the Distribute front, and the most developed part of TESSIA today. It works one thread at a time.

  1. Pick one thread.

    One recurring responsibility, like refilling a prescription or managing appointments. Not all of care at once.

  2. Name why it still runs through you.

    One of five reasons keeps it tied to you.

  3. Move it one step up.

    Findable, then runnable, then shareable. If there's no one to hand it to, reduce it instead.

Step 2 · the five reasons

Knowledge

It lives in your head.

Information

It exists, but no one else can find it.

Access

They can't log in, sign or call.

Next step

They don't know when to act.

Autonomy

Every exception comes back to you.

Step 3 · moving it up

Findablesomeone can locate it
Runnablesomeone can do it
Shareablesomeone can own it
OR
Reduce itno one to hand it to

The Continuity Ladder

From “only you” to “fully taken over”, in five steps.

Handing off a thread from step 0 or 1 is what makes it come back. A handoff is proven at the first exception, not at the agreement.

Step 0

Only you

No one can run it yet. Reduce it.

Step 1

Instructed help

Acts only with live instructions.

Step 2

Informed help

Works from notes, waits for your cue.

Step 3

Delegated

Runs the routine. Exceptions return.

Step 4

Taken over

Owns the outcome, exceptions too.

← depends on youless of the thread depends on you →

Vocabulary

The words the method runs on.

Six moves structure the work: Map → Externalize → Operationalize → Back up → Hand off → Review. They are a toolkit, not a required sequence.

  • Care Thread
    The smallest piece of care someone else can fully take over.
  • Five reasons
    Knowledge, information, access, next step, autonomy.

    Why a thread still runs through you.

  • Boomerang Test
    A handoff is proven at the first exception, not at the agreement.
  • Continuity Brief
    If I'm unavailable, start here.

    Two short pages for the person stepping in.

  • Reduce first
    Don't hand off work that shouldn't exist.
FOUNDATION

Seven ways out that don't involve asking your family.

In order of preference. Every time a thread leaves through one of the first six, you didn't have to ask anyone for anything.

1

Eliminate

2

Simplify

3

Automate safely

4

Hire a service or professional

5

Document it for whoever comes next

6

Build redundancy

7

Assign it to a family member

No one had to be asked
Last resort

Where the method stands. The TESSIA method is in active development and refined with real families. The Distribute front has its own method today; Plan and Organize are being built the same way. Our thinking about care as a process draws on care ethics, including Joan Tronto's phases of care: noticing a need, taking responsibility, doing the work and seeing how it's received.

Find where to start How we design

[ Free Care Continuity Check · for adult children of aging parents ]

If you were unavailable for seven days, what would stop working?

In about 3 minutes, find one fragile point in your parent's care and leave with a one-page handoff someone else can use.

Start the free check