January 2020 - March 2020
Mobile Application
Senior Product Designer
Our goal is to create an app that CXO users could easily navigate to view energy optimization metrics. Having this information available on an app will significantly reduce the time these users require to determine the best solutions for their buildings portfolios moving forward.
The primary users of EOS are customer executives, the key decision-makers in upgrading their buildings to be more energy efficient. Providing an easy application to track energy savings and related climate impacts enables these users to better understand how their buildings are impacting the environment and will compel them to optimize for more energy efficiency.
Artifacts: Multiple discovery- and define-stage research, conceptual, and visual models
At AWS, we adopt a design delivery method that integrates crucial phases: Discovery, Concept, Detail, and Deploy—for all our projects.
At Honeywell, our product organization leverages a design approach for definition, development, delivery, and monetization which we call Z21--moving us from “zero to one” or from new idea to first revenue--to increase the value of our offerings and speed them to market. Before I can begin designing, I need to better understand the user's perspective leveraging two targeted design exercises: Z21 Discovery and competitive analysis.
My design team's pre-discovery started with a Z21 presentation lead by the product owner, breaking down the objective, timeline, and workshopped high-level diagrams.
I worked with our research team to create a competitive analysis that would help us understand what others were producing in the sustainability and energy optimization space. We analyzed competitor companies and other third-parties to determine the main functions driving this market.
Intensive research helped us determine what were the most informative use cases we needed to articulate and design toward. Also How would the app be structured.
We concluded that multiple app version releases would best meet our engineering timelines while at the same time delivering a flexible and feedback-driven augmentation model. Thus, a first release “MVP0” would ship in early March, followed shortly thereafter by MVP1.
Upon understanding the project needs through the Z21 proposal and competitive analysis, the next step was to create a product sitemap to organize content and show visually the relationships between pages.
As part of one of the first teams within Honeywell to build a net-new native app, I was eager to design something both eye-catching and highly usable.
I tend to create my initial designs in my notebook because I find that I can quickly iterate using paper and pencil. This is important because you can quickly redesign the task flows without committing to a final design, reducing stress, time, and avoiding design debt.
While working on various sketch iterations, I met with the Honeywell design system team to better understand and align my efforts to Honeywell’s overarching mobile strategy. To that end, I created three candidate card design specifications to communicate requirements to the engineering teams.
I developed multiple high-fidelity wireframe iterations to test against our design specifications, gather feedback, and incrementally lift the user experience.
Once my low-fidelity wireframes were reviewed and validated, my efforts quickly transitioned to creating the first artifacts for wider testing and iteration.
We achieved our design goals within timeline and budget. Currently, the EOS application is under development and slated for an early March MVP0 release.
Elevating User Experience to Meet Industry Standards
A UX Case Study on Innovative Solution Integration