craft as ai moat
the bottleneck was never speed. it was judgment.
productboard’s hubert palan keeps making a point that’s been rattling around in our heads: agents ship faster than ever, and what most products are short of is someone deciding the right thing to ship.
the point productboard’s hubert palan1 keeps making is the one that’s been rattling around in our heads. shipping fast is not the constraint any more. agents ship faster than ever. what most products are short of is someone deciding the right thing to ship.
read it again.
for two decades, the product industry operated on a shared assumption: if we could just ship faster, we’d ship better. agile was supposed to solve it. lean was supposed to solve it. devops was supposed to solve it. each wave promised that speed would deliver quality.
then ai showed up and gave us speed. real speed. the kind where a founder with claude and a figma make subscription gets from idea to working prototype in a single afternoon.
the speed problem is, for practical purposes, solved.
and the products still suck.
not all of them. but the volume of mediocre software has never been higher. the app stores are flooded with it. linkedin is flooded with it. every landing page looks like every other landing page because they’re all generated by systems trained on the same averages.
which proves what thoughtful builders have been saying for years: the bottleneck was never speed. it was judgment.
speed lets you iterate on a bad idea faster. it doesn’t tell you whether the idea is worth iterating on. it doesn’t tell you which of the forty features to cut. it doesn’t tell you that the onboarding flow everyone thinks is fine is actually the reason retention is dying in week two.
that’s a different muscle. taste. experience. the human layer ai hasn’t touched.
the market is signaling this. 45% of senior creative directors are now actively rejecting ai-generated assets for major campaigns. not because the output is ugly, it’s often passable. passable is exactly the problem. when everyone’s output hits the same “good enough,” the bar moves.
figma’s 2026 state of the designer report2 caught another signal. designers now define craft as two things: visual polish (57%) and thoughtful problem-solving (47%). design systems, what most companies still treat as component libraries, are evolving into what figma calls “living frameworks that scale taste.”
taste as infrastructure. not decoration.
the companies that win the next five years won’t be the ones that ship fastest. they’ll be the ones with a strong enough point of view to know what to ship in the first place, and the craft discipline to make sure what they ship actually feels like something.
not features. not speed. direction.
that’s the whole game now.
sources