If you do not like code, estimates will make you lie. You will pad the number, hide the fear, and perform knowledge you do not have. That is how designers get pushed into "being technical" without ever forming an opinion.
Artists already know what happens when a piece has no edge. It expands until it is everything and nothing. Software culture often calls that "being ambitious." Basecamp's Shape Up book calls the opposite move an appetite: how much time the work is worth, decided before you fall in love with a solution. Appetite is direction. It is a no with a calendar.
Ryan Singer's language is useful here because it is visual. You shape a problem the way you shape a massing: enough form to know the boundaries, not a full set of construction drawings. Then you bet a cycle. Then you stop.
This is how a designer who was told to code gets taste in the work without becoming a project manager. Observation names the problem. Opinion names the form. Appetite names what you will not add.
Appetite is not an estimate
An estimate starts with a design and ends with a number. An appetite starts with a number and ends with a design.
That sentence is the whole method. If you only have six evenings this month, the piece is a six-evening piece. You do not ask "how long will a particle system take." You ask "what particle system is worth six evenings." Scope yields. Time does not.
Shape Up usually sets two sizes for a product team: a small batch (one or two weeks) and a big batch (a six-week cycle). You do not need Basecamp's calendar. You need the same honesty:
- Small batch: one visible sketch that ships. A p5.js study. A node patch that outputs one motion.
- Big batch: a tool you can hand to someone else. A tiny UI. A generator with three controls.
If the idea cannot be hammered into that box, you have not shaped it. You have a mood.
Shaping before you type
Shaping is the studio equivalent of a fat-marker sketch. You name the problem, the appetite, and a solution at the level of masses, not pixels.
A shaped bet for a designer-learning-code might look like this:
- Problem: I keep making posters that I cannot vary without redrawing.
- Appetite: two weeks of evenings.
- Solution (shaped, not specified): a browser sketch with three sliders: density, rotation, palette. Export a PNG. No accounts. No backend.
That is enough. It is not a backlog. It is not a Figma file of every state. Builders (you, later this week) get to choose the path inside the boundary.
Basecamp's six weeks is "long enough to finish something meaningful and still short enough to see the end from the beginning." Your version can be fourteen focused hours. The principle is the same: see the end from the start.
The circuit breaker is a kindness
If the cycle ends and the piece is not done, the default is not an extension. Shape Up calls this a circuit breaker. It sounds severe. It is how you stop a runaway project from eating the next idea.
For a solo artist, the breaker is: when the two weeks are up, you either publish the sketch or you put it on the wall as a study and walk away. You do not secretly add a third week because the Censor wants polish.
If it still matters in the next cycle, you reshape it. Maybe the appetite was wrong. Maybe the problem was two problems. That is not failure. That is seeing.
Cool-down is an Artist Date with a job
After a cycle, Shape Up puts in two weeks of cool-down: bugs, loose ends, no new bet. Cameron's Artist Date is the same instinct with a different costume: assigned play, once a week, alone.
Use cool-down as both:
- Fix the export button.
- Walk through a building and photograph one repeating joint.
- Do not start a new "real" project because you feel empty.
Morning Pages still come first. Three handwritten pages. Not a standup. The pages keep the bet from turning into self-punishment.
How this accelerates literacy
Estimates make you lie. You pad, you hide, you perform knowledge you do not have. Appetite makes you choose a form that fits the time you actually have. Choosing a smaller form is a design skill. It is the same skill as cropping.
Each finished small batch is a pattern you now own: a loop, a parameter, a file you can open next month. Literacy is a pile of owned patterns, not a certificate.
Pair this with Code Starts as Shape, Not Syntax. Shape is the language. Appetite is how long you are willing to stay in the room with it.
A betting table for one
You do not need a company. Once a month, write three shaped pitches on paper. Pick one. The others are not a backlog that haunts you. If they still have heat next month, they can return. Most will not. That is the point of not keeping a graveyard of tickets.
The bet you pick should scare you a little and still be drawable. If you cannot fat-marker it, you cannot code it yet. Go back to seeing.
What not to put on the table
Do not bet a clone of a tool you do not use. Do not bet authentication. Do not bet "the whole product." Those are unshaped moods. They are also how people who dislike code prove the dislike was destiny.
Shape Up's circuit breaker exists so a bad pitch cannot eat the next cycle. Pair it with the refuse-list in what not to build when code is cheap. The skill they wanted was never velocity. It was the ability to let an idea die in public and still have an opinion in the morning.
If the only thing you ship this month is a smaller no, that is still a coded practice. You changed the system by not adding a shrine.