About the practice
A desk in Thirsk, a room that travels.
Workspace Nodehub began when three product people in the United Kingdom grew tired of analytics programmes that taught tools first and judgement never.
Mission
We exist so that the person who owns an app can read their own instrumentation without waiting for a vendor’s customer-success deck. App analytics, in our rooms, is a literary problem as much as a statistical one: what did we name, what did we omit, and what claim survives a hostile question.
The practice is small on purpose. Cohorts stay short enough that tutors still read the homework. We would rather turn someone away than dilute the studio into a content mill.
Pedagogy
Each module opens with a messy export from a living product — never a sanitised sample. Students annotate, argue, and only then build a view. We borrow the seminar more than the bootcamp: silence is allowed, slides are few, and the tutor’s job is to interrupt a tidy story.
SQL appears when a question cannot be answered without it. We do not pretend a weekend of joins makes someone an analyst. We do insist that a product manager can sit beside one without feeling like a guest.
Community
Graduates remain in a quiet mailing list — no points, no leaderboard. Once a quarter we host a Thursday evening in London or Manchester where people bring a single chart they regret. The rule is courtesy: you may criticise the metric, not the person who shipped it.
Visiting tutors come from fintech, public-interest media, and a pair of health apps that will not be named here because their legal teams asked nicely. They do not pitch. They sit and mark.
The student journey
Most people arrive mid-crisis: a board asking for a north star, a tracking plan that survived three reorgs, a funnel that looks like a cliff. You write to the desk, we suggest a room, and you spend the first week producing a one-page map of what the product actually emits.
By the last week you owe us a claim, a reservation, and a next measurement you are willing to defend. Certificates exist if procurement requires them. They are not the point of the work.
