Design Process
​​
Requirement Gathering
Research and Analysis​
​
​
​
Project Status Analysis
UX AI Definition
Site Map​​
​
​
High-fi Design
Accessibility Design
Demo​
​
​
Demo Feedback
Iteration
QA testing​
​
Understand
As we've seen, this project is complex and lacked clear leadership, a Business Analyst, and other key resources. Without a kickoff meeting to start, we still tried to get aligned, and to be proactive. We started a series of meetings with stakeholders, PMs, solution architects, tech leads, and others to gather requirements, needs, and goals. To better understand these requirements, we listed them out and reviewed them within our design team. In parallel, we did some exploration and research into myEbusiness (old internal tool) and myEntergy (sister website) to determine their pros and cons. Due to the constrained timeline, we also made weekly plans for design sprints.
Website exploration and research
Fig.1- myEbusiness & myEntergy research
Ideation
Based on the insights we discovered from stakeholder meetings and existing sister websites research, we crafted our site map to help us navigate the site, as well as UX/UI action items. Since Entergy had moved to Salesforce, residential customers were already using a new application created in Salesforce Community Cloud. We also evaluated the legacy tool against the Salesforce successor and their key features.​
Primary Navigation Site Map
Fig.1- Legacy vs. Salesforce
Prototype
After we defined key features, we started designing and creating new components, keeping in mind that the user experience had to be designed to match the highly customized residential sister-site.​
Feature 1: Account Manager: manage and add accounts
Feature 2: Bills payments and auto pay
Make a Payment Flow
Auto Pay Flow
How were we collaborating with developers and cross-functional teams?
Jira was the main collaboration tool for working in close cooperation with developers and QA testers, along with demo reviews twice a week with all teams for quick feedback-driven iterations.
Reflection
This was a 5-month project off to a bad start: no clear leadership, no Business Analyst on the team, difficulty getting the right people involved to help, no kick off meeting, and inefficient communication channels.
​​
Some learnings I got from this project:
-
Be proactive and involve the appropriate project partners as soon as you notice any issues.
-
Advocate for your work or the work of others.
-
Develop relationships so that you know how and where to go for help.​
-
Open up communication channels to ensure that the right people are involved in breaking down silos.​