We've heard this many times when people hear we have deep focus scheduled: "You'd better respond or you'll lose customers". But we use teams. The team responds. There's always many more than one person on-call and/or available to respond. If one person is unavailable we have others from the team able to step in.
An outage that can only be resolved using a single hero individual that must always be available to swoop in to save the day means there was no team backing them up. That seems less effective: It means no one is really taking leave. No one is taking real breaks. No one is doing real handovers either on a regular basis.
The "no real handovers" aspect means that the current state of each system isn't being checkpointed. We see that as a business risk. Not unlike what source code control protects against. Imagine you didn't commit code into git or similar for awhile. Still feel safe about rolling back changes? How are you going to roll changes back? Its a similar thing in people. If you don't do any handovers then stuff stays in one individual's head.
I experienced something similar with Electron applications too. If you're an Electron dev, do NOT handle authentication within Electron. Handle it in their default browser.
Ooo, that's definitely an interesting idea. Might be interesting to see if there's publicly available data for the largest companies that are active in that area.
Had to Google "Field of Dreams" haha. Love the term.
Yeah classic marketing strategies of pitching value and getting an entire team to buy in is no longer going to work for communications products like these...
It's all about capturing enough single user joy to incentivize user invitation.