27 — Product Scope Recommendation Execution (Blueprint §1)

27 — Product Scope Recommendation Execution (Blueprint §1)

Source: 02-Implementation-Blueprint.md — §1) Product Scope Recommendation.

Product alignment: 01-Post-Purchase-Video-Testimonial-Collector-Plan.md — MVP strategy and value proposition.

This document is a build spec only. No code changes are implied until a task references this file.

Related: 06 (public submission), 09/10/12 (moderation), 11/05 (publication + widget), 20 (schema).

---

0) Goal (one sentence)

Operationalize the blueprint’s video-first, photo-supported strategy so product decisions stay consistent across capture flow, moderation, analytics, and storefront presentation.

---

1) Blueprint scope statement (canonical)

Blueprint §1 recommends:

• Video-first, photo-supported strategy.
• Primary CTA: “Record a quick video testimonial”
• Secondary CTA: “Upload a photo + short text”
• Same moderation and publication workflow for both media types.

This section is a product scope constraint, not just UI copy.

---

2) Scope boundaries (what video-first means in implementation)

2.1 Required behavior

1. Public submission UI defaults to video capture path first.
2. Photo path remains available but visually secondary.
3. Moderation pipeline handles video and photo with same status lifecycle.
4. Storefront defaults should prioritize video where both exist (home widget default video_only).

2.2 Non-goals

• Do not make photo path impossible.
• Do not split into two separate products/workflows.
• Do not require text-only submissions in MVP.

---

3) UX rules by surface

3.1 Public submission page (06)

• Order of media choices:

  1. Record video (primary, emphasized)
  2. Upload video
  3. Upload photo (secondary)

• CTA copy:

  • Primary action: “Record your video”
  • Secondary link/button: “Prefer photo instead?”

• Guidance text:

  • Recommend target video length (e.g. 15–60 sec)
  • Keep photo instructions concise

3.2 Widget settings and storefront (05, 11)

• Home defaults:
  • media filter: video_only
  • max cards: 5
• PDP defaults:
  • may allow mixed media based on merchant config

3.3 Admin messaging

• Screens should frame value around video social proof first, while still showing photo metrics and controls.

---

4) Data model implications (20)

4.1 Must-have

• TestimonialSubmission.mediaType as required field (video | photo).
• TestimonialMediaAsset supports both media types (mime + size + dimensions).

4.2 Recommended derived fields

• hasVideo boolean (optional denormalized for fast filters)
• videoDurationSec via media metadata for quality checks

4.3 Indexing for video-first queries

• add/confirm index patterns used by home widget and moderation filters:
  • (shopId, mediaType, published)
  • (shopId, mediaType, status)

---

5) Moderation policy implications (12)

Video-first does not mean weaker controls.

Recommended defaults:

• Photos may be auto-approvable (if merchant enables).
• Videos generally require manual review unless future AI rules mature.
• Separate min/max length checks apply to video only.

Same moderation status model for both:

• pending -> approved/rejected/archived

---

6) Analytics implications (14)

Track split as first-class KPI:

• video submissions count/rate
• photo submissions count/rate
• approval and publish rates by media type

This validates whether “video-first” actually drives target behavior.

---

7) Campaign and template implications (17, 18, 16)

7.1 Campaigns

• No separate campaign type required for video/photo in MVP.
• Campaign copy and incentive language should encourage video naturally.

7.2 Templates

Provide default templates with video-first tone:

• “Share a quick video testimonial”
• mention photo fallback in body as optional path

---

8) Quality gates for scope adherence

Before release, verify:

• Public submission page highlights video capture first.
• Photo flow still works and reaches same moderation pipeline.
• Home widget defaults to video-only.
• Analytics shows media-type split.
• Merchant can switch defaults in settings if desired.

If any fail, scope recommendation is not implemented correctly.

---

9) Product copy standards

Use consistent language:

• “Video testimonial” (primary)
• “Photo testimonial” (secondary)
• Avoid generic “upload file” wording as main CTA.

Maintain tone alignment across:

• campaign templates
• public submission page
• widget headers/help text
• admin onboarding snippets

---

10) Risks and mitigations

1. Low video completion rate
   • Mitigate with short target duration prompts and simple recording UX.
2. Merchants over-rely on photo auto-approval
   • Mitigate with defaults and moderation warnings.
3. Storefront appears sparse with video-only
   • Mitigate with configurable fallback in widget settings.

---

11) Implementation order (for Cursor)

1. Apply media-type schema and API contracts (20, 06).
2. Build submission UI with video-first ordering.
3. Set widget defaults to video-first (05).
4. Ensure moderation and inbox support both types uniformly (09, 10, 12).
5. Add media split analytics (14).
6. Tune template defaults to reinforce primary CTA (16).

---

12) References

• 02-Implementation-Blueprint.md — Section 1
• 01-Post-Purchase-Video-Testimonial-Collector-Plan.md — MVP framing
• 05, 06, 09, 10, 11, 12, 14, 16, 20

---

13) Note on numbering

This folder already includes 05 through 26 plans. This file is 27-....