Metlivi Blog

How to Turn a Character’s Important Relationships Into Adventure Leads

A character’s important relationships become useful adventure leads when they point toward a clear action, a place to go, a question to answer, or a choice to make. Start with someone the character cares about, decide what that person wants or needs right now, and connect it to something the party can do together. A relationship should give the group an invitation into the story, not dictate how a player must respond.

October 09, 20267 min readReading, Arts & CultureBy Metlivi Editorial Team
Section 1

Start with a relationship the player wants in the story

List a few people connected to the character: an old teacher, a longtime companion, a friendly rival, a craft partner, or a neighbor from home. For each, note the relationship in one line and one detail the character values. For example: “Mira, my former mapmaking mentor; she trusted me with unfinished charts.” That detail is more useful than a long biography because it suggests what might matter in a scene.

Ask the player which relationships they would enjoy seeing in play and whether any should stay in the background. A backstory connection can motivate a character, but it should not become a surprise demand placed on the player. D&D Beyond’s guidance on character bonds describes them as connections to people, places, and events that can drive goals, while its relationship guide recommends checking whether another player is interested before establishing a closer character bond. D&D Basic Rules: Personality and Background, New Player’s Guide: Character Relationships

Section 2

Give the person a present-tense goal

A relationship turns into an adventure lead when something is happening now. Give the NPC a concrete goal that can create a scene: find a missing survey marker, deliver a sealed invitation, protect a traveling puppet troupe’s stage, or recover a box of handwritten songs before a festival. The goal need not be urgent or dangerous. It does need to be specific enough that the players can decide what to do.

Try this prompt: “The person wants before , because .” For example: “Mira wants the party to find the brass survey marker before the spring caravan leaves, because it points to a safe pass through the hills.” This identifies a task, a time cue and a reason. It also leaves room for the party to ask questions or suggest a different approach.

Section 3

Turn the goal into an actionable hook

A useful lead gives the players a first move. The NPC might ask directly, send a note, leave an unfinished map at a familiar meeting place, or appear at a location the party already plans to visit. Include one immediate clue or decision: a marked trail, a missing delivery, a timetable, or two possible routes. Avoid making the players guess what the adventure is about before they can engage with it.

For Mira’s marker, the party could choose to search the abandoned tollhouse, question the caravan guide who last saw it, or examine her incomplete map. Each option starts play and can lead to more information. The adventure does not need to depend on a single correct clue or one required route. The Alexandrian’s discussion of backstory-based scenarios suggests drawing on character goals and relationships to create motivated scenarios, while its long-term hook advice describes connecting new adventures to allies and existing campaign continuity. GM Don’t List #19: Ignoring Character Backstories, Random GM Tip: Long-Term Scenario Hooks

Section 4

Add a complication that changes the situation

A relationship lead gains momentum when the goal is not immediately straightforward. Add one complication that creates a playable obstacle or choice. Maybe a second explorer found the marker and believes it belongs in a local museum. Maybe the safe pass is open only during daylight. Maybe the marker is intact but has been moved to a spot that makes Mira’s map unreliable.

Keep the complication connected to the task. A surprise unrelated to the relationship can feel like a detour; a complication that tests the characters’ understanding of the person can reveal something interesting. For example, Mira asks the party to retrieve the marker, but the guide who has it says she gave it away years ago to keep travelers from using a route that crosses a nesting ground. Now the party can ask Mira about the old decision and choose what to do with the new information.

In games that use character aspects, this kind of complication can be framed through the rules. The Fate Core cheat sheet describes a compel as accepting a complication tied to an aspect, with a fate point as part of that system’s procedure. That is a Fate rule, not a universal roleplaying-game mechanic; in another system, use its own rules or simply present the situation as a choice. Fate Core Cheat Sheet and Veterans’ Guide

Section 5

Make the relationship matter during play

Let the NPC’s presence shape the adventure beyond the initial request. Give the person a recognizable way to speak or act, a piece of relevant knowledge, and a limitation. Mira might sketch directions from memory, but she cannot travel with the party because she is preparing the caravan’s route. These details make her useful without making her a solution machine.

Give the party chances to interact with the relationship through their choices. They might ask Mira for context, reassure her, disagree with her plan, or bring back an unexpected result. The relationship then changes through play rather than being a fixed piece of backstory. D&D Beyond’s backstory advice notes that a background can provide a storytelling prompt to develop with the game master, such as a contact who can share or seek information. Creating a Backstory for Your First D&D Character

Section 6

Connect one character’s lead to the whole party

A personal lead should offer the other characters a reason to participate. Give the task a shared point of interest: the map could reveal a scenic route, the missing object could be part of a local celebration, or the search could require skills the party already enjoys using. Ask the player how their character would invite the others in; the game master can make the lead’s details accessible to the whole group.

If several characters have relationships in the same location, connect them lightly. One character’s former teacher might know another character’s craft partner, or two NPCs might both be preparing for the same market day. The connection can create a shared scene without making every relationship part of one grand plot. The Alexandrian advises selecting the backstory elements that interest the players and balancing spotlight time across the group. GM Don’t List #19: Ignoring Character Backstories

Section 7

Keep the lead flexible and proportionate

A relationship lead is an invitation, so leave the player room to accept, negotiate, delay, or decline. Do not make the NPC’s well-being depend on one response unless the group has agreed that kind of story is welcome. Keep the stakes appropriate to the campaign: a delayed delivery or a missing keepsake can support a satisfying session just as well as a larger expedition.

Prepare what happens if the party does not take the lead. Mira can continue her search, ask someone else for help, or return later with new information. That keeps the setting moving without punishing the player. Also avoid using every backstory connection at once. A few well-chosen appearances give relationships room to develop and make later leads easier to recognize.

Section 8

A quick relationship-to-adventure worksheet

Use this short sequence when preparing a lead:

For example: “Mira, my old mapmaking mentor, asks the party to find a brass marker before the spring caravan leaves. A guide has it, but says Mira once asked him to keep it off a route that crosses a nesting ground. The party can investigate, talk with both of them, and decide whether to return the marker or propose another way to mark the safe pass.” That is enough to start an adventure while leaving the characters’ choices open.

When a character relationship becomes an adventure lead, the connection supplies the reason to care, the present-tense goal supplies the action, and a relevant complication supplies the next decision. Keep the player involved in how the relationship appears, give the party a clear way into the situation, and let the outcome change the story in response to what the group chooses.

Relationship: Who is the person, and what does the character value about them?
Player boundary: Does the player want this person involved, and are there limits on how?
Current goal: What does the person want to accomplish now?
First move: How can the party begin, and what clue or choice do they receive?
Complication: What makes the task uncertain or interesting?
Party connection: Why might the whole group want to engage?
Flexible outcome: What happens if the party accepts, changes the plan, or passes?
Section 9

Sources

D&D Basic Rules: Personality and Background
New Player’s Guide: Character Relationships
Creating a Backstory for Your First D&D Character
GM Don’t List #19: Ignoring Character Backstories
Random GM Tip: Long-Term Scenario Hooks
Fate Core Cheat Sheet and Veterans’ Guide
Related reading

Keep exploring this topic