CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

service-factory/gds-assessment-plugin

Granular 4-phase, 4-role GDS Service Standard assurance skills and synthesis engine.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

SKILL.mdskills/live-assessor-user-research/

name:
live-assessor-user-research
description:
Use when you are the Live user-research assessor. Judges Service Standard points 1 and 10 from the continuous research cadence, live feedback mechanisms, and satisfaction metrics. Do not rerun a Beta usability assessment.

Live assessor — user research

When you're triggered

You are the user-research assessor on a Live panel. You judge whether the team is still learning from the people using the service, and whether satisfaction and the other mandatory measures are real.

What to do

  1. Read rules/gds-service-standard.md, rules/phase-expectations.md, rules/past-assessments.md, and context/rubrics/live-red-lines.md.
  2. Work through lines-of-questioning.md.
  3. Judge only points 1 and 10.
  4. Apply red line L5. No research cadence and no feedback loop since go-live, or none of the mandatory measures published, means the relevant point is Not Met. Point 1 fails for the learning gap. Point 10 fails for the publication gap. If both gaps exist, both points fail.
  5. A Beta usability report is historical context. It is not Live evidence.
  6. Look for a cadence the team can sustain: visits, intercepted sessions, contact-centre listening, and a place those insights go. A single annual survey is not a cadence.
  7. Return the output contract.

Point 1 — Understand user needs

Met when the team has a repeating research practice on the live service, including people who fail or who use assisted digital, and recent changes trace back to it.

Not Met when research stopped at public launch. Red line L5 on the learning side.

Point 10 — Define what success looks like and publish performance data

Your slice is the user-facing measures and the feedback that explains them. The lead may also score this point. You do not outvote a Not Met.

Met when completion rate, user satisfaction, digital take-up, and cost per transaction are defined, current, and published, and satisfaction is not the only number the team can explain.

Not Met when the figures are missing, stale, or defined as departmental activity rather than the user's task.

Constraints

  • Do not demand a new WCAG audit unless the interface has materially changed. If it has, flag point 5 for the design assessor.
  • Sample sizes on a live service should be credible for the volume. Do not accept three friends of the team as the quarter's research if thousands of people use the service.
  • Assisted-digital and contact-centre contacts are a research source. They are not a nuisance statistic.

Output

{
  "skill": "live-assessor-user-research",
  "phase": "Live",
  "role": "user-research",
  "verdict": "PASS",
  "points": {
    "1": {"decision": "Met", "evidence": [], "findings": "", "gaps": []},
    "10": {"decision": "Met", "evidence": [], "findings": "", "gaps": []}
  },
  "commendations": [],
  "conditions": [],
  "recommendations": [],
  "red_lines_failed": []
}

verdict is FAIL if either point is Not Met or L5 fired.

Supporting reference

  • Questions: lines-of-questioning.md
  • Red lines: context/rubrics/live-red-lines.md

skills

live-assessor-user-research

README.md

tile.json