Security Rapids - Test Round Details - Week 1: Onboarding, Configuration, & Policy Governance

Rapid Validation for Security - Test Round Details

This is to manage an individual test round for Rapid Validation Research for Security Concepts.

Team

• Title: Onboarding
• Designer(s):
• Additional stakeholder(s):
• ReOps: @marianacardinali
• UXR: @nshechtmann

Session Timeline

• Session moderator & attendee: @nshechtmann
• Session dates: 29 to 31 of October, 2025
• Number of sessions: 6 Sessions
  • Please keep in mind that we do not cancel sessions without a reasonable reason. Even if the numbers and feedback collected is achieved, to keep GitLab good image and great participants' experience, all the scheduled sessions needs to be completed.

Recruitment Criteria for this Test Round

• Screener: Rapid Validation for Security FY26 - Screener
• Recruitment Criteria TBD

Key Documents

Templates

• Research design [link: Security Concept Validations - Research Design]
• Test script template [link: Security Concept Validations - Test Script Template]
• Findings doc template [link: Security Concept Validations - Report Template]

Documents for this Test Week

• Original Context Comment: link coming soon
• Research Design: Onboarding - Research Design
• Materials for test: link coming soon
• Test Script: Onboarding - Test Script
• Findings: link coming soon

Task Tracker

Step	Due Dates Test Week: 10-27 to 10-31 (tentative)	Tasks Key documents are linked above
Intake & Design (1-2 weeks before the test week)	All tasks done 2 Fridays before test week (except Context Comment)	[Due 10-10]PD: Create a Context Comment on the Security Rapids Main Issue that includes: description of the design/concept, the 1-3 specific aspects you're unsure about, context on timing/urgency, and target user segments [Due 10-17]PD + Research: Meet to walk through early prototype ideas and begin to align on testing goals, participant recruitment criteria, and timeline for sessions, script, and design materials. Set up meeting week before testing to review script and design materials. [Due 10-17]Research: Create this dedicated research issue linked to main issue to track operations for testing [Due 10-17]Research: Draft Test Round Research Design, including refined Context Comment, research goals, research questions, recruitment criteria, and task specifications [Due 10-17]PD + other stakeholders: Review and confirm agreement with Test Round Research Design [Due 10-17]Research: Draft Test Session Script and share with PD and other stakeholders
ReOps Preparation (1-2 weeks before the test week)	All tasks done 2 Fridays before test week	[Due 10-17]PD + Research: confirm dates and availability for sessions with ReOps (recorded above). Select ~2-3 days, ensure at least 6 sessions x 60 min can be accommodated, ideally with some buffer time to offer flexible scheduling options for participants. Must specify timezone and ensure calendar is updated for those days. [Due 10-17]Research: Confirm recruitment criteria and screener with ReOps (recorded above). [Due 10-17]ReOps: Provide project Rally link to team Rally (Internal Panel): https://app.rallyuxr.com/gitlab/study/cmfz4z35d3ehmi9lj9x3i69qp/builder/plan Rally + Respondent: https://app.rallyuxr.com/gitlab/study/cmfmcz7k68a30i3ll4ymj6dzp/builder/plan
Prepare for Testing (week before testing)	All tasks done week before test week	[Due 10-24]PD: Prepare materials for testing (e.g. prototype, wireframes, sketches, concept description, etc.) - deadline: Thursday before testing [link(s): session materials] [Due 10-22 - Wednesday before testing]ReOps: Begin scheduling sessions [Due 10-24]Research + PD: Meet to review test materials and test script [Due 10-24]PD + other stakeholders: Review and confirm agreement with Test Session Script
Testing Week	10-27 to 10-31	[Due 10-28]Research: Finalize test script adjustments (Monday/Tuesday) [Due 10-28]PD: Finalize testing materials (Monday/Tuesday) [Due 10-28]Research: Set up note taking template (Monday/Tuesday) Research: Moderate user sessions, ensuring insights on key metrics are captured on notes (either live or from recordings) (Wednesday/Thursday/Friday) PD: Observe sessions and support note-taking (Wednesday/Thursday/Friday)
After Testing	Week after testing	[Due 11-5]ReOps: Process incentives Research: Analyze data and write report draft [link: Report Draft] PD + other stakeholders: Review and provide input on Report Draft PD: Define and commit to 1-3 specific actions based on research recommendations, adding them to the designated section of the report Research: Finalize report, based on feedback  Research: Add final report to the research issue Research: Share insights summary in Slack (#ai-rapid-research and ux_research_reports)