>Automatically create the online meeting spaces for collaboration
>Manage TODO items so nothing falls through the cracks
I work in incident response, and I feel a huge misunderstanding of incident response products fail to understand that companies already have established tools for collaborations and meetings and for capturing planned work.
I find adding these things is seen as nice and inclusive and it is easier to sell a product that does a lot, but it turns into complete bloat and makes adoption harder, and makes it harder to support a larger product.
This was a big learning for us when we were first building out Kintaba[1].
Re: task management specifically-- having previously been at FAANG companies that built all their own tools I had not realized just how prevalent Jira is. It. is. EVERYWHERE. and IT orgs at companies from 3 to 300,000 people are absolutely married to their carefully customized version of it as a system of record for everything that happens or will happen.
We see many on-premise implementations as well despite the announced sunsetting of that product.
I'm sure there's a #2 and #3 out there but honestly I almost never see it (we do see clubhouse/shortcut from time to time... but even those folks tend to move to Jira within 6 months).
OT but it really makes me doubly impressed that Slack was able move into organizations so successfully from all corners such that it was able to dodge what would traditionally be a pretty big Atlassian-owned barrier.
the on-prem version helps you ensure that it's running fast and secure, or you can end up fucking up the performance part. But on-prem also means systems that are firewalled from internet might have access to it, which helps with integration.
I think the problem is trying to present an abstraction layer to management, because we have those same features of todo lists, and recording information, in Jira and ServiceNow and like a dozen other pieces that's purpose is to coordinate and track work, and often they are unpopular with developers because they end up trying to provide an abstraction layer to the Execs to replace their management by spreadsheets, but unfortunately as anyone who has worked in software for long enough can tell you, abstractions are leaky.
Hence the dissatisfaction with a lot of these tools.
What do you think is the solution - when an enterprise already has Jira, Github and Confluence, how do you think a product like Grafana Incident should integrate with these somewhat overlapping products?
This feels like a central question of post-cloud / post-SaaS outsourcing.
In the end, it boils down to two options: offer deep APIs into your product, or don't.
IMHO, what needs to happen to support the former is for every SaaS purchase to include full technical due diligence on external integration capabilities.
Integration needs to start being a headline feature in purchasing. And less an afterthought when a horrified engineer looks at some new enterprise product that's already being adopted.
>Manage TODO items so nothing falls through the cracks
I work in incident response, and I feel a huge misunderstanding of incident response products fail to understand that companies already have established tools for collaborations and meetings and for capturing planned work.
I find adding these things is seen as nice and inclusive and it is easier to sell a product that does a lot, but it turns into complete bloat and makes adoption harder, and makes it harder to support a larger product.