I have always had an overflow of curiosity. Over the years, I started multiple side projects simultaneously and explored diverse fields—learning English, Japanese, piano, illustration, and web engineering. While trying many things helped me discover what suited me and what didn't, looking back after a few years revealed an uncomfortable realization: I hadn't truly finished or proven many of them.
When energy is divided across five distinct initiatives at once, each progresses at an agonizingly slow pace. Before reaching meaningful escape velocity, momentum fades, and projects end up quietly abandoned.
I still have endless ambitions. However, I have learned to structure that appetite. Instead of scattershot experimentation, my goal now is to tackle one thing at a time, get it into a provable, sustainable orbit, and only then expand outward. I call this mental model building my own solar system.
The Solar System Framework
[ The Sun ] (You / Focus)
│
┌─────┴───────────────┐
▼ ▼
[ Planet A ] [ Planet B ]
(Autonomous Orbit) (Next In Line)
│
▼
[ Satellite ] (Newsletter / Complementary Tool)
1. Build One Planet First
A planet orbits the Sun under stable gravitational equilibrium:
- In project terms, orbiting means the product, content, or system maintains itself or generates linear growth with minimal continuous intervention.
- For example, if you build a technical blog or a niche utility, it reaches orbit when steady search traffic and value delivery continue even when you pause writing or shipping for weeks.
- Define explicit criteria for orbit in advance, including a target timeline and validation metrics (e.g., maintaining 100 daily active users or consistent monthly recurring traffic within three months). If it misses the target, make a clear decision: iterate with a defined deadline, or cleanly decommission it.
2. Monotasking: Never Build Two Planets in Parallel
Do not start a second project until the current one has either achieved stable orbit or been cleanly written off as an experiment. Parallel creation is the single fastest killer of early-stage side projects.
3. Branching: Choose Between New Planets or Moons
Once a planet successfully achieves self-sustaining orbit, you gain two strategic options:
- Build a new planet: Start the next standalone domain or application.
- Build a moon (satellite): Create a secondary project that orbits the existing planet.
4. Build Moons to Compound Growth
A moon orbits a planet, deriving context and gravity from it:
- A moon is a targeted extension built on top of an established planet.
- Moons generate super-linear leverage: if you have an established software library, a moon might be interactive documentation, a CLI wrapper, or a hosted service. If you have an established blog, a moon could be a targeted newsletter or a community.
5. Cultivating the Complete System
By repeating this deliberate cycle—validating one planet, letting it settle into autonomous orbit, and selectively deploying moons—you assemble a coherent personal constellation rather than a graveyard of unfinished repos.
Moving Beyond Fragmented Ambition
This model may not suit everyone; rapid spray-and-pray prototyping works for some. But for builders who suffer from scattered focus and chronic unfinished prototypes, the solar system framework provides clear constraints: protect the sun's core energy, demand orbit before expanding, and let gravity do the compounding.