I sincerely wish you luck on this. I suspect I won't be using this, but that's more of an issue of workflow, as opposed to a judgement of the device. I don't like being interrupted while I work. I don't run Slack continuously, like many do. Also I'm a hired gun. I don't have a constant gig, and 90% of my work is alone.
I think a device approach is reasonable. People like a device. They tend to not like a bunch of devices, which is why smartphones became so popular. But since this is something that would basically be a desk accessory, it might work.
One thing to be careful of, though, is that C-suite folks will often project their workflows onto their employees. What I see particularly hard-hit, is respect for "The Flow." This is that "magic productivity sauce" that comes from uninterrupted working time. Managers and executives have very little of this, but it is vital -vital- for engineers and creatives (I was a manager for a very long time, and the most valuable thing I did, was act as a buffer between sources of interruption, and my team).
Nowadays, the absolute worst thing that can happen, is I get a phone call or messaging interruption, while I'm chasing down a bug, or learning a new technique. It makes me blow my top. I tend to be rather abrupt, when answering those calls. Especially since the vast majority are robocalls, and I plonk them immediately (even that little interruption is painful).
I'd say that maybe having some published "best practices" to accompany it, might help. Maybe a blog -vlog?- that is accessible from these devices, could be nice.
Of course, it goes without saying that responsiveness (less than 500ms latency) and frictionless infrastructure is also vital for everyone, but I assume that is already there.
I think a device approach is reasonable. People like a device. They tend to not like a bunch of devices, which is why smartphones became so popular. But since this is something that would basically be a desk accessory, it might work.
One thing to be careful of, though, is that C-suite folks will often project their workflows onto their employees. What I see particularly hard-hit, is respect for "The Flow." This is that "magic productivity sauce" that comes from uninterrupted working time. Managers and executives have very little of this, but it is vital -vital- for engineers and creatives (I was a manager for a very long time, and the most valuable thing I did, was act as a buffer between sources of interruption, and my team).
Nowadays, the absolute worst thing that can happen, is I get a phone call or messaging interruption, while I'm chasing down a bug, or learning a new technique. It makes me blow my top. I tend to be rather abrupt, when answering those calls. Especially since the vast majority are robocalls, and I plonk them immediately (even that little interruption is painful).
I'd say that maybe having some published "best practices" to accompany it, might help. Maybe a blog -vlog?- that is accessible from these devices, could be nice.
Of course, it goes without saying that responsiveness (less than 500ms latency) and frictionless infrastructure is also vital for everyone, but I assume that is already there.