Every hand-off is a place quality leaks out
The conventional studio scales by adding people and dividing work. A strategist briefs a designer, who briefs a junior, who passes a file to a developer, who flags a question back up the chain. Each of those edges is a translation, and every translation loses something. The intent gets a little blurrier, the context a little thinner. By the time the work ships, no single person can hold the whole thing in their head. We built Norvik to avoid exactly this. A small senior team has fewer edges, so there is less for quality to leak through.
This is not a romantic preference for smallness. It is a structural claim. The cost of coordination grows faster than the number of people, while the depth any one person can hold stays roughly fixed. Past a certain size, you are spending more of your effort keeping everyone aligned than doing the work itself.
Seniority is what makes small possible
A small team only works if the people in it are deep enough to span disciplines. A senior designer who can think strategically and reason about engineering constraints replaces three hand-offs with one mind. That breadth is expensive and rare, which is precisely why it is valuable: it collapses the coordination problem instead of managing it. We would rather pay for one person who can hold strategy, craft and feasibility together than assemble a relay team that has to reconcile three partial views.
It also changes the texture of the work. When the person designing the system is the same person who will reason about how it ships, the design is feasible by construction. Fewer ideas die in the gap between what looked good and what could actually be built.
Speed is not the result of working harder. It is the result of removing the distance between a decision and the work it affects.
Fast turnaround is a side effect of structure
Clients notice our turnaround — an average of five days per defined deliverable — and assume we have found some productivity trick. We have not. The speed is a side effect of structure. When there is no queue of briefings, no waiting on a hand-off, and no reconciliation meeting to schedule, work simply moves. The clock that usually runs in the gaps between people barely runs at all. We are not sprinting; we have removed most of the reasons to wait.
This is also why we are careful about how many engagements we run at once. A small senior team is a high-trust, high-context machine, and it stays fast only if it is not stretched across too many fronts. Saying no to volume is part of how we protect the speed.
The trade-off, stated honestly
There is a real cost to this model, and we would rather name it. A small senior team cannot absorb unlimited scope, and it cannot be in five places at once. If a project genuinely needs a large parallel workforce, we are the wrong studio for it. But for the work we do best — brand systems, products and the engineering that ships them — depth beats headcount almost every time. We would rather be the right size for the work than the right size for the invoice.