Summary for Helphub Design Meeting Jan 10


@mapk @krogsgard @v @wizzard_ @versatility @Kenshino @hlashbrooke attended

User Personas

The initial overlook into understanding user motivations has led us to discover the possibility of a need for Guides. Guides are logical grouping of single topic articles. For example, a person looking into 2FA solutions for security, may also follow a guide that contains that information with other security recommendations. This does not however distract a person looking for specific information.

Components Inventory

We are working on on creating a list of components of Helphub so we’ll be able to create quick prototypes for UXUX UX is an acronym for User Experience - the way the user uses the UI. Think ‘what they are doing’ and less about how they do it. testing


The team with @wizzard_ leading survey efforts will continue to work towards churning our surveys for both users and the Support Team. To better understand user motivations of course.

Information Architecture

Based on the quick general categories that @wizzard_ has created to categorise the articles, a proper IA is being built.

Style guide

While this is more related to content, each basic article should be written on one single topic. This is built to adhere to the known motivation of a user wanting specific information.

TrelloTrello Project management system using the concepts of boards and cards to organize tasks in a sane way. This is what the team uses for example:

We are working on individual tasks via Trello. Join us there?

Moving ahead

We’re hoping to have some quick development tasks for the developers who are finishing up

Design Lead

A design lead will be nominated to head design efforts. Nominations can be made for self or others.

Read the meeting transcript in the Slack archives. (A Slack account is required)