User-Test ytt Schema Validation

[pivotaljohn]

With the core validation rules implemented, let's get usability and suitability feedback from users.

The goal is to vet our assumptions so that we can either confidently adjust or move forward with our implementation towards General Availability of this feature.

---

📝 ytt Validations Usability Testing Plan (Google Doc)

Plan:

• Identify use-cases and create interview materials for each:
  • Conduct exploratory testing to surface questionable UX use cases.
    • Explore: create different combinations of inputs, run them and scrutinize the output
    • Capture questionable UX'es in the Testing Plan doc; frame it as a "claim" to make about a proposed change in the UX
  • Prioritize and scope the claims that we'll test
  • For each "claim" that is in-scope, produce an example and instructions that would place the user in that scenario.
  • Test-drive the example to ensure:
    • it works (and that all the needed resources/information are provided);
    • it will create the desired situation; and
    • that there are as few anchor biases as possible in the materials.
• Identify Candidates
  • Identify people whom we might interview
  • Determine who is willing to be interviewed

Interview:

• Interview 1 — Vijay
  • schedule
  • conduct
• Interview 2 — Clemens
  • schedule
  • conduct
• Interview 3 — Robert
  • schedule
  • conduct
• Interview 4 — Jay
  • schedule
  • conduct
• Interview 5 — Scott
  • schedule
  • conduct
• Interview 6 — Pradnya (CNR)
  • schedule
  • conduct

Results:

• Synthesize results of interviews
• Author User Stories describing improvements

[pivotaljohn]

While there's some ongoing previews/interviews; we've completed the scope of interviews required to validate/confirm the requisite API claims. 👍🏻