EverVolt
Multi-platform
PROJECT PITCH
Home Energy Management System and support ecosystem
CLIENT
Panasonic
ROLE & TEAM composition
Product designer
PM, 2x QA, 2x React Native devs, 3x FE, 2x BE
PERIOD
December 2021 - May 2022 (6 months)
TOOLS
Figma, MUI X, Miro
KEY RESPONSIBILITIES
Gathering business logic from stakeholder
Conducting end-user interviews
Refining requirements and designing them into features
UI Kit maintenance and synchronisation with front-end
Designing new features
Improving existing functionalities
KEY DELIVERABLES
UI Kit
Smartphone iOS/Android app for end-users
Smartphone iOS/Android app for installers
Back-office panel for admins
Mockups & prototypes of new functionalities
Design notes for developer handoff
STATUS
COMPLETED
Emphatise
This project presented a challenge due to the involvement of multiple personas in various applications within the same multiplatform.
What and how
PERSONAS
I first established distinct personas for each application, taking into consideration their specific goals, work patterns, and pain points. Later, I confirmed whether these personas aligned with the research insights.
What and how
CO-CREATION WORKSPACE
Took part in three event storming sessions with the client to map out the process, functional clusters, and Command-Query Responsibility Segregation which gave the team valuable insights since this project heavily relied on software-hardware communication.
What and how
STAKEHOLDER REVIEWS
Before starting developing each application, we've scheduled calls where I presented either a rough or hi-fi prototype of the flows and functionalities to monitor if we're on the right track.
What and how
COMPETITIVE ANALYSIS
Researched and created a feature matrix of the competitors products.
What and how
JOURNEY MAPPING
The different personas each interacted with a distinct application, resulting in unique journeys. However, these journeys were interdependent and interconnected with each other. Identifying the “total journey” from the outset was essential for comprehending the project.
What and how
USER SURVEY
I used surveys at the beginning and during the alpha phase of the project to gather real user inputs on ideas and build solutions.
Define
The project's MVPs were initially outlined by the customer at the beginning of the project. The web apps involved in this project utilized the organization's own "accelerator" SaaS, which we rebranded to their preference.
PRODUCT #1
Web and native application for homeowners to track and manage their home energy systems.
PerSONA #1: HOME OWNER
Tech savvy
Energy conscious
Data-driven
Cost-conscious
Environmentally conscious
User-friendly
Time-sensitive
PLANNED FEATURES
Aggregated energy dashboard
Live "flow" energy diagram
History data
System usage profiles
Alerts view (/w suggested solutions)
Profile settings
Contact support
Power demand requests
Electricity cost
Net grid metrics
PAIN POINTS TO ADDRESS
Complex installation process
Limited compatibility
Inaccurate data and readings
Lack of user-friendly interface
Insufficient support and updates
goals that were met during the project duration
PRODUCT #2
On-site application for technicians to effortlessly set up a new system at the residential client's place.
PerSONA #2: INSTALLER
Tech savvy
Expert at solar installations
Electrician
PLANNED FEATURES
List of commissioned sites
Comissioning process
No-internet fallback
Safety checkllist
Firmware update
Access to live data of sites
Access to site logs
Advanced inverted settings
PAIN POINTS TO ADDRESS
Complex installation process
Lack of mobile app
Connectivity issues
Resistance to change
Multiple apps to complete commissioning
goals that were met during the project duration
PRODUCT #3
Web application for sysadmins to oversee, manage, and assist residential users and installation professionals.
PerSONA #3: SYSTEMS ADMINISTRATOR
Tech savvy
Knowledge of HEMS installations
Attention to details
Problemsolver
PLANNED FEATURES
Dashboard of commissioned sites (/w map)
In-depth view of each site
Ability to modify site devices
Ability to define system-wide assets
Alerts dashboard
Remote firmware update
User and organization management
Ability to change Power Profiles remotely
PAIN POINTS TO ADDRESS
Dated software with bad UX
Lack of asset management
Lack of alert descriptions and solutions
goals that were met during the project duration
Ideate
Given the customer's precise idea of the desired outcome, and our use of our exclusive SaaS solution as the project's “backbone,” most high-level processes and features were established. The primary concern was to cater to the unique client requirements and adhere to the project completion deadline.
How I've handled it
HOW MIGHT WE?
Given the problem statements defined in the early stage of the project I've turned those challenges into questions "How might we solve problem statement X". This opened up mine and the team way of thinking to come up with novel solutions.
How I've handled it
MIND-MAPPING
By mapping all of the flows, functions and processes we managed to iterate them faster than by presenting lo/hi-fi mockups to the client. Those were discussed in the next phase.
How I've handled it
SCAMPER
This method provided a good key to question existing flows and processes to optimise for development, and future releases.
Prototype
The deliverables that I’ve created for this project ranged from a multi-platform UI kit to annotated user-flows for easier dev-handoff.
Home Owner app
platforms: iOS/ANDROID + WEB
Installer app
platforms: iOS/ANDROID
Challenges & Solutions
Although I lacked prior experience in the insurance industry, I overcame the challenge of entering this project by conducting research and engaging in extensive Q&A sessions with team members, stakeholders, and users. Through these efforts, I successfully familiarized myself with the workings of the platform and gained an understanding of its underlying real-world processes.
How I've handled it
HARDWARE COMPATIBILITY
Due to the strong reliance on software - hardware communication, I had to actively participate in multiple meetings and seek guidance from my tech-lead to understand the intricacies of the platform design flow.
How I've handled it
MUlTI-PLATFORM UK KIT
Since the project had strict and short deadlines, the fact that there was one centralised UI kit accelerated the design and implementation of the web, and mobile apps.
How I've handled it
TEAM COMMUNICATION
To facilitate the implementation of the next step, I created interactive prototypes and provided notes and comments, as each application was developed in parallel, emphasizing the importance of documenting and communicating the designs through Figma.
Key outcomes and impact of the team
DEVELOPED AND Published on
3
platforms
2x iOS, 2x Android, 2x Web
ONBOARDED
3
USER TYPES
Home owners, Installers, and a System Admin
ALL PROJECTS USED
ONE UI KIT
With some platform differences all applications soursed a single UI kit.
Upnext
©️ 2024 marcinbauer.com
Last updated: 25.03.2024