Reducing friction in a cloud-native security platform
Panoptica was Cisco Outshift's SaaS solution for securing microservices in cloud-native environments. While powerful, its onboarding process was so complex it required white-glove support.
My challenge was to make it self-serve, reducing friction, increasing activation, and giving users a clearer path to value. Acting as a player-coach, I led the design team while working hands-on to prototype, test, and validate new growth flows.
Scrappy experiments
With engineering deep in a major architectural overhaul, waiting for code changes wasn't an option. We used Appcues overlays to rapidly validate new onboarding paths without touching the product itself. This let us run experiments at a pace engineering couldn't support, generating real signal from real users while the platform was still being rebuilt underneath.

Streamlining touchpoints
We then mapped the full funnel and identified where users were dropping off. Rather than redesigning everything, we focused only on the critical moments: marketing pages, Recon.cloud, IAM, and the product's first-run experience. Simplifying those touchpoints end to end reduced the cognitive load without requiring a complete overhaul.

Adaptive flows
Not all users had the same needs. We introduced flows that adapted to the user: lighter and exploratory for hobbyist developers, more structured and outcome-driven for enterprise buyers. Keeping both paths relevant without bloating the experience required constant prioritization and a willingness to cut.


Proving self-serve was possible
These quick, scrappy interventions traded polish for speed, but they worked. We demonstrated that users could successfully activate without a solution engineer, and in doing so, laid the groundwork for future growth experiments.
Key takeaway: In complex enterprise ecosystems, success isn't about perfect cohesion, it's about finding the moments of value and helping users get there fast.