If you only have ten minutes to understand the new rules of work-from-home etiquette this week, here's the version that actually matters.
What's changing
The shift began quietly. A handful of teams, working in parallel and mostly unaware of each other, arrived at similar conclusions: the old approach optimized for a constraint that no longer binds. Hardware got cheaper. Models got smaller. Distribution got more direct. Each individual change felt incremental — but together they reset the cost curve.
Why it matters
Skeptics will point out — correctly — that we've seen similar inflection-point claims fizzle. The honest answer is that you don't need certainty to act, just better expected value. The downside of moving too early in this category is small; the downside of moving too late is structural.
What to do about it
The shift began quietly. A handful of teams, working in parallel and mostly unaware of each other, arrived at similar conclusions: the old approach optimized for a constraint that no longer binds. Hardware got cheaper. Models got smaller. Distribution got more direct. Each individual change felt incremental — but together they reset the cost curve.
- Adopt early — the cost of waiting is higher than the cost of failing fast.
- Measure honestly — pick two metrics, ignore the rest for the first month.
- Talk to users — the gap between assumption and reality is wider than ever.
The takeaway
We don't need another framework — we need a better default. For most teams, the right move is to test the contrarian position with one project and let the results decide.
