Product

IBM NS1 traffic steering

IBM NS1 traffic steering

Product designer

Release post

Team

Product designer

Product manager

Technical documentation

Back end engineers

Front end development

Make it the network troubleshooting tool it was meant to be, instead of the data-visualization tool it behaves as.

When a website experiences a slowdown or an error the immediate thing to check is if it is dealing with a network issue.

Pulsar isn't just a data tool — it should get users to the next step in understanding why an error is occurring.

When a website experiences a slowdown or an error the immediate thing to check is if it is dealing with a network issue.
Pulsar is not just a data tool and it needs to be tool that gets users to the next steps in understanding why an error might be occurring

When a website experiences a slowdown or an error the immediate thing to check is if it is dealing with a network issue.

Pulsar is not just a data tool and it needs to be tool that gets users to the next steps in understanding why an error might be occurring

What we tackled

Pulsar automation solution behaves as a black box. Met with PM and Back end to see what data we can pull.

Transitioned to a new design system mid-project, coordinating with frontend and pivoting fast to avoid slowdowns.

I designed through ambiguity, working in parallel with backend before feasibility was fully known. 

Design process

  1. Defined requirements with Product in discovery 

  2. User interviews with low fi prototypes 

  3. User interviews with mid fi prototypes

  4. Hi fidelity hand off with development

  5. Design iterations based on time limitations

Big wins

Largest feature update for the product that was successfully released and it caused a 73.1% spike in page visits.

Amaya Mali
Intentionally made, carefully grown.