Jeli Reviews

I love the Narrative Builder and being able to import selected messages and entire channels from Slack into Jeli. This enables me to easily document what happened and when, and provide links to the actual Slack discussions that took place! I also really appreciate how friendly and available Jeli support is. They are always quick to answer my questions and I have seen many feature requests and the occasional bugs I find addressed very quickly!

There are a lot of different fields and places you can put information, and sometimes it can be a little confusing to know the best place to put different types of information.

Jeli removed the tedius task that was searching around and typing up an incident report in Google Docs, and replaced it with an easy-to-use Narrative Builder that allows Slack messages to be imported and attached to events that are automatically displayed on a timeline! It is much easier to get content together for a prompt incident review.

Our use case is for engineers to take charge of incident analysis, and Jeli does all of the heavy lifting for us. It makes it simple and quick to gather the information you need in one place, and integrates so well with Slack. It has helped us to increase participation in PIR meetings, improve documentation around incident learnings, and is supporting our path to prioritizing tech debt. It is so simple to understand and has now become our place for centralized management of incident outcomes.

There is nothing that we dislike about Jeli, however we would really use the tagging feature more to find related incidents if this was a bit more seamless.

Tackling tech debt, learning from incidents, on-call and incident management uplift, documentation around known issues

Jeli has been incredibly easy to use. We were looking for a solution that would provide an approachable and scalable full incident lifecycle framework, and are very happy with our choice to select Jeli as a vendor. While we did offer Jeli training to our organization, most people were able to figure out how to use Jeli with minimal to no training. Jeli has allowed us to unify all our various other tools into one central hub for incidents. It has helped with our communication across the organization during incidents as well as coordinating various engineering teams during incidents. We also love that they continue to roll out new and useful features. Finally, Jeli's customer support has been among the best of any vendor we've worked with. When we have questions they are often answered within minutes, and when we've found small bugs they are normally fixed same day. We never feel like we are waiting in a ticket queue or are just a number on a support ticket. The product is great, their customer support is even better.

We have not found much that we dislike. Occasionally we run into growing pains such as having specifics of our use case that have not yet been addressed, but normally those corner cases are fixed same day. The only real feedback I've gotten is that during the integrations (Jira, Zoom, etc) people wished there was some more detail around things like needed permissions in the integrating application.

We currently use Jeli for incident response. This includes communicating via broadcast channels during an incident, mechanics of running our incident response, integration of other tools such as Jira and Pagerduty, and facilitating collaboration during incidents. We are also using Jeli to create incident timelines for post-incident retrospectives and will be leaning more into the incident analysis part of the product in the future.

Jeli has been a fantastic partner in helping to get our IR/IM house in order. We're able to use it to combine multiple disparate tools into a single location, make it very simple for our front line responders to quickly, accurately, and with a full audit trail respond to, investigate, and escalate incidents as the occur. The reporting and evaluations that I have seen thus far have been very helpful in identifying several opportunities for us to improve and that provides a lot of value for me. Jeli has helped at every step of the integration including creating new methods for existing application integrations. I am looking forward to using them for the foreseeable future.

I would like a little more control over what gets ingested from Slack, including deactivated users prior to implementation of Jeli. The integration catalog could use more tools but I do know that they're working on adding more regularly and many I can get by with just using the webhooks in a pinch.

The largest problem that is being addressed in the consolidation of IR/IM processes across many disparate teams with many different tools.

Jeli has been fantastic to work with and they are at the forefront of incident management. I have been working with Lesleanne and her team for a few months now and they are always willing to help or take on feedback. They are changing the way that we do incident analysis, and they are always introducing much needed capabilities. It is very well designed and so easy to use.

I look forward to our continued work together and seeing what they have in the pipeline.

Jeli has so much to work with. The only downside is I need more time to play around with it!

Jeli is making PIRs fun and from those PIRs they are extracting really useful data when it comes to how people are experiencing incidents and it brings to light issues that may not have been clear before using the Learning Center functionality. I believe that LFI is really important for companies to really shift the needle and Jeli does this really well.

Jeli provides the structures and reminders the team needs without getting in the way. It's got a low barrier to creating incidents, automated workflows are incredibly optional, and the incident reports at the end are informative and readable. We use it for every incident and the incident overviews are great at giving Customer Support the right amount of information.

It can take a long time to really put together a good timeline and determine which messages are the most critical.

Jeli provides a light weight way to structure incidents. Easy to forget pieces of process like updating the incident status can be automated through reminders for example. We bought it for incident reporting, but we use it for every incident because it makes the actual incident process so much smoother.

Great insights into our incidents. Helps our incident responders write awesome incident reviews that make it easy for others to learn from. Beyond a really great product, the team truly treats us like partners, and have gone out of their way to help us level up our incident response and review process.

I haven't seen any so far, it's been a huge help and the people we work with are incredible resources.

Incident review, along with all of the learning that is necessary to make incidents have value for our teams and our customers.

I like the flexibility of Jeli. It acts as a Swiss army knife for incident analysis and can support a wide array of uses to learn more from incidents.

I use it every day and it has made analysing incidents so much easier (and fun) compared to doing it manually.

Being able to pull in multiple incident Slack channels and individual messages allows me to tell more interesting and complex incident narratives. The end results with the visual narrative look better too.

Creating the narratives takes effort but it forces the investigators to pause and look closely at what happened. Investigators pick up on a lot more threads to pull on in the investigation and for the Post Incident Review meeting which leads to better insights and more engaging PIRs.

Could support conversations between incident analysts and readers of the report better

We use Jeli for Incident Analysis (after incident is resolved).

Different roles use the tool to a different extent.

a) In my department at the higher level we use Jeli to gain an overview across incidents and make use of the exec summaries.

b) At a group level we also use Incident Narratives and Takeaways that allow non-responders to understand what happened and what we learned. It also allows us to see patterns.

c) Individual Incident Investigators, often Team Leads/Lead Engineers/Principal Engineers or Senior Engineers, create Incident Narratives to build a better understanding of what happened even for incidents where we don't run a PIR.

d) Investigators use Jeli during the PIR meetings to summarise the incident via the visual narrative timeline and capture insights from the PIR meeting in the takeaway section afterwards

e) We also sometimes use Jeli as a training/education tool in that we analyse the coordination and communication aspects of past incident response and use that to teach other incident responders.

The UI is very intuitive and sleek. We love using Jeli for incident reviews! Being able to export incident messages straight from Slack into Jeli to create a timeline is very useful.

There are a few features that would make Jeli even better, just as having the ability to collaborate on the meeting notes together. Otherwise, I don't dislike Jeli at all.

Jeli is making it easier for us to conduct incident reviews and facilitate learnings/healthy discussions around incidents.

The platform has everything you need for using as a tool to learn from incident. It has all the cool features that you can use for PIR meetings, and also the team is great at getting feedback to improve their tools and fix any issues that may arise.

Maybe the learning curve is not really low, so you still need to learn it a bit, but then after 1 or 2 times using it, it will be super easy.

It helps to provide the tool to be easy to learn from incident, by exploring different angles of the incidents.