3 ms·
Kintaba cofounder here-- thanks for the feedback! We really wanted the interface to feel comfortable for non-technical folks who needed to stay up to date on i
by quartz 7y ago
Kintaba cofounder here-- thanks for the feedback!
We really wanted the interface to feel comfortable for non-technical folks who needed to stay up to date on incidents so we focused on bringing as much of a human element as possible into the dashboard. Hopefully we can find the right balance of friendliness and informativeness, we certainly don't intend to become a social network (but we would love it if we were as easy to use as something like Slack or Discord)...
We experienced the same pain you're describing with keeping others updated and the politics (and subpolitices and subsubpolitics) that come out of major incidents over our careers. Luckily we also saw companies that did it right, usually with custom built tooling. Our biggest discovery was the more open you make the whole incident process the better everyone understands the work being done and also the less of those insidious little subpolitical conversations happen where facts are skewed and people are blamed for process challenges.
It's definitely a big hill to climb.
- duxup 7y agoYeah we used to do the political stuff via email updates at a place I was at. It wasn't the worst way but also not a "system" for sure. Half the battle with political stuff was really was defining the problem in a way that everyone outside engineering understood, and keeping everyone updated / aware of what was factually (not rumors or panic) going on, what was known, not known, what was happening, and when they would get their next update. And that's not even the technical stuff where folks here are asking about recording conference calls and etc ;)