homeworksmiso help center

🔎 behind the scenes of MISO Help Center that helps 25% more

Published Jun 2, 2024
Updated Jul 13, 2024
5 minutes read
UX ResearchUX DesignEnergy SectorSaaS

The Lay of the Land 🌎

MISO's Help Center started as most help centers do - a place to find answers. But in the world of energy market operations, where every second of downtime can impact millions of homes, it needed to be much more. But like many platforms that grow organically with their user base, it had started showing its age. Finding information felt like solving a puzzle, and users were spending more time searching than doing.

The challenges weren't just skin deep. Market participants would often keep multiple tabs open, cross-referencing information between different sections, hoping they hadn't missed anything critical. It was a digital juggling act that nobody had time for, especially when dealing with time-sensitive market operations.

What's MISO?

The Midcontinent Independent System Operator (MISO) manages one of North America's largest power grids, ensuring reliable electricity delivery to 42 million people across 15 U.S. states and Manitoba, Canada.

An Honest Conversation 💭

My Role

UX Researcher owning research from end to end

Team

2 Product designers, 2 Product managers & 5+ engineers

Timelines

Aug 23 - May 24

When our team first sat down with MISO's stakeholders, the initial ask seemed straightforward - give the Help Center a visual refresh. But after a few hours of digging into user feedback and watching people interact with the platform, we realized we were dealing with something far more fundamental.

The real story emerged during our third stakeholder interview. "I've been here ten years," one operator told us, "and I still have to write down where to find certain procedures because the navigation just isn't intuitive." This wasn't just about making things look better - it was about fundamentally rethinking how critical information should be organized and accessed.

The navigation felt like a maze, and finding relevant articles was a daily struggle. We knew the information was there - we just couldn't get to it quickly enough.

MISO Market Participant

Understanding the Complexity 🧩

Our first week was spent just understanding how market participants used the Help Center. The complexity was staggering. We shadowed operators during their work hours, watched market participants navigate through their daily workflows, and sat in on support calls. Each group had their own patterns, their own workarounds, their own way of dealing with the system's shortcomings.

The issues were clear:

What made this particularly challenging was the critical nature of the information. This wasn't just documentation - these were procedures and guidelines that impacted millions of dollars in energy transactions and affected power delivery to millions of homes.

Heuristic evaluations on specific tasks

Early heuristic evaluations revealed deep usability issues

A Familiar Problem Space 🎯

The challenge of organizing vast amounts of technical information wasn't new to us, but MISO's case was unique. We needed to create a system that could handle everything from routine market operations to emergency procedures. It needed to be both comprehensive and lightning-fast.

We spent days just mapping out the different types of information and how they interrelated:

It was like trying to organize a library where every book was equally important and might be needed at a moment's notice.

Looking Outside 🔍

We studied other Independent System Operators like CAISO, NYISO, and ERCOT. Each had their own approach, but we were particularly interested in NYISO's Member Community concept. There was something there about fostering collaboration that felt right.

The competitive analysis wasn't just about checking boxes - it was about understanding how different organizations handled similar challenges. We found that each ISO had developed unique solutions based on their specific needs, but there were common threads we could learn from.

Competitive analysis of other Help Centers

Analyzing how other ISOs handled their information architecture

Following the Data 📊

Numbers never lie, but they do tell interesting stories. Through Google Analytics and search logs analysis, we uncovered patterns that even regular users hadn't noticed. The data showed us:

This wasn't just data - it was a map of user frustration and needs. Every abandoned search represented time lost, and in MISO's world, time was literally money.

Visualization of quantitative analysis

**Data analysis revealed clear patterns in user behavior**

The Human Element 👥

User interviews revealed frustrations we hadn't anticipated. One market participant had created their own docs of important pages because they couldn't rely on the search. Another kept a spreadsheet of "emergency bookmarks" for critical procedures. These weren't just workarounds - they were cries for help.

The issues were deeply human:

Issues in the Help Center

User feedback highlighted critical pain points

Making it Work ⚡

We approached the redesign with three core principles, each born from our research and user insights:

  1. Enhanced Search Experience 🔍
    • Revamped the search flow with better filtering
    • Added popular searches based on user patterns
    • Implemented auto-suggestions for longer queries
    • Built in context-aware search results

The search improvements weren't just about better algorithms - they were about understanding how people actually looked for information in pressure situations.

Redesigned search interface

**The new search interface prioritized speed and accuracy**

  1. Streamlined Navigation 🧭
    • Implemented a modern pop-up design that reduced cognitive load
    • Optimized menu structures based on usage patterns
    • Ensured accessibility compliance for all users
    • Created quick-access paths to critical information
Modern design components

Modern design components

  1. Knowledge Base Overhaul 📚
    • Redesigned the front page for intuitive access
    • Improved link styles and navigation paths
    • Ensured content stayed current with automated update checks
    • Built in real-time notification systems for critical updates
Overhaul of knowledge base

Overhaul of knowledge base

The Results 📈

The numbers told a compelling story after launch:

But the real victory was in the qualitative feedback. Users were finding what they needed faster, support tickets for documentation issues plummeted, and the Help Center was finally living up to its name.

Final design flow

The final design balanced functionality with usability

Key Takeaways 🎓

  1. Start With User Needs 👥
    Our initial assumptions about what needed fixing were way off. Only by watching users work did we understand the real problems. Sometimes the biggest insights come from just sitting quietly and observing.

  2. Think Beyond the Interface 💡
    The best solution isn't always a new feature - sometimes it's removing barriers users have learned to work around. We found that simplifying existing paths often had more impact than adding new ones.

  3. Design for Impact
    In critical infrastructure, every second counts. Design decisions need to prioritize speed and accuracy above all else. What looks good in a portfolio might not work in the real world.

  4. Trust the Process 🔄
    Some of our early design decisions didn't work out, but that's okay. The iterative process of design, test, learn, and improve led us to better solutions than we could have planned upfront.



Want to dive deeper into the technical details? 🤓
Get in touch to schedule a presentation.

09:00:02 PM

24th of January, 2025