The 5-second version
The better AI gets at building things, the less your value depends on building everything yourself.
What matters more is spotting fast that something is off ("this is boring," "nobody will click this," "it works, but I don't want to use it"), explaining why, handing AI the goal and the limits, and then judging the real result again.
So instead of writing all the code yourself, you run a loop:
notice that something feels off → talk it through → plan from 0 to 1 → build → look at the real thing → notice the next thing that feels off
From the outside, it looks like a boss who only complains.
But if you are not dictating pixels, it is not micromanagement. You keep the goal and the quality bar. AI gets the searching and the building.
1. It started with a homepage that was tidy and painfully boring
A site's homepage listed its categories and article counts in neat rows.
The information was organized. Nothing was broken. Every choice could be explained.
And the first reaction was still:
"Wow, this is boring."
That kind of feeling is annoying to deal with.
It is not a bug like a broken button. Tests pass. Nothing breaks the spec. You just don't want to touch it.
Talking it over with a chat AI slowly put words to the problem.
The site owner was showing off stock: "Relationships: 98 articles," "Decisions and comparisons: 78 articles." A first-time visitor doesn't care about stock. They are wondering:
"Is there anything fun here for me right now?" "I have this problem. Where do I tap?" "I'm not looking for anything. I just want to stumble on something."
Then the whole problem went back to a planning AI built for starting from scratch. The homepage changed from a category warehouse into message cards you enter from your mood or need.
That was not a bit of CSS polish.
It was rethinking what the homepage is for in the first place.
2. Your job starts to look like being a nightmare client
Once AI does the building too, the human side of the work looks weird.
"This looks cheap." "Technically correct, but I don't want to click it." "The feature is there, but the experience feels like junk." "Can't this be more fun?"
Read on their own, those lines sound like the client from hell.
Real micromanagement looks different:
"Make the margin 12px." "Always use 3 columns of cards." "Put this sentence right here."
That is the human locking in the solution.
Here it was the other way around.
The human owned the judging: Is this good? Does it fit the goal? What feels wrong?
How to fix it went largely to the planning AI and the coding AI.
So the "nightmare client" is really doing the jobs of product owner, editor-in-chief, creative director, and quality checker at once.
The keyboard got quieter. The job title got heavier.
3. A gut feeling is a great alarm, but it is not a spec
"I don't like it" matters.
But throwing it straight at a coding AI is risky.
It might just be your personal taste. It might be a side effect of a fix somewhere else. An AI can faithfully build your complaint and break the whole thing.
That is where talking it through with a chat AI helps.
At the very least, turn the feeling into this:
- Symptom: what exactly made you go "ugh"?
- Possible cause: why does it feel that way?
- Reader: who actually has a problem with it?
- Goal: what should people be able to do?
- Limits: what must not break?
- Done when: what would show it got better?
"The homepage is boring" becomes:
"The site's own categories are front and center, so a first-time reader can't easily start from what they want. We want a way in based on mood or need, not article counts."
Now the complaint is something you can design from.
4. Talking it through turns "my taste" into something you can test
The key is not to treat your gut feeling as gospel.
"I don't like it" and "it's bad for users" are not the same thing.
So you throw research, existing design rules, counterexamples, and real usage data at it.
For example, you break it down:
"Is it bad because there's too much on the screen?" "Is it bad because it's sorted the way the owner thinks, not the reader?" "Is it bad because people with no goal have no way in?" "Wouldn't regular visitors actually find the list faster?"
This step keeps your instinct alive while stopping it from running wild.
The gut feeling is the alarm.
Talking it through is the diagnosis.
Building is the treatment.
Don't run into surgery the moment the alarm beeps.
5. "Make it like IKEA or Costco" is not lazy, it narrows the search
Concrete examples are powerful.
"Make it more fun" gives AI far too much room to wander.
But try:
"Like walking through a huge store and finding things you never came for." "Not a list of categories, but something where you keep discovering stuff as you look."
Now the experience you want is much clearer.
The point is not to copy another store's look.
Don't copy the colors, the spacing, or the card shapes. Lift it one level up:
"finding things you weren't looking for" "wandering around" "wanting to see the next thing" "showing an experience, not a stockroom"
Use examples to set the direction, not to lock in the answer.
That way AI still has room to think.
6. Split the from-scratch planner from the builder
Fixing a known bug doesn't need a giant planning meeting every time.
Find the cause, fix it, test it.
But for work closer to 0 to 1, like "make the homepage fundamentally more fun," it pays to run it once through a strong planning AI before building.
Give each one its own role.
The chat AI breaks down the feeling and writes down what's needed.
The from-scratch planning AI explores options, structure, and how the experience should feel.
The coding AI handles code, tests, and checking nothing else broke.
The human owns the goal, the limits, the priorities, and the final yes or no.
There's no need to go round and round in AI meetings that only produce plans.
Planning only counts once it turns into something built.
7. Research says human + AI is not automatically the best team
This part matters.
A 2024 meta-analysis in Nature Human Behaviour pulled together 106 experiments and 370 effect sizes that directly compared humans alone, AI alone, and humans working with AI.[1]
On average, human + AI beat humans alone.
But compared with whichever was better on its own, human or AI, the combo did worse on average.
Adding a human at the end doesn't automatically make things stronger.
On top of that, the combo tended to fall short on decision-making tasks, while it looked more promising on creative tasks.
So the real question isn't "Should we use AI?"
It's:
Who does which part?
Not "a human signs off on everything," and not "dump it all on AI."
How you split up the work decides how well it goes.
8. What AI is good at has a jagged edge
A 2026 experiment published in Organization Science followed 758 knowledge workers. On 18 tasks well within what AI handles well, people using AI finished 12.2% more tasks, worked 25.1% faster, and turned in better work on average.[2]
But on a tricky business problem just outside what AI handles well, AI users were 19% less likely to get the right answer.
Two jobs can both look like "brain work," yet AI helps on one and hurts on the other.
That's the "jagged frontier."
So instead of saying
"AI is smart, let it handle it,"
you say
"AI takes this kind of work. A human judges this part."
Humans: spotting what feels off, setting goals, big trade-offs, keeping the whole thing consistent.
AI: exploring at scale, coming up with alternatives, writing, building, and mechanical checks.
For now at least, that split feels like the natural one.
9. Research backs moving people from writing first drafts to editing
In a 2023 experiment in Science, 453 professionals did writing tasks. Those using generative AI finished 40% faster on average, and their work was rated 18% higher in quality.[3]
A 2025 study in the Quarterly Journal of Economics looked at real data from 5,172 customer support agents. With AI help, issues resolved per hour went up 15% on average, and the gains were biggest for less experienced staff.[4]
To be clear, none of this proves a company runs itself if the boss just says "this feels off."
But it does fit a simpler idea: when first drafts, routine work, generating options, and writing get cheaper, people can spend more time on "what should we make," "what do we keep," and "what's off here."
Hands-on skill doesn't stop mattering.
It just stops being the only thing holding you back.
10. The biggest trap: fixing every complaint until nothing fits together
Fix the cards.
Fix the ads.
Fix the related articles.
Fix search.
Each one got better.
And yet the whole site got cluttered.
This happens all the time.
Squashing complaints one by one can make each part better and the whole worse.
So every so often, you have to step back and look from above:
"Who is coming here?" "What are they coming to do?" "What's the first thing they should do?" "Where do we want them to wander?" "What should they leave with?" "Is there a feature we should actually delete?"
Improving parts and checking the big picture are separate jobs.
And humans get pulled along by AI suggestions too. One experiment showed a feedback loop where human and AI judgments fed each other and the bias got bigger.[5]
So "the AI agrees with me" is not proof.
Go back to research, real usage, counterexamples, and the world outside.
11. "Just make it nice" only works after you've built up shared context
"Just make it nice" is honestly a risky instruction.
With no context, it's a slot machine.
But it means something else once these are shared:
The goal What are we trying to improve?
The anti-goal What do we never want?
The limits What rules, costs, safety, or daily operations must not break?
The reference What kind of experience are we aiming for?
Done when What would show it worked?
Once that builds up, "just make it nice" becomes shorthand.
It's not dumping the work.
It's calling up a long shared history in a few words.
Same as on a strong human team, where "you know, the usual" is all anyone needs to say.
With AI, that's finally starting to work too.
12. If the coding AI goes down, don't let the whole project stall
The coding AI's app crashed.
Right before the usage limit reset.
"I wanted to cram everything in while I still could."
Outages like that quietly hurt.
But they also point to a practical answer:
Keep the thinking line and the doing line separate.
Even while the coding agent is down, you can still:
collect what feels off, talk it through, form guesses about the cause, check them against research, set priorities, write down what "done" means.
The moment it comes back, the coding AI doesn't start by figuring things out. It just works through jobs that are already lined up.
One service going down shouldn't freeze your whole team's brain.
It saves money, but more than that, it keeps you going when things break.
13. The AI-era boss doesn't need to know every answer
Run this loop once and the human's role looks very different.
You don't have to be able to write all the code.
You don't have to draw the perfect screen on the first try.
You don't have to know the fix.
But you do hold on to:
"This isn't it." "Here's why." "Who should be better off, and how?" "What must not break?" "Can we go with this idea?"
AI can churn out fixes.
It can build them.
It can check a lot of them too.
But if you hand off even the call on what this product counts as good, there's nothing left to aim at.
So the human job doesn't vanish so much as move upstream and get smaller.
In old-school boss terms, it's not
"I'll build it all myself."
It's
"This isn't it. Here's why. Here's where we're going. Do it whatever way works best."
"Just make it nice" is finally turning into a real skill.
References (5)
[1] Vaccaro, M., Almaatouq, A., & Malone, T. (2024). When combinations of humans and AI are useful: A systematic review and meta-analysis. Nature Human Behaviour, 8, 2293–2303. https://doi.org/10.1038/s41562-024-02024-1
[2] Dell’Acqua, F., et al. (2026). Navigating the Jagged Technological Frontier: Field Experimental Evidence of the Effects of Artificial Intelligence on Knowledge Worker Productivity and Quality. Organization Science, 37(2), 403–423. https://doi.org/10.1287/orsc.2025.21838
[3] Noy, S., & Zhang, W. (2023). Experimental evidence on the productivity effects of generative artificial intelligence. Science, 381(6654), 187–192. https://doi.org/10.1126/science.adh2586
[4] Brynjolfsson, E., Li, D., & Raymond, L. (2025). Generative AI at Work. The Quarterly Journal of Economics, 140(2), 889–942. https://doi.org/10.1093/qje/qjae044
[5] Glickman, M., & Sharot, T. (2025). How human–AI feedback loops alter human perceptual, emotional and social judgements. Nature Human Behaviour, 9, 345–359. https://doi.org/10.1038/s41562-024-02077-2
