Operations and product infrastructure case study
BlightFall Operations & Product Infrastructure.
As BlightFall’s Community & Operations Lead, I designed and operationalized a repository-backed project system for a distributed Roblox development team, replacing scattered workspace practices with structured records, controlled changes, portable reporting, and AI-assisted implementation workflows.
- Structured records
- 72
- currently validated in the Ops Hub
- Migration review
- 168
- Notion export entries preserved and reviewed
- Reporting contexts
- 5
- internal, leadership, team, Discord, and external
- Project status
- Ongoing
- private Roblox game project
At a glance
A clearer route from project input to follow-through.
Capture
Decisions, actions, risks, meetings, resources, and ownership.
Review
Proposed changes are checked before they become shared records.
Translate
Project information becomes useful views for different audiences.
Continue
Owners, dependencies, next steps, and recovery material stay traceable.
Context and role
Building continuity around the game.
My role combines operations leadership, product thinking, systems design, implementation direction, documentation, stakeholder coordination, and acceptance testing.
BlightFall is an ongoing Roblox project in development. As the team’s operational needs grew, I led a staged move away from subscription-dependent Notion infrastructure toward a maintainable system the project could own, validate, and recover.
Migration strategy
Preserve first, retire carefully.
I evaluated the existing workspace, classified what needed to be retained, and organized the migration into approval-gated work packages. Each package included testing, rollback, continuity, and retirement criteria so the team could move deliberately without losing useful project history.
The review preserved and assessed a 168-entry Notion export. The team is retiring the older infrastructure in stages, using parity and recoverability checks to guide each transition.
Source of truth
Connecting the tools without confusing their roles.
I designed the source-of-truth architecture across the game repository, Ops Hub, Dev Tracker, cloud documents, AI workspaces, development tools, and planned Discord integrations. The model gives each system a clear purpose while keeping decisions, ownership, dependencies, evidence references, and follow-through traceable.
The internal Ops Hub now validates 72 structured records covering decisions, actions, workstreams, risks, meetings, people, resources, ownership, relationships, and next steps.
Controlled changes
Making operational updates reviewable and recoverable.
I directed the introduction of preview-and-apply transactions, validation, revision checks, audit history, and recovery procedures. Changes can be checked before they are applied, conflicting revisions are caught, and the resulting history remains understandable later.
Automated transaction, relationship, privacy, and regression checks help protect the quality of the shared records as the system evolves.
Reporting and handoffs
Turning project records into useful views.
I directed and tested audience-aware reporting for internal, leadership, team-facing, Discord-ready, and external use. Outputs include formatted previews, Markdown and PDF exports, concise Discord summaries, and weekly digests.
I also designed a structured AI-assisted handoff that turns planning conversations into traceable, reviewable implementation requests.
Testing and readiness
Proving the system before depending on it.
I coordinated acceptance testing and stakeholder review across information routing, meeting workflows, report parity, continuity rehearsals, and recovery backups. Recovery materials were packaged, checksum-verified, and downloaded back to confirm their integrity.
I also direct continuing development of a review-gated Discord bridge for operational intake, developer accountability, reminders, and Dev Tracker updates.
Project foundation
Preparing for a project that can grow responsibly.
Alongside the internal operations work, I established the official blightfall.ca domain, business-email foundation, account-recovery planning, and a multi-platform social presence.
Together, these systems replace ad-hoc operational knowledge with a maintainable foundation for project continuity, institutional memory, accountability, and future company readiness.
What this demonstrates
Experience that transfers directly to:
- Product operations
- Production coordination
- Systems and workflow design
- Information governance
- Documentation and reporting
- Acceptance testing and QA
- Stakeholder coordination
- AI-assisted delivery
Operations and community, together.
The companion community case study covers Discord leadership, moderation, live developer events, player feedback, and member support for the same project.
View community work