Bugsnag Engineering Leadership Forum San Francisco 2019

Define ownership and communication work streams

There’s no point finding bugs, unless you have a path to fixing them, and that has to be a team process change. Define ownership and communication work streams for managing application stability.

Crashes reveal that we may need better process

Crashes reveal more than just bugs. They expose a bigger picture operationally — that we may need better process, better ownership, more QA, more collaboration, and better knowledge sharing on systems working together.

Investigate the context of crashes

Keeping a low crash rate requires investment, not only in the pipeline and the tooling, but also in the investigation of the context of crashes.

Segment by app version and key customers

Not all crashes are equal. Prioritize engineering efforts by segmenting error data by app version and key customers.

Make predictive models about where to invest

Look back on error data, and make predictive models about where to invest engineering team's resources. 

Correlate user behavior with bug history

Correlate user behavior with bug history, and define your customer experience roadmap by building a rich data record.

Attach diagnostics to the root cause of problems

Several factors can cause a crash. Attach custom metadata to error reports to rule out possible sources. Attach diagnostics to the root cause of problems.

Set stability as a KPI

Set stability as a KPI for engineering teams to improve morale and efficiency. 

Tailor Bugsnag for your unique requirements

Push the limits on Bugsnag, and you’ll discover the infinite ways to hack it for your unique requirements and needs.