Built around real work
Different teams.
Shared follow-through.
Start with the recurring work where context, ownership, and handoffs matter most.
01 / PEOPLE OPERATIONSA better first day
A better first day
starts before day one.
Keep each new hire’s onboarding in a thread, with clear actions for IT, the hiring manager, and People Operations.
- Use a template for repeatable steps and responsibilities.
- Keep equipment, access, and orientation owners visible.
- Record completion and the final onboarding outcome.
EXAMPLE WORKFLOW
Welcome, Alex.
Employee onboarding
- MCPrepare equipmentMaya · ITReady
- EPPlan orientationElena · People OperationsReady
- JEConfirm first-week planJordan · Hiring managerWaiting
One thread, with the context everyone needs.
02 / INTERNAL REQUESTS“Who’s handling this?”
“Who’s handling this?”
Already answered.
Give an internal question or request a clear owner and a shared history, without losing the discussion that explains it.
- Invite the people needed for a specific thread.
- Assign the next step separately from participation.
- Keep the answer, attachments, and result together.
From request to result“Can we update the customer welcome guide?”
Discuss the change → Assign a review → Record the result
03 / CROSS-TEAM COORDINATIONMake the handoff
Make the handoff
part of the plan.
When progress depends on someone else’s work, make that relationship visible instead of leaving it in a follow-up message.
- Connect prerequisite actions within the thread.
- Distinguish ready, waiting, and blocked work.
- Use project insights to see where work is accumulating.
FINANCE
Review supplier details
Prerequisite actionOPERATIONS
Confirm the order
Ready when its prerequisites are completedIllustrative workflow
Make the next step clear
Less chasing.
More follow-through.
Bring your team’s conversations and commitments together.