Most people are using AI like a very fast search engine.
They ask for code.
They ask for answers.
They ask for solutions.
And sometimes, that works.
But if you’ve spent any time building real software—software that needs to grow, change, and survive contact with reality—you’ve probably felt that something is missing.
What’s missing isn’t a better prompt.
It’s design thinking.
Design Isn’t a Phase—It’s a Conversation
In traditional software development, design is often treated as an upfront activity: “Let’s design it, then build it.”
But experienced developers know the truth:
design happens throughout the development process.
We iterate because we learn.
We refactor because we see more clearly.
We redesign because new forces emerge.
Design is not a document.
It’s an ongoing conversation with the problem.
When we work with AI, that conversation becomes even more important—not less.
Prompting Is the First Step, Not the Discipline.
Prompting matters.
Clarity matters.
Good instructions matter.
But prompting alone is not design thinking.
Design thinking is a mindset that helps us:
•understand the problem space
•recognize forces and constraints
•model what matters
•design for change, not just correctness
Prompting is how we enter the conversation.
Design thinking is what allows the conversation to go somewhere interesting.
Without that context, AI can only do what it’s told.
With context, it can reason, explore, and propose.
Context Is the Activator—Especially “Why”
One of the most common mistakes I see is that people omit the why.
They tell AI what to build.
They rarely explain why it exists, what might change, or what matters most.
When we skip the why:
•AI produces procedural solutions
•designs become brittle
•concerns get mixed
•extensibility disappears
But when we explain intent, forces, and motivation, something shifts.
The conversation elevates.
New options appear.
Better designs emerge.
AI doesn’t just follow instructions—it starts to think with us.
Design Thinking Activates AI’s Latent Intelligence
AI has more intelligence than we usually allow it to express.
Whether that intelligence shows up depends on how we engage it.
If we treat AI like a tool, it behaves like one.
If we treat it like a collaborator, it often rises to the occasion.
Design thinking is what activates that latent intelligence.
By talking about:
•what we’re trying to learn
•how the system might evolve
•which virtues and qualities matter
•where we want flexibility and where we don’t
…we invite AI into the design space instead of limiting it to execution.
Why Experienced Developers Are Uniquely Positioned
There’s a quiet misconception that AI favors beginners.
My experience has been the opposite.
Experienced developers already understand:
•tradeoffs
•abstractions
•design principles
•the cost of change
•the importance of clarity
What AI removes is the burden:
•framework setup
•boilerplate
•syntax recall
•full-stack friction
This frees experienced developers to focus on what they do best:
thinking, modeling, and designing for change.
You don’t need to relearn everything.
In many cases, what you already know is exactly what AI needs.
Doing the Simplest Thing—Even When AI Can Do More
AI can generate a lot of code very quickly.
That makes restraint more important than ever.
Good design doesn’t mean building the ideal system.
It means doing the least amount of work necessary now while preserving the ability to grow later.
That’s why practices that support virtues like:
•simplicity
•extensibility
•testability
…still matter deeply in an AI-driven world.
AI helps us move faster—but we still have to decide where to go.
What We’ll Explore in Q1
This quarter, I’ll be exploring AI-Driven Design Thinking—not as a theory, but as a lived practice.
We’ll look at:
•treating AI as a thinking partner
•discovering design through conversation
•activating AI’s reasoning with context
•building changeable software incrementally
•using experience as a strength, not a liability
If you’re curious about working with AI rather than just asking it for answers, you’re in the right place.
Design has always been about understanding.
AI doesn’t change that—it makes it more visible.
