Humans own the outcome
Humans own the outcome and keep the judgment. AI does the typing. Roles, review and decision rights are redrawn to match.
The problem
In the old method, a team as a whole owns the outcome, so when something breaks nobody in particular answers for it. Decisions are routed up to a manager or a director, so the people doing the work never own anything end to end. And quality is left to a separate QA step: the people who build the thing count on QA to catch what they missed.
Getting an agent to demo something is easy; the work is getting it to production reliability, and owning it when it breaks.
How I approach it
As the tools take over the mechanical work, the human job moves toward owning the outcome end to end and raising the bar on what done means.
- The humans involved own it. Ownership lies with the humans involved in achieving the outcome, not with a team and not with one person, and it does not pass to someone else between stages. If something is nobody’s job and it touches my outcome, it is mine until someone owns it.
- Capacity comes from the leader. Ownership pushed down without capacity is ownership in name only. If I ask people to own an outcome, I owe them the room to deliver it: protected time for the improvement work, escalation rules that keep unplanned work from taking over the plan, and the platform investments no single team can make on its own.
- Roles written for the work. Senior engineers write the testable spec, design the validation and steer the agents. Managers coach instead of deciding. Quality is owned by the humans who own the outcome, not by a separate QA team.
- Judgment stays with people. The calls that depend on context, the sign-offs, and the confirmation before anything destructive runs are made by a person.
- Verify by risk. AI output is verified by risk, not line by line: the closest checks go to the changes that can do the most damage and to the hotspots, the parts of the code that break most often. Every technical claim is grounded in the real code and data, not in memory or a doc.
- Organized around ownership. Teams of one or two human engineers + agents form around outcomes, and the ownership of the outcome lies with the humans that achieved it.
- The tool is never the reason. “QA will catch it” is not a plan, and “the tool did it” is never a reason to stop checking.
What it produces
Every outcome owned by the humans who achieved it, and roles written for the work as it is now.
In the Luci House
The AI-staffed team I run every day as a working prototype.
Each member has a role and a lane, and when a question belongs to someone else's lane, the member who received it routes it to the owner instead of improvising an answer. One rule sits above the rest: nothing goes out of the house without my yes. A member can draft an email; it does not send one. The members change how they work all the time, inside rules that only I set. How it is organized