Digital Product Designer
weatherlinkcom.png

WeatherLink.com


THE PRODUCT

Weatherlink is a dashboard website that serves as a platform for users to view live and archived data from their weather and agricultural sensors. Besides visualizing data, this website needs to support sharing and managing sharing of stations, display a map that can accommodate tens of thousands of public stations, support account specific tiers/locked features, contain settings for calibrating sensors, export data,

MY ROLE

The challenge

Visual Design, User Experience

Work with managers and engineers to figure out how new and legacy devices can be incorporated into this new web application in a cohesive manner. Ensure all data readouts are formatted to industry standards and include features from legacy software.

Before starting the visual design, it was important for me to figure out how this new piece of software would fit into the existing ecosystem and to understand all the unique use cases and scenario’s that we would have to support based on the variety of different users we would have. To help guide our team, I worked with firmware engineers, product managers and software engineers to create a variety of charts and tables to help keep track of the various requirements.


For our design styles and basic components we leveraged as much as we could from what we had created in the Enviromonitor project to ensure consistency across our applications. Throughout the process of this project multiple presentations were give to stakeholders to pitch features improvements and gain consensus on how to proceed with the product, shown below was one of the presentations.


After getting stakeholder approval, I created documentation for the engineer to help aid in implementation. Shown below are various examples from different presentation keynotes. For specifications we used Zeplin and then migrated to Figma later.


As the product matured we began to add more features to the web app. One of the more difficult features to add was a share functionality. But because the share functionality has dependencies on what paid tier they have, the type of devices they own, which particular section the user is looking at and the access level they have it became really difficult for members of the team to keep track of the business logic. To help with that I worked with stakeholders to build a comprehensive spreadsheet to keep track of every scenario.