hackforla / hackforla/knowledgebase-content
Create a Guide/Template: Usability testing vs A/B testing
- Vorherrschende Sprache
- Keine Sprachdaten
- Sterne
- 2
- Forks
- 1
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
### Overview
We need to create a guide to make clear the difference between usability testing vs A/B testing so that the UX team members know when to use each.
### Action Items
The phases in the guide-making process are listed below. Each phase displayed in blue is linked to a wiki page with instructions on how to complete that phase. Open the wiki page in a new tab, copy the instructions for each part into the section labeled 'Tasks' at the bottom of this issue, and complete each task listed.
- [ ] [Gather Examples Solo](https://github.com/hackforla/guides/wiki/How-to-Gather-Examples:-Solo) (open in a new tab)
- [ ] [Gather Examples Collaboratively](https://github.com/hackforla/guides/wiki/Phase-2-%E2%80%90-Gather-Examples-Collaboratively)
- [ ] [Create a Guide Draft](https://github.com/hackforla/guides/wiki/How-to-Draft-a-Guide)
- [ ] If needed, create a template
- [ ] [Have your guide peer reviewed](https://github.com/hackforla/guides/wiki/Peer-Reviews-for-Guides)
- [ ] [Present your guide for leadership review](https://github.com/hackforla/guides/wiki/Submitting-Your-Guide-for-Leadership-Review)
### Resources/Instructions
Google Drive Folder for this Guide’s documents [0043 [DRAFT] Usability testing vs A/B testing](https://drive.google.com/drive/folders/1R0pk2I9JWkQU4PZ7qEBBf-bMbScVflwG)
### Projects to Check
### Tasks
- [ ] This is where you will copy instructions from the wiki page for the step you are currently on.
Beitragsleitfaden
Rechercherichtung
Start with the linked wiki instructions for gathering examples, drafting, peer review, and leadership review, then inspect the Google Drive folder for “0043 [DRAFT] Usability testing vs A/B testing.” Done means producing and reviewing a guide that clearly explains when UX team members should use usability testing versus A/B testing.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Bereich
- documentation
- Issue-Typ
- Dokumentation
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 35/100