2. Before You Get Started

Ok, you have gathered input and requirements from the client and stakeholders. Bur before opening the Application Builder, make sure you can answer a few key questions that will guide the design of the application.

What is the purpose of this application?

Define what the application is meant to achieve. Summarize the requirements in one or two sentences. If the purpose is difficult to articulate, you may need more input from stakeholders or consider splitting the scope into several applications.

Example:
The purpose of this application is to provide an overview of the client’s KPIs, Targets, and Initiatives, and to show who is responsible for each.

Who is the target user of this application?

Identify the intended users and their needs. Understanding the audience will influence complexity, terminology, and priorities in the design.

Example:
The application is aimed at C-level executives and directors within the client’s organization: Anne-Frid (Head of Finance), Agneta (CEO), Björn (CTO), and Benny (Marketing Director). With the exception of the CTO, their technical expertise is limited.

What are the main use cases this application should address?

Break down the key tasks the application needs to support. Listing the use cases helps ensure that all essential needs are covered.

Example:
• View the progress of all ongoing KPIs and their targets.
• Search for individual initiatives, with visibility into progress and responsible parties.
• Understand how KPIs relate to the organization’s objectives.

What matters most?

Determine the most important use case for the target user. The answer should not be “everything.” Even when creating an overview, some aspects will be more relevant than others. Frequency of use often indicates priority. If all use cases are treated equally, there is a risk of ending up in a “can’t see the forest for the trees” situation

Example:
The most important daily task is tracking KPI progress. Searching for initiatives and responsible persons is less frequently needed.

© 2025 Inorigo AB. All rights reserved.