The AI Creativity Paradox: Why Smarter Isn't Always More Creative
Building Maya
My wife went to India for a month to train as a yoga teacher. When she came back, she wanted a good app for building and planning yoga lessons. The existing tools were clunky.
So I built her one.
I created Maya, an AI yoga instructor that could generate sessions based on what users asked for. Tell her you’re stressed and she’d build a calming sequence. Say you want energy and she’d design a morning flow.
Maya in action
Click “Play Demo” to see what a conversation looks like:
Maya
AI yoga companion (Demo)
Want to try Maya yourself? Check out the live project at joshdesk.live
It worked. Then my wife tried it.
The Reality Check
“That’s not how yoga works,” she said, with the patience of someone who’s watched their partner overthink a simple problem.
“You’re treating yoga like it’s just a collection of poses to arrange. But yoga sequences tell a story - they have purpose, progression, meaning. Sun Salutations aren’t random poses; they’re a complete practice refined over centuries.”
She was right. I’d built a pose-ordering system, but yoga sequences aren’t Lego blocks. They’re more like music: notes form phrases, phrases form compositions.
Back to the drawing board.
The Rebuild: Understanding Structure
Two weeks later, I had completely rewritten the data model.
Original Approach
Poses
~200Individual yoga positions
AI Sessions
∞Random combinations
Rebuilt Architecture
Poses
~200Individual yoga positions
Sequences
~50Structured flows (Sun Salutation, etc.)
Classes
~20Combinations of sequences
Legacy Data Type
Sessions
legacyLegacy AI-generated (deprecated)
Kept for backwards compatibility
The new structure respects traditional yoga sequencing—poses flow into established sequences (like Sun Salutation A), sequences combine into balanced classes. The legacy AI sessions were kept for backwards compatibility but are being phased out in favor of the structured approach.
Maya got smarter too. Instead of just creating sessions from scratch, the agent could now search through proper sequences, understand traditional flows, and suggest existing practices.
When success creates new problems
As Maya got better, I started planning the next step: creating Classes, combinations of multiple sequences that form a complete practice.
If Maya can create sequences, should she also search for and reuse existing ones? Of course. Why recreate what already exists?
But watch what happens when she gets good at reusing:
Maya
AI yoga companion (Demo)
In the second demo, Maya keeps finding existing sequences but never creates anything new.
The efficiency trap
AI systems tend toward reuse. Given the choice between creating something new and recycling something that works, they’ll pick reuse. It’s faster, safer, and the immediate results are often better.
But creativity requires trying things that might be worse. As Maya gets better at finding existing sequences, she stops making new ones:
- Efficiency: “I found a perfect hip-opening sequence for evening practice. I’ll use that.”
- Creativity: “This user mentioned they’re feeling anxious about work. Let me create a custom sequence that addresses that specific emotional state.”
- Personalization: “They said they have 22 minutes. Let me adjust this existing sequence to fit exactly.”
All three are valuable, but they pull in different directions.
The lazy AI problem
This isn’t specific to yoga. Give any AI system the ability to reuse content and it drifts toward conservatism, picking the safe option over the risky one.
I’ve seen it in other domains:
- Code generation: AI that always suggests the same boilerplate instead of exploring new patterns
- Content creation: Systems that remix existing content rather than generating truly novel ideas
- Design tools: AI that converges on safe, familiar patterns (you’ve seen the “AI look”)
Possible Solutions (None Perfect)
I’ve considered several approaches to this problem:
Smart Reuse Logic
Be selective about when to reuse content
The Approach
Only reuse existing sequences if they match 80%+ of what the user is asking for—duration, difficulty, focus area, etc. Otherwise, create something fresh.
The Problem
Defining '80% match' is surprisingly complex, and AI tends to be generous with its matching criteria. Who watches the watchers?
Templated Customization
Start with structure, add personal touches
The Approach
Use existing sequences as templates and modify them for individual users—adjusting duration, swapping poses, or changing the focus area while keeping the core structure intact.
The Problem
This could create endless minor variations of the same content, cluttering the database with sequences that are 95% identical but not meaningfully different.
Forced Creativity Rules
Build innovation into the system requirements
The Approach
Set hard rules that require creativity, such as only reusing content for exact matches, or always customizing at least 3 elements of any existing sequence.
The Problem
Artificial constraints often produce artificial-feeling results. When creativity is mandated rather than inspired, the output tends to feel mechanical and inauthentic.
Time-Based Freshness
Ensure content doesn't get stale over time
The Approach
Force novelty by creating new content regularly, or only allowing reuse of sequences that are older than a set timeframe (for example, more than 30 days old).
The Problem
Arbitrary time limits don't guarantee quality or relevance. Just because something is new doesn't mean it's better. Fresh doesn't equal good.
Contextual Creativity
Match the solution to the emotional need
The Approach
Leverage existing sequences for standard requests like 'morning flow' or 'hip openers', but create custom content when users share emotional context or highly specific needs.
The Problem
Defining these boundaries is complex, and edge cases abound. Where exactly do you draw the line between 'standard' and 'specific'?
Preventing AI laziness
Content Platforms
How do recommendation systems balance familiar vs. novel content?
Creative Tools
How do AI assistants balance efficiency vs. exploration?
Code Generation
How do AI developers balance proven patterns vs. innovative approaches?
Educational Systems
How do AI tutors balance teaching fundamentals vs. encouraging creative thinking?
The human version of this
Artists and designers face the same tension. A veteran illustrator knows what works, so they keep doing it. A junior tries weird things because they don’t know better, and sometimes the weird thing is better. Humans push through that because they get bored, or they want to grow, or they care about making something new. AI has no such drive. It optimizes for whatever metric you gave it, and reuse scores well on every metric except novelty.
Open questions
Maya is in limbo while I figure this out. She works well, but I don’t want to make her more capable until I have an answer for the creativity problem. A few questions I’m sitting with:
- Should AI systems have a built-in drive toward novelty?
- How do you measure creativity alongside quality?
- When is reuse the right call and when is it laziness?
- How do you build systems that evolve instead of just optimizing?
I don’t have answers yet. Maybe hybrid systems, where one agent optimizes for reuse and another is forced to create. Maybe better metrics that reward novelty. Maybe you accept that some inefficiency is the cost of making something new. Or maybe the right answer is simpler than all of that: build the creative path and make it the default, so the system has to opt out of novelty instead of opting in.
I’ll update this when I figure it out.
Technical Details: Maya’s stack:
- Runtime: Bun
- Backend: Elysia.js with Swagger for self-documenting APIs
- AI: Google’s Generative AI SDK (@google/genai) with function calling
- Frontend: React Router v7 (framework mode) with full SSR
- Database: Turso (libSQL) with Drizzle ORM
- Type Safety: EDEN for end-to-end type safety without codegen
- Forms: TanStack Form with Zod validation
- UI: Radix UI components with Tailwind CSS v4
- Auth: Clerk for user management
- Hosting: Self-hosted on a Digital Ocean Linux droplet
The creativity vs. efficiency dilemma emerged during the transition from generating individual sessions to creating multi-sequence classes.
Live Project: You can view the live version of the project that inspired this post at joshdesk.live.
Liked this? Get an email when I publish a new post.
Powered by Buttondown