Aembit – Case Study | Solving Workload IAM
Building Access Policies

Aembit – Case Study | Solving Workload IAM

Challenge

An early-stage start-up, Aembit is the?Identity Platform?that lets #DevOps and #Security manage, enforce, and audit access between federated workloads.?

Identity and access management (#IAM) for users has existed for years, but there was nothing for workloads/services. Aembit seized the opportunity to fill this need and quickly built an MVP platform using an off-the-shelf framework.

We had worked with the CTO and Co-Founder at a previous successful start-up 10 years ago (acquired by Okta 2 years later) and kept in touch, so he knew our capabilities and brought us on board to help.

Aembit had already been selected as a Gartner Cool Vendor in Identity-First Security. So while the MVP was functional, they needed to unify the workflow with a more intuitive user interface.?

Also, we needed to move fast so we constrained ourselves by addressing only what currently existed—adding no major new features.


No alt text provided for this image
Access Policy Builder view – Empty
No alt text provided for this image
Access Policy Builder view – Completed
No alt text provided for this image
Access Policy view



Approach

Before the engagement, Aembit had built a platform based on assumptions of their customers’ behaviors. One of our first steps was to validate (or invalidate) those assumptions. This means watching real customers use their MVP product.


No alt text provided for this image
User testing the MVP product


We started with wireframes to capture all current features and reworked the flow into a more logical process. We tested with users. In doing so, we recognized there was a missing element that tied the core of the platform together. After some iteration, a builder view was introduced to perfectly solve the problem. Throughout the entire process, we user tested, and tested, and tested, to validate every assumption.?


No alt text provided for this image
Testing the wireframes

Another key feature was the ability to add, edit, and delete entities without navigating away from the current view or using modals. We resolved this by introducing a slider panel design pattern.

As the wireframes became firm, we transitioned into creating a more unique design system that better reflected Aembit’s brand.?

With solid wireframes and a design system in place, we quickly designed mockups that were constantly user-tested.


No alt text provided for this image
Testing the mockups

Results

Testing with customers gave Aembit the confidence to build a new critical feature – an Access Policy wizard that unified the workflow. Testing also convinced us not to build a complex feature the team was excited about.

The end result is a heavily tested platform with a unique and scalable interface. Aembit was able to sell new customers and raise?$16.6M in seed funding?from Ballistic Ventures and Ten Eleven Ventures .


No alt text provided for this image


“Aembit had an MVP demonstrating product market fit, but our platform needed an intuitive and uniform UI.
This was my second time partnering with Sodium Halogen on a cybersecurity interface design, so I knew they would deliver. But their relentless incorporation of user research is what impressed me most. We had talked to these customers before, but Sodium Halogen's approach discovered new insights into how they wanted to use Aembit.
Through their user testing, we identified the need for a better way for customers to understand how the different parts of an access policy fit together. Sodium Halogen designed a policy builder that just clicked with users.
Our work together helped bring on new customers, gave our investors a clear picture of Aembit's near future, and helped close our Seed round of funding.”
Kevin Sapp , Co-Founder/CTO of Aembit



No alt text provided for this image
Client workloads
No alt text provided for this image
Workload events

要查看或添加评论,请登录

Sodium Halogen的更多文章

社区洞察

其他会员也浏览了