Redesigning Nectar’s Navigation & Activity Page

Nectar

2022-2023

Who is Nectar

Nectar is a precision beekeeping software platform designed to help commercial beekeepers modernize and optimize their operations. By combining hardware and software, Nectar empowers migratory beekeepers to manage hives efficiently, remotely, and scientifically.

Tools
Year

2022 - 2023

My Role

Lead Product Designer

Industry

Agri-tech / Precision Agriculture (SaaS)

Team

Tamara Laforest, Senior Product Designer

Thomas Poblete, Product Manager

Felipe da Silva Pinho, Back End Developer

Grace Scharf, Front End Developer

A streamlined activity dashboard that gives managers instant clarity on yard operations—without adding complexity for field workers.

Context

To understand this use case, it’s important to first see how Nectar works and how yards and hives are organized within a beekeeping operation.

Typical Beekeeping Operation

A beekeeping operation is usually structured into yards (groups of hives) and the hives themselves.

How Nectar Works

Nectar digitizes this structure by making it easy for workers to capture field data and for managers to monitor operations. The workflow is simple:

Scan

Workers scan hive tags using their phone or an RFID scanner.

Log Data

After scanning, they record the actions performed on the hives or yards.

Visualize

Managers track progress in real time, reviewing field activities and completed tasks.

Inspections in Nectar

There are two types of inspections:

  • Yard InspectionApplies the same values and observations to all hives within a yard.

  • Hive InspectionApplies values only to the hives that are scanned, even if they belong to different yards.

Activities

Once inspections are complete, managers can view the results at multiple levels:

  • Operation LevelOverview of all yards and their activities.

  • Yard LevelOverview of activities within a single yard.

  • Hive LevelDetailed view of individual hives.

My role

As the Senior Product Designer, I partnered closely with the Product Manager to shape the vision and execution of this project. My responsibilities included:

  • Leading the design process from wireframes to high-fidelity prototypes.

  • Running usability tests with internal staff and client beekeepers to validate concepts and gather feedback.

  • Designing the final activity dashboard and navigation system, ensuring it balanced clarity for managers with ease of use for field workers.

  • Documenting design decisions and maintaining an organized Figma file to streamline collaboration and developer handoff.

This role required tight collaboration with the Product Manager to align business goals with user needs, while I focused on translating insights into intuitive, scalable design solutions.

Creation Process

The problem

The activity panel lacked the capability to display inspection report details at the operation level. Users were required to access individual yards to view in-depth information, which resulted in inefficient operation management.

Goal

The goal was to provide managers with an accurate, consolidated view of past fieldwork so they could confidently plan upcoming tasks for the next day, week, and beyond. The redesign aimed to reduce the time spent gathering data, improve visibility into team performance, and support better decision-making through a clear and intuitive interface.

My role

As the Senior Product Designer, I partnered closely with the Product Manager to shape the vision and execution of this project. My responsibilities included:

  • Leading the design process from wireframes to high-fidelity prototypes.

  • Running usability tests with internal staff and client beekeepers to validate concepts and gather feedback.

  • Designing the final activity dashboard and navigation system, ensuring it balanced clarity for managers with ease of use for field workers.

  • Documenting design decisions and maintaining an organized Figma file to streamline collaboration and developer handoff.

This role required tight collaboration with the Product Manager to align business goals with user needs, while I focused on translating insights into intuitive, scalable design solutions.

Exploration 1 - Wireframe

What Worked

Displaying operation-level metrics, giving managers a broad overview.

Providing access to detailed inspection data within the same page.

Adding filters so users could refine results and focus on what mattered most.

Using a dedicated page for activities, which offered enough space for content and potential future enhancements.

What Didn’t Work

The metrics shown were not the most relevant for the user’s needs.

The layout of metrics wasn’t scalable if more data points needed to be added later.

The location of the activity page created inconsistencies with other pages.

Separating hive and yard inspections limited the ability to provide a quick, unified overview at the yard level, which is essential for users.

Exploration 2 - Wireframe

What Worked

Improved layout of metrics, making the data easier to interpret.

Regrouped both inspection types under a new activity category called “yard visits.”

Updated navigation so that all activity levels are now accessible through tabs, improving consistency.

What Didn’t Work

The metrics still didn’t represent the most relevant data for users.

At a glance, managers couldn’t see the full picture of what happened at the yard. They needed to click into both yard and hive inspections separately to view details, whereas users expected a consolidated overview of all practices applied at the yard, regardless of inspection type.

User Testing & Insights

To validate the new navigation and activity page, I conducted usability tests with 5 participants: 3 internal Nectar employees and 3 beekeepers operation managers. Using a Figma prototype, participants were asked to complete a series of tasks while I observed their ease of use, efficiency, and overall comprehension.

What Worked

The new navigation felt clearer and better organized.

Users appreciated the visual charts, which made data easier to interpret.

Most tasks were completed successfully, with 12 out of 14 tasks achieving 100% completion

What Didn’t Work

Some terminology was confusing.

Users requested more filters for specific practices (e.g., feeding types).

Managers struggled to get a quick yard-level overview without clicking into multiple inspections.

Impact on the Design

Based on these insights, I made several improvements:

  • Regrouped hive and yard inspections into a single activity type, “Yard Visits”, for clearer yard-level visibility.

  • Renamed confusing labels to improve comprehension.

  • Refined filters to focus on practices and date ranges most relevant to managers.

  • Adjusted chart displays at the yard level to reduce noise and improve clarity.

Overall, testing confirmed that the new activity page added significant value for day-to-day decision-making, while also highlighting where adjustments were needed before finalizing the design.

Prototype used for testing

Final Solution

The final design consolidates hive inspections and yard inspections into a single activity type called “Yard Visit.” This provides managers with a complete overview of all practices applied within a yard, regardless of whether they came from hive-level or yard-level actions.

Unified Overview
All practices are displayed in one place, eliminating the need to switch between inspection types. This gives managers the quick clarity they need to understand yard activity at a glance.

Detailed Drill-Down
If users need more granularity, they can open an in-depth detail modal to review specific inspection data without leaving the page. This balances quick visibility with access to detail when necessary.

Relevant Metrics

Metrics displayed are now aligned with managers’ real priorities, helping them better plan their day and make informed decisions.

Focused Filters
Only the most important and frequently used filters are shown at this level, reducing clutter and allowing managers to refine results efficiently.

Overall, this solution provides both high-level visibility and drill-down flexibility, making it faster and easier for managers to monitor operations, track practices, and plan their workday.

Figma Organization

To streamline collaboration with developers, I structured the Figma file with clear organization and documentation. Each page included explanations of components and flows, making it easy for developers to understand functionality at a glance. I also designed every possible use case and variation, ensuring that no scenarios were overlooked during development and handoff.

Looking back

Looking back

What I learned

Beekeeping operations vary widely, and designing a solution flexible enough to meet different needs while keeping the experience simple is a real challenge.

What went well

Collaboration with the team was smooth and efficient, and early validation with users provided quick, actionable insights that guided the design.

What could be improved

Involving a broader range of user types during testing would have uncovered additional perspectives and ensured the solution addressed an even wider set of needs.

Let’s work

together

2025 © tamara laforest

Back to top

Let’s work

together

2025 © tamara laforest

Back to top

Let’s work

together

2025 © tamara laforest

Back to top