When someone’s away
Call @twin-sarah in the thread. Sarah’s Twin answers from what Sarah has chosen to share, or passes the question on for when Sarah’s back.
Work stalls on questions only one person can answer. Bring your team, their Twins and your company knowledge into one conversation, so the answer doesn’t depend on who’s free.
Working across teams / Illustrative example
@twin-sarah when do Northwind’s invoices go out?
On the third working day, once the reconciliation check is done. Northwind’s team expects them by noon.
With its sources. Sarah can see what it said.
Experts get asked the same questions all day, and everyone else waits for them. Give those questions somewhere to go, and leave people to the ones only they can answer.
Call @twin-sarah in the thread. Sarah’s Twin answers from what Sarah has chosen to share, or passes the question on for when Sarah’s back.
Get the background now rather than the next morning, with the sources behind it.
Let a Twin handle it. Correct an answer once and it remembers, so experts stop repeating themselves.
Ask your own Twin to draft the follow-up or create the ticket. Review it, approve it and carry on.
Bring in the documents, decisions and conversations behind a question, without leaving the thread.
Each person controls what their Twin shares, and a Twin never reveals what someone in the thread isn’t allowed to see.
Start where the interruptions are: finance, operations, engineering or whoever everyone depends on.
Each person chooses who can ask and what can be shared, then adds the answers they give most often.
Colleagues ask in the thread. Owners see every answer and correct what needs correcting.
It answers only from what its owner shared and shows its sources. If it isn’t sure, it can pass the question to them, and each person can always check for certain topics first. Owners can see and correct every answer.
No. It handles the questions that shouldn’t need a meeting, so there is more time for the conversations that should happen.
Yes. Start with one team or one recurring problem, then add people as it proves useful.
Start with one team and the question they keep asking.