EdTech · Student Nutrition · 18-Month Project
Cybersoft — PrimeroEdge 2.0

Insights that feed futures.

Designing the data module that helps schools make better nutrition decisions for students — from raw data to clear, actionable insights.
Duration
18 Months
Release
5.0
Role
Sole Designer
Tools
Figma · FigJam
What this project is about
"Designing for students means every design decision has a real-world consequence — better data visibility leads to better nutrition decisions, which means healthier kids."
18
Months
5.0
Release
1
Designer
🎯
Release 5.0 completed successfully. From concept through final UI — designed, tested, and shipped solo.
🥗
Student Nutrition
📊
Data Insights
🏫
Schools Nationwide
✅
Release 5.0 Shipped
👤
Sole Designer
Project Overview

A module that
matters to real kids.

PrimeroEdge 2.0 is Cybersoft's school nutrition management platform. My role was to design the Insights module — a new data visualization and analytics layer that helps school nutrition teams understand student meal patterns, identify gaps, and make data-driven decisions at scale. I owned this module from day one, as the only designer on the project.

My Contribution

Deep collaboration with the data team to understand what student nutrition insights were available and how they could be surfaced meaningfully.
Product owner discussions to translate data into design requirements — bridging technical and business thinking.
Defined icons and visual system specific to the Insights module — including designing the Insights logo from scratch.
End-to-end design ownership — user flows, personas, wireframes, high-fidelity mockups, and final UI handed off to development.
Card sorting sessions with Sales and Support to validate information architecture and identify quick wins.
Project Scope
Product
PrimeroEdge 2.0 — Insights Module
Domain
School Nutrition · EdTech
Duration
18 Months
Release
5.0 — Completed ✓
Role
Concept · Wireframes · Prototype · Final UI
Tools
Figma · FigJam
Focus
ICC Dashboard — Desktop
Research Approach

Quantitative meets
qualitative — always.

To design an insights module that actually delivered insight, I needed to first understand how school nutrition teams currently made decisions — and where they struggled. My research mixed numbers with conversations: surveys told me what was happening, interviews told me why.

Quantitative
Surveys & Analytics
Distributed surveys to gather quantitative data on user behaviors and preferences. Kept questions concise, clear, and unbiased. Cross-referenced with existing platform analytics to identify patterns before interviews.
Qualitative
In-Depth Interviews
Conducted one-on-one interviews with school nutrition managers to explore their experiences, frustrations, and motivations. Built rapport, asked open-ended questions, and probed deeper to get past surface-level answers.
Analysis
Data Synthesis
Used statistical methods to identify trends in survey data. Transcribed and coded interview responses to surface common themes. Distilled findings into a clear summary of user needs, pain points, and priority opportunities.
Data Team Collaboration
Before any user research, I spent significant time with Cybersoft's data team understanding what student nutrition data was available — meal participation rates, nutritional content, allergy flags, and district-level trends. This shaped what insights were actually possible to surface in the module.
Product Owner Alignment
Translated data team findings into design requirements through structured discussions with the product owner. Bridged the gap between "what data exists" and "what decisions does the user need to make" — ensuring the module served real workflows, not just showcased data.
Research Overview
Research & Clarify Overview Insights Module
Ideation
Ideation Session Clarify & Ideate Phase
Development Phase

From first sketch
to final screen.

The ICC Dashboard Desktop was the heart of the Insights module — and the centrepiece of every development decision. Rather than creating mood boards, I built three distinct landing page mockups using the same layout but different visual directions. Seeing real screens made stakeholder decisions faster and more confident than abstract references ever could.

01
// Low-Fidelity
Sketches & Flow Mapping
Started with hand-drawn and rough digital sketches in Figma and FigJam to brainstorm layouts quickly. Focused purely on information hierarchy — where does key nutrition data live, and in what order does a user need to see it? Mapped user flows before touching visual design.
Key decision: ICC Dashboard would be the primary entry point. All other views branch from there.
02
// Three Directions
Three Mockups, One Layout
Rather than mood boards, I created three high-concept landing page mockups — same structure, three different visual approaches. This gave stakeholders a concrete visual choice rather than an abstract aesthetic discussion. Faster alignment, clearer decisions.
Result: Stakeholders chose a direction in the first review. Zero rounds of "can we see it differently?"
03
// High-Fidelity
Detailed Wireframes & Prototype
Built high-fidelity wireframes with precise layout, spacing, and interaction details. Annotated every component to ensure developers had context, not just pixels. Conducted usability testing with real users to validate structure and flow before moving to prototype.
Shared with stakeholders and made adjustments based on feedback before investing in interactive prototype.
04
// Final UI · Release 5.0
Final UI & Developer Handoff
Completed the full desktop UI for the Insights module, including the ICC Dashboard landing page. Shared all prototypes and mockups with the UI development team, and worked alongside them through implementation until the final output matched design intent exactly.
✓ Release 5.0 shipped successfully. Zero design debt requests post-launch.
Wireframe 1
ICC Dashboard — Wireframe Direction 1 Development Phase
Wireframe 2
Direction 2 Visual Exploration
Wireframe 3
Direction 3 Final Selection
Implementation Phase

Testing with the
people who know best.

Before finalising the dashboard's information architecture, I ran structured sessions with the people closest to the product's users — Sales and Support teams. Their daily interactions with clients gave them invaluable perspective on what actually mattered on the dashboard vs. what was just noise.

🃏
Card Sorting
Ran card sorting sessions with Sales and Support team members to determine which dashboard features should stay, be relocated, or be cut — based on real platform usage patterns and user value.
Method: Open card sort · 8 participants
📋
Client-Facing Survey
Sent a focused survey to client-facing teammates to quickly identify what should be added or removed. Goal: discover simple, high-value improvements that could be executed quickly — the quick wins that build user trust early.
Outcome: 5 quick wins identified & shipped
🤝
Dev Collaboration
Worked directly with the UI development team through implementation — not just handing off files and disappearing. Reviewed builds, flagged inconsistencies, and stayed engaged until the final output matched the design intent.
Shipped: Release 5.0 · On schedule ✓
Final UI 1
PrimeroEdge Insights — Final UI ICC Dashboard
Final UI 2
Final Implementation Desktop Version ✓
Reflection
"Designing for students is different. The stakes feel real in a way that most enterprise projects don't — because behind every dashboard metric is a real kid in a real school cafeteria. That responsibility made me a more careful, more empathetic designer."
— Mahesh Guntivenkata, Product Designer
lesson_01
Start with the data team, not the users
For a data-heavy module, understanding what data exists — and what's reliable — before talking to users prevents designing around impossible features.
lesson_02
Real screens beat mood boards
Three concrete mockups generated faster, better stakeholder decisions than abstract aesthetic discussions. Concrete is always clearer than conceptual.
lesson_03
Internal users know more than you think
Sales and Support teams had invaluable client knowledge. Card sorting sessions surfaced dashboard improvements that no amount of user research would have revealed as quickly.
← T-Mobile
All 5 projects complete ✓
Back to Portfolio →