Case Study
6 articles on case study.
How a Healthtech CTO Scaled to 100 Engineers Without Tripling Meetings (Composite)
Composite scenario: a healthtech CTO grows engineering from 40 to 100 while keeping the meeting load roughly flat through declared state infrastructure.
How a Remote-First Company Runs Without a Wiki (Composite)
Composite scenario: a remote-first company replaces its decaying wiki with declared state and a queryable representative layer.
How an APAC-EU Engineering Team Killed the Morning Catchup Meeting (Composite)
Composite scenario: an APAC-EU engineering team replaces the morning catchup with declared wraps and a queryable record across the six-hour offset.
How a CTO Reduced Cross-Timezone Meetings by 70% (Composite)
Composite scenario: a CTO of a distributed engineering org cuts cross-timezone meeting load by replacing status syncs with declared state.
How a Distributed Team Onboarded 5 Engineers in One Week (Composite)
Composite scenario: a distributed team ramps five new engineers in a week using declared state and a queryable team context layer.
How a 30-Person Engineering Team Eliminated Morning Standups (Composite)
Composite scenario: a 30-engineer distributed team replaces morning standups with declared wraps. The patterns, the friction, the directional results.
Your team’s week, answered from the work.
If this is your team’s week, see what a StandIn does with it.