AI Ready
Direct Messages card, MethodKit for AI Readiness
Card 16 of 48 · MethodKit for AI Readiness
  • ThemeDark Context
  • CardCard 16 of 48
  • Questions5 to explore
Dark Context

Direct Messages

Side conversations in DMs, SMS and chat

The conversations that happen one-to-one, in DMs, SMS, and private chat, carry context that never makes it to any shared system.

Direct messages are where people say what they actually think. A client's real concern about a deliverable. A manager's actual stance on a budget question. A colleague's informal agreement to handle something. These conversations shape outcomes, but they live in personal inboxes and app threads that no tool, and often no colleague, can reach.

The problem compounds across platforms. The same relationship might have threads in Slack DMs, WhatsApp, iMessage, and LinkedIn messages, with no way to get a coherent picture of what has been said and agreed. When someone needs context on a relationship or a project, they have to ask the person, and the person has to remember.

This is not about surveilling private conversation. It is about recognising that a lot of working context lives in a format that is both fragile and invisible, and deciding deliberately which parts of that are worth capturing in a more durable form.

Make it visibleAfter your next DM exchange where something important is agreed or shared, write one sentence capturing the key point and drop it into a note or doc titled with the person's name and the date. Build a small log of consequential private conversations.

Why AI needs this

Each part of your work matters to AI in a specific way. Some of it is context a tool needs before it can help, some of it is work a tool can take on, and some of it is judgment that should stay with you.

Informal commitments

Things agreed in a DM rarely make it into a task system or shared record. A habit of summarising key points from important DM conversations into a shared note makes them reachable and reduces dropped balls.

Relationship context

A tool trying to help you draft a message to a client or colleague has no idea what has been agreed privately. Even a brief note on the current state of a relationship can help it calibrate tone and substance.

Cross-platform fragmentation

Context split across Slack, WhatsApp, email, and SMS is effectively invisible to any tool. Choosing one channel per relationship and occasionally summarising key points is a practical workaround.

Sensitive but useful

Private messages often contain the most honest feedback and the most direct signals about what is going wrong. Some of that is worth capturing (anonymised, summarised) in a place where it can inform decisions.

Questions to explore

Use these on your own or in a group. There are no right answers, only better conversations.

  1. Which of your current projects have important context that only exists in private messages between two people?

  2. If you were away for two weeks, which DM conversations would a colleague need to read to understand where things stand?

  3. When a client tells you something important informally, in a WhatsApp message or a quick Slack DM, where does it go?

  4. How much of your working context is trapped in personal inboxes that would disappear if you or a colleague left tomorrow?

  5. Which relationships have important context distributed across so many platforms that no one has a complete picture?

Readiness traps

  • Capturing private messages at scale is a significant privacy issue. The goal is deliberate, selective summarisation of consequential context, not logging private conversations wholesale.
  • Context captured from DMs that involves a third party (a client, a stakeholder) requires care. Summarising what someone said privately and routing it into a shared system raises trust and confidentiality questions.
  • The habit of summarising key DM context works best when it is done close to the conversation, not reconstructed weeks later when memory has faded.