How to find a career mentor without turning one person into a life plan

Dev is a fictional 26-year-old junior urban planner seeking broader career perspective in Calgary, Alberta. Dev has helpful supervisors, questions about public versus private practice, and five people he admires for different reasons. He keeps waiting for one perfect mentor relationship.

Priya, Luis, Maren, Jo, and Eli are not interchangeable names on a networking list.

A useful next ask depends on what Dev would do with the answer; Jo and Eli can remain later without becoming rejected mentors.

In You.one's Superboard view, Dev can give “Build a small circle of specific conversations that helps Dev test career directions without asking anyone to own his future” a Board of its own. That Board connects five people with five different questions, three plausible next conversations, and invitations that remain unsent; opening “Ask Priya, Luis, or Maren next” creates a Room for its evidence, discussion, state, and decision.

The mission is specific: Build a small circle of specific conversations that helps Dev test career directions without asking anyone to own his future.

The consequential choice is not something a board or an AI should quietly make: Whether to ask Priya about public-sector growth, Luis about consulting, or Maren about first-promotion patterns next.

You.one can keep the work, evidence, and “Ask Priya, Luis, or Maren next” decision visible through its Superboard view. The Owner boundary stays explicit: Dev chooses the next question and owns every invitation. Each person owns whether to participate and what to share.

The Mentor circle Board gives this mission one durable operating picture. Dev can use familiar language instead of translating the situation into project-management jargon. Its three Lists separate the kinds of attention this situation actually requires.

Its Cards deliberately distinguish actions, evidence, and decisions while keeping unsent questions in owned work. A Waiting List would be premature until a named request or outside condition is actually in motion. That separation makes the current choice, evidence, and next move easier to scan.

These Card titles come directly from Dev's situation: “Ask Priya, Luis, or Maren next” is the live choice, “Five people with five different questions” holds evidence, and “Draft the chosen invitation” is still work Dev controls—not a fake Waiting item. The point is recognition, not a perfect taxonomy.

Opening the Card gives the visible item durable depth. Stage can hold Conversation-purpose brief: Place only Priya's public-sector experience, Luis's consulting move, Maren's promotion path, and Dev's use-of-answer test together for the current decision. Live choice: Whether to ask Priya about public-sector growth, Luis about consulting, or Maren about first-promotion patterns next.. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show “Open decision: Dev will decide whether to ask Priya about public-sector growth, Luis about consulting, or Maren about first-promotion patterns next.” Activity can preserve this attributed receipt: “Ava compared the options in Card Chat using the Conversation-purpose brief and this Card Room's visible notes and left “Ask Priya, Luis, or Maren next” with Dev.”

A useful Card Chat request would be: “Using only this Card Room and the Conversation-purpose brief, compare asking Priya, Luis, or Maren next. Name missing evidence; do not contact anyone or choose.” When live AI is configured, current Ava can respond to an explicit Card mention using supported Room context and can make limited reversible changes inside this Card Room after an explicit request. She uses only supported Room context; she cannot summarize the Board, watch other Lists, or act outside this Card Room. She does not gain authority over the decision merely because the context is organized.

Dev's call remains explicit: Dev chooses the next question and owns every invitation. Each person owns whether to participate and what to share.

These requests use the visible supported context inside the “Ask Priya, Luis, or Maren next” Card Room. They do not imply that current Ava automatically surveys the whole Board or follows up on her own; Dev must provide the relevant facts and check the result.

Current Ava can reply in this Room to an explicit Card mention using supported Room context. She cannot summarize the Board, make the choice, represent Dev, watch other Lists, or act outside this Card Room.

Dev chooses the next question and owns every invitation. Each person owns whether to participate and what to share. Ava compares only evidence in the choice Card Room and does not contact anyone or decide.

Dev finishes “Write what Dev would do differently after a useful answer from Priya, Luis, or Maren,” keeps “Five people with five different questions” beside “Ask Priya, Luis, or Maren next,” and does not treat “Draft the chosen invitation” as completed or sent before doing the work.

• Request idea: using only this Card Room and the Conversation-purpose brief, compare asking Priya, Luis, or Maren next. Name missing evidence; do not contact anyone or choose.
• Request idea: use only the Conversation-purpose brief and notes the Owner has placed in this Card Room to separate facts, assumptions, and unanswered questions
• Request idea: name which visible Room note could most change the comparison; do not watch other Lists or follow up autonomously

A list of admired people is enough when “Draft a 25-minute ask” and “Draft the chosen invitation” no longer change the “Ask Priya, Luis, or Maren next” choice.

It starts to break when “Five people with five different questions” and “Draft the chosen invitation” must inform the same choice.

The Mentor circle Board earns its place only when the familiar tool—a list of admired people—can no longer keep the reason, Conversation-purpose brief, conversation, current state, decision, and history connected.

Dev should rename every List or Card that feels artificial. This recipe succeeds when “Ask Priya, Luis, or Maren next” becomes easier to decide and fewer open loops depend on memory—not when the Board looks tidy.

Later, if new evidence follows “Draft the chosen invitation”, Ava may bring Dev back to “Ask Priya, Luis, or Maren next,” show which part of the Conversation-purpose brief changed, and stop before choosing or acting. “Write what Dev would do differently after a useful answer from Priya, Luis, or Maren” remains human-owned.

A future unified You.one experience could carry relevant context from “Ask Priya, Luis, or Maren next” across guidance and the Superboard view. Broad proactive coordination, cross-surface personalized memory, realtime shared editing, and general external execution are not available today. Any future action would still require the applicable capability, connection, grant, and human authority.

• Dev is fictional and is not a customer, testimonial, research participant, or disguised real person.
• This fictional example is not employment, representation, relationship, or professional mentoring advice; each person chooses their participation and the career decision remains Dev's.
• It does not show Ava completing external actions or contacting anyone for Dev.
• It does not report a measured result, and this Board is a starting shape to adapt—not a universal prescription.