✛ Relationship copilot
How you two build together.
Two people building the same thing rarely fail on talent. They fail on the seams: who owns what, where they pull in different directions, and the quarter of the work neither of them is drawn to. The copilot reads both your results and maps exactly that.
✛ What a pairing brief looks like
A real example: an Architect and an Igniter building together. Yours reads from your own two results.
✛ How you two build together
Architect + Igniter
Neighbours on the cycle
Watch out for
- · Architect: can treat a finished design as finished work, when nothing has yet met a real user or a real load.
- · Igniter: can create more heat than the product, team, or system is ready to absorb.
Neither of you covers
- · Scalers: Make what works repeatable: growth that is stable, dependable, and no longer needs heroes.
- · Marshals: Create the discipline and rhythm that make a working system perform.
This is the type-level read. The Relationship copilot goes further: who should own what, the recurring argument you two will have, and how to run your first working session together.
✛ What you get
Who owns what
The decisions that should route through each of you, and the ones that should not.
Where the friction is
The recurring argument your two shapes will have, named before it costs you.
What neither covers
The quarter of the building cycle you will both skip, and how to cover it.
✛ Read your own pairing
Pairing briefs read from your Full Profile result. Take the free test to find your type, then unlock the Full Profile to map every relationship you build in.