← Back
Tenable - Landing page iteration
Background
Leading up to a pilot release, my team had different hypotheses about the hierarchy of some content on the landing page we were releasing.
What hypothesis were we trying to test?
- Users would engage more with a breakdown of their exploitable vulnerabilities than with summaries of their overall vulnerabilities, assets and scans.
Outcome
- Used telemetry to learn that the summary information was at least as important as the exploitable vulnerabilities data and iterated on the design to promote that data.
Early wireframe
From the start, I felt it was important to feature a summary of a user's vulnerabilities, assets and scans on the landing page. Not only did this data provide a succinct overview of the user's environment, but they also served as navigation to those parts of the application.
First Release
As we approached the first release, the Product team held a different hypothesis: that the user would gravitate toward seeing a breakdown of their exploitable vulnerabilities.
We agreed to release a first version in line with this hypothesis, using telemetry to learn how users were engaging with the page. Exploitable vulnerabilities was put front and center, while the summary info was provided as support below.
Findings after the first two weeks of use
After two weeks, we gathered the data and found that while users were engaging the first slice of the exploitable vulnerabilities hero widget, they were equally seeking out the summaries placed below.
Proposed design update
In response to these findings, we updated the design to promote the vulnerabilities, assets and scans overviews to a location where they could better serve as highlights and navigation (aka, the top of the page 😄).
