An idea becomes useful when it leaves your imagination and enters another person’s world. Build Something helps you start with a real problem, create the smallest useful version, put it into someone’s hands, and let visible proof guide what you build next.
You have probably built things in your head that nobody else has ever seen.
A book you keep talking about. A business you could start. A workshop that would solve a problem you keep seeing. A project inside your organization that everybody agrees would be useful. Perhaps it is a podcast, a community, a tool, an event, an online course, a service, or simply a different way of doing something that frustrates you every week.
The idea may have been with you for months.
Sometimes years.
You have imagined what it could become. You may already have a name for it, a folder full of notes, books you bought because of it, screenshots you saved, and conversations in which you explained what you intend to create someday.
There is nothing wrong with thinking before you build. Some ideas become clearer when we allow them to mature.
But eventually an idea reaches a point where thinking about it cannot teach you much more.
Something has to exist.
Not the whole thing. Not the perfect thing. Not the version you will still be proud of ten years from now.
Something real enough to use.
That is what Build Something is about.
The question is:
How can I turn an important idea into something real, useful, and valuable?
Ideas feel safer before they become real
An idea inside your head has extraordinary advantages.
It does not fail.
Nobody misunderstands it. Nobody tells you the price is too high, the instructions are confusing, the chapter is boring, the event is inconvenient, or the feature you love is something they do not need.
Inside your imagination, all the parts fit.
Reality is less polite.
The moment you make something and put it in front of another person, the idea has to survive contact with a world that did not help you imagine it.
That can be uncomfortable.
So we prepare.
We research. We collect examples. We make plans. We study successful people. We compare platforms. We revise the outline. We ask which software is best. We think about branding, pricing, distribution, partnerships, launch dates, websites, funnels, and everything else the finished thing might eventually require.
All of these can become legitimate building work.
They can also become a very sophisticated way of never building.
What matters is not that you made something
I like builders.
I like people who start businesses, write books, make tools, create programs, solve problems, organize events, build communities, and invent ways to make things work.
But I do not think building is automatically good.
You can build something nobody needs.
You can create a beautifully designed solution to a problem that does not matter. You can spend a year writing a book because you want to become an author without deciding whether the book will help a reader. You can create another workshop because workshops are what you know how to create, even when the problem requires something else.
Production is not contribution simply because it took effort.
So before we celebrate the builder, I want to ask a less exciting question:
Who or what will be served because this thing exists?
Perhaps you want a supervisor to give instructions that people understand the first time. Perhaps you want a young entrepreneur to avoid an expensive mistake. You want parents in your community to know where they can get help. You want readers to make a decision they have delayed. You want customers to solve a problem without calling you every time.
Now we have somewhere to begin.
A thing becomes worth building when it helps make something that matters possible.
I wanted to write a book in 1996
I remember the notebook.
It had a blue cover. I wrote several possible titles on the first page because I wanted to become an author.
Then I stopped.
At the time, I had many reasons. I thought real authors were experts with impressive credentials. They were people with doctorates, awards, publishers, polished English, and enough authority to deserve hundreds of pages.
I had ideas and stories.
I did not think that was enough.
So I waited until I was ready.
The strange thing about waiting for readiness is that it can feel responsible. I was not avoiding the work, I told myself. I was preparing for it. I needed more experience. More knowledge. More confidence. Perhaps I needed a stronger idea.
Years passed.
I started again from time to time, then stopped again. I kept wanting to write the book while protecting myself from discovering whether I could actually write one.
Eventually the number of years became harder to ignore than the fear.
I began thinking about books differently. Instead of asking whether I was qualified to become an author, I became interested in a much simpler possibility: Could I write something useful?
That question gave me somewhere to work.
A useful book did not require me to prove that I knew everything. It required me to understand a problem, bring what I knew and had experienced to it, and help a reader make a move.
So I began building.
Not everything I wrote was good. Not every book became what I imagined. Some ideas changed radically once I tried to give them form.
But pages existed.
Then books existed.
And something happened that thinking about writing for twenty years could never have given me: the work began answering back.
The real enemy is keeping the idea safe from reality
We usually think the builder’s enemy is lack of resources.
Not enough money. Not enough time. Not enough expertise. No team. No audience. No equipment. No investor.
Those limitations can be real.
But many worthwhile projects die long before resources become the deciding problem. They remain unfinished because the builder keeps protecting the idea from the moment when reality can answer it.
That is the real enemy:
Keeping an important idea safe from reality.
We protect it through endless preparation. We make the first version enormous so that beginning becomes difficult. We polish privately because showing unfinished work feels dangerous. We create a brand before we know whether the thing underneath the brand helps anyone.
And sometimes we call all of this building.
The idea remains safe.
It also remains imaginary.
Change the question
When people have a meaningful idea, a very natural question is:
How do I build this?
That question can immediately produce a large project.
A book becomes twenty chapters. A business needs products, a website, branding, registration, marketing, systems, and staff. A leadership problem becomes a two-day workshop. A community idea becomes membership levels, committees, programs, and a launch event.
Soon the builder is staring at a mountain.
Try another question:
What is the smallest useful thing I can put into someone’s hands?
Notice that I did not say the smallest thing you can make.
Small alone is not enough.
It has to be useful.
And “someone’s hands” matters too, because the first version does not need an imaginary mass audience. It needs contact with a real person who has the problem you are trying to help solve.
Now the mountain starts producing stones you can actually move.
Build for use, not admiration
This is one of the most important disciplines I have learned from designing workshops, books, tools, and what I now call Minimum Lovable Plays.
Builders know too much.
That creates a strange danger.
Because we know many things about the subject, we want the first version to carry everything we know. If the topic is delegation, we want to explain all of delegation. If it is leadership, we want a complete leadership system. If we are writing about personal change, we begin with twenty-five principles because each one seems necessary.
We mistake completeness for usefulness.
But the person using what we build does not encounter the whole subject at once.
They encounter moments.
A supervisor is about to give an instruction. A customer is trying to choose. A reader is facing a decision. A manager is ending a meeting. A new entrepreneur is wondering whether anybody will pay for the offer.
Build for that moment.
Suppose supervisors regularly give instructions that produce rework. You could create an eight-hour communication workshop.
Perhaps one day you should.
But first you might build a small play: before work begins, state the outcome, show the standard, and ask the person to repeat back what they understood.
Now there is something to try.
If the play works, you learn.
If it fails, you learn.
Either way, reality has finally entered the design process.
Start with the promise
This is why I want builders to think about the promise before becoming attached to the product.
A product is what you make.
A promise is what you hope becomes possible because somebody uses it.
You may think you want to build a course. Perhaps what you actually want is for first-time managers to conduct one useful coaching conversation every week.
You may want to write a book. Perhaps what matters is that a reader who has postponed an important project finally makes the first visible move.
You may want to create an app. Perhaps what matters is that parents can find reliable information in three minutes instead of spending an anxious evening searching.
The promise gives the product a job.
It also gives you permission to change the product.
If the workshop does not create the result, you can redesign the workshop. If people do not need the app, perhaps a simple service solves the problem. If the book becomes too large to use, perhaps it needs to become a series of smaller guides.
When you are loyal to the promise, you can be flexible about the form.
Build the Minimum Lovable Version
I use the phrase Minimum Lovable Version because I want to hold two disciplines together.
Minimum protects us from trying to build everything before we learn anything.
Lovable protects us from using “minimum” as permission to produce something careless.
The first version does not have to contain every feature. It does need enough care and usefulness that somebody can experience the promise.
A Minimum Lovable Version of a book might be one short guide that completely helps with one problem. A workshop might begin as a 60-minute session around one situation and one play. A consulting service might begin with one client and one clearly defined result. A community may begin with five people gathering around one useful purpose rather than five hundred names on a membership list.
The question is not, How little can I get away with?
Ask:
What is the smallest version that can create a real win for someone?
That difference matters.
One real person can teach you more than one hundred imaginary customers
Builders often imagine audiences.
“We are building this for managers.”
“This is for entrepreneurs.”
“This is for Filipino professionals.”
Those descriptions may become useful later. But when you are creating the first version, a category cannot answer you.
A person can.
Show the thing to someone who has the problem.
Watch what happens.
Do not begin by asking, “Do you like it?” People can like something and never use it.
Look closer.
Where did they hesitate? What did they misunderstand? What did they use immediately? What did they ignore? Did your tool make the next decision easier? Did the conversation change? Did they ask for the thing again?
This is where building becomes interesting.
The person is no longer merely evaluating your creation.
They are helping reality redesign it.
Feedback should change the work
There is another danger once we begin showing our work.
Everyone has an opinion.
One person wants more features. Another wants fewer. Someone likes the title. Someone hates it. A customer asks for something completely outside the original offer. A friend confidently tells you what your audience really wants.
If you obey everybody, the work loses shape.
If you listen to nobody, the work stops learning.
So return to the promise.
Ask whether the feedback reveals something about the result you are trying to create.
Perhaps your instructions are unclear. Change them.
Perhaps people need a different format. Test it.
Perhaps the person you thought had the problem does not care enough to solve it. That is important evidence.
Feedback can change the product without controlling the purpose.
You are not building by committee.
You are learning in public enough for reality to improve your judgment.
Proof changes the way you build
Before something exists, builders work largely from belief.
We think people will want it. We believe the problem matters. We imagine the experience will help.
Belief is necessary for beginning.
It is not enough for continuing.
Once the work enters the world, start collecting proof.
Proof does not need to be dramatic.
A person uses the checklist without your help. A reader emails because she tried the exercise. A customer pays for the first version. A participant runs the play on Monday. Five people return to the next gathering. A client says, “Can we use this with the other team?”
Those are not final verdicts.
They are signals.
The first version creates the first evidence. That evidence informs the next version. The next version creates more evidence.
This is why building is different from planning.
Planning tries to predict reality.
Building lets reality participate.
Your first version is allowed to be replaced
People become strangely loyal to things they have worked hard to create.
You spent three months designing the workshop, so you defend the activities. You paid for the website, so you keep the offer even when nobody buys it. You wrote seven chapters, so changing the book’s premise feels wasteful.
But the purpose of version one is not to become permanent.
Its job is to teach you enough to build version two.
You are allowed to discover that the customer is different from the one you imagined. You may learn that the book should be shorter, the program should be longer, the event should become a community, or the business idea should stop entirely.
Stopping can also be part of building wisely.
Not every idea deserves another year of your life.
The work has to keep earning the resources you give it.
Building does not require becoming an entrepreneur
I want to make this clear because the word build often gets pulled immediately into business.
Entrepreneurs build.
But so do teachers.
Parents build routines. Employees build tools nobody assigned them to create. Community leaders build gatherings. Writers build bodies of work. Facilitators build experiences. Managers build systems. A young professional may build a portfolio. Someone recovering from a difficult season may build a practice that helps life become workable again.
The form changes.
The discipline does not.
See something worth making possible.
Give it a form.
Put the form into reality.
Watch what happens.
Build again.
Try the Build One Useful Thing Play
Think of one idea you have been carrying.
Do not begin with the entire project. Instead, take a page and answer five questions in complete sentences:
What problem or possibility matters enough for me to build around? Name something specific enough that you can recognize it happening in real life.
Who experiences it? Choose a real person if you can, not only a market category.
What do I want to become possible for that person? This is the promise.
What is the smallest useful version I can put in front of them? A page, conversation, offer, prototype, short session, checklist, event, sample, or first working version may be enough.
What will I watch to know whether it helped? Name something the person will do, understand, decide, use, request, complete, or pay for.
Then build that.
You may eventually need the business plan, website, team, platform, book proposal, marketing system, or larger program.
But do not make the whole future a requirement for discovering whether the first useful thing can work.
The first win is not finishing the dream
Your first win is much smaller.
Something that existed only in your imagination now exists in the world.
Someone can see it.
Someone can use it.
Someone can respond to it.
And because they can respond, you know something today that you could not have learned while the idea remained inside your head.
That is a meaningful shift.
You are no longer only imagining what could work.
You are building with evidence.
Build again
Most worthwhile things do not emerge fully formed.
The first book teaches you how to write the second. The first customer teaches you which problem you are really solving. The first workshop exposes the instruction nobody understands. The first community gathering shows you what people actually come back for.
So do not ask version one to prove your worth.
Ask it to teach you.
Then make the next version.
This is where Finish What You Start eventually becomes important. Building requires starting, but worthwhile work also has to survive the point when novelty disappears and carrying the project becomes work.
And when the thing becomes useful enough that more people should experience it, Create Your Stage asks the next question: where will people see, test, trust, and use what you made?
For now, stay with the builder’s first responsibility.
Take something that matters.
Give it a useful form.
Put it into reality soon enough for reality to answer.
Then follow the proof.
Follow the Proof
For the next seven days, do not measure progress by how much more you learned about your idea.
Watch what became real.
Did a page get written? Did somebody use the prototype? Did you make the offer? Did a participant try the play? Did a customer show you what was confusing? Did the first conversation reveal that you were solving the wrong problem?
Pay attention especially to surprises.
The part people ignore may matter as much as the part they praise. A question you keep receiving may point to the next version. A feature nobody uses may deserve removal. A tiny piece people repeatedly ask for may contain more value than the large thing you thought you were building.
That is the builder’s advantage.
You do not have to know everything before you begin.
You need to build something useful enough for the world to teach you what comes next.
Explore Build Something
Begin With a Problem Worth Solving
Read this when you have several ideas but cannot tell which problem deserves your time, effort, and attention.
Start With a Promise, Not a Product
Read this when you already know what you want to make but have not yet defined what should become possible for the person who uses it.
Build the Minimum Lovable Version
Read this when the project has become too large to begin and you need a first version small enough to build but useful enough to matter.
Show It to One Real Person
Read this when you keep polishing privately because the work does not yet feel ready to be seen, tested, or used.
Let Feedback Change the Work, Not the Purpose
Read this when your first users, readers, customers, or participants are giving you information and you need to decide what deserves to change.
Explore all Build Something articles in the sitemap →
Other paths
Choose What Matters — Go here when you have many things you could build and first need to decide which one deserves protection and commitment now.
Move First — Go here when you know what matters but hesitation, uncertainty, or waiting for readiness is keeping you from making the first move.
Finish What You Start — Go here when something useful already exists and the challenge has become carrying the work through resistance, revision, and completion.
Create Your Stage — Go here when the work is becoming useful and you need places where people can discover, experience, test, and trust it.