---
###### tags: `UX Research`
---

# UX Sync 3-23-22: TW + e2t > Nike Deck Review

### Holistic Research Hierarchy

- Management structures: clouds, deity-level
- Product UX: ground level, in the weeds
- UX writing and terminology: language level, the beginning of understand

---

### Extraction from E2T's Nike Deck

- Inception: solo self-found
- Description
- Point Estimate
- Business criteria
- Service requirements
All the information is collected into a Wiki. Basically a tagging mechanics for organizing data into an IA.

- Discovery: collab with reps from every team (Dragons)
- QA User Stories: BDD Behavior Driven Development in [*Cucumber*](https://en.wikipedia.org/wiki/Cucumber_(software)#:~:text=Cucumber%20command%2Dline-,Gherkin%20language,relating%20to%20a%20software%20system.)
- Given
- When
- And
- Then
- *Design the test before designing the features: test driven development*
- Design Considerations > Flows > Mockups
- Strings: Key > (technical descriptions) > (laymen explanation) > Value
- Delivery: kanban board
- Breakdown details of the specs
- Comments are kept with the specs so all information is in one place
- Different qualities/lengths of communication are more/less appropriate for different coms channels
- Release: widespread release
- Quality Management
- Regression (make sure it doesn't break)
- Release Candidate (stamp of approval)
- Shipment

---

### UX Terminology
- Needs a string/syntax/glossary based on:
- Key (code) > technical descriptions > laymen explanation > default value defined by DH > user defined values they can customize (templates?)

### Testing
- Automated: code level
- Manual: QA, trying to break the build
- User: community use