Compare Arseni Riajski’s operational and creative structure to Fabien Baron after French Vogue. Baron remained a highly central aesthetic authority yet appears able to operate across multiple luxury brands, publications, and campaigns without personally handling every operational layer. How does someone like Baron realistically delegate?
Compare to Arseni’s structure at iHouseDesign: flagship client relationships, founder-centered judgment, high aesthetic standards, systems thinking, many simultaneous operational layers, recurring technical/emergency interception, weak middle layers historically.
Main question: Is the problem actually “failure to delegate” — or failure to build a Baron-style hierarchy where the founder remains aesthetic/intellectual gravity but lieutenants absorb interpretation, production, operations, and execution filtering?
If Baron went to Cuba for 3 weeks with one major client: what continues without him? What still routes upward? What people/systems make that possible?
Analyze operational dependency vs aesthetic authorship vs judgment transfer vs creative mythology vs layered delegation in elite creative organizations. Also whether Arseni’s SOP/automation obsession is Baron-style cognitive filtering without the human middle layer.
Baron is the right comparison, because he is the working proof that an auteur can scale — remain the aesthetic center across many luxury houses at once without being operationally trapped. The mechanism is specific, and it is not “letting go.” It is layered delegation with a particular shape.
He never delegates the authorship layer: the aesthetic standard itself (what “good” is), the core concept — the conceptual leap at the start of a project, the final yes/no on anything going out under his name, the curation of which clients and projects to take, and the mythology — he cannot delegate being Fabien Baron, because the name is part of what the luxury house is buying.
He aggressively delegates everything else, and “everything else” is larger than people assume. All production goes to producers — he does not book a studio or a crew. All client churn, timelines, and approval cycles go to an account/project layer — he does not sit on status calls. All technical craft — retouching, prepress, motion — goes to specialists. Presentation and decks go to designers.
And, critically, the development of a concept once he has set the direction goes to senior art directors. So your list — PMs, producers, senior art directors, technical operators, presentation designers, client-facing creative translators — the answer is yes to all of them. That list is essentially the Baron & Baron org chart.
But the most important role on it is the one that sounds least operational: the senior art director who interprets rather than executes.
Here is the distinction your whole question turns on. Operational dependency and aesthetic authorship look similar from outside and are completely separable. Baron removed himself from operational dependency entirely and kept aesthetic authorship totally. He does it three ways.
That third point is judgment transfer, and it is the thing your SOPs cannot do. Baron’s senior art directors can develop a campaign “the way Baron would” because they spent years beside him — doing the work, being corrected, converging on his eye. Judgment transfers by apprenticeship: a slow, human, relational process. An SOP transfers a process. Only apprenticeship transfers taste. There is no shortcut, and it is the single layer iHouseDesign does not have.
Creative mythology: the myth requires Baron to be the author of record and the final eye. It does not require his hours. A house buys “a Baron campaign” — the myth is satisfied by his standard and his signature, not by his presence at the shoot. The auteur’s trap is conflating “my judgment is the product” (true) with “my operational presence is required” (false). The mythology is fed by authorship. It is not fed by interception.
No. That frame is wrong, and you were right to rule it out. “Failure to delegate” implies a behavior fix — push work down. Arseni’s problem is structural: the missing middle.
Baron’s organization has four working layers — auteur → senior lieutenants who interpret → producers and account who absorb operations and client → technical execution. Arseni’s has two: Arseni, personally occupying layers one, two, three, and most of four — and then executors. Ivan, Mujtaba, the contractors are bottom-layer executors. There is no interpretation layer above them and below Arseni.
You cannot delegate interpretation to a pure executor; that is precisely why Ivan sends 130 questions a month — there is no lieutenant for them to go to instead. The “weak or incomplete middle layers” in your own bullet list is the diagnosis. It is not a failure to delegate. It is the absence of the thing delegation requires as its destination. You cannot let go into a vacuum.
One honest amendment: Baron’s domain is pure creative, and a producer can fully own a shoot. Yours is creative-technology, which carries an operational-emergency tail Baron simply does not have — hosting, servers, malware, SSL. Baron never gets a 2am “the campaign server is down” call. So your structure must be heavier than his: Baron’s four layers plus a technical-operations owner — or you shed that surface entirely. Your middle is both missing and wider.
Whether the SOP/automation obsession is a substitute for that middle — yes, exactly.
What a lieutenant does is cognitive filtering: absorb the chaos, the options, the sub-decisions, the client noise — and pass upward only what genuinely needs the auteur, already developed to 90%, framed as one clean choice. Arseni sensed, correctly, that he needed exactly this filtering layer — and built it in software: iBrain surfaces what needs attention, the OQE, the SOPs that try to encode his judgment. That is a correct intuition expressed in the wrong medium.
It cannot fully work, for two reasons. Software routes decisions; a human absorbs them. A dashboard that surfaces the six things needing your attention has organized your load, not reduced it — a lieutenant would have handled five and brought you one. And software handles only the anticipated; the entire value of the middle layer is judgment on the unanticipated, the weird case, the novel ambiguity.
So the systems make Arseni a faster bottleneck, not a freed founder. He built the filter out of code because code is controllable, does not require years of apprenticeship, and does not disappoint you while it learns. But a digital filter only tidies the cognition. Only a human filter removes it.
It passes — and with a single client, easily.
What makes it possible is five things at once: the lieutenant layer, the producer layer, the account layer, a named deputy, and the fact that his judgment was front-loaded so projects in flight already contain his direction. Arseni’s Cuba freezes because he has none of the five.
The synthesis: Your instincts have been right the whole time. You correctly sensed you need a cognitive-filtering layer and an auteur structure — and you have spent years building it. You built it in software because software is the material you trust and control.
The one thing you have not built is the human middle, because that layer cannot be coded — it has to be apprenticed, over years, with tolerance for imperfection while it converges on your eye. The Baron model is not “let go.” It is: build the three human layers beneath you, transfer your judgment into the top of them by apprenticeship, then operate by concentrated direction and gate review.
That is a construction project, not a personality change — which makes it a more precise and more hopeful diagnosis than “failure to delegate,” because it tells you the exact thing to build.