de3b4624e858b9a299805f65e72b3d9ebe48b0c1
new file mode 100644
index 0000000..5e54ded
@@ -0,0 +1,50 @@
+---
+visibility: public-edit
+---
+
+# connection & community playbook
+
+a practical, opinionated guide to building genuine connections and communities. not self-help — specific tools, formats, and systems grounded in real experience.
+
+the operating principle: **intentionality compounds.** small, consistent investments in relationships and community create disproportionate returns over time. the people who seem effortlessly connected aren't effortless — they're systematic.
+
+---
+
+## the playbook
+
+### [icebreakers & conversation starters](wiki/icebreakers)
+curated collection of the best icebreakers — the nick gray format, 36 questions for increasing closeness, we're not really strangers, authentic relating games, askhole, and more. includes a context guide for which icebreaker fits which setting, and anti-patterns to avoid.
+
+### [books & resources](wiki/books-resources)
+the best books and articles on connection and community, tiered by priority. supercommunicators, the 2-hour cocktail party, the mom test, never eat alone, the art of gathering, neel nanda's making friends guide, and more. includes what not to read.
+
+### [building a community from scratch](wiki/building-community)
+practical guide based on running socratica, build chain, and observing SF builder communities. covers the socratica format, lessons from failure, what makes communities stick vs. die, the minimum viable community, how to get the first 10 people, and scaling to 50.
+
+### [relationship maintenance systems](wiki/relationship-maintenance)
+how to maintain relationships at scale. the tiered system (weekly/monthly/quarterly/annual), what touchpoints look like at each tier, CRM tools (dex, monica, notion), deliberate relationship repair, and common failure modes.
+
+### [event formats that work](wiki/event-formats)
+specific event formats that create connection: co-working + demo (socratica), dinner parties, hackathons, demo days, unconferences, salons, and the walk-and-talk. each with format details, group sizes, and failure modes.
+
+### [the art of the introduction](wiki/introductions)
+how to introduce people well: the double opt-in intro, anatomy of a good introduction, when not to introduce, the pre-conversation questionnaire, and how to be introduced well.
+
+### [online community building](wiki/online-community)
+building community in digital spaces: discord server design, slack dynamics, twitter/X community building, what makes online communities die, the hybrid model, and the 1% rule.
+
+---
+
+## sources and influences
+
+this playbook draws from:
+- running [socratica](https://www.socratica.info/) at my school
+- organizing build chain (16-person relay-build project)
+- co-organizing startup pitch hackathons
+- maintaining 124+ contacts in a tiered CRM
+- the SF builder community (AGI house, SVFounders, sunday dinners, a builder house, dorm lectures at a university)
+- [neel nanda's making friends guide](https://www.neelnanda.io/blog/43-making-friends)
+- nick gray's *the 2-hour cocktail party*
+- charles duhigg's *supercommunicators*
+- priya parker's *the art of gathering*
+- [build irl](https://www.buildirl.com/) and the IRL community building movement
\ No newline at end of file
new file mode 100644
index 0000000..5e14a54
@@ -0,0 +1,92 @@
+---
+visibility: public-edit
+---
+
+# books & resources
+
+not an exhaustive list — just the ones worth your time, that I've actually read and used.
+
+---
+
+## tier 1: read these first
+
+### supercommunicators — charles duhigg (2024)
+the core idea: every conversation is one of three types — practical ("what's this about?"), emotional ("how do we feel?"), or social ("who are we?"). most miscommunication happens when people are having different types of conversations simultaneously.
+
+**key takeaway:** before trying to solve someone's problem, figure out if they're asking for help or asking to be heard. matching the conversation type is more important than having the right answer.
+
+### the 2-hour cocktail party — nick gray (2022)
+a step-by-step formula for hosting gatherings that build your network. the core insight: most people don't host because they think it has to be perfect. this is the most practical guide to [[building-community|building community]] through hosting. nick's format is deliberately low-effort — no cooking, 2-hour hard stop, structured [[icebreakers]], name tags.
+
+**the formula:**
+- monday, tuesday, or wednesday evening (less competition for attendance)
+- 2-hour hard stop (creates urgency, makes it easy to commit)
+- no cooking — just drinks and snacks
+- name tags for everyone
+- structured icebreaker at the 30-minute mark
+- invite 2x more people than you want to show up
+
+**key takeaway:** hosting is a learnable skill with a repeatable formula. the most immediately actionable book on this list.
+
+### the mom test — rob fitzpatrick (2013)
+technically about customer interviews for startups, but the principles apply to every conversation. the core rule: never tell someone your idea and ask if they like it. instead, ask about their life and let the truth emerge.
+
+**key principles:**
+- talk about their life, not your idea
+- ask about specifics in the past, not generics about the future
+- listen more than you talk
+- "would you use this?" is a useless question. "when's the last time you dealt with this problem?" is gold.
+
+**key takeaway:** most conversations fail because people ask bad questions. good questions are about behavior, not opinions.
+
+---
+
+## tier 2: go deeper
+
+### never eat alone — keith ferrazzi (2005, updated 2014)
+the bible of relationship-building for ambitious people. ferrazzi's central argument: your network is your net worth, and the way to build one is through generosity, not transactionalism.
+
+**key concepts:**
+- the relationship action plan: systematically identify who you want to know and find ways to add value first
+- "pinging": regular, lightweight touchpoints (a relevant article, a congratulations note) — see [[relationship-maintenance]] for a modern system
+- conference behavior: arrive early, stay late, follow up within 24 hours
+
+**caveat:** heavy hustle-culture energy. filter for the structural advice and ignore the motivational filler.
+
+### how to win friends and influence people — dale carnegie (1936)
+90 years old and still the foundation. the core principles: become genuinely interested in other people, be a good listener, talk in terms of the other person's interests, make the other person feel important sincerely.
+
+the meta-lesson: focus outward, not inward. most social anxiety comes from self-focus. shifting attention to the other person solves 80% of it.
+
+### the art of gathering — priya parker (2018)
+the most thoughtful book on why most [[event-formats|events]] fail. parker's argument: gatherings fail because hosts don't make choices.
+
+**key principles:**
+- decide why you're gathering before anything else. "because we always do" is not a reason.
+- over-specify the purpose: "a dinner party" is vague. "a dinner for six people navigating career transitions" creates connection.
+- close the door: who you exclude defines the gathering as much as who you include.
+- don't be a "chill host" — people need structure and permission, not a blank canvas.
+
+---
+
+## articles & blog posts
+
+### [intentionally making close friends — neel nanda](https://www.neelnanda.io/blog/43-making-friends)
+the single best blog post on making friends as an adult. key frameworks:
+- **hits-based approach:** meet many people, filter quickly, invest deeply in the ones that click
+- **recursive curiosity:** ask open-ended questions, notice what excites you, follow up on that specific thing 3-4 times until you're in novel territory
+- **strategic vulnerability:** share small vulnerabilities throughout the conversation, not one big disclosure
+- **systematic follow-up:** get contact info, reach out within days, use a spreadsheet to track touch frequency
+
+the meta-insight: making friends is a skill, not a trait. you can get better at it through deliberate practice.
+
+### the double opt-in intro — various
+the gold standard for [[introductions]]. before introducing two people, ask both if they'd like to be introduced. include context about why. never blind-cc someone into a connection they didn't ask for.
+
+---
+
+## what not to read
+
+**most "networking" books** — they frame relationships as transactions and optimize for quantity over quality. if the advice boils down to "collect business cards," skip it. for building connections in digital spaces, see [[online-community]].
+
+**anything that promises "instant charisma"** — charisma is a byproduct of genuine interest in other people, confidence from competence, and presence. there's no hack.
\ No newline at end of file
new file mode 100644
index 0000000..3be7e1c
@@ -0,0 +1,140 @@
+---
+visibility: public-edit
+---
+
+# building a community from scratch
+
+practical guide to starting a community that actually lasts. based on real experience running Socratica, Build Chain, and observing what works in SF builder communities.
+
+the uncomfortable truth: most communities die within 3 months. the ones that survive have a clear format, a committed core, and a reason to keep showing up.
+
+---
+
+## the socratica model
+
+[socratica](https://www.socratica.info/) is a co-working community that started in waterloo and now runs in 40+ cities. the format is dead simple — and that's why it works.
+
+### the format
+1. **[[icebreakers|introductions]]** — everyone says who they are and what they're working on
+2. **work block 1** (50 min) — heads down, work on your passion project
+3. **work block 2** (50 min) — more work
+4. **demos** — casual show-and-tell. share what you made, even if it's a rough google doc
+5. **snacks** — hang out, talk about what you saw
+
+### why it works
+- **low barrier to entry:** you don't need to prepare anything. just show up and work.
+- **the demo creates accountability:** knowing you'll share something at the end makes the work block productive.
+- **weekly cadence builds habit:** every sunday, same time. people build it into their routine.
+- **self-selecting community:** the format attracts people who actually make things, not people who just talk about making things.
+- **no hierarchy:** there's no speaker, no panel, no "expert." everyone is equal in the room.
+
+### starting a chapter
+I started a socratica chapter at my school (december 2025). the key decisions:
+- pick a consistent day and time (sunday afternoons)
+- find a free venue (school, library, someone's house)
+- start with 5-8 people you personally invite
+- run the format exactly — don't improvise too much at first
+- demos are non-negotiable. they're what makes socratica socratica.
+
+---
+
+## lessons from build chain (what not to do)
+
+build chain was a project where 16 friends would relay-build a single project — each person adds something, then passes it to the next. the idea was creative and ambitious. the execution failed.
+
+### what went wrong
+- **insufficient buy-in:** people were invited to participate, but many didn't feel real ownership of the project. excitement at announcement ≠ commitment to execution.
+- **framing mismatch:** the organizer's enthusiasm didn't translate to participants understanding what they were signing up for. the concept needed to be sold, not just explained.
+- **too many people, too little structure:** with 16 people in a chain, any single dropout breaks the whole thing. the format was fragile by design.
+- **no fallback for momentum loss:** once a few people dropped off, there was no mechanism to recover.
+
+### the lesson
+community projects need more than a good idea — they need individual commitment secured before launch. the right sequence: 1) share the concept, 2) get explicit yes/no from each person, 3) only start when you have enough committed people with buffer for dropouts.
+
+---
+
+## what makes communities stick vs. die
+
+### communities that stick have:
+- **a recurring rhythm.** weekly or biweekly, same time, same place. monthly is too infrequent to build habit. quarterly is a conference, not a community.
+- **a clear format.** people know what to expect. socratica's intro → work → demo [[event-formats|format]]. sunday dinners' cook → eat → talk format. ambiguity kills attendance.
+- **a committed core.** 3-5 people who will show up no matter what. everyone else orbits the core. if the core disappears, the community dies.
+- **a shared identity.** "we're the people who build things on sundays." "we're the people who cook together." the identity is about what you do together, not just who you are.
+- **low cost to attend.** time and money. if it takes planning, people won't come consistently. if it costs money, you better be delivering clear value.
+
+### communities that die from:
+- **organizer burnout.** if one person does everything — venue, comms, facilitation, cleanup — they'll quit within 6 months. distribute the work or keep the format so simple that organizing is trivial.
+- **growing too fast.** individual [[relationship-maintenance]] matters more than group size. 5 committed people → 50 curious people → social dynamics shift → original members leave → new members don't stick → ghost town. grow slowly.
+- **loss of purpose.** "we're a community of builders" gradually becomes "we're a community of people who used to build things and now just hang out." either is fine, but the transition kills communities that don't acknowledge it.
+- **no filtering.** communities need some barrier to entry, even a small one. an RSVP, a question on the signup form, a friend-of-friend requirement. zero barriers → zero commitment.
+- **event-driven, not habit-driven.** if every gathering requires a special event or speaker, the community dies when the organizer stops booking speakers. the best communities are boring and consistent.
+
+---
+
+## the minimum viable community
+
+you need less than you think.
+
+**the absolute minimum:**
+- 5 people who said yes (not "maybe" — explicit yes)
+- a time and place (someone's living room works fine)
+- a format (even "we eat dinner and go around the table sharing highlights" counts)
+- a commitment to do it again next week
+
+**what you don't need:**
+- a website
+- a slack/discord
+- a logo
+- a mission statement
+- a venue with AV equipment
+- speakers or special guests
+- money
+
+the premature scaling trap: building infrastructure before you have a community to use it. don't set up a discord until you have 15+ people who already know each other. see [[online-community]] for when and how to add a digital layer. don't build a website until you have a waitlist problem.
+
+---
+
+## how to get the first 10 people
+
+### the personal invitation
+the #1 most effective strategy. text people individually. "hey, i'm starting a sunday co-working session for people who make things. first one is this sunday at 2pm at my place. want to come?"
+
+personal invitations work because:
+- they signal that you specifically want this person
+- they create social obligation (not manipulatively — genuinely)
+- they're harder to ignore than a mass email
+
+### the friend-of-friend ask
+"do you know anyone who'd be into this?" after each session, ask your attendees to bring one friend next time. organic growth through trusted connections.
+
+### the target list
+make a list of 20 people you'd love in this community. reach out to each one individually. expect a 30-50% yes rate. don't be discouraged by no's — some people aren't joiners.
+
+### the public posting (use sparingly)
+a tweet, a slack message in a relevant community, a post in a group chat. works for getting volume but not for getting commitment. anyone who shows up from a public post should be treated as a trial — they need to experience the value before they'll commit.
+
+### the anchor event
+host one great [[event-formats|event]] with a specific purpose. "i'm hosting a demo day for side projects — 5 people presenting, 15 watching, then drinks." use the energy from that event to recruit for the recurring community.
+
+---
+
+## scaling from 10 to 50
+
+once you have a working community of 10, growth is different:
+
+- **promote from within.** find 2-3 people who are as invested as you are. give them ownership of something — hosting duties, comms, a specific role. this is your insurance against organizer burnout.
+- **maintain the format.** the temptation is to "improve" things by adding speakers, panels, workshops. resist. the format is what people signed up for.
+- **create tiers of involvement.** not everyone needs to come every week. some people are core (every week), some are regulars (2x/month), some are occasional (monthly). all three are valid.
+- **introduce slowly.** when new people join, have a regular [[introductions|introduce them]] or pair them with someone. don't let newcomers feel lost in a group of friends.
+- **fork, don't bloat.** if your dinner party grows past 12, don't try to seat 20. start a second dinner. if your co-working session hits 30, encourage someone to start a tuesday edition.
+
+---
+
+## community builders worth studying
+
+- **socratica** — the co-working demo day format, now in 40+ cities
+- **build irl** — supports IRL club builders with tools and grants. their insight: 5 committed members beats 500 fleeting attendees. they emphasize membership, contribution, and "closing the door" on uncommitted attendees.
+- **sunday dinners** — the recurring meal-based gathering format
+- **south park commons** — SF community for people in transition, exploring what to build next
+- **the stoa** — online community built around philosophical dialogue
+- **recurse center** — "writer's retreat for programmers" — a masterclass in community design through self-selection and norms
\ No newline at end of file
new file mode 100644
index 0000000..25aeaac
@@ -0,0 +1,194 @@
+---
+visibility: public-edit
+---
+
+# event formats that work
+
+specific event formats that create genuine connection, tested by real communities. each one optimizes for a different thing — pick the format that matches your goal.
+
+---
+
+## co-working + demo (the socratica format)
+
+**goal:** productive work sessions with built-in accountability and community
+**group size:** 8-30
+**duration:** 3-4 hours
+**cadence:** weekly
+
+**the format:**
+1. introductions — name, what you're working on today (2 min total per person)
+2. work block 1 — 50 minutes of focused work
+3. short break — 5 minutes, stretch, get water
+4. work block 2 — 50 minutes
+5. demos — anyone can share what they worked on. rough is fine. google docs, napkin sketches, half-working prototypes all count.
+6. hang out — snacks, conversation, the social part
+
+**why it works:** the demo creates a natural reason to talk to each other. "hey, loved your demo — how did you approach [thing]?" is 10x better than "so... what do you do?" people bond over shared creative energy. the format also filters for doers over talkers.
+
+**failure modes:** skipping demos (then it's just a coworking space), making demos feel like presentations (keeps it casual or people get stage fright), not having snacks (people leave immediately after demos).
+
+---
+
+## the dinner party
+
+**goal:** deep conversation, intimacy, shared experience
+**group size:** 6-12 (8 is the sweet spot)
+**duration:** 2-4 hours
+**cadence:** weekly, biweekly, or monthly
+
+**the format (sunday dinners style):**
+1. cooking together (optional but powerful — shared labor builds bonds)
+2. sit-down dinner with intentional seating (mix people who don't know each other)
+3. a question or prompt for the table: "what are you most excited about right now?" or "what's a lesson you learned the hard way?"
+4. dessert/drinks — conversation flows naturally by this point
+
+**key decisions:**
+- **who cooks?** options: host cooks, everyone brings a dish (potluck), cook together. cooking together is the most bonding but the most chaotic.
+- **seating?** for 8+ people, assigned-ish seating prevents friend-clusters from forming. just put name cards out.
+- **conversation structure?** one prompt for the whole table works for 6-8 people. for 10+, you need a more structured round or the table fragments into side conversations.
+
+**the nick gray overlay:** apply the 2-hour cocktail party principles to dinner — name tags, structured [[icebreakers|icebreaker]] at the start, a hard end time.
+
+**failure modes:** too many people (kills intimacy), no conversation structure (defaults to weather/work chat), same people every time (becomes a friend group, not a community).
+
+---
+
+## the hackathon (social edition)
+
+**goal:** intense collaboration, making things together, energy
+**group size:** 15-60
+**duration:** 4-12 hours (or a full weekend)
+**cadence:** monthly or quarterly
+
+**the format:**
+1. arrivals + food
+2. pitch session — anyone with an idea pitches it in 60 seconds
+3. team formation — people join projects they're excited about
+4. build time — 3-8 hours of focused work
+5. demos — each team presents what they built
+6. voting/prizes (optional — can create energy but also competitiveness)
+7. social time
+
+**what makes it connection-oriented (not just a coding sprint):**
+- team formation is where the magic happens. working with strangers on a shared problem for 6 hours creates real bonds.
+- keep the pitches short and low-stakes. "i want to build X, who's in?" not a full slide deck.
+- provide food and drinks throughout. hungry people leave.
+- demos should celebrate effort, not polish.
+
+**failure modes:** too competitive (people optimize for winning, not connecting), solo builders (defeats the purpose), overly rigid themes (kills creativity).
+
+---
+
+## demo day
+
+**goal:** showcase work, create serendipitous connections, celebrate builders
+**group size:** 20-100
+**duration:** 2-3 hours
+**cadence:** monthly or quarterly
+
+**the format:**
+1. 5-8 presenters, each gets 5-7 minutes + 3 minutes Q&A
+2. break between presentations for mingling
+3. social hour after all presentations
+
+**what makes it work:**
+- curate the presenters. a mix of stages (early idea → shipped product) keeps it interesting.
+- the audience should be 3-5x the number of presenters. enough to create energy, not so many that it feels like a conference.
+- the break between presentations is where connections happen. don't rush through.
+- demos should show the thing, not talk about the thing. screen shares, live demos, physical prototypes.
+
+**failure modes:** too many presenters (audience fatigues after 8), no social time (people sit, watch, leave), presenters who pitch instead of demo.
+
+---
+
+## the unconference
+
+this format also works for [[online-community|virtual gatherings]] with breakout rooms replacing physical spaces.
+
+**goal:** participant-driven discussion, emergent topics, distributed leadership
+**group size:** 20-100
+**duration:** half day or full day
+**cadence:** quarterly or annual
+
+**the format (open space technology):**
+1. opening circle — everyone gathers. the facilitator explains the rules.
+2. marketplace — anyone can propose a session topic. write it on a sticky note, announce it to the group, put it on the schedule board.
+3. sessions — multiple sessions run in parallel. each session is 30-60 minutes.
+4. closing circle — reconvene, share takeaways.
+
+**the law of two feet:** if you're in a session and you're not learning or contributing, leave and go to another one. this is the core rule — it gives people permission to follow their energy.
+
+**the four principles:**
+1. whoever comes are the right people
+2. whatever happens is the only thing that could have
+3. whenever it starts is the right time
+4. when it's over, it's over
+
+**why it works:** no pre-planned speakers means topics are exactly what the group cares about right now. the law of two feet prevents dead sessions from holding people hostage.
+
+**failure modes:** no one proposes sessions (prime the pump with 3-4 pre-planned topics), too many sessions (limit to 3-4 parallel tracks), no closing circle (people miss the synthesis).
+
+---
+
+## dorm lectures / salon
+
+**goal:** intellectual conversation, learning, meeting people through ideas
+**group size:** 10-30
+**duration:** 1.5-2 hours
+**cadence:** weekly or biweekly
+
+**the format:**
+1. one person presents a topic they're deeply interested in (15-20 minutes). not a polished talk — more like "here's what i've been thinking about."
+2. open discussion (30-40 minutes). the presenter facilitates but doesn't dominate.
+3. social time — drinks, snacks, continued conversation.
+
+**what makes it work:**
+- the presenter doesn't need to be an expert. "i've been reading about [topic] and here's what confused me" is a better talk than a TED-style polished presentation.
+- the discussion should feel like a conversation, not a Q&A. the presenter's job is to ask good questions back.
+- rotating presenters means everyone gets a chance to share their obsessions.
+
+**failure modes:** only one person ever presents (becomes a lecture series, not a community), discussion gets dominated by one voice (facilitator needs to actively redirect), topics are too niche (audience can't engage).
+
+---
+
+## the walk-and-talk
+
+**goal:** deep 1-on-1 conversation, relationship building
+**group size:** 2 (or small groups of 3-4)
+**duration:** 45-90 minutes
+**cadence:** as needed
+
+**the format:** meet somewhere. walk. talk. that's it.
+
+**why it's underrated:**
+- side-by-side conversation removes the intensity of face-to-face
+- movement creates energy and reduces awkwardness
+- no phones (hard to text and walk)
+- natural end point when the walk ends
+- fresh air and nature are genuinely good for conversation quality
+
+**when to use:** reconnecting with someone after a long gap, having a difficult conversation, getting to know someone new without the pressure of a "meeting," [[relationship-maintenance|relationship repair]].
+
+---
+
+## format comparison
+
+| format | best for | group size | prep required | connection depth |
+|---|---|---|---|---|
+| co-working + demo | builder communities | 8-30 | low | medium |
+| dinner party | intimate groups | 6-12 | medium | high |
+| hackathon | high-energy collaboration | 15-60 | high | medium-high |
+| demo day | showcasing work | 20-100 | medium | low-medium |
+| unconference | large group discussion | 20-100 | low | medium |
+| salon/dorm lecture | intellectual community | 10-30 | medium | medium-high |
+| walk-and-talk | deep 1-on-1 | 2-4 | none | very high |
+
+---
+
+## meta-principles for any format
+
+1. **have a hard end time.** people commit more easily when they know when it ends. "7-9pm" is better than "7pm onwards."
+2. **feed people.** food is social lubricant. it doesn't need to be fancy — chips and salsa work.
+3. **name tags at 15+ people.** nobody remembers 15 names. don't make them pretend.
+4. **someone has to be the host.** not the "chill host" who lets things happen — an active host who starts the icebreaker, redirects conversation, makes [[introductions]]. priya parker's rule (from [[books-resources|The Art of Gathering]]): a gathering without a host is just people in a room.
+5. **create a reason to return.** "same time next week" is the most powerful sentence in [[building-community|community building]].
\ No newline at end of file
new file mode 100644
index 0000000..7b1bb0b
@@ -0,0 +1,190 @@
+---
+visibility: public-edit
+---
+
+# icebreakers & conversation starters
+
+a curated collection of the best icebreakers, conversation games, and connection tools — tested in real settings, not from a corporate HR handbook.
+
+the goal of any icebreaker is the same: get people past the "what do you do" loop and into a real conversation. the best ones feel natural, not forced. but icebreakers are just the beginning — see [[relationship-maintenance]] for what comes after the first conversation.
+
+---
+
+## the nick gray icebreaker (the 2-hour cocktail party)
+
+from nick gray's [[books-resources|book]] *The 2-Hour Cocktail Party*. the simplest, most reliable icebreaker for events of 15-50 people.
+
+**format:** everyone goes around and shares three things:
+1. their name
+2. what they do during the day
+3. one fun or interesting fact about themselves
+
+**why it works:** the "interesting fact" gives everyone a conversational hook. after the round, people approach each other based on facts that resonated — natural [[introductions]] happen organically. it's low-stakes, fast, and gives wallflowers a reason to talk to someone.
+
+**when to use:** house parties, networking events, [[event-formats|dinner parties]], any group of 10+. works best when the host explicitly pauses the room and runs it.
+
+**tip:** as the host, go first and model vulnerability with your fun fact. "i collect vintage typewriters" is better than "i like traveling."
+
+---
+
+## 36 questions for increasing closeness (arthur aron)
+
+from a 1997 psychology study by arthur aron. pairs of strangers who went through these questions felt closer than most long-term acquaintances. the study made people fall in love — literally.
+
+the questions escalate through three sets, from light to deeply personal.
+
+### set I (surface)
+1. given the choice of anyone in the world, whom would you want as a dinner guest?
+2. would you like to be famous? in what way?
+3. before making a telephone call, do you ever rehearse what you are going to say? why?
+4. what would constitute a "perfect" day for you?
+5. when did you last sing to yourself? to someone else?
+6. if you could live to the age of 90 and retain either the mind or body of a 30-year-old for the last 60 years, which would you want?
+7. do you have a secret hunch about how you will die?
+8. name three things you and your partner appear to have in common.
+9. for what in your life do you feel most grateful?
+10. if you could change anything about the way you were raised, what would it be?
+11. take four minutes and tell your partner your life story in as much detail as possible.
+12. if you could wake up tomorrow having gained any one quality or ability, what would it be?
+
+### set II (mid-depth)
+13. if a crystal ball could tell you the truth about yourself, your life, the future, or anything else, what would you want to know?
+14. is there something you've dreamed of doing for a long time? why haven't you done it?
+15. what is the greatest accomplishment of your life?
+16. what do you value most in a friendship?
+17. what is your most treasured memory?
+18. what is your most terrible memory?
+19. if you knew that in one year you would die suddenly, would you change anything about the way you are now living? why?
+20. what does friendship mean to you?
+21. what roles do love and affection play in your life?
+22. alternate sharing something you consider a positive characteristic of your partner. share a total of five items.
+23. how close and warm is your family? do you feel your childhood was happier than most other people's?
+24. how do you feel about your relationship with your mother?
+
+### set III (deep)
+25. make three true "we" statements each. for instance, "we are both in this room feeling..."
+26. complete this sentence: "i wish i had someone with whom i could share..."
+27. if you were going to become a close friend with your partner, please share what would be important for them to know.
+28. tell your partner what you like about them; be very honest this time, saying things you might not say to someone you've just met.
+29. share with your partner an embarrassing moment in your life.
+30. when did you last cry in front of another person? by yourself?
+31. tell your partner something that you like about them already.
+32. what, if anything, is too serious to be joked about?
+33. if you were to die this evening with no opportunity to communicate with anyone, what would you most regret not having told someone? why haven't you told them yet?
+34. your house catches fire. after saving loved ones and pets, you have time to save one item. what would it be? why?
+35. of all the people in your family, whose death would you find most disturbing? why?
+36. share a personal problem and ask your partner's advice on how they might handle it.
+
+**when to use:** 1-on-1 or pairs at a dinner. don't try to do all 36 at once — pick 5-10 from different sets based on how deep you want to go. set I questions are great warm-ups for any dinner party.
+
+**tip:** the magic is in the escalation. start with set I, and by the time you hit set III people are genuinely sharing. skipping straight to set III feels invasive.
+
+---
+
+## we're not really strangers
+
+a card game designed for deepening connection. three levels that escalate from perception to connection to reflection.
+
+**level 1 — perception:** surface-level but surprisingly revealing questions. "what's one thing you'd change about yourself?" "what do you think my love language is?"
+
+**level 2 — connection:** the meat of the game. "what's been your biggest struggle lately?" "what do you wish more people understood about you?" "when was the last time you felt truly seen?"
+
+**level 3 — reflection:** the deepest level. "what's one thing you want to tell me but haven't?" "what surprised you most about this conversation?"
+
+**wildcard prompts:** action-oriented cards like "write down what you'd text this person at 2am" or "tell me something you've never told anyone."
+
+**when to use:** small groups (2-6), dinner parties, dates, close friend hangs. avoid using it with people who didn't opt in — the depth can feel forced if someone's not ready.
+
+**variants:** there are expansion packs (honest dating, inner child, self-reflection, race & privilege). the TKS/builder variant swaps in questions about ambition, craft, and creative process.
+
+---
+
+## authentic relating games
+
+a collection of exercises from the Authentic Relating movement. these go deep fast — use them with groups that are ready for vulnerability.
+
+### hot seat
+one person sits in the center. the group asks them questions for 5-10 minutes. the person in the hot seat can pass on any question. what makes it powerful: the group learns to ask questions they actually want answered, and the person learns what they're willing to share.
+
+### noticing
+pairs face each other. one person says "i notice..." followed by something they observe about the other person — body language, energy, expression, clothing. the other person responds with how that lands. "i notice you seem relaxed" / "hearing that, i feel seen." builds the muscle of articulating what you're actually perceiving.
+
+### curiosity
+one person shares something. the listener responds only with "i'm curious about..." statements. no advice, no stories about themselves. forces deep listening and follow-up rather than the standard conversational tennis.
+
+### fish bowl
+a small group (3-4) has a conversation in the center of a larger circle. the outer circle observes silently. afterward, the observers share what they noticed. creates a meta-awareness of how conversations work.
+
+### two truths and a desire
+variation on two truths and a lie. instead of a lie, share something you deeply desire. "i've traveled to 12 countries, i speak three languages, and i want to write a novel before i'm 30." the desire reveals more than a lie ever would.
+
+**when to use:** retreats, close-knit groups, communities that have already built some trust. for lighter-touch connection in digital spaces, see [[online-community]]. not for networking events or first meetings — the vulnerability is too high for strangers who didn't sign up for it.
+
+---
+
+## askhole
+
+a rapid-fire question game where you answer honestly and quickly. the speed prevents overthinking — you get raw, unfiltered responses.
+
+**format:** one person reads questions from a list. the other person answers immediately — no pausing to think. questions range from silly to deep.
+
+**sample questions:**
+- what's a hill you'd die on?
+- who's your celebrity hall pass?
+- what's a belief you held strongly that turned out to be wrong?
+- if you could have dinner with any historical figure, who?
+- what's the most embarrassing thing you've googled?
+- what's something you pretend to understand but don't?
+- what would your TED talk be about?
+
+**when to use:** car rides, casual hangs, dates. good for groups of 2-4. the rapid-fire format keeps it fun and prevents it from getting too heavy.
+
+---
+
+## more good ones
+
+### "what are you excited about right now?"
+the single best replacement for "what do you do?" — it gets at what someone actually cares about, not their job title. from neel nanda's making friends guide.
+
+### the rose, bud, thorn
+each person shares a rose (something good), a bud (something they're looking forward to), and a thorn (something challenging). simple but effective for groups that meet regularly — it becomes a ritual.
+
+### "if you could have any superpower for a day..."
+sounds childish. works every time. the answer reveals values — flying = freedom, time travel = regret/curiosity, telepathy = connection/trust issues.
+
+### speed meeting
+like speed dating but for making friends. 3-minute conversations, then rotate. give people a single question to start with. works for events of 20+.
+
+### the highlight reel
+each person shares the highlight of their week in 30 seconds. fast, positive, creates shared context. good for recurring groups.
+
+---
+
+## context guide: which icebreaker for which setting
+
+| setting | best icebreakers |
+|---|---|
+| large event (20+) | nick gray format, speed meeting, highlight reel |
+| dinner party (6-12) | 36 questions (set I-II), we're not really strangers, rose/bud/thorn |
+| small group (3-5) | authentic relating games, we're not really strangers, askhole |
+| 1-on-1 | 36 questions, "what are you excited about?", askhole |
+| recurring group | rose/bud/thorn, highlight reel, hot seat rotation |
+| first meeting | nick gray format, "what are you excited about?", superpower question |
+
+---
+
+## anti-patterns: what not to do
+
+**"let's go around and say your name and a fun fact"** — without structure, this produces anxiety and forgettable facts. nick gray's version works because it includes "what you do during the day" as scaffolding.
+
+**two truths and a lie** — sounds good in theory. in practice, people pick obscure truths that don't spark conversation and the lie-detection game overshadows actual connection.
+
+**"tell us something nobody knows about you"** — too much pressure, too high stakes for a group that just met. you'll get either boring answers or oversharing.
+
+**forced physical contact** — trust falls, group hugs, hand-holding circles. never do this with people who haven't explicitly opted in.
+
+**going too deep too fast** — jumping straight to "what's your biggest fear?" with strangers feels like an interrogation, not connection. the magic of good icebreakers is the escalation. a well-run icebreaker is the first step to [[building-community|building real community]].
+
+**the interviewer trap** — asking rapid-fire questions without sharing anything yourself. connection requires reciprocity. if you ask three questions, share something back.
+
+**"so what do you do?"** — the default conversation opener in every networking event. it's not terrible, but it immediately frames the conversation in terms of professional status. "what are you excited about right now?" gets to the same place without the hierarchy.
\ No newline at end of file
new file mode 100644
index 0000000..e4b2502
@@ -0,0 +1,138 @@
+---
+visibility: public-edit
+---
+
+# the art of the introduction
+
+introducing people well is one of the highest-leverage social skills. see [[books-resources]] for books that go deeper on connection. a good introduction creates a new relationship. a bad one wastes two people's time and spends your social capital.
+
+---
+
+## the double opt-in intro
+
+the single most important rule of introductions: **ask both people before connecting them.**
+
+### how it works
+1. you think person A and person B should know each other
+2. message person A: "hey, i know someone named [B] who [relevant context]. i think you two would hit it off because [specific reason]. would you be up for an intro?"
+3. wait for person A to say yes
+4. message person B with the same pitch
+5. wait for person B to say yes
+6. only then send the intro email/message
+
+### why this matters
+- respects both people's time and inbox
+- gives both people context and a reason to engage
+- lets someone gracefully decline without the awkwardness of being on a cc'd email they didn't want
+- preserves your reputation as someone who makes quality introductions
+
+### the blind intro problem
+the alternative — just cc'ing two people and saying "you two should meet!" — puts both people in an awkward position. neither asked for this. neither has context. someone has to do the work of figuring out why they're talking. it's lazy and it burns social capital.
+
+---
+
+## the anatomy of a good introduction
+
+a great intro email/message has four parts:
+
+### 1. context about each person
+not a resume. a human description of what they're about and why they're interesting.
+
+**bad:** "meet sarah — she's a product manager at google."
+**good:** "meet sarah — she's been thinking a lot about how AI changes the way teams make decisions. she ran a bunch of experiments at google on this."
+
+### 2. why these two specifically
+the connection should be obvious and specific. if you can't articulate why they should meet, don't introduce them.
+
+**bad:** "you're both in tech, so you should chat!"
+**good:** "you're both building tools for community organizers and approaching it from completely different angles — i think comparing notes would be genuinely useful."
+
+### 3. a suggested next step
+don't leave it open-ended. give them something to do.
+
+**bad:** "i'll let you two take it from here!"
+**good:** "sarah, maybe you could share that doc you mentioned about your AI experiment results? i think marcus would find it directly relevant to what he's building."
+
+### 4. a graceful exit
+after sending the intro, get out of the way. you don't need to be in the conversation.
+
+**template:**
+> hey [A] and [B],
+>
+> wanted to connect you two. [A] — [1-2 sentences about B and what they're working on]. [B] — [1-2 sentences about A and what they're working on].
+>
+> i think you'd have a great conversation about [specific topic] because [specific reason].
+>
+> i'll let you two take it from here — [suggested next step].
+
+---
+
+## when NOT to introduce people
+
+### they didn't ask
+if someone doesn't want to meet new people right now, respect that. some people are in heads-down mode and another "you should meet..." email is noise.
+
+### the connection is vague
+"you're both interesting" is not a reason. "you're both in SF" is not a reason. if the only connection is demographic or geographic, skip it.
+
+### one person is way more senior
+introducing a college student to a CEO with "you should chat!" puts the senior person in an uncomfortable position. they get 50 of these a week. if you're going to make an asymmetric intro, there needs to be a clear value proposition for the senior person — not just "this person wants your advice."
+
+### you're doing it to seem connected
+if the intro is more about you looking like a connector than about genuine value for both people, they can tell. stop.
+
+### you don't know both people well enough
+if you haven't had a real conversation with both people, you don't have enough context to make a quality introduction. introducing two people based on their linkedin profiles is a waste of everyone's time.
+
+---
+
+## the pre-conversation questionnaire ("basic info exchanger")
+
+an idea for structured intros: before two people meet, they each fill out a brief form with basic context. eliminates the first 10 minutes of "so what do you do?" — a structured alternative to [[icebreakers]]
+
+### what to include
+- what you're working on right now
+- what you're most excited about
+- what you're looking for (advice, collaborators, friends, customers)
+- one thing you'd love to talk about
+- one thing you can help with
+
+### when this makes sense
+- before a structured [[event-formats|networking event]] (send the form to all attendees, share responses)
+- before a double opt-in intro (include each person's answers in the intro)
+- before a 1-on-1 coffee meeting with someone you don't know well
+
+### when this is overkill
+- casual social settings
+- meeting friends of friends
+- any context where filling out a form would feel weird
+
+---
+
+## being introduced well
+
+the other side of the equation: how to behave when someone introduces you.
+
+### respond quickly
+whether the intro happens over email or in an [[online-community|online community]], reply within 24 hours. even if it's just "thanks for connecting us! [person], would love to chat — here's my calendly / how about tuesday?"
+
+### reference the connector
+"[connector] mentioned you're working on [thing] — i'd love to hear more about that." this validates the intro and gives the conversation a starting point.
+
+### actually follow through
+this is where [[relationship-maintenance]] begins. if you agree to meet, meet. canceling or ghosting after someone vouched for you burns the connector's social capital, not just yours.
+
+### report back
+after the meeting, text the connector: "hey, great intro — we had a really good conversation about [topic]. thanks for connecting us." this is uncommon enough that it makes you memorable and encourages more intros.
+
+---
+
+## becoming known as a great introducer
+
+if you consistently make high-quality introductions, people start sending opportunities your way — you become a hub for [[building-community|community]] — because they know you'll connect them to the right person.
+
+**the key:** quality over quantity. 3 great introductions per month > 20 random ones. every bad intro dilutes your reputation as a connector.
+
+**the habit:** when you meet someone interesting, ask yourself: "who do i know that this person should meet?" if someone comes to mind immediately and the reason is specific, file it away and make the intro (double opt-in, always).
+
+**the signal:** the best connectors are the ones who introduce people with zero expectation of anything in return. if you're keeping score, you're doing it wrong.
\ No newline at end of file
new file mode 100644
index 0000000..e23bc3d
@@ -0,0 +1,124 @@
+---
+visibility: public-edit
+---
+
+# online community building
+
+[[building-community|building community]] in digital spaces is a different game than IRL. the tools are different, the failure modes are different, and the bar for what "connection" means is lower. but online communities can be powerful — especially as a complement to in-person gatherings.
+
+---
+
+## discord server design
+
+discord is the default platform for builder/creator communities. it's flexible, free, and most people under 30 already have an account. but most discord servers are ghost towns.
+
+### what works
+
+**fewer channels, more activity.** the #1 mistake is creating 30 channels on day one. nobody posts in #random-thoughts and #cool-links and #introduce-yourself when there are 12 members. start with 3-4 channels max:
+- **#general** — the main feed. everything goes here until the volume justifies splitting.
+- **#introductions** — new members post who they are and what they're working on. pin good ones.
+- **#showcase** — share what you've built or are building. the discord equivalent of socratica demos.
+- **#resources** — links, articles, tools people find useful.
+
+add channels only when an existing channel has too much volume on a specific topic.
+
+**daily or weekly prompts.** a scheduled message that asks a question: "what are you working on this week?" or "what's one thing you learned recently?" — these are digital [[icebreakers]] gives people a low-barrier reason to post. the first few weeks, the organizer answers their own prompts to model participation.
+
+**voice channels used regularly.** text-only communities feel transactional. schedule a weekly "open office hours" or "co-working voice channel" — adapting [[event-formats|IRL event formats]] to digital where people drop in and work together with mics on. the ambient presence of other people working is powerful.
+
+**roles that mean something.** don't create 15 vanity roles. roles should indicate something useful: what someone's working on, what they can help with, whether they're a new or established member.
+
+### what kills discord servers
+
+- **too many channels too early** — the graveyard effect. 20 empty channels signals "nobody is here."
+- **no moderation norms** — one bad actor can poison the vibe. set norms early and enforce them.
+- **announcements-only energy** — if the admins only post announcements and never engage in conversation, it feels like a broadcast channel, not a community.
+- **no regular cadence** — without recurring events (weekly calls, daily prompts, monthly demos), the server has no heartbeat.
+
+---
+
+## slack community dynamics
+
+slack is better for professional/industry communities. it feels more "work" and less "hangout" than discord — which can be a feature or a bug.
+
+### what works
+
+**threading culture.** the single biggest difference between good and bad slack communities. if every conversation happens in the main channel, it becomes unreadable. communities that use threads well stay useful at scale.
+
+**focused, high-signal channels.** slack communities that thrive tend to have:
+- a #jobs channel (people share and find opportunities)
+- a #help channel (ask questions, get answers)
+- a #launches channel (share what you shipped)
+- a #introductions channel
+
+the value proposition is clear: you get access to a network, opportunities, and knowledge.
+
+### what kills slack communities
+
+- **notification fatigue** — if every channel is active, members mute the workspace and never come back.
+- **no clear value.** "a slack for [demographic]" isn't enough. people need a reason to check it daily.
+
+---
+
+## twitter/X community building
+
+twitter isn't a "community platform" in the traditional sense, but some of the strongest communities emerge from twitter interactions.
+
+### how it works
+
+**the reply-first strategy.** you don't build a twitter community by posting — you build it by engaging with other people's posts. thoughtful replies on someone's thread get you noticed faster than your own thread.
+
+**the small group DM.** twitter group DMs of 5-15 people are some of the tightest communities online. they're invite-only, high-trust, and often more honest than any public conversation.
+
+**building in public.** sharing your work, learnings, and failures publicly attracts people on a similar path. public work leads to organic [[introductions]]. "here's what i built this week" tweets create a breadcrumb trail that like-minded people follow.
+
+### what doesn't work
+
+- **engagement farming.** "like this tweet if you agree!" feels hollow. people who optimize for engagement metrics rarely build real communities.
+- **growth hacking.** follow-for-follow, engagement pods, and viral thread templates build numbers, not community.
+- **being always-on.** the platform is designed to be addictive — don't let it consume you.
+
+---
+
+## online + IRL: the hybrid model
+
+the strongest communities have both an online and in-person presence. the online space keeps the community alive between events — a form of [[relationship-maintenance]] at scale. the in-person events create the depth that online can't.
+
+**the pattern:**
+- IRL events create the foundation of trust and shared experience
+- the online space maintains the connection between events
+- online conversations surface topics for the next IRL gathering
+- IRL relationships make online conversations richer (you're texting with people you've actually met)
+
+socratica has a discord for coordination, but the real community happens in-person on sundays. builder communities often have a slack for async collaboration and monthly in-person demos.
+
+**the trap:** substituting online activity for IRL presence. if your "community" is just a discord server, it's a chat room. the in-person component is what makes it a community.
+
+---
+
+## moderation
+
+communities die from two moderation extremes:
+- **too little:** one toxic member drives away ten good members. by the time you act, the culture is already damaged.
+- **too much:** over-moderation kills spontaneity. if every message feels policed, people stop posting anything real.
+
+clear rules published upfront (3-5 rules max), consistent enforcement, and a culture where members self-moderate by modeling good behavior.
+
+---
+
+## platform dependency
+
+building your community entirely on someone else's platform means you're one policy change away from losing everything. own an email list. have a backup communication channel. the community is the people, not the tool. see [[books-resources]] for deeper thinking on gathering design.
+
+---
+
+## tools comparison
+
+| platform | best for | group size | depth of connection | effort to maintain |
+|---|---|---|---|---|
+| discord | builder/creator communities, gaming, under-30 | 10-5000 | medium | medium |
+| slack | professional/industry communities | 50-5000 | medium | medium-high |
+| twitter/X | public community building, thought leadership | unbounded | low-medium | high |
+| group DMs (any platform) | tight inner circles | 5-15 | high | low |
+| email list | announcements, long-form, resilient | unbounded | low | low |
+| whatsapp/signal group | local groups, family, close friends | 5-50 | medium-high | low |
\ No newline at end of file
new file mode 100644
index 0000000..3e990a8
@@ -0,0 +1,112 @@
+---
+visibility: public-edit
+---
+
+# relationship maintenance systems
+
+how to actually maintain relationships at scale without it feeling like a chore. [[building-community|building a community]] gets people in the door; this page is about keeping them close. the system should feel like a natural extension of caring about people, not a sales pipeline.
+
+---
+
+## the tiered relationship system
+
+not all relationships need the same frequency. trying to maintain weekly contact with 100 people will burn you out and annoy half of them. instead: tier your relationships by desired frequency.
+
+### the tiers
+
+**tier 1 — weekly (5-10 people)**
+your closest people. the ones you'd call at 2am. this tier doesn't need a system; it happens naturally. if it's not happening, the relationship might not be tier 1.
+
+**tier 2 — monthly (15-25 people)**
+strong relationships that need regular watering. a monthly check-in keeps these warm. a text, a voice memo, grabbing coffee, sending them something relevant.
+
+**tier 3 — quarterly (30-50 people)**
+people you like and respect but don't need frequent contact with. a quarterly ping — "saw this and thought of you," "how's [specific thing] going?" — keeps the connection alive.
+
+**tier 4 — annual (50-100+ people)**
+the long tail. a birthday message, a holiday note, a congratulations on a life event. the goal isn't deep connection — it's keeping the door open.
+
+### the math
+at these frequencies, maintaining 124 contacts looks like:
+- 8 tier 1 × weekly = 8 touches/week
+- 20 tier 2 × monthly = 5 touches/week
+- 40 tier 3 × quarterly = 3 touches/week
+- 56 tier 4 × annual = 1 touch/week
+
+that's ~17 touchpoints per week, or about 2-3 per day. most of these are a quick text. totally doable.
+
+---
+
+## what a "touchpoint" actually looks like
+
+this is not about sending generic "checking in!" messages. each tier has natural touchpoint styles.
+
+### low-effort, high-signal
+- **the relevant share:** "saw this article about [their interest] and thought of you" — shows you remember what they care about
+- **the reaction:** reply to their instagram story or tweet with something specific, not just an emoji — [[online-community|online interactions]] count as real touchpoints
+- **the congratulations:** "congrats on [specific thing]" when they post about a milestone
+- **the recommendation:** "you should check out [thing] — feels right up your alley"
+
+### medium-effort
+- **the voice memo:** 60 seconds of genuine update. more personal than text, less commitment than a call.
+- **the question:** "hey, you know a lot about [topic] — quick question: [question]." people love being asked for their expertise.
+- **the invite:** "i'm going to [[event-formats|an event]] on friday — want to come?" including people is the easiest form of generosity.
+- **the introduction:** "you and [person] should know each other because [specific reason]." — see [[introductions]] for the full double opt-in playbook.
+
+### high-effort (reserve for tier 1-2)
+- **the gift:** doesn't need to be expensive. a book you loved, something related to their hobby, a joke gift referencing an inside joke.
+- **the in-person visit:** traveling to see someone, or making time when you're in their city.
+
+---
+
+## tracking with Dex
+
+I use Dex as my personal CRM — 124+ contacts, tiered. it syncs with linkedin, email, and social media, auto-updates contact info when people change jobs. the browser extension integrates with linkedin and gmail so you can add notes in context.
+
+the columns that matter most:
+- tier (1-4)
+- last contacted / next contact due
+- what they care about (the most important column)
+- open threads (things you talked about that you can follow up on)
+
+if a full CRM feels heavy, a spreadsheet with these same columns works fine. the tool matters less than the habit. see [[books-resources]] for deeper reading on relationship systems.
+
+---
+
+## deliberate relationship repair
+
+sometimes relationships drift or break. the instinct is to let them fade, but many are worth repairing — especially when the distance was circumstantial, not personal.
+
+### the startup internship experience
+during a neurotech startup internship, relationships with a couple of teammates needed repair. the approach that worked: **one-on-one walks.** not a confrontation, not a group setting. walking side by side, talking about what happened, no agenda beyond reconnecting.
+
+### why walks work for repair
+- side-by-side is less confrontational than face-to-face
+- movement reduces tension
+- no time pressure (unlike a scheduled meeting)
+- the physical activity gives you something to do during silences
+
+### the repair framework
+1. **acknowledge the gap.** "we haven't talked in a while. i wanted to change that." simple, direct, no guilt-tripping.
+2. **take responsibility for your part.** even if it's just "i should have reached out sooner." this creates safety.
+3. **ask, don't assume.** "how have you been? what's been going on?" don't project your narrative onto their experience.
+4. **make the next step concrete.** "want to grab coffee next wednesday?" vague "we should hang out" goes nowhere.
+
+### when not to repair
+- if the relationship was actually toxic
+- if the other person has clearly signaled they don't want contact
+- if you're only reaching out because you need something
+
+---
+
+## common failure modes
+
+**over-systematizing:** if your CRM feels like a sales funnel, you've gone too far. the system should remind you to reach out. the actual interaction should be genuine.
+
+**frequency mismatch:** reaching out weekly to someone who's a quarterly relationship feels like stalking. if someone takes 2 weeks to respond, they're probably tier 3-4, not tier 1-2.
+
+**the "checking in" trap:** "hey, just checking in!" is the emptiest possible message. always include something specific — a question, a share, a reference to something you last talked about.
+
+**guilt spirals:** you'll miss weeks. you'll let touchpoints slip. don't let guilt about a missed month turn into six months of avoidance. just reach out. "it's been a while — been thinking about you" always works.
+
+**treating it like networking:** the goal is not to "build a network." the goal is to maintain relationships with people you genuinely care about. if you're reaching out to someone only because they might be useful, stop. they can tell.
\ No newline at end of file