Nejat Özalp's profile
Handling malicious emails

Email-based attacks are responsible for more than 90% of all cyber security breaches. Most successful attacks start with an email. Especially when a person opens the email and gives out private information, or downloads a file.
Incident Responder is a product on Keepnet Labs which is a platform with various products to prevent email-based attacks. Incident Responder allows you to recognize and dispose of malicious emails and phishing attacks in your organization’s mailboxes.


The project’s goal is to re-design the product that gives the ability to detect and eliminate mal-intended emails sent to your organization’s mailboxes. There was already a working MVP with frequent users, but it was not really user-friendly. I had to keep what works for the user and build a user-friendly experience without having hundreds of users learn a new tool all over again. I conducted all phases of the design process from research to UI design. 

Most of the products, including the foundations and layout, were designed and developed while I was the only designer in the team. Our team has expanded since, and some additional features are the results of teamwork.

Who are these people? And why would they use this?
I interviewed lots of users and my colleagues who work directly with customers and gathered information on user habits, motivations, user feedback, requested features, competitor products, market needs, legal requirements, etc.

Defining Priorities
According to the information I collected over dozens of interviews I defined user goals and business goals. I defined KPIs and metrics that are necessary to achieve these goals

Seeking solutions
In order to find answers to the questions above, I conducted brainstorming sessions and meetings with dev teams, PM and executives. We ideated solutions on present problems and feature ones to be designed and developed, to discover potential problems and feasibility of our ideas, and avoid any future technical difficulties.

Wireframing and user testing
Based on the ideas and suggested flows that came together in the previous step, I iterated on wireframes to explore layouts and details. I prepared prototypes to test those ideas.
have created a detailed design system with a component library in Figma, I could quickly get together hi-fi wireframes with our UI elements. This abled me to test designs that look really close to final designs so stakeholders and test subjects had a more clear idea of what they see.
Tests were conducted by me, testing real users either on one-on-one sessions or as unmoderated user tests over user testing platforms and tools such as and

UI Design
I created a design system including typography, colors, a component library, spaces, effects like drop shadows, rules and restrictions for components(such as maximum character limit for form inputs and spacings), modals, forms and wizards, etc. based on Google’s material design guidelines.

Thanks to our very talented developers the final product look and works exactly how it is designed. I feel very proud to be a part of this project. This product participates in the efforts of experts for preventing hacking attempts that could cost millions of dollars.
We heard a lot of praise and good words from our users. They found new designs much more intuitive and user-friendly compared to our MVP and the product’s counterparts.
We keep tracking user behavior via analytics tools and collecting user feedback to continue improving the product.

I learned that even every product has a feature in a certain way, this doesn’t mean we shouldn’t test it and strive for the better.
Thank you for reading. Say
Handling malicious emails

Handling malicious emails