Back to all projects

Augmented Reality KPI Visualization Platform

A digital solution designed to present KPIs and reports through augmented reality, allowing information to be explored using tablets and AR glasses, while a supporting web application handled data management and administration.

My contribution focused on understanding the requirements across these different touchpoints, translating them into a connected prototype, and preparing clear documentation to help users understand how the solution works.

The Challenge

Designing one coherent experience across very different interfaces.

The project introduced a different kind of interaction from a conventional web system.

The experience needed to connect a web-based management layer with the way users would access and explore KPI information through tablets and augmented-reality devices.

The challenge was to understand how requirements translated across these different interfaces while keeping the overall experience coherent and understandable.

My Contribution

From requirements to an experience users could understand.

Structured Requirements Across Multiple Touchpoints

Worked with the team to collect, analyze, and document requirements for the solution, considering both the administrative web experience and the augmented-reality interactions.

This required looking beyond individual screens and understanding how information would move from its management source to the experience presented to the end user.

Structuring the solution required connecting business logic, data management, and multiple interaction environments.

Translated Requirements into a Cross-Platform Prototype

Designed a prototype representing the proposed experience across the web application and AR interface.

The prototype helped make an emerging and less familiar interaction model easier to communicate by showing how users would navigate key processes and interact with the solution across different devices.

From the web management experience to the AR interaction flow, the prototype helped connect the different parts of the solution.

Made an Unfamiliar Experience Easier to Understand

Because augmented-reality interactions are less familiar than standard web interfaces, visualizing the intended experience became especially valuable.

The prototype provided a clearer reference for discussing how users would move through the solution rather than relying on written descriptions alone.

  1. Requirements
  2. Experience
  3. Prototype
  4. Shared Understanding

Turned the Final Experience into Practical Guidance

Prepared comprehensive user documentation explaining the system and its main workflows.

The guides combined written instructions with annotated interface visuals, helping translate both the web and AR experiences into step-by-step material that users could follow.

Annotated visual guides translated system behavior into practical steps users could follow.

Key Deliverables

Turning analysis into something visible and usable.

01

Requirements Documentation

Structured and documented the functional needs across the web and augmented-reality parts of the solution.

02

Cross-Platform Prototype

Visualized how the experience connects across different interaction environments.

03

Interaction Flows

Represented how users move through key scenarios and interact with the proposed solution.

04

User Guides

Produced structured, visual documentation to support users in understanding and navigating the system.

Skills in Practice

What this project allowed me to practice.

  • Requirements Elicitation
  • Requirements Analysis
  • Cross-Platform Thinking
  • User Flows
  • Interactive Prototyping
  • Information Architecture
  • User Documentation
  • Information Design

Takeaway

New technology still needs familiar clarity.

Working with an AR-based experience reinforced something I find important in solution design: introducing a new interaction technology does not reduce the need for clarity, it increases it.

When users move between web interfaces, tablets, and augmented reality, the relationships between information, actions, and interfaces need to be especially clear.

In this project, prototyping and documentation became two ways of making a less familiar experience easier to understand before and after implementation.