Before starting a Qlik Sense application development project, it is essential to understand who we are building the interface for and what is expected of it.
There are numerous people involved in a Qlik Sense app project on the customer side, typically including stakeholders in the IT team, the business team, directors and managers, and the person responsible for the project to evolve (that is the person who chose you or the company where you work to provide the service).
With so many people involved, it is not uncommon that you will need to find the appropriate stakeholder who is developing the application trying to serve everyone’s needs.
Even though a list of requirements and indicators to be considered has been raised, it is essential for the project’s success to detail each of the required indicators directly with the people who are in fact going to be using the solution (and not just the developers).
To help identify these indicators, it is common practice to execute a client briefing. Possible questions that you may raise during this phase include:
- What is your audience’s profile? (position, age group, familiarity with management software, etc.)
- How does your audience currently read information? (do they use other software, spreadsheets, etc.)
- Is the audience familiar with Qlik Sense?
- What is the most used screen resolution?
- What reading devices should you consider? (smartphones, tablets, etc.)
- Is there a visual identity or brand line already defined?
- What are the main questions users will want answered with your solution? (at least 3-4 questions per tab)
Image: Disclosure / Qlik
In essence, the briefing phase aims to clarify points regarding your target audience’s profile (or profiles), the main questions that this audience will ask (and which the application must answer quickly and simply), graphic references for the development of the visual style, among other things.
Having these answers documented is important so that, at the end of the project, they can be reviewed and checked upon to determine project success. The more faithful the end result is to the original briefing, the greater the degree of user satisfaction.
Note: unlike the survey of metrics and KPI’s (which is a technical document and is generally detailed before the project starts), the briefing has an informal character and aims to qualify the information that was collected during the survey of metrics and KPIs.
Looking for more?
Be the first to know
Get first-hand access to our free Design and Dataviz content directly in your inbox