Operations Cleanup for a Lean Studio
A lean creative studio was producing excellent work and burning out its best people. We mapped the operational drag, removed three meetings, killed two tools, and gave the team a delivery rhythm they could trust without the founder approving every step.

An independent creative studio working with founder-led brands on identity and digital products.
Site
fieldhouse.studio
Industry
Brand & Digital Design
Locations
Copenhagen
We removed two tools, retired three meetings, and the studio simply became a calmer place to do excellent work. Two people who were about to leave stayed.

Sofie Lindqvist
Founder @ Fieldhouse Studio
A studio that produced excellent work and exhausted its best people
The studio’s portfolio was the kind of portfolio that wins arguments. Every project shipped on time, every client renewed, and the work was genuinely admired by peers — which is the rarest signal in a service business. From the outside, the studio looked like a model of how a lean creative team should operate. From the inside, three of the most senior people were quietly considering leaving, and the founder had stopped sleeping through the weekend.
When we asked the team what was wrong, they could not point at anything specific, which is the most useful kind of answer. Every individual was clear on what they were working on. None of them could describe what the studio as a whole was working on, or which decisions were live, or where to find the current version of anything without asking someone. Status was being tracked in four places, and the act of keeping those four places in sync had become a quiet, full-time job that nobody had been hired for and everyone resented in silence.
A two-week shadow, and the invisible cost of reformatting
We shadowed three live projects from kickoff to delivery — not to audit them, but to count the seams. The same piece of information would move through five tools before it reached the client: a brief written in one document, summarised in a project tool, restated in a chat thread, reformatted into a deck, then exported into a deliverable. At every seam, someone reformatted. Most of the seams added no judgment and no decision. They added formatting work, performed by senior people whose time the studio was paying for.
The cumulative effect was that the team felt slow even though every individual was fast. The system was the bottleneck, and the system had grown organically, one tool at a time, each one added to solve a real problem that the previous tool had created. None of the tools were wrong on their own. The combination was the problem, and nobody had ever been given permission to look at the combination as the unit of analysis.
Removing tools, removing meetings, refusing to add a methodology
Two tools were deprecated outright and replaced by a single source of truth for project status — the same tool the studio already used for delivery, with a small adjustment to how status was written. The weekly all-hands and two standing project meetings were collapsed into a single short asynchronous update with a clear escalation path. We did not introduce a project-management methodology, we did not hire an operations lead, and we explicitly refused to add a layer of process on top of the existing one.
The harder change was cultural. The studio had grown up with a habit of asking the founder for sign-off on small decisions, and the founder had grown up with a habit of giving it, and both sides knew this had become a problem and neither side had quite known how to stop. We rebuilt the delivery rhythm so that the founder’s input was needed at two predictable moments per cycle — kickoff and mid-cycle review — and not at any other time by default. That single change reclaimed the founder’s calendar and stopped fragmenting the senior team’s days into thirty-minute slivers.
A delivery rhythm the team owns, and the outcome nobody predicted
Each project now runs on a fixed two-week rhythm with one mid-cycle checkpoint and one end-of-cycle review. The rhythm is the same for every project, which means the team stops re-inventing the cadence at the start of every engagement and clients stop asking when the next update is coming. Utilisation went up because fewer hours were spent reformatting and re-deciding. But the more important change was the one we could not have promised in advance.
The team stopped working in evenings. Not because anyone told them to stop, but because the day stopped fragmenting and they could finish what they started. Two people who had been quietly considering leaving stayed and have since taken larger roles. The studio did not become bigger, more efficient, or more sophisticated in any way that would show up on a slide. It became a place where excellent work could be produced at a sustainable rhythm, which is what the founder had been trying to build all along and had not had the right diagnosis for.
+
Services
Notes on pricing, positioning, and the work itself.
Field notes from inside premium service businesses — on pricing, positioning, and the operational decisions that quietly compound.
From overlapping tools and messy handoffs to unclear responsibilities, operational inefficiencies drain.

