3 ms·

Full disclosure: I used to work at PagerDuty and am a shareholder. These views are my own. Take this with appropriate salt. Congrats on the release. Looking a

Full disclosure: I used to work at PagerDuty and am a shareholder. These views are my own. Take this with appropriate salt. Congrats on the release. Looking at this, it’s difficult to determine how it’s different or why it’s better than PagerDuty, OpsGenie, or VictorOps. The page talks about a close integration with Slack, but it’s unclear what problem that solves for me wrt incident management. Note keeping / scribing is one part of incident management, but theres also: - mustering. Getting other SMEs on the call. Both knowing who to page and actually paging them are two important problems. - triage. Quickly knowing the severity of an incident. - context. Sorting through all of the incoming data and metrics to find the cause. Does this tool help with those? From what I recall about VictorOps, they started out with a similar thesis to incident management and focused on chat / mobile / collaboration out of the box. I don’t know if they validated their hypothesis, but their marketing material did change in recent years to cover other aspects of incident management. I take that as evidence that the chat piece alone wasn’t sufficient. Final thing I’d recommend is making it easier for potential customers to self select on your home page. Right now you’re targetting the IM market at large with “Things break. Be ready.” Is that your customer though? Any sized organization? Could you take on a 500 user company? 1000 person? Maybe something like “we help small businesses manage incidents”. “come fight fires with us” makes it sound like your team is actively helping resolve my incidents.

btables 8y ago
This feedback is great and very appreciated. With the other competitors I get the point of targeting smaller customers. With that said, I think a point might be missed with what I'm trying to accomplish with this initially: Context being lost through engineers finding things. Metrics, logs, traces, etc all don't tell a root cause when its a new incident. That's usually a human putting 2 and 2 together. When that happens it can be lost never to be seen again (the trail of tears getting to the solution). This is a super early release and this feedback was invaluable so thank you very much! There are plenty of ideas I'll be implementing in the coming weeks now that this first release is finally out of the way.

btables 8y ago

This feedback is great and very appreciated. With the other competitors I get the point of targeting smaller customers. With that said, I think a point might be missed with what I'm trying to accomplish with this initially: Context being lost through engineers finding things. Metrics, logs, traces, etc all don't tell a root cause when its a new incident. That's usually a human putting 2 and 2 together. When that happens it can be lost never to be seen again (the trail of tears getting to the solution). This is a super early release and this feedback was invaluable so thank you very much! There are plenty of ideas I'll be implementing in the coming weeks now that this first release is finally out of the way.