Porter is a Reponse Tool for Blockchain activity for the internal analysts team. Customers of signed web3 clients would link their smart contracts to Porter, to which the internal analysts team would identify and manage automated alerts, ensuring the safety of the customer.
I took part in the redesign of our client, Porter’s, internal alert software, the Incident Response Tool. The main challenges were time constraints, the lack of design files, and the steep learning curve in a new industry. I diligently documented and shared my work through active communication and regular feedback with the Response team and development teams to overcome these challenges. This effort successfully resolved a crucial issue within the tool, greatly enhancing the team's efficiency and scalability for future opportunities.
My specific role was to redesign the summary view page to streamline alert searches. I had worked with a lead designer on this project for a fast two week sprint. I would lead meetings with the Response team, design, and then converge with the lead designer.
On average, each analyst handles 120 alerts daily, which involves a lot of repetitive work in their workflow.
Reinforcing efficiency in their work processes is paramount to save repetition.
After conducting user testing and gaining insights into how the response team works, I defined the scope of the redesign project. Given the tight two week timeline, I had to prioritize tasks strategically. To ensure alignment with the team, I crafted a journey map that visually highlighted the most pressing areas for our initial focus.
Approaching the goals of the Response Agent:
The incidents should quickly: Identify, Track, Analyze
Insufficient information in the Summary View and unclear UI elements make it difficult for users to promptly identify alerts, resulting in repetitive interactions.
Not enough information in the Summary View caused inefficiencies as users find themselves frequently toggling back and forth to access alert details. Given that users perform this action repeatedly throughout their shifts, it became imperative to rethink the importance of this summary view.
Have a project or opportunity in mind?
Porter is a Reponse Tool for Blockchain activity for the internal analysts team. Customers of signed web3 clients would link their smart contracts to Porter, to which the internal analysts team would identify and manage automated alerts, ensuring the safety of the customer.
I took part in the redesign of our client, Porter’s, internal alert software, the Incident Response Tool. The main challenges were time constraints, the lack of design files, and the steep learning curve in a new industry. I diligently documented and shared my work through active communication and regular feedback with the Response team and development teams to overcome these challenges. This effort successfully resolved a crucial issue within the tool, greatly enhancing the team's efficiency and scalability for future opportunities.
My specific role was to redesign the summary view page to streamline alert searches. I had worked with a lead designer on this project for a fast two week sprint. I would lead meetings with the Response team, design, and then converge with the lead designer.
On average, each analyst handles 120 alerts daily, which involves a lot of repetitive work in their workflow.
Reinforcing efficiency in their work processes is paramount to save repetition.
After conducting user testing and gaining insights into how the response team works, I defined the scope of the redesign project. Given the tight two week timeline, I had to prioritize tasks strategically. To ensure alignment with the team, I crafted a journey map that visually highlighted the most pressing areas for our initial focus.
Approaching the goals of the Response Agent:
The incidents should quickly: Identify, Track, Analyze
Insufficient information in the Summary View and unclear UI elements make it difficult for users to promptly identify alerts, resulting in repetitive interactions.
Not enough information in the Summary View caused inefficiencies as users find themselves frequently toggling back and forth to access alert details. Given that users perform this action repeatedly throughout their shifts, it became imperative to rethink the importance of this summary view.
Have a project or opportunity in mind?
Porter is a Reponse Tool for Blockchain activity for the internal analysts team. Customers of signed web3 clients would link their smart contracts to Porter, to which the internal analysts team would identify and manage automated alerts, ensuring the safety of the customer.
I took part in the redesign of our client, Porter’s, internal alert software, the Incident Response Tool. The main challenges were time constraints, the lack of design files, and the steep learning curve in a new industry. I diligently documented and shared my work through active communication and regular feedback with the Response team and development teams to overcome these challenges. This effort successfully resolved a crucial issue within the tool, greatly enhancing the team's efficiency and scalability for future opportunities.
My specific role was to redesign the summary view page to streamline alert searches. I had worked with a lead designer on this project for a fast two week sprint. I would lead meetings with the Response team, design, and then converge with the lead designer.
On average, each analyst handles 120 alerts daily, which involves a lot of repetitive work in their workflow.
Reinforcing efficiency in their work processes is paramount to save repetition.
After conducting user testing and gaining insights into how the response team works, I defined the scope of the redesign project. Given the tight two week timeline, I had to prioritize tasks strategically. To ensure alignment with the team, I crafted a journey map that visually highlighted the most pressing areas for our initial focus.
Approaching the goals of the Response Agent:
The incidents should quickly: Identify, Track, Analyze
Insufficient information in the Summary View and unclear UI elements make it difficult for users to promptly identify alerts, resulting in repetitive interactions.
Not enough information in the Summary View caused inefficiencies as users find themselves frequently toggling back and forth to access alert details. Given that users perform this action repeatedly throughout their shifts, it became imperative to rethink the importance of this summary view.
Have a project or opportunity in mind?