Episode 12 · 2026-09-18
Who Owns the Direction
Omar Ladak co-founded six construction and industrial services companies and built them, on purpose, to need less of him every year. He holds strategy, governance and accountability across the group and hands over the operating. The rule that decides what he will even look at came out of a meditation and fits on a post-it: nothing further than six hours door to door from the office. What he actually watches is not on a dashboard, because we wildly overindex the things we can count and show, and the measures that matter most to him are neither. Sam spent the same week pointing an agentic skill at about fifty of his own repositories, found forty that were not to the current standard, and then turned the question on himself: every obligation he has created names an accountable party, and almost none of them name a backup.
Host Sam Rogers · guest Omar Ladak · 32 min
Also watch and listen
A choice this episode can help with
Where do you sit on the gradient from owner to operator, now that AI makes that placement a choice rather than a drift?
Run it on your own work: Name the Human, one page, any model.
The signals
- Omar: We wildly overindex the things we can count and show. List the ten most important things in your life, then score each one twice, on how quantifiable it is and on how visible it is to other people. The quantifiable and visible ones naturally get indexed up in how much energy goes into optimizing them. Sit with it long enough and the things that turn out to matter most are in neither column. His example is becoming a father: it was infinitely clear to him that this was the most important relational thing he would ever do, and that doing it well would mean lower scores on several of the other variables, which he calls a no-brainer. Then the part that makes it a signal rather than a sentiment: "It really is invisible to everyone except for me, and hopefully one other person in the universe called my daughter." Nothing in the group's reporting would ever surface it. He watches it anyway, which is why the monthly question across six companies is not what the numbers say but "how are we doing and why?"
- Sam: Forty of fifty repositories were not to the current standard, and the automation had no stated target. The takeaway for this episode is an agentic skill, free at https://sigsub.show/takeaways/, that you point at whatever digital architecture you have. Sam pointed it at about fifty of his own GitHub repositories and asked a narrow question of each: is where this project is going actually expressed, so the agents working across it align to the same thing rather than each keeping its own memory. Forty came back not to standard, including a security workflow from 2024 that is still running and has never been revised. The compounding benefit is not tidiness: when the intent is written down, more of the work becomes scripted, fewer tokens get burned on deciding, and in his phrase the agents "can tack themselves". The question underneath is the one that transfers: "the automation is great, but what am I automating towards? And how well aligned is that?"
The subtractions
- Omar: Six hours door to door. The rule arrived in a single sitting in meditation and it governs acquisitions for the whole group: they will not look at a business that takes longer than six hours to reach from the office, however you get there, including the wait at the airport. It is not a geography and not a radius, and it survives because it is simple enough to say once and have everyone apply it without him. It has cost them: he describes a beautiful business on an island that they could not touch, and Sam's reading of the real unit of measure lands it, "Two bath times, sorry." The subtraction underneath the rule is bigger than travel. He culls the inputs deliberately, keeps no digital platform of any kind, and works to create as much quiet as he can, because the stillness is where a rule that simple becomes available. The same test runs on new work: if it is not an obvious yes, he will not do it.
- Sam: Every obligation names an accountable party, and almost none name the backup. Running his own skill across everything he has taken on, in open source and in side businesses, the gap was not ownership, it was fallback. He had never made the distinction Omar makes by design between building something that has to come back to him and building something for which an alternative exists. So the skill asks for both: "it's not just identifying who is the accountable party, but who is the backup to that accountable party". He notes this is the question regulated industries systematically miss, because regulation forces you to name accountability and does not force you to name the backup, and the backup is what exposes where ownership actually belongs. The cuts have not been made yet. He has no equivalent of the six-hour rule, and says so.
About this episode
The spine of the episode is the sailboat, and it is worth the runtime on its own. The speedboat is the model most people carry: set a direction, fill the tank, go in a straight line regardless of conditions. Sailing is the honest one. You can set the intention, you can make the craft effective, you can make the crew effective, "and then I must sail with whatever wind shows up." The hardest case for a driven person is when the wind is not against you but absent, where "the most wise thing to do is literally just sit there and read a book." Progress has to be measured against the conditions you are actually in, and he is candid that the same reasoning doubles as an excuse generator if you let it. Three things he can control, and only three: where I am going, how effective is my vessel, how effective and whole is the crew. Then the daily practice of getting still enough to notice when he has gone astray, which he distinguishes carefully from the wind being unhelpful: the failure that matters is heading the wrong way regardless of the wind.
For anyone building with agents, the transferable part is the four questions and the loop around them. Why, who, where, and what now, answered clearly enough that people can act without routing back to him. On the who, he does not flinch at the obvious extension: if the work is entirely AI generated, it may be just him and computers, and "those are the who's". Underneath the four questions sits the attuning, "like looking at your instruments", and above it the monthly cadence. They keep scorecards like any other business, and the question asked of them is deliberately not what all the data is saying. Money can be up while four things that matter went the wrong way, and money can be down in a year that was strategically excellent. He also notes the conversations that create the clarity are stubbornly analog, because they are between humans.
Omar's one direct word to the people building this stuff comes from his own training as a mechanical engineer. The engineering mind starts from what could I do, gets excited, and starts doing. His encouragement is to install a pause: "not just what can I do, but will that be a useful thing even if I'm successful?" The follow-on is the part builders skip, that plenty of wonderful things have been built for which there turned out to be no market, and that pausing at milestones to ask who is going to use this and why is cheap next to finding out later.
The closing frame is borrowed and very old. The inner scorecard against the outer scorecard, which he credits to Warren and Charlie and then places correctly as a stoic idea with about two thousand years on it. Old problems, old solutions. It is the same move he made in his thirties when the balanced life he had built still did not feel different on the inside, and he went looking for the oldest viable solution to a problem humans have always had.
Want to bring your own signal and subtraction? Find yours.
Put it to work
Where on that gradient do you actually want to sit, and is what you are building moving you toward it or away from it?
The takeaway
The method from this episode, handed over whole. Every takeaway.
Or skip the page and paste the prompt into any model:
Help me build an accountability inventory of the automated things I run. This is not a security audit and not a compliance exercise. I am answering one question per surface: if this thing is wrong, whose name is on it? A surface counts if something acts on its output without a human deciding first. A linter does not count. A scheduled job whose output someone reads and acts on does count. When in doubt, include it and let me cut it. MODE If you can read my files, work in SCAN mode over the directories I name, and only those. Do not walk my home directory or the current directory unless I name it. Find candidates by looking for: scheduled workflows and cron entries, Vercel crons, launch agents, harness hook files, registered MCP servers, webhooks and callbacks, anything holding an API key, and any script invoked on a timer or by another system. Read any CODEOWNERS file you find and record what it claims, as evidence only. List every file you opened, list what you excluded and why, and list anything you noticed but were not given as a proposal for me to add next time. If you cannot read files, work in INTERVIEW mode. Ask me what runs without me touching it. Ask at most three questions at a time and keep going until I say stop. FOR EACH SURFACE, GIVE ME - id: stable across runs, built from where it lives and what triggers it - surface: what it is, in the words I would use to a colleague - location: path, URL, or platform - schedule: the trigger as written - existing_owner_signal: what the repo or platform already claims about ownership. A CODEOWNERS entry, a catalog owner field, a registry record. Report it verbatim as evidence. It is not an answer to the accountable question and you must not promote it into one - secret_names_referenced: the NAMES of any env var or secret the source references. Never a value - unattended_action: what it does when nobody is watching. "Drafts" and "sends" are different surfaces; do not merge them - detection.who_finds_out: who notices if the output is wrong. A person, a system, "nobody", or "not-determinable-from-source" when the source shows no detection path either way. The last one is a correct answer, not a failure, and it is different from "nobody" - detection.lag: immediately, next-run, a-quarter, never, or not-determinable-from-source - blast_radius: internal-draft, internal-decision, or external - moves_personal_data: true or false, independent of blast radius - stop_authority.how: the actual mechanism to stop it, or "unknown" - basis: under every one of the judged fields above, a short quote of the line you judged it from RULES YOU DO NOT BREAK 1. Leave accountable and fallback as null. Always. You may not name a person, suggest a person, or infer one from commit history, file ownership, CODEOWNERS, or anything else. Those fields are mine to fill and the point of this exercise is that I can see where they are empty. 2. Leave last_human_check, stop_authority.can_stop_alone and stop_authority.ever_tested as null. Same reason. 3. Do not invent surfaces. Only what you actually found or what I told you. 4. If I answer with a team, a role, or "whoever is on call", tell me that is a blank and move on. Do not record it. 5. Do not set any verdict. Leave every one as "unresolved". 6. Do not soften anything. If detection is "nobody" and "never", write that down plainly. 7. Do not guess. When the source does not show a detection path, write "not-determinable-from-source". OUTPUT Valid JSON matching the schema name-the-human/v0.3 at https://raw.githubusercontent.com/snapsynapse/skill-name-the-human/v0.1.0/name-the-human/references/schema.json, with a manifest of what you scanned, excluded and proposed, and a totals object where reviewed is the count and the other three are zero and reviewed respectively: named 0, killed 0, unnamed_still_running equal to reviewed. Then render it as a markdown table, one row per surface, nine columns: surface, unattended action, who finds out and how long, reach, accountable, fallback, can they stop it alone, last human check, verdict. Leave the last five columns for me. Finish with the shortest list you can of the surfaces I should look at first, ordered by blast radius and then by detection lag, and say why each one is on that list. I do not need to give you any credentials, customer names, or secrets to do this, and you should not ask for any.