Hogrefe Quick Scoring Service

Hogrefe’s Smart Scoring Service is a web app that lets psychology professionals score clinical questionnaires on screen instead of by hand. Scoring assessments on paper is slow and error-prone, so the promise is real: enter the responses, let the tool do the math, get a report. The question was whether the tool actually delivers on that promise, or quietly gets in the user’s way.

Which layout gives professionals the most usable, satisfying way to score a questionnaire, and which elements can be optimised to make it faster and clearer?

I led the research side of a mixed-method usability study: planning and moderating the sessions, then synthesising what we saw into a prioritised set of design recommendations.

A small sample only produces reliable signal if you look at it from several angles, so I stacked five methods around the same scoring tasks. What people said, what they did, and where they actually looked, captured together, let me triangulate friction instead of guessing at it.

Four psychology students from PFH University took part, close to the real user: familiar with questionnaires and scoring, but not with this particular tool.

Two user types framed the study, and they need different things from the same screens. One scores assessments constantly and wants speed; the other is still learning and needs the interface to teach as it goes.

LBLenaJMJonas

Lena

Clinical psychologist

Scores assessments every week

Lena runs psychological assessments and scores questionnaires constantly. Hand-scoring is slow and easy to get wrong, so a digital tool is genuinely welcome, but only if it is faster than paper and does not ask her for things she should not have to share.

Goals

• Score a completed questionnaire quickly and correctly
• Trust the result without double-checking against a legend
• Get in and out without unnecessary data-entry steps

Frustrations

• Transcribing dozens of digits by hand from a paper sheet
• Being asked for personal details that feel unnecessary
• Hunting for the scoring legend while entering values

Rather than ask for opinions, I put the tool to work with two realistic use cases drawn from how professionals actually score assessments.

That second task, transferring responses from the paper sheet into the app, is where most of the friction surfaced.

Before reading the findings, it helps to see the path. The tool walks the user from an access code through basic data and raw-score entry to a final report. Two steps quietly carry most of the risk: who the basic data belongs to, and the long stretch of transcribing scores.

The headline is encouraging: people liked the tool. The friction clustered in a few specific spots rather than spreading across the whole experience, which made it fixable.

And three frustrations came up again and again.

The score-entry screen is where the study earned its keep. People told us it was “fine,” but the eye-tracking told a different story. Instead of flowing smoothly down the form, attention scattered, bouncing between the score fields and the legend box tucked over on the right.

That scatter is the friction made visible. Every glance over to the legend and back is a small tax on a task users repeat hundreds of times, and it is exactly the kind of problem interviews alone would have missed.

I paired each friction point with a concrete, layout-driven fix. The first two are about clarity and trust; the third, the score grid, is where the design changes do the most work.

The score-grid redesign came down to four specific moves.

• Move the legend left

  Place the scoring legend next to the grid, where attention already lands.

• Show real progress

  The screen shows 55 items when there are 140; add a scroll indicator for what is left.

• Gate the continue button

  Keep Continue inactive until every score is entered, so nothing is submitted half-done.

• Fit the device

  A horizontal layout that maps the grid to the screen instead of fighting it.

The study handed Hogrefe a prioritised, layout-specific set of changes rather than a vague “make it nicer.” Each recommendation traces back to observed behavior, so the team could act with confidence about what to fix first and why.

• Calmer score entry

  Moving the legend in beside the grid is aimed straight at the gaze scatter the eye-tracking exposed.

• Fewer abandoned forms

  A real progress cue plus a gated Continue reduce the chance of submitting an incomplete score sheet.

• Confident first use

  A single on-screen instruction removes the most common first-time hesitation.

• Protecting what worked

  The light, low-typing input people liked stays intact; the fixes refine it rather than replace it.

Because the tool was already well received, this was refinement, not rescue, and the most valuable outcome was turning “it’s fine” into a short list of changes the team could ship.

People told us the tool was “fine.” Their eyes told a different story.

That gap is what stuck with me. On the score-entry screen, gaze jumped around instead of settling, and pairing what users said with where they actually looked is what turned vague frustration into three specific, fixable recommendations. It is the clearest reminder I have that self-reported ease and observed behavior are not the same thing.

I am honest about the edges, too: four participants, all from one university, and a heatmap capture that was partly lost to a software glitch. The triangulation held the signal together, but the natural next step is to test the redesigned score-entry layout with practicing clinicians and validate whether moving the legend and adding progress cues actually calms that scatter.