Skip to content
Milijana Smiljanic

Integrity X, Beta Users
First-Impressions Study

A rapid yet rigorous study that blended quantitative questions with open‑ended feedback from beta users to confirm what’s a “winner” in the new UI, and where to invest the next iteration.

Summary

A fast, mixed‑method survey with beta users validated the redesign, surfaced performance priorities, clarified automation readiness, and aligned the roadmap. I combined lightweight quant (rankings/ratings) with open‑ended prompts for context. The result: high confidence to ship, with a focused set of next‑iteration bets.

My Role

Lead UX Researcher, wrote the survey, ran analysis (quant + thematic qual), synthesized findings, and aligned decisions with PM/Design/Eng/Support.

Team structure

  • Lead UX Research
  • UX Designer
  • Product Manager
  • Marketing Team

Context & Objectives

Integrity X (25.1) introduced a refreshed navigation model, visible API hooks, and always‑on metrics. We needed to quickly:

  1. Validate whether the new UI is genuinely faster and clearer;
  2. Understand automation awareness and early usage;
  3. Identify which metrics matter most;
  4. Stress‑test operational features (Backup/Restore, Support bundle, CSV);
  5. Check localization and accessibility basics.

Participants & Method

Participants
Beta users from enterprise environments (admins/engineers across DNS, DHCP, IPAM).

Method
Mixed‑method survey, Likert ratings and value ranking + open questions for “why/how”.

Analysis
Percentages and rank order for signals; rapid thematic coding to explain drivers and edge cases.

At‑a‑Glance Metrics

93%

Reported a positive or very positive experience

Comparing to previous versions.

86%

Found having external access to Prometheus/Grafana very useful

Most valuable features:

  • 64%Thee‑view + advanced tables
  • 57%UI/UX enhancements
  • 50%Quick Search
66%

Reported the new navigation, and menu are intuitive.

Comparing to previous versions.

60%

Called CSV import / export time saving.

40% haven’t tried it yet.

Least valuable features:

  • 71%Built‑in multilingual
  • 36%Support bundle
  • 29%Backup / Restore
53%

Noticed Integrity have URL↔API alignment

While 1 in 4, have already automated some task.

93%

Rated translations at least moderately accurate

Localization accuracy.

100%

Integrity is DDI winner

What We Learned Based On Numbers?

UI & Navigation
The new navigation, advanced tables, and searchable tree‑view reduce steps and errors. Main friction: search/load performance on large data sets and a desire for light personalization.

API & Automation
What we learned: Users recognize URL↔API alignment; some already automate (Postman→PowerShell/Python). Many plan to expand usage.

Metrics & Monitoring
Always‑on metrics are valuable; Prometheus/Grafana access is broadly useful.
Gaps: historical trends, alerting/anomaly detection, deeper DHCP/DNS insights, API/failed‑login/IP allocation stats, XHA health.

Backup/Restore, Support Bundle, CSV
Discoverability/naming of Support bundle could be clearer. CSV saves time; some haven’t tried it yet.

Localization & Accessibility
Translations are broadly accurate; A11y gaps remain (keyboard reach, header contrast). Multilingual is low value in English‑only teams but important for global orgs.

Outcomes

Decision confidence
Clear “keep/refine” signals on navigation and tables; focused performance bets for the next iteration

Engineering buy‑in
Concrete, prioritized problems (e.g., search at scale, XHA visibility) translated smoothly into backlog items.

UXR Next Steps

  1. Targeted usability checks on search/DNS at scale with time‑to‑task metrics.
  2. Alerting/trends MVP → measure adoption and incident reduction.
  3. Post‑launch research: broadened evaluation of real‑world usage and habituation.
  • Objectives: track adoption & feature usage (search, metrics, alerting, backup/restore), time‑to‑task and error rates, API automation uptake, A11y effectiveness in day‑to‑day work, perceived reliability, CSAT/NPS, and support/incident trends vs. pre‑launch.
  • Method: product analytics + 1:1 interviews across cohorts (new vs experienced, English‑only vs multilingual, power vs general users).
  • Outcomes: keep/tweak/retire decisions, prioritized backlog for 26.1 ; 26.2 enablement/content gaps, refreshed ROI metrics.