Kinnetly
Relationship context rarely fits one label. Maya might be a former colleague, a current friend, a member of the same founders' group and the person who introduced you to a trusted designer. Calling her only a "former colleague" is accurate, but incomplete.
Social-network researchers use the term multiplex relationship when the same two people are connected in more than one way. The idea has been studied for decades, including in friendships that also involve work, family, neighbourhood or shared activities. It sounds academic. The practical point is simple: the history between two people often crosses roles and settings.
That history helps you remember what matters before the next conversation. It also stops a current job title from overwriting everything that came before.
One label freezes a changing relationship
A contact list tends to give each person one row, one company and perhaps one category. Real relationships keep moving.
Someone you met at a conference may later join your professional association. You might work on a project together, then stay friends after both of you change jobs. None of those contexts makes the others false.
The trouble starts when the latest context replaces the earlier ones. Updating a company field can erase where the relationship began. Changing a tag from "client" to "friend" can hide the professional history that still shapes how you know each other.
You don't need a perfect record. You need enough continuity to answer:
- Where did we first meet, or who introduced us?
- Which contexts are current?
- What has changed?
- What matters for our next interaction?
Those questions are more useful than trying to find one permanent label.
Multiplex relationships describe overlap, not quality
A multiplex relationship is not automatically close, healthy or valuable. It simply has more than one basis.
That distinction matters. Research on workplace friendships found a mixed picture: relationships that combined friendship and task-focused interaction were associated with trust and positive affect, but also with maintenance difficulty and emotional exhaustion. The studies were conducted in workplace settings, so they should not be treated as a rule for every friendship. They do show why overlapping roles can bring both understanding and competing expectations.
A study of one higher-education cohort also found overlap among friendship, learning and working ties. Again, the setting was narrow. Its useful lesson is that "How do you know this person?" can have several honest answers.
Context is descriptive. It doesn't prove trust, closeness, consent or obligation.
Four kinds of relationship context worth separating
A small distinction prevents a lot of confusion:
| Context | Example | What to preserve |
|---|---|---|
| Current structural context | Works at Company A or belongs to Group B | The connection that is active now |
| Historical structural context | Formerly worked with you at Company C | The old setting and, if useful, when it ended |
| Relational context | Friend, mentor or collaborator | A careful description, without assuming they use the same label |
| Provenance context | Introduced by Priya at an industry event | The origin of the relationship and the date, when known |
These types can overlap without being merged. A former employer is not a current employer. An introduction explains how contact began, not how close two people are today. "Mentor" may describe your experience of a relationship without being a formal or reciprocal title.
This is where structural connections often work better than piling on tags. Tags can help you retrieve people by a useful label. A company, group, event or introducer records the context itself.
Map one relationship in six steps
Pick one person you currently describe mainly by their job title. Use this short exercise to rebuild the relationship context around them.
1. Keep one person record
Don't create "Alex from work" and "Alex from the association" as separate contacts. Start with one person, then connect the relevant settings around them.
2. Record the origin
Add where you first met or who introduced you, if you know. A shared event and an introducer are different facts, and both may matter.
If remembering the origin is the hard part, use this guide to record where you met someone without turning the note into a biography.
3. Separate current and former contexts
Keep the current company or group visible. Preserve an old workplace or membership as history rather than deleting it or leaving it looking current.
Dates help when you know them. An approximate memory should stay approximate instead of becoming a precise-looking fact.
4. Add one sentence about the overlap
Write only what will help you remember accurately. For example:
Met through the design association in 2022. Later worked together at North Street. We still compare notes on service design a few times a year.
That sentence carries more useful relationship context than four unexplained labels. It also leaves room for the relationship to change.
5. Log a meaningful interaction selectively
Record a conversation, meeting or shared activity when it creates useful continuity. You don't need to capture every message.
A short activity note can preserve what was discussed, while a separate note holds durable context. If there is a real commitment, give it its own reminder. Keeping those jobs separate makes later review easier.
6. Set a follow-up only when there is a reason
Detailed context doesn't create an obligation to contact someone. Add a reminder when you promised something, planned a next step or have a genuine reason to reconnect.
No action is sometimes the right answer.
Save less, connect it better
Relationship context can be useful without becoming intrusive. Before saving a detail, ask:
- Will this help me remember the relationship accurately or keep a commitment?
- Did they share it in a setting where saving it is reasonable?
- Is it a fact, my interpretation or something likely to change?
- Could a shorter, more neutral note do the job?
Leave out sensitive details that have no clear purpose. Don't infer identity traits or private circumstances. And review old notes when the relationship changes, especially if a label could now be misleading.
People are more than job titles, but that doesn't mean you need to catalogue every part of them.
A relationship map still needs your judgement
A graph can show that one person connects to a current company, a former workplace, a group, an event and an introducer. It can preserve dates, notes and selected activity. That structure supports recall because you can see the contexts together.
It cannot decide which role matters most to the other person. It cannot tell you whether friendship is reciprocal, whether an introduction is welcome or whether an old note remains fair. Those decisions stay with you.
Kinnetly's personal relationship map lets you keep one person connected to companies, groups, events and introducers. Company and group links can be marked as former, while notes, manually logged activities and deliberate reminders preserve the parts you choose to keep. It doesn't infer what a relationship means or automatically log your inbox and calendar.
One person, with the history intact
Choose one relationship that currently lives under a single label. Add the event, group, company or introduction that explains its history. Mark what has changed. Then stop when the record is useful.
Map the context behind one important relationship in Kinnetly.
Sources
- Verbrugge, "Multiplexity in Adult Friendships", Social Forces, 1979.
- Methot et al., "Are Workplace Friendships a Mixed Blessing? Exploring Tradeoffs of Multiplex Relationships and their Associations with Job Performance", Personnel Psychology, 2016.
- Lindholm, "The Constructive Overlap: What Organizational Memberships Can Add to Relationships", 2021.