Priya's Story — Vertex Games | Side Conversations

Data Infrastructure: Option Comparison Priya & Remi — working notes

Database

✗Requires setup time and schema design

✗Team needs SQL access or a front-end tool

✓Powerful queries if dataset grows large

Overkill for 50–100 assets

Shared Spreadsheet ★
✓Zero setup — whole team already has access
✓Supports all four data areas in separate tabs
✓Formulas handle before/after comparisons
△Consistency risk — must enforce input standards
Recommended: fits decisions to support

Asset Tracking Tool

✗Designed for task management, not data analysis

✗Can't generate the visualisations we need

✓Good for status tracking only

Wrong tool for this purpose

Asset_Tracking_v2.xlsx — Tab 1: Asset Data ⚠ Consistency issue flagged

Asset Name	Type	Poly Count	Measured By	Method	Std. Method	File Size	Status
Bench_01	Prop	12,200	Marcus	Blender	✓ Blender	3.1 MB	In Progress
StreetLamp_01	Prop	8,400	Sam	Unity Inspector	✗ Unity Inspector	2.8 MB	Not Started
Fountain_01	Hero	14,000	Marcus	Blender	✓ Blender	4.2 MB	Not Started
FireHydrant_01	Prop	6,100	Kai	Unity Stats	✗ Unity Stats	1.9 MB	Queued
BusStop_01	Hero	15,600	Sam	Unity Inspector	✗ Unity Inspector	5.6 MB	Queued

FPS Before vs After Scene 3 Optimisation

REVISED ✓

Priya

Remi

Gap 1 · Data Lab

Remi Osei · Data Engineer

💬

Gap 1 Complete

Title

Key Insight