Even though we made efforts to make Insight's onboarding process as simple as possible, it is constantly improving. We are far from where we started a year ago and definitely not where we will be in a year from now.
The solution we bring comes with quite a few challenges. For starters, not every team is convinced that they need analytics in the first place. So we blog about the benefits of measures and transparency in software development. Some teams are more interested in the money they will save by optimizing their process, so we built the ROI page that demonstrates how measuring your process could save 10 times what Insight costs.
Since the field of software development analytics is still in it's early stages, it's only natural that some teams are not exactly sure of where they should be starting to get the fastest results. We handle this by providing an awesome documentation and educational emails to guide users along the way.
Step 1: The quick tour
On the first login, Mauka welcomes new users with a series of guided steps. Those steps are meant as a quick tour (5 to 15 minutes total) of the most common use-cases. Every step is meant to teach our users something new about the app and give them a better idea of what the tool is all about.
By the end of this quick tour, they have built their very own board and they will have an additional week of free Insight, Yay!
Step 2: The templates
During the quick tour, one of the steps asks the user to choose a template. Those templates are tailored from the most common use-cases we have seen in the past while working with project managers, CTOs and CEOs. Each of those templates is meant as a starting point, but they may require some tweaking to fit a real use-case.
We encourage users to try those templates as they are a great starting point and it helps them see how other people are building their agile analytics.
Step 3: The documentation
Playing around and experimenting with the app is excellent for hands-on practice and it may deliver the results you are looking for, but the documentation is really the place to learn a bit more about each chart, the filters and labels.
The documentation has information about how each component works and goes into more details about what is possible with each chart and KPI.
We plan on reviewing and improving this documentation in the coming weeks, so stay tuned.
All those tools are just a start and they are meant to ensure our users get the most out of their boards.
In the future, we plan on having a series of emails that would go deeper into specific charts and KPIs. Our plan with this whole initiative is to help development teams become more efficient while also providing the simple KPIs to keep stakeholders informed.
Which part of Insight is not clear or would need more explanation? Let me know below...