portfolio-positioning-review

name	portfolio-positioning-review
description	Review portfolio content for senior TPM, product operations, game production, live operations, and community platform leadership positioning. Use when editing README, homepage, About, Career, Now, Contact, or top-level portfolio messaging.
paths	["README.md","portfolio-config.json","src/content/**/*.md","src/pages/**/*.astro","src/data/**/*.ts"]

Purpose

Review portfolio copy as a senior hiring-manager-facing portfolio, not as a generic personal website.

Target roles

Optimize for:

• Senior Technical Program Manager
• Product Operations / Platform Operations Lead
• Game Production / Live Ops Producer
• Director-level Operations or Community Platform Leadership
• Operations Systems Builder

Core positioning

T. Riley Garrett builds operational systems for complex environments: gaming platforms, live events, large communities, support operations, and military execution. His work turns ambiguous needs into requirements, workflows, automation, governance, and delivery systems that teams can actually run.

Evaluation criteria

When reviewing or editing content, check whether it clearly communicates:

1. Scope

   • company/org
   • audience
   • scale
   • stakeholder complexity
   • operational environment

2. Ownership

   • what Riley owned
   • what Riley influenced
   • what Riley coordinated
   • what was cross-functional vs solo

3. Business or operational impact

   • quantified result when verified
   • concrete qualitative result when no metric exists
   • no invented numbers

4. Role alignment

   • TPM language for roadmap, requirements, delivery, risk, dependencies
   • Product Ops language for workflows, systems, adoption, operational scale
   • Game Production language for Jira, Perforce, QA, releases, testing, community feedback
   • Community Platform language for governance, moderation systems, privacy, analytics, member experience

5. Recruiter scanability

   • strongest result first
   • short paragraphs
   • specific bullets
   • portable skill labels
   • minimal internal jargon

Required critique format

Return:

1. Overall verdict
2. Strongest current signal
3. Weakest current signal
4. Specific recommended edits
5. Any risks of overclaiming
6. Suggested rewrite only where needed

Style rules

Use direct, professional language. Avoid hype. Avoid generic corporate filler. Do not invent metrics. Do not remove useful specificity.