INSUBCONTINENT EXCLUSIVE:
and hack attacks plague engineering teams
Yet the tools for waking up the right employees, assembling a team to fix the problem and doing a post-mortem to assess how to prevent it
for actually learning from mistakes
Alerting systems like PagerDuty focus on the rapid response, but not the educational process in the aftermath
Years later, when they tried to build a blockchain startup and the whole stack was constantly in flames, they longed for a better incident
It integrates with Slack, and lets team members subscribe to different levels of alerts or search through issues with categorized
contained, Kintaba provides a rich text editor connected to its dashboard for quickly constructing a post-mortem of what went wrong, why,
what fixes were tried, what worked and how to safeguard systems for the future
add up to Kintaba taking away all the annoying administrative overhead and organization that comes with running a successful modern incident
met while working at Facebook, which is known for spawning other enterprise productivity startups based on its top-notch internal tools
Facebook co-founder Dustin Moskovitz built a task management system to reduce how many meetings he had to hold, then left to turn that into
Asana, which filed to go public this week.The trio had been working on internal communication and engineering tools as well as the
procedures for employing them
an engineering nightmare without clear product market fit
servers have stopped serving data
You declare an incident with high severity and the system creates a collaborative space that automatically adds an experienced IMOC
(incident manager on call) along with other relevant on calls
Kintaba also posts in a company-wide incident Slack channel
stakeholders updated by directing them to the Kintaba incident page instead of sending out update emails
Interested parties can get quick info from the stickied comments and #tags
Once the incident is resolved, Kintaba helps you write a postmortem of what went wrong, how it was fixed, and what will be done to prevent
Kintaba then automatically distributes the postmortem and sets up an incident review on your calendar.Essentially, instead of having one
employee panicking about what to do until the team struggles to coordinate across a bunch of fragmented messaging threads, a smoother
incident reporting process and all the discussion happens in Kintaba
management chain to try and figure out who needs to be involved
affected by the downtime, other teams are also throwing slack channels together, email threads are happening all over the place, and
multiple groups of people are trying to solve the problem at once
saved outside that email chain
Managers blame each other and point fingers at people instead of taking a level headed approach to reviewing the process that led to the
necessary add-on that companies should pay $12 per user per month
four-person team sees adjacent markets in task prioritization, knowledge sharing, observability and team collaboration, though those would
pit it against some massive rivals
major screw-ups to their communication platforms.When asked why he wanted to build a legacy atop software that might seem a bit boring on
