Need more details?
SHIPPED
Savvy's playbook lifecycle
The reverse engineering of a no-code security tool
About
We had a clear concept for "Tara"—an end-user-facing security interface designed to mitigate risks in real-time by engaging employees at critical moments. To activate Tara, we needed a way for security administrators to configure her actions and triggers. This led us to reverse-engineer the security playbooks that define when and how Tara would appear.
Step by step, we developed the Playbook Lifecycle, allowing admins to browse, customize, and publish playbook templates to specific end-users, ensuring Tara interacts with them in critical situations.
Company
Savvy Security
Role
Product Design Lead
Time frame
2022-2023
Research & Ideation
Our journey began with researching existing security automation tools and no-code platforms, and analyzing how different industries approach similar challenges. We interviewed our Desogn Partners to understand their workflows, pain points, and what features would add the most value.
During ideation, we focused on balancing flexibility and simplicity, testing early concepts like playbook templates, modular building blocks, and streamlined workflows. Collaborating with design partners, we refined these ideas, ensuring the final solution would be both powerful and intuitive.
Our challenge was to transform Tara's intuitive functionality into a simple yet flexible no-code backoffice for security admins.
Solution
What must happen on the backend for Tara to work effectively on the frontend? How could we give CISOs the power to manage when and how Tara intervenes without making the process too complicated?
We began by sketching out the lifecycle of a playbook:
Browsing Templates: Playbook catalog of pre-made playbooks with filtering and search capabilities to help them find what best fit their needs
Previewing Playbooks: Admins needed to be able to see how a playbook worked before committing
Editing Playbooks: Once a template was selected, the playbook editor would allow to modify it
Testing and Publishing: Allow gradual rollouts, before fully launching a playbook
Monitoring: After publishing, the admin could monitor all playbooks under "My Playbooks"
Learning
Continuous design testing
Throughout the design process, we worked closely with our design partners, CISOs from various organizations.
We did feedback sessions on initial prototypes and observed them using developed features. This allowed us to refine the flow constantly to our users' needs.
Key takeaways
Our biggest learning was that simplicity is key. Our users are already busy. What helped them most were well-made templates and smart recommendations, rather than the deep customization capabilities. Every step of the flow is important, but the UX of the Playbook Catalog should have been the heart of it, not the Playbook Editor.
Want to hear more about this project?
Let's get in touch.
lukalaraf@gmail.com
Luka Lara Fritzsche
© 2024
Made with ♥
Let's get in touch.
lukalaraf@gmail.com
Luka Lara Fritzsche
© 2024
Made with ♥
I'm Luka
Product Designer based in Tel Aviv.
I love turning complex tasks into simple designs.
This portfolio shines best on desktop 🌟
Hop over for the full experience.