[{"data":1,"prerenderedAt":301},["ShallowReactive",2],{"article-\u002Fblog\u002Fdesigning-beyond-the-interface-escape":3},{"id":4,"title":5,"aiSummary":6,"articleSection":7,"author":8,"body":12,"breadcrumbs":265,"cover":274,"cta":275,"date":277,"dateModified":277,"datePublished":277,"description":278,"extension":279,"externalUrl":280,"faq":280,"footerCta":6,"footerCtaLabel":281,"footerCtaText":282,"howToDescription":280,"howToName":280,"howToSteps":280,"howToTotalTime":280,"image":280,"imageHeight":280,"imageWidth":280,"keywords":283,"lang":290,"meta":291,"navigation":276,"path":292,"publisher":280,"readingTime":293,"seo":294,"source":280,"stem":295,"tags":296,"type":299,"wordCount":280,"__hash__":300},"blog\u002Fblog\u002Fdesigning-beyond-the-interface-escape.md","Designing beyond the interface: Escape in developers' workflows",false,"Product Design",{"name":9,"url":10,"jobTitle":11},"Sophie Boulaaouli","https:\u002F\u002Fprodju.com","Product Designer & Fondatrice",{"type":13,"value":14,"toc":250},"minimark",[15,23,26,29,34,37,50,54,57,66,70,75,78,83,87,95,102,106,109,115,119,125,135,141,145,148,163,167,170,181,184,195,237,240],[16,17,18],"p",{},[19,20],"img",{"alt":21,"src":22},"Escape integration into CI\u002FCD workflow","\u002Fscreens\u002Fescape-ui-onboarding.png",[16,24,25],{},"When designing a product, it's easy to focus on the interface. But in complex B2B environments, the real challenge lies elsewhere. A product doesn't live on a screen, it lives inside an ecosystem.",[16,27,28],{},"This is exactly what I worked on as Founding Product Designer at Escape, a cybersecurity SaaS built for technical teams.",[30,31,33],"h2",{"id":32},"from-tool-to-workflow-integration","From tool to workflow integration",[16,35,36],{},"Escape is not a standalone product used occasionally. It is deeply embedded into the daily workflow of developers, security teams, and companies shipping code continuously.",[38,39,42],"alert-callout",{"label":40,"type":41},"Founding principle","tip",[16,43,44,45,49],{},"Instead of asking users to \"come to the product\", we designed Escape to ",[46,47,48],"strong",{},"meet users where they already work",".",[30,51,53],{"id":52},"understanding-the-real-user-journey","Understanding the real user journey",[16,55,56],{},"A typical user is not \"using a cybersecurity tool\". They are writing code, shipping features, reviewing pull requests, fixing bugs. Security is just one part of that flow.",[16,58,59,60,63],{},"So the question wasn't \"How do we design a good interface?\", but",[61,62],"br",{},[46,64,65],{},"\"How does Escape fit naturally into the way teams already build and ship software?\"",[30,67,69],{"id":68},"a-product-embedded-in-the-development-lifecycle","A product embedded in the development lifecycle",[71,72,74],"h3",{"id":73},"_1-continuous-scanning-within-cicd","1. Continuous scanning within CI\u002FCD",[16,76,77],{},"Escape integrates directly into the CI pipeline. When a developer ships a new feature, a security scan is automatically triggered. No extra step, no context switching. Security becomes part of the delivery process, not a separate task.",[16,79,80],{},[19,81],{"alt":21,"src":82},"\u002Fimages\u002Fescape-into-workflow.png",[71,84,86],{"id":85},"_2-from-issue-detection-to-actionable-insight","2. From issue detection to actionable insight",[16,88,89,90,94],{},"When a vulnerability is detected, a link is generated and the developer is redirected into Escape product. They don't see raw data, they see a clear explanation of the issue, its impact, and most importantly ",[91,92,93],"em",{},"how to fix it",". Turning complex security data into actionable decisions was one of the central design challenges.",[16,96,97],{},[19,98],{"alt":99,"src":100,"style":101},"Escape Issue explanation","\u002Fscreens\u002Fescape-issue.png","width:50%; display: block; margin: 0 auto; border-radius: 0.5rem",[71,103,105],{"id":104},"_3-integration-with-existing-tools-jira","3. Integration with existing tools (Jira)",[16,107,108],{},"Fixing an issue should not break the workflow. From Escape, users can create a Jira ticket directly, assign it, and integrate it into their existing backlog. Escape doesn't replace tools — it connects them.",[16,110,111],{},[19,112],{"alt":113,"src":114},"Escape Jira integration","\u002Fscreens\u002Fescape-with-jira-integration.png",[71,116,118],{"id":117},"_4-supporting-two-personas-developers-cisos","4. Supporting two personas: developers → CISOs",[16,120,121,122,124],{},"Developers need fast, clear, actionable feedback. They want to fix issues without friction. Security teams and CISOs need visibility and the ability to track progress over time.",[61,123],{}," To serve both realities:",[126,127,128,132],"ul",{},[129,130,131],"li",{},"detailed issue views for developers,",[129,133,134],{},"and a monitoring dashboard for security leaders (number of vulnerabilities, resolution status, evolution over time)",[16,136,137],{},[19,138],{"alt":139,"src":140},"Escape monitoring dashboard","\u002Fscreens\u002Fescape-ciso-monitoring.png",[30,142,144],{"id":143},"designing-for-systems-not-screens","Designing for systems, not screens",[16,146,147],{},"One of the key challenges was handling complexity: APIs, technical data, multiple integrations, different user roles. The goal was never to simplify the system itself, it was to make it understandable and actionable.",[149,150,152],"key-takeaways",{"title":151},"Design principles",[126,153,154,157,160],{},[129,155,156],{},"Prioritize clarity over exhaustiveness",[129,158,159],{},"Guide users toward action",[129,161,162],{},"Reduce cognitive load in high-complexity contexts",[30,164,166],{"id":165},"discovery-design-system-and-impact","Discovery, design system and impact",[16,168,169],{},"To make the right decisions, we stayed close to users:",[126,171,172,175,178],{},[129,173,174],{},"a Discord channel to interact directly with active users,",[129,176,177],{},"regular interviews,",[129,179,180],{},"and continuous feedback loops.",[16,182,183],{},"This allowed us to identify friction points early, validate assumptions quickly, and iterate fast in a startup environment.",[16,185,186,187,194],{},"As the product grew, we also built a ",[188,189,193],"a",{"href":190,"rel":191},"https:\u002F\u002Fescape.tech\u002Fblog\u002Fescape-design-system\u002F",[192],"nofollow","design system integrated with Storybook",", to ensure consistency across the product, accelerate delivery, and create a shared language between design and engineering.",[38,196,198,205],{"label":197,"type":41},"Impact",[16,199,200,201,203],{},"By integrating Escape directly into existing developer workflows, we achieved:",[61,202],{},[61,204],{},[126,206,207,213,219,225,231],{},[129,208,209,212],{},[46,210,211],{},"Reduced Friction:"," Eliminated context-switching by embedding security processes directly into the CI\u002FCD pipeline.",[129,214,215,218],{},[46,216,217],{},"Accelerated Resolution:"," Shortened the time-to-fix by transforming raw security data into clear, actionable developer tasks.",[129,220,221,224],{},[46,222,223],{},"High Technical Adoption:"," Drove consistent product usage by respecting the natural coding habits and tools (like Jira) of engineering teams.",[129,226,227,230],{},[46,228,229],{},"Strategic Visibility:"," Empowered CISOs and security leaders with real-time tracking of vulnerability trends and resolution progress.",[129,232,233,236],{},[46,234,235],{},"Cultural Shift:"," Successfully transitioned security from a \"final check\" bottleneck to a continuous, integrated part of the development lifecycle.",[238,239],"hr",{},[241,242,247],"cta-block",{"external":243,"href":244,"label":245,"title":246},"true","https:\u002F\u002Fcal.com\u002Fprodju\u002F30min","Let's talk about your product","Building a complex B2B product?",[16,248,249],{},"30 minutes to talk about your product integration challenges and user adoption strategy.",{"title":251,"searchDepth":252,"depth":252,"links":253},"",2,[254,255,256,263,264],{"id":32,"depth":252,"text":33},{"id":52,"depth":252,"text":53},{"id":68,"depth":252,"text":69,"children":257},[258,260,261,262],{"id":73,"depth":259,"text":74},3,{"id":85,"depth":259,"text":86},{"id":104,"depth":259,"text":105},{"id":117,"depth":259,"text":118},{"id":143,"depth":252,"text":144},{"id":165,"depth":252,"text":166},[266,268,271],{"name":267,"url":10},"Accueil",{"name":269,"url":270},"Blog","https:\u002F\u002Fprodju.com\u002Fblog",{"name":272,"url":273},"Designing beyond the interface: how Escape integrates into developers' workflows","https:\u002F\u002Fprodju.com\u002Fblog\u002Fdesigning-beyond-the-interface-escape","\u002Fscreens\u002Fescape-ui-design-interface-inventory.png",{"title":246,"description":249,"href":244,"label":245,"external":276},true,"2026-04-28","In complex B2B environments, the real challenge isn't designing a great interface. It's designing how a product fits into its users' ecosystem. A look back at my experience as Founding Product Designer at Escape.","md",null,"Let's talk","Working on a SaaS product or MVP?",[284,7,285,286,287,288,289],"Escape","B2B SaaS","developer workflow","cybersecurity","CI\u002FCD","Founding Product Designer","en",{},"\u002Fblog\u002Fdesigning-beyond-the-interface-escape",6,{"title":5,"description":278},"blog\u002Fdesigning-beyond-the-interface-escape",[7,297,298],"B2B","Cybersecurity","BlogPosting","lg3XUa5ZJLtqJTQolA-46Iz36xQ-kI-FOPbezV204Kk",1779132605949]