Network Map

Cliche? Perhaps; but I feel there is (maybe a lot) more to be done here.

My Role

I served as the principal designer and project lead for this project. I led a core team of 2 junior designers and 4 software developers.

I led and coordinated all facets of the redesign from start to finish, including: project scoping, requirements gathering, technology analysis, information architecture, user task flows, interaction flows, prototyping, and development. I also conducted user research using methods such as interviews, surveys, focus groups, and participatory design in order to address both user behavior and attitudes.

As the principal designer it was my responsibility to provide the initial wireframes and broad-stroke composition of the design. These patterns were to be the first step in rationalizing the feasibility of a planned total redesign of the product’s graphical user interface. I then oversaw junior designers through the process of designing the atomic design elements and layout flows.

The Problem

  • What’s the problem you want to solve?
    • summary here… details later
    • page was dated
    • lacked options for managing and filter data
    • lacked data discoverability
    • configuration sizes caused the page to crash!
    • external memory - forced navigating away

Problem Statement

  • Wanted to create a new “single pane of glass”
    • New landing page

Target Users

  • Who are the users?
    • F5 field engineers commonly used this to diagnose issues
    • Network engineer (Marco)
      • … but not as much due to lack of discoverability

Design Process

  • iHealth analysis to show common config sizes
  • analysis of config sizes w/ load times and crashes!
  • technology evaluation
  • reviewed multiple times with field engineers
    • design was drastically changed, back to the old design
    • initial task flows defined

Design Validation

  • Repeated task flows, to show “single pane of glass”

Next Steps

  • we’re rolling it into the mBIP