Data Organisation Build from Zero

When the engagement with Stage.in began, there was no data organisation. The platform had 5M+ monthly active users, a growing product and content operation, and no dedicated data capability to support it. Everything that required data — reporting, analysis, instrumentation, tooling — was either not happening or happening inconsistently.

Build a data organisation from scratch: define the structure, hire the team, establish the engineering practices, and stand up the delivery framework — while simultaneously architecting and building the technical infrastructure the team would operate on.

Building a data team while simultaneously building the infrastructure they will own is a sequencing problem as much as a hiring problem. Hiring before the work is defined means new hires inherit ambiguity; defining the work without hiring means operating at reduced capacity for too long. The approach was to sequence technical work slightly ahead of hiring — each system designed and partially built before the role responsible for owning it was filled, so every new hire could onboard into something concrete.

Engineering standards, management rituals, and agile practices were established before the first hire started, because they are nearly impossible to introduce convincingly once a codebase and team culture already exist. Career ladders were defined early to give hires clarity on what growth looked like — critical for retention in a team being built from scratch.