In Practice

How teams use StandIn

Real blueprints. No abstract theory.
Here is exactly how context moves between time zones.

Product & Engineering

London to New York Handoff

The London team finishes their day at 6 PM. Instead of writing long documentation or leaving silently, they publish structured Wraps.

When New York logs on 5 hours later, they don't ping London (who are asleep). They query the project context directly.

The Result

  • Zero "just checking in" pings after hours.
  • PRs get reviewed during the overlap window, not debated.
#project-atlasToday
L
Liam (London)17:45
Wrapped for the day
• Stripe API v3 migration complete.
• PR #102 is ready for review.
• Blocker: Waiting on new API keys from Ops.
Is the Stripe migration ready for QA?
Rachel (NY) • 09:15
StandInAPP
Yes. Liam wrapped at 17:45 noting "Stripe API v3 migration complete."
View PR #102

Customer Support & Ops

Shift Handoffs & Escalation

We are seeing 500 errors on the payment gateway. Who is on call?
Agent Smith • 02:30
StandInAPP
I've routed this to @Dave (On-Call) based on the "Critical Payment" rule.
Context: Liam's wrap mentioned "Waiting on new API keys from Ops." This might be related.

Support teams operate in shifts. Context loss between shifts causes duplicate ticket work and slow escalations.

StandIn acts as the "Shift Captain" that never sleeps. It knows the known issues from the previous shift and routes new emergencies to the correct on-call engineer immediately.

The Result

Support agents don't wake up the wrong engineer. The system checks the Wrap context first ("Is this a known issue?") before escalating.

Leadership & PM

Clarity without Meetings

Leaders often call "sync meetings" just to get information that already exists in people's heads.

With StandIn, leaders query the Project Representative. It aggregates status from individual wraps into a coherent project-level view.

Constraint in Action

VP: "Who is working the most hours?"
StandIn: "I cannot answer that. I do not track activity or presence."

What is the status of the Q3 Launch?
VP Product • 10:00
StandIn

Status: At Risk

Summary from 4 recent wraps:

  • Design is complete (Sarah, Yesterday).
  • Frontend is blocked on API keys (Liam, Yesterday).
  • Ops is investigating key generation failure (Dave, Today).

Early-Stage vs. Scaled Teams

Early Stage (5-20 ppl)

  • Channels
    StandIn lives in #general and #eng.
  • Wraps
    Minimal. Bullet points only. "What I did, what's blocked."
  • Value
    Replacing the daily standup meeting.

Scaled Org (100+ ppl)

  • Channels
    Dedicated Project Representatives in #proj-atlas, #proj-zeus.
  • Wraps
    Structured. Linked to Jira tickets. Used for compliance logs.
  • Value
    Routing. Preventing 500 people from asking "who owns this?".

What these teams stop doing

Fewer Standups

"Let's go around the room" becomes redundant when context is searchable.

Fewer "Quick Calls"

Calls are reserved for complex decision making, not information transfer.

Less Apologizing

No more "Sorry I missed this, I was asleep." It's okay to be asleep.

Copy these blueprints.