Identifying use cases
Through our user interviews, we identified the use cases that were the most common, starting off with the technology industry. These use cases ran alongside typical agile/scrum methodology including sprint planning, bug bash, goals & OKRs, product roadmap and more.
We took each of these use cases and asked our users what they typically need for each use case in order to be successful. With each use case we shaped individual templates that might consist of one main channel, one or more board templates, one or more pre-made task checklists and one or more integrations.
With testing, we confirmed that there would be at least two groups of users of Mattermost customers. The first group of users are more likely to be experienced users or have a bias for action and learning by doing. They would want to dive right in and create their channel template immediately. They could accomplish this by clicking a "Quick Start" button that appears on hover over a template on the first page (Create new channel) above.
The second group of users, most likely first time users, would want to better understand the template elements before using the template. This flow would be longer and would include the preview page (shown here on the right) as well as a customization page that lets the user customize the template with a title and a level of privacy access.