Eco-Innovate

TIMELINE

January 2020 - March 2020

PLATFORM

Mobile Application

MY ROLE

Senior Product Designer

THE CHALLENGE

Creating an emotional connection in 3 weeks

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.

Our High Level Goals:
  1. Connection and Stickiness - Building a powerful yet easy-to-use app will create emotional connection, thus keeping the CXO user engaged with the FORGE platform.
  2. Arrow in the Quiver - The app will further promote the FORGE platform with CXOs and executive champions---especially in cases where funding will come from the customer’s sustainability budget.
  3. Strong Message and Solution - Serving as an emotional hook, the app will help Honeywell capitalize on the market's current sustainability movement, while the attention and focus is high.

Users and Audience

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.

Scope of Work

Artifacts: Multiple discovery- and define-stage research, conceptual, and visual models

The Process

Trust the Process

At AWS, we adopt a design delivery method that integrates crucial phases: Discovery, Concept, Detail, and Deploy—for all our projects.

In this project we used:

  • Discovery - Understand users' needs and problems they face
  • Concept - Gather insight from the Discovery phase to further define challenges
  • Detail - Detail designs from Define-phase challenges and collaborate with a team of designers and project stakeholders
  • Deploy - Test and improve on solutions
Discovery

Discovering what users need

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.

Research Deliverables:
  • Z21 Proposal
  • Compeititve Analysis

Z21 Proposal

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.

Compeititve Analysis

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.

Concept phase

Defining an experience one task at a time

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.

Concept Deliverables:
  • Sitemap
  • Use Cases and Task Flows

Sitemap

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.

Design phase

Designing for the new product

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.

Design Deliverables:

Wireframes

I developed multiple high-fidelity wireframe iterations to test against our design specifications, gather feedback, and incrementally lift the user experience.

Deliver phase

Putting it all together

Once my low-fidelity wireframes were reviewed and validated, my efforts quickly transitioned to creating the first artifacts for wider testing and iteration.

Develop Deliverables:
  • High fidelity user flows
REFLECTION

Outcome

We achieved our design goals within timeline and budget. Currently, the EOS application is under development and slated for an early March MVP0 release.

Key Takeaways

  • Create a strategic plan to launch an MVP - This helps control out-of-scope requests that could potentially derail the project and helps to deliver a quality product within the given timeline.
  • User testing does not end after development - Design is constant iteration on improving experiences for the user. We will continue to find solutions for collecting feedback and improving the user experience.
  • Involve engineering upfront - Understanding technical limitations upfront helps inform design strategy and reduces rework.

More to explore

UX/UI
Web app
Mobile app
Team Lead
B2B

Industrial Enterprise Revamp

Elevating User Experience to Meet Industry Standards

View case study
UX/UI
Web app
Team Lead
B2C
SaaS

Reporting solution

A UX Case Study on Innovative Solution Integration

View case study