The month of reckoning, week two. The proposition is thrown, so this week we look at human hands. When the domain stands at the front, what actually happens on the desk?
This Week's Signal
One person, the work of many hands. One axis of this month's field piece. PM Han Ji-yeon (41) weaves a flow at a translation company that links scheduling, assignment, review, and delivery. In the old way, a planner wrote requirements, a developer made the screen, and the planner asked for changes again — a round trip. Now, Han Ji-yeon weaves that flow directly, alone. The work that many hands passed back and forth ends within one hand. The point isn't that it got faster — it's that what leaked between the handoffs no longer leaks.
The deadline raises its hand first. Newly joined tax accountant Yun Jae-seong (39). He has 180 client firms. Their deadlines differ from firm to firm, so by human memory one always slipped through. What he built isn't a grand system — it's a small flow where the schedule you mustn't miss raises its hand first on the screen. A person who doesn't know tax can't build this screen. The person who knows tax best is the one who could. This is the most concrete face of "the domain stands at the front."
Evidence is now a list. Once the Build piece bundled five stages of hardware into one catalog, the tone of inquiries changed. From "does this really work?" to "which cell number is ours?" Once verification crosses from anecdote to frame, people stop asking whether it's possible and start finding their own place. And once they start finding a place, the next question is always the same — "then who should stand at the front for us, too?" The answer is the same all month. The person who knows that equipment, that work, best.
Tool & Package Notes
This week's note is about flow. People often picture "an app," but what both Han Ji-yeon and Yun Jae-seong built isn't a single screen — it's a path along which work flows. When a schedule comes in, it goes to assignment; when assignment ends, to review; when a deadline nears, to a notification. The screen is just a station on that path. Here is why the person who knows the domain is strong — it isn't that they draw screens beautifully, but that they know best in what order the work flows. Someone from outside would have to learn that order first. The person who was inside already knows it in their body. So in the work of weaving a flow, the time spent teaching disappears entirely.
A Brief Thought
"One person, the work of many hands" has a trap. It can sound like a call to cut headcount. But look at the two of them, and it's the opposite. What shrank is the friction of handoffs, not people. Han Ji-yeon spends the freed-up time on harder planning. Yun Jae-seong empties the part of his head that tracked deadlines and uses it for consulting. Hands don't shrink — hands move to where they're more valuable.
From the Field
A word from Yun Jae-seong. "At first I thought, 'what kind of screen would a tax accountant make?' But once I did it, I hadn't made a screen — I'd transplanted the logic of my own work exactly as it was. The hard part wasn't the tool; it was how precisely I know my own work." What remains where the tool's threshold has been lowered — is the depth of the domain.
This Week's Question · Next Month's Preview
In your work, where is the point that "leaks as it passes through many hands"? If you brought that round trip into one hand, what would change? Next week (week three) we look more deeply at "All of This on One Runtime," where five proofs gather into a single pattern, and follow how far the two people's flows grow. And in week four, the six-month retrospective since launch.
makemind.dev "Signal" — once a week, what flowed that week.