Home
ResearchOps landing page.
Default state
Initial loaded page state.
Screenshot evidenceRoute-level Cucumber evidenceState-level acceptance criteriaAccessibility evidenceDesign-risk notes
What this screen state should support
Feature: Access the ResearchOps home page
As a user researcher
I want to access the ResearchOps home page
So that I can choose the right ResearchOps journey for my work
Background:
Given I am a user researcher
When I visit the ResearchOps home page
Scenario: View the ResearchOps service identity
Then I should see the service name "ResearchOps Demo Suite"
And I should see the tagline "Objective orientated applied user research done well."
And I should see the page heading "ResearchOps Demo Suite"
And I should see introductory text that says "Use ResearchOps to structure applied user research with operations, governance and accessibility baked in."
Scenario: Understand that the service is a prototype
Then I should see a prototype banner
And the banner should say "This is a ResearchOps prototype. Do not enter real participant personal data."
Scenario: Navigate using the primary navigation
Then I should see primary navigation links for:
| Home |
| Start research project |
| Projects |
And the "Home" navigation item should be shown as the current page
Scenario: Start with a research project
Then I should see guidance headed "Start by creating a research project"
And I should see text explaining that "A project gives you somewhere to hold studies, participants, sessions, notes, evidence, insights and recommendations."
And I should see text explaining that "Create the project first. Later parts of the service become useful once the research work has somewhere to live."
And the primary call to action should be "Start a research project"
Scenario: Move to project creation
Given I can see the "Start a research project" call to action
When I select "Start a research project"
Then I should be taken to the start research project service
Scenario: Understand the ResearchOps lifecycle
Then I should see a section called "How ResearchOps supports a research project"
And I should see text explaining that "ResearchOps follows the shape of a user research project. Start by creating a project. Then add studies, participants, sessions, notes, evidence, insights and recommendations as the work develops."
And I should see text explaining that "This sequence is a mental model, not a set of first-visit shortcuts. It shows how the work becomes connected over time."
And I should see text explaining that "Define the research work, service phase, team context and objectives."
And I should see text explaining that "Plan a specific round of research within the project."
And I should see text explaining that "Recruit and manage people taking part in the study."
And I should see text explaining that "Schedule and run research sessions."
And I should see text explaining that "Capture observations and structured session notes."
And I should see text explaining that "Organise what was seen, heard or recorded."
And I should see text explaining that "Analyse evidence into meaningful findings."
And I should see text explaining that "Turn findings into decisions, actions and service improvements."
Scenario: View the lifecycle sequence as a mental model
Then I should see the lifecycle stages in this order:
| Step | Stage | Purpose |
| Step 1 of 8 | Project | Define the research work, service phase, team context and objectives. |
| Step 2 of 8 | Study | Plan a specific round of research within the project. |
| Step 3 of 8 | Participants | Recruit and manage people taking part in the study. |
| Step 4 of 8 | Sessions | Schedule and run research sessions. |
| Step 5 of 8 | Notes | Capture observations and structured session notes. |
| Step 6 of 8 | Evidence | Organise what was seen, heard or recorded. |
| Step 7 of 8 | Insights | Analyse evidence into meaningful findings. |
| Step 8 of 8 | Recommendations | Turn findings into decisions, actions and service improvements. |
And each stage should include a short explanation of what happens at that point
Scenario: Avoid misleading lifecycle links
Then lifecycle stages should be presented as orientation rather than as a menu
And later lifecycle stages should not be presented as first-visit shortcuts
And the page should make it clear that later work becomes useful after a project has been created
Scenario: Review later ResearchOps tasks
Then I should see a section called "What you can do after creating a project"
And I should see text explaining that "These parts of ResearchOps are shown as orientation. They make more sense after a project record has been created."
And I should see orientation cards for:
| Task | Category | Availability |
| Set clear research objectives | Team alignment | Available after project creation |
| Recruit participants for user research studies | Recruitment | Available after study planning |
| Turn research evidence into recommendations | Evidence and analysis | Available after sessions |
Scenario: Understand the "Set clear research objectives" task
Given I can see the "Set clear research objectives" orientation card
Then I should see that it is "Available after project creation"
And I should see the question "How might we overcome the impact of unclear objectives in user research?"
And I should see supporting text that says "Use the project space to align stakeholder objectives with research, design and delivery work."
Scenario: Understand the "Recruit participants for user research studies" task
Given I can see the "Recruit participants for user research studies" orientation card
Then I should see that it is "Available after study planning"
And I should see the question "How might we ensure that participant recruitment reflects the diversity and needs of the service’s real users?"
And I should see supporting text that says "Plan recruitment so findings are not biased, exclusionary or weakly connected to the service’s real users."
Scenario: Understand the "Turn research evidence into recommendations" task
Given I can see the "Turn research evidence into recommendations" orientation card
Then I should see that it is "Available after sessions"
And I should see the question "How might we keep evidence, insights and recommendations connected?"
And I should see supporting text that says "Use structured notes and evidence trails to show how research findings lead to service decisions."
Scenario: Use the lifecycle sequence on a mobile device
Given I am viewing the home page on a mobile device
Then the lifecycle sequence should remain readable
And the stages should appear in the correct order
And no content should require horizontal scrolling
Scenario: Access the home page using a keyboard
Given I am navigating with a keyboard
Then I should be able to move focus through the primary navigation links
And I should be able to move focus to "Start a research project"
And I should be able to activate links, buttons and form controls without a mouse
Scenario: Understand the page structure with assistive technology
Then the page should have one clear main heading
And the start guidance section should have a meaningful heading
And the lifecycle should be marked up as an ordered sequence
And each lifecycle stage should expose its name and explanation in a logical reading order
And each orientation card should expose its title, supporting text and availability in a logical reading order
Scenario: View footer information
Then I should see the footer text "© 2026 Home Office Biometrics · ResearchOps v1.0.0"Design-risk notes
- Design risk
- The landing page may look visually complete while failing to explain the safest route into research setup, evidence review or synthesis work.
- Impact
- User researchers could choose the wrong workflow, duplicate records or miss the intended evidence-to-insight traceability model.
- Recommended change
- Review the page against GOV.UK start-point conventions, link purpose, visible service identity and keyboard-accessible navigation.
- Owner
- UCD team
- Status
- Needs UCD review
Screenshot evidence
Screenshot evidence
