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.
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 ;)
Looks like StackOverflow to me but clean. I like the UI. I don't know if I will ever see that utility where I work since we wikify things like this post-chaos. The office I work in is a small enough team to where we have plenty of flexibility.
Like when I think of dealing with a situation I see that and think of some sales guy going off in his comment about
OMG THIS IS JUST LIKE THAT OTHER TIME WHY ISN'T THIS FIXED!?!!?
Now the whole comment thread is off track because sales guy brought his own FUD to the game, and god help us all if someone brings it up on a conference call as fact.
Now obviously that is not the fault of the UI if you've got a sales guy does that, but as things scale up organizationally that kinda thing ... happens ;)
Granted this system might be intended for engineering teams, but it's also something that inevitably leaks out when folks find out it is there.
Even if they don't have an answer some way of making sure FUD doesn't take off too quickly.
I'd say a high % of managing any situation and the politics that follow is accurately defining / revising the problem and making sure everyone is on the same page with it. Dodging / handing the inaccurate information leaks sometimes is a big job.
Granted that's all office politics stuff and not just technical... still gotta solve the problem ;)
Anyway it's an interesting idea. I worked in a support center for decades and demands for updates and managing P1 type situations, giving updates to the dozen interested parties (each of whom were competent in some ways, less so in others), managing misinformation, and the varying politics was a constant hassel for folks who were technical.
There were times where "oh man my phone just went down" (I unplugged it).
That's no small thing to try to deal with, with software.