Flowscape

I worked as a UX / Product Designer on FlowAnalytics over a 6-month period, from research and early exploration to MVP design, implementation support, and handoff.

I was responsible for the UX work across research, dashboard structure, information architecture, wireframes, UI design, KPI cards, filter patterns, navigation, microcopy, design system work, and developer handoff.

The project was highly collaborative. I had regular UX feedback sessions with my supervisor several times a week, where we discussed design decisions, tested ideas, and refined the direction together.

I also worked closely with the product owner and backend analytics stakeholder through weekly product meetings, where we aligned on scope, data logic, user needs, and what was realistic for the MVP. As the design moved closer to implementation, I collaborated with the frontend developer to check feasibility, clarify handoff details, and make sure the design patterns could work in the product.

A key decision point came after the first research phase. I explored broader ways to rethink the analytics experience, including more simplified alternatives. But because the MVP needed to move quickly and still support advanced analysis, we chose to keep the dashboard model and improve it from within.

That meant focusing on clearer structure, better hierarchy, more useful KPI context, predictable filters, clearer navigation, and a more consistent visual system.

FlowAnalytics contained a lot of useful workplace data, but the experience had become difficult to scan, understand, and use in daily decision-making.

Users could get value from parts of the analytics experience, especially when preparing insights for meetings, but many dashboards and graphs were rarely used. The problem was not only the amount of data, but how it was presented. The interface felt dense, the visual style was inconsistent, and many KPI cards relied on short labels without enough explanation.

In the previous setup, dashboards could take a long time to load, and it was not always clear when the data was still loading, filters were being applied, or the dashboard was ready to use. Exporting was also slow and inflexible. Users often had to export a whole dashboard instead of one specific graph or view, which was frustrating when they needed material before a meeting.

Navigation also created friction. Some views and tabs were placed in ways that did not match common dashboard patterns, which made it harder for users to understand what was clickable or where to go next.

Because dashboard purposes were not always clear, users often stayed in one or two familiar views instead of exploring the full analytics experience. Filters could also be hard to keep track of, which made it difficult to understand exactly what data was being shown.

The challenge was not simply to show more data. It was to make the data easier to scan, understand, filter, navigate, and act on.

The product supported workplace teams, facility managers, HR, administrators, and people responsible for understanding how office spaces were used.

They needed to understand occupancy, utilization, space performance, and workplace patterns over time. Some users needed quick answers before meetings, while others needed deeper analysis to understand trends and make decisions.

A key user behavior was that many users stayed in one or two familiar dashboards instead of exploring the full analytics experience. That showed that the product needed clearer dashboard purposes, stronger orientation, and better support for interpretation.

I started the project with a research phase to understand the product, the users, and the business context behind workplace analytics. Since the domain was new to me, I spent time learning the language of facility management, how workplace data is used, and what decisions the analytics experience needed to support.

The project resulted in a new FlowAnalytics MVP with 5 redesigned dashboards, a lightweight design system, reusable component patterns, design files, prototypes, and developer handoff material. The designs I delivered were implemented into the new analytics portal.

For users, the new experience made workplace data easier to scan, navigate, and interpret. KPI cards gave more context around key numbers, filters became more transparent, navigation became easier to understand, and the visual system made the product feel more consistent.

Testing and feedback indicated that the new direction was easier to understand and navigate, but because user testing happened late, some findings became recommendations for future iterations.

This was one of the reasons Flowscape wanted to move away from the previous Power BI-based setup and build FlowAnalytics as part of their own product. The new setup gave the team more control over performance, export logic, frontend patterns, and the overall user experience. My UX work built on that opportunity by improving clarity, feedback, structure, loading states, export touchpoints, and the overall experience.

Internal feedback was positive. My supervisor highlighted my role in making complex data easier to understand and use for decision-making, adapting to a fast-paced MVP environment, aligning with stakeholders, creating clear developer handoffs, and exploring AI as a way to iterate more efficiently.