Ship Something Today

Ship something today means finishing a useful piece of work and choosing an appropriate audience or use. It can help interrupt endless preparation, but it is not a rule to publish unfinished work every day. Make the next piece small, meet the checks its purpose requires, and learn from feedback. Research, private practice, and rest belong in the process.

A folder full of drafts can represent serious work. It can also become a place to hide from a decision. The useful question is what the next piece needs: more information, focused practice, a review, or release.

You do not have to turn everything you learn into public content. But if you want to make something, give making a place in the week rather than waiting for the perfect feeling.

Why can consumption feel like progress without moving a project forward?

Reading, listening, and watching can produce real learning. They can also become substitutes for applying an idea when the next step feels uncertain. Judge the activity against its purpose: did it answer a needed question, develop understanding, provide rest, or merely postpone work you already know how to begin?

Cal Newport's Deep Work argues for protecting attention for demanding tasks. It is a practitioner's synthesis, not a neuroscience study showing that consumption always produces dopamine while creation feels neutral or unpleasant. Making can be enjoyable; research can be difficult. Neither feeling alone measures usefulness.

Try writing one sentence before opening another tutorial: “The question this needs to answer is …” Afterward, test the answer in your project. If you are learning for pleasure, that is a valid purpose too. The problem is not consuming information; it is repeatedly calling avoidance the next necessary step.

There is no universal ten-to-one ratio separating spectators from creators, and you cannot meaningfully ship more pieces than you make. Choose an appropriate balance for the task. Stop consuming, start creating is an invitation to begin applying knowledge, not a dismissal of reading, listening, or careful preparation.

What does deliberate practice research say about creating?

Deliberate practice is structured work intended to improve a specific aspect of performance. Simply producing more output or publishing frequently does not guarantee that improvement. Identify a weakness, practise it with attention, obtain useful feedback, and revise. Some of this work can remain private; public release is not part of the definition.

Ericsson, Krampe, and Tesch-Römer's 1993 work examined prolonged practice and expert performance. It did not establish that daily publishing makes every writer, programmer, or designer an expert. Later research has also debated how practice is defined and how much performance variation it explains.

Macnamara and colleagues' 2014 meta-analysis reported contributions that differed sharply by domain: 21% of performance variance in music and less than 1% in professions. These estimates do not make practice pointless, but they rule out treating repetition as a complete explanation of skill. Opportunity, instruction, feedback, and other differences matter.

For a writer, a useful repetition might be revising one unclear paragraph after a reader explains where they got lost. For a designer, it might be testing whether someone can understand a screen. The tenth or hundredth attempt is not automatically better if the same mistake survives unchanged. Mastery takes time, and it also takes attention to what the time is doing.

What does shipping look like in practice?

Shipping means bringing a piece to an appropriate point of completion and putting it into use or sharing it with a suitable audience. That audience may be one trusted reviewer, a small test group, or the public. The right scope depends on the work, its purpose, and what could happen if it is wrong.

Examples include sending an agreed draft for comment, sharing a sketch with a collaborator, testing a small tool, publishing a checked explanation, or serving a meal. A private journal can be valuable without being shipped. Not every act of creation needs exposure to strangers.

The German edition's three release stages help make the distinction concrete:

A draft can be incomplete and still ready for feedback. Calling something a draft does not excuse exposing private information or making unsupported claims. Build before you talk can mean producing something reviewable before making a public promise.

Amabile and Kramer's research drew on nearly 12,000 diary reports from 238 workers. It connected progress on meaningful work with positive inner work life. Amabile says, “Even incremental ‘small wins’ can contribute to what we call positive inner work life.” Progress in that research was not restricted to daily public launches; solving a problem or moving a project forward can matter too.

When does done over perfect help?

Done over perfect helps when “perfect” means endless polishing that no longer improves a useful, sufficiently checked piece. Sharing at the right stage can expose misunderstandings and invite feedback. It does not mean rough work is always better than delayed work, or that speed should override accuracy, consent, safety, or the needs of the audience.

Seth Godin's The Practice encourages a regular creative process and the willingness to share work. It is practical advice, not a controlled study proving that daily publishers outperform everyone who revises longer. Different projects require different cycles, and a public response is only one kind of feedback.

Before sharing, name one question: Is the instruction clear? Does the tool solve the intended problem? Does the argument follow? Ask someone suited to that question. Then separate useful observations from taste, insults, and requests outside the project's purpose. Silence is ambiguous; it may reflect reach or timing rather than quality.

Private tests, peer review, and rehearsal can reveal problems before a public launch. You do not learn nothing from unreleased work. The aim is to shorten an unnecessary delay while keeping the review the work needs. Trust the process when it includes both making and evaluating, rather than counting release dates alone.

How do I build a sustainable shipping practice?

Define one small piece, its intended use, the next audience, and the checks required before sharing. Reserve a realistic work period, then review what happened. A daily session may suit you; a weekly release may be more appropriate. Neither a monthly output quota nor six months of tracking proves that a creator identity has become automatic.

Try this sequence:

1. Choose a concrete unit. One paragraph, sketch, code change, diagram, or draft explanation.
2. Set a workable session. Twenty-five minutes is one option, not a required dose. Stop or adjust when circumstances require it.
3. Define readiness. Decide what the piece must do at this stage and which checks matter.
4. Share appropriately. Ask a reviewer, test with permission, or release when ready. Keep private material private.
5. Record the lesson. What became clearer? What feedback was useful? What will change in the next version?

Twenty-five minutes on each of 365 days would total about 152 hours. That arithmetic illustrates accumulation, not a promise about quality or a reason to skip recovery. A smaller number of focused sessions can be a meaningful practice too.

Review the month by looking at completed work, learning, effects, and workload. Some months involve research or a large revision rather than many releases. Avoid arbitrary judgements that fewer than fifteen outputs makes someone a disguised consumer. A thousand unchecked releases need not teach more than a smaller body of thoughtful work. Consistency and a daily audit help when they support learning instead of punishment.

Being THE ONE

Make the next useful piece small enough to begin. Give it the attention and checks it needs. Share it at an appropriate stage and listen for something that can improve the work.

You do not have to prove your worth through constant output. Creating something useful today can be a good next step without becoming a demand for every day of your life.

Frequently asked questions

How do I combine regular delivery with quality?

Define the stage and audience before setting the deadline. A sketch for a reviewer and a public product have different requirements. Keep essential checks even when you reduce scope; make the piece smaller rather than hiding important shortcomings.

How should I handle negative feedback?

Look for specific information about the work, compare it with the intended purpose, and decide what to change. You can ask for clarification. Not every opinion is useful, and harassment does not become valuable merely because it arrived after a release.

What role can mentors play?

A suitable mentor can help identify a specific weakness or offer informed feedback. Agree on what you are asking and respect their time. Mentorship supports your practice; it does not require a public launch every day or guarantee faster progress.

Ready to make something? Begin a short creation practice and choose a small piece to work on.