Legacy to next generation · UX strategy · Desktop application
Reviving a Legacy Leader - The AppScan Standard Revamp
Modernizing the experience, architecture, and workflows of a revenue-critical AST product to match the strength of its engine and defend its position against a new wave of competitors.
Context & problem
A first-class engine wrapped in a legacy experience
AppScan Standard, as the company's flagship DAST product, carried most of the revenue. The scanning engine was and is still the strongest in the market and improving every release, but the surrounding experience hadn't kept up.
Meanwhile, a new wave of security competitors and well-funded startups were entering the AST space with modern interfaces, clearer workflows, and lower learning curves — putting a mature, high-margin product at strategic risk.
Why a revamp was needed now
Consumerization of IT. Users now expected enterprise tools to feel like the consumer apps they used daily; navigation and interaction patterns had to align with current standards.
Accessibility. Basic UX hygiene was missing and had become a hurdle for sales.
Technology shift to WPF. UI changes could become easier, but the design system and structure need to support faster delivery as well.
Usability debt. Years of feature additions on top of legacy IA had created friction in nearly every core flow.
Section
Discovery & validation
Grounding the revamp in evidence
Before committing to a direction, I ran a structured discovery phase to make sure the revamp would solve real user problems — not just refresh the visuals.
Methods
Heuristic evaluation. Deep, screen-by-screen audit of the legacy product with concrete, prioritized recommendations.
Customer interview analysis — re-coding raw transcripts from existing interviews to surface recurring pain themes across personas (security analysts, Developers, CISOs).
Competitive research — mapping how emerging AST competitors framed scanning, triage, and reporting workflows in a modern UI.
Themes that emerged
Five problem areas kept surfacing:
Low user efficiency
Lack of data-driven decisions
Missing guidance and communication
Weak accessibility and standards alignment
Painful troubleshooting
These became the pillars for the concept.
Solution
A pillar-driven concept, executed across the product's most-used surfaces
Concept pillars
User efficiency. Fewer clicks, clear defaults, less context-switching across core flows.
Data-driven decisions. Surfacing the right signals at the right moment instead of burying them in dialogs.
Guidance & communication. Telling the user what just happened, what to do next, and why - something the legacy product almost entirely lacked.
Accessibility & standards alignment. Meeting baseline accessibility and aligning with patterns users are familiar with.
Troubleshooting. Making it easier to self-diagnose scan and configuration issues without a support call.
Where the pillars showed up
Navigation & information architecture. Restructured around core workflows.
New home page & dashboard. A "welcome surface" giving status and next actions at a glance.
Scan flow with contextual actions. Exposing most relevant actions per state.
Basic vs. advanced configuration. Split flow so first-time users could succeed quickly while power users kept full control.
Status & contextual guidance. From status indications on main flows, to inline guidance on specific configuration items.
The transition
Moving from a legacy product to a new architecture meant carefully scoping what had to ship as a coherent MVP vs. what could safely come later. Decisions were made against the pillars, not against feature parity for its own sake.
Customer communication ran in parallel — release notes, webinars, direct outreach, and TA enablement — so existing customers understood what was changing, why, and what to expect.
Impact
Market recognition, customer enthusiasm, measurable adoption
Customer interviews after launch surfaced strong enthusiasm for the new experience, and TAs reported a clear shift: support tickets moved from usability questions toward genuinely technical issues — the outcome the revamp was aiming for.
How I led it
Owning the product end-to-end within three months of joining
Strategy & launch. Defined inbound and outbound launch strategy across marketing, sales, and support.
Pillars & IA. Designed the concept pillars, workflows, and information architecture that anchored every design decision.
Decision discipline. Made sure every product decision, including transition trade-offs, traced back to a defined pillar.
Support enablement. Built the enablement that let TAs handle technical issues instead of usability questions.
External presence. Led conferences, customer presentations, and the design partner program.
Full ownership. Took complete responsibility for the product within three months of joining the company.
What I learned as a UX
A clear strategy creates ownership. A well defined strategy and understanding of a product vision shifts one from UX only to product ownership.
Pillars beat feature lists. A small set of well-defined pillars made hundreds of micro-decisions consistent and defensible.
Transition is a product feature. How customers move to the new version matters as much as the version itself.