Document Library
← Document library
iHouseDesign · Operations

The Team

May 21, 2026 · Operations · Team · Ivan · Mira · Mujtaba

Right — and the first thing to say is that intellect isn’t the issue for them either, and neither is effort or character. Ivan has shown up reliably for fifteen years. Mira is the strongest operator you have. Mujtaba answered work calls from a hospital bed. These are not lazy or low-quality people.

So whatever holds each of them back, it is not a moral failing and it is not stupidity — which, exactly as with you, is the hopeful part, because it means the cause is structural and structure can be built. But the specific gap is different for each of the three.

Ivan

Ivan is a superb executor missing one thing: a judgment framework. He can produce anything, fast, and has done it loyally since 2011. What he cannot do is decide what is right for a client without you — and the telling detail is that he doesn’t even try. He works “strictly within his lane,” calls himself “not a Photoshop artist,” routes every real decision to you.

That looks like a limitation, but read it again: it is also fifteen years of conditioning. The arrangement was always “Ivan makes, Arseni decides,” so neither of you ever built the alternative. And remember — Ivan himself asked for more autonomy on small calls so he’d stop interrupting you. He is willing. What holds him back is that the judgment was never written down and handed to him, and the dependency became a habit on both sides.

Give him the aesthetic brief and defined parameters and he will rise — but be honest about how far: Ivan’s realistic ceiling is “trusted senior executor who self-approves within clear boundaries,” not “creative director who owns client taste.” That is a large unlock and it is the right one. Pushing him past it would be pushing against who he actually is.

Mira

Mira is the opposite problem, and the more dangerous one. She is not missing capability — she has judgment, she’s internalized David’s aesthetic, she runs five parallel flows and “nothing drops,” she pushes back on you when she thinks you’re wrong. She is, functionally, already a creative director.

Three things hold her back. First, capacity — she’s at roughly two clients’ worth of load and she is full; there is simply no more Mira. Second, her excellence is tacit — she runs it in her head, resists tracking, keeps the system in her own memory. That works for her, and it means none of it can be transferred or scaled — she is a smaller mirror of your exact problem. Third, and most urgent: she is carrying emotional weight she shouldn’t be — David uses her as a therapist, she absorbs the team’s failures — and there is real friction between the two of you; she has already, on a call, threatened to quit.

So what holds Mira back is not Mira. It is that she has no leverage beneath her, no documented system around her, and a load on top of her that is fraying the relationship. She is your most valuable person and your single biggest flight risk at once. The move with Mira is not to fix her — it is to give her a junior to lever through, get her tacit system written down, lift the emotional labor off her, and repair the relationship, before she walks. She is the person you build the senior layer around — if you don’t lose her first.

Mujtaba

Mujtaba is the one whose story is still unfinished. He is eager, loyal, communicative — the hospital-bed detail tells you his character is not in question. Two things hold him back.

He has real gaps in technical judgment — “technical common sense,” as Mira put it — part inexperience, part unknown. And when he hits a wall or an ambiguous task, his pattern is to freeze and go quiet. That looks like the passivity that sank Mohammed, but it comes from the opposite place: Mohammed went silent to avoid work; Mujtaba goes silent because he doesn’t know what to do and going quiet feels safer than exposing that.

That is a far more sympathetic and far more fixable failure — a confidence-and-structure problem, not an avoidance one. What holds him back: skill gaps, the freeze reflex, and the absence of a rule that makes asking for help mandatory and safe rather than an admission of failure.

Give him tightly scoped tasks at his real level and a hard escalation rule — stuck for thirty minutes, you must post in the channel — and he likely becomes a solid, reliable technical assistant. Whether he can grow past “executes well-defined tasks” into someone with independent technical judgment remains an open question — and the only fair thing is to give him a few months of that structure and measure. Don’t pre-decide it either way, and don’t build the company assuming he becomes a senior mind he hasn’t yet shown himself to be.

The through-line

Put the three side by side and the pattern is exact: each person is stuck one rung below their potential, and in every case the missing rung is the same kind of thing — a framework, a documented system, a defined boundary, an escalation rule, a layer of leverage.

Ivan is missing the judgment framework. Mira is missing leverage and formalization. Mujtaba is missing scoped structure and a safe way to be unblocked. None of them is missing intelligence, drive, or loyalty. What holds the team back is precisely what holds you back — the company never built the connective tissue, the scaffolding, that turns a group of capable individuals into a firm. You are all stuck one level below where you could be, because nobody built the ladder.

And this is consistent with your own rule that drive can’t be trained and you shouldn’t build process around underperformers — because these three are not that. The genuine wrong-fits you already removed: Mohammed, Nina, Asif, Andre are gone. What’s left — Ivan, Mira, Mujtaba, Riaan — is the keeper team.

For keepers, “missing scaffolding” is not a reason to despair. It is the most fixable problem there is.