Before
Internal logic was visible to the team but unclear to new users.
Ragnarok Labs · Structural Investigation · 02
The team knew the system. Customers didn’t.
A three-month behavioral research investigation revealed how internal familiarity was hiding customer friction inside a legacy digital infrastructure platform.
Internal confidence was not user evidence .
// hidden friction
The most dangerous UX problem was invisible.
The platform appeared usable internally because employees already understood the terminology, workflows, navigation logic and expected outcomes. External users revealed a different reality. They were not beginners. They already understood email, domains, servers and basic infrastructure workflows. Still, usability dropped sharply. The issue was not user incompetence. The issue was platform dependency on prior internal knowledge.
Anonymised research artifact · not a public client result claim
76.75
Internal SUS score
68
External SUS score
7.1
Corrected LTR score
11%
Familiarity compensation
3mo
Research before redesign
// anonymised artifact
Before / after comprehension slot
After
Decision order, labels, and next actions were rebuilt around external comprehension.
// internal vs external
Internal Familiarity vs External Reality.
The score dropped when the product was tested outside the company.
01
68 SUS baseline
The starting point for external usability measurement.
02
76.75 Internal
Internal users rated the system higher because exposure reduced uncertainty.
03
68 External
External users exposed the real clarity gap.
04
68 Corrected
The corrected view removed internal familiarity from the signal.
05
−8.75 point reality drop
The product was easier for employees because they already knew the system.
The system was not easier. Employees were trained by exposure .
// familiarity inflation
Familiarity inflated usability.
Internal users rated the system higher because repeated exposure reduced uncertainty. They knew what the interface meant before the interface had to explain itself. That created a false safety signal. The company was not measuring usability. It was measuring adaptation.
Internal users were testing memory, not clarity.
When a system only works because the team already understands it, the product is carrying hidden onboarding debt.
// recommendation risk
Then usability became a recommendation problem.
SUS exposed usability pressure. LTR exposed something more dangerous: users were not confident enough to recommend the experience. After familiarity correction, the LTR score settled around 7.1 — a passive zone. Not rejection. Not advocacy. The kind of lukewarm response that lets competitors win quietly. Participants compared the platform against more modern alternatives with clearer flows, more predictable interfaces and stronger visual confidence.
// ltr / nps zone
LTR / NPS Zone: Recommendation Risk.
The experience landed in passive territory — usable enough to survive, not strong enough to create promoters. Detractor. Passive. Promoter.
01
Detractor
Users who would actively discourage adoption.
02
Passive
The corrected experience landed around 7.1: acceptable, but not advocacy.
03
Promoter
The product still needed stronger clarity and confidence to create recommendation momentum.
04
7.1 Corrected LTR score
The product was usable enough to survive. Not strong enough to create promoters.
The product was usable enough to survive. Not strong enough to create promoters.
// exposed issues
What the investigation exposed.
The research separated internal comfort from external clarity and showed where the product depended on organizational memory.
01
Terminology
Labels reflected internal operational language, not customer mental models.
02
Validation
Password and form feedback interrupted confidence after users had already committed effort.
03
Forms
Optional fields, required inputs and unclear hierarchy created silent onboarding drag.
04
Competition
Modern competitors made the platform feel heavier, older and less recommendable.
// method
Ragnarok investigation method.
The investigation measured behavior before redesign and separated adaptation from actual product clarity.
01
Observe real hesitation
Behavior mattered more than stakeholder opinions.
02
Separate familiarity from usability
Internal knowledge was treated as a distortion layer.
03
Compare perception groups
The SUS gap exposed organizational adaptation to friction.
04
Measure recommendation risk
LTR showed whether usability translated into confidence and advocacy.
05
Redesign for external clarity
The live redesign focused on terminology, validation, sequencing and operational visibility.
// shipped live
The redesign shipped live.
The final redesign changed onboarding behavior, account setup flow, terminology structure, validation timing and operational visibility.
01
Clearer account creation flow
Earlier validation feedback.
02
Reduced terminology ambiguity
Improved self-service confidence.
03
Less reliance on internal knowledge
Stronger recommendation potential.
Never confuse internal familiarity with user clarity .
Real usability begins where internal knowledge ends.
Internal confidence is not evidence. External behavior is.