Start with the Plate

The seed catalogs arrive in December, which is a month early for planting and exactly the right month for a mistake. They come into a house that is still eating the evidence of its actual habits: the drawer with the three wilted scallions, the bag of carrots half gone, the salad greens bought on Saturday and softened by the following Friday. A person sitting at the kitchen table in midwinter, circling photographs of heirloom tomatoes, is not looking at that drawer. This is the first planning mistake of the season, and almost everyone makes it, because the catalogs are beautiful and the drawer is not.

I made it myself. My first garden, more than twenty years ago, was planned from a catalog in a rented duplex with a south-facing strip of grass along the driveway. I grew what looked good on the page: purple-podded beans, a specialty eggplant, three kinds of basil. I can tell you what I did not grow, because I remember the grocery trips. I did not grow onions, though I bought them every single week for soups and sauces. I did not grow carrots, though my son ate them daily in his lunch. I grew a striking eggplant that ripened into a vegetable nobody in the house had ever cooked, and it sat on the counter until it was no longer an eggplant. That garden produced photographs. The garden I run now, and the ones I help people plan through our county program, are judged by a different standard: what did the household eat.

So before you order a single seed packet, do something less appealing than a catalog and more useful. Take one ordinary week, sometime in December or early January, and write down the vegetables your household actually ate. Not the vegetables you approve of, and not the vegetables you intend to eat after the garden comes in. The ones that went into mouths. Where they appeared in a meal, what form they arrived in, fresh or frozen or canned or cooked into something, and where they came from. Bought at the store, pulled from your freezer, given by a neighbor with an oversized zucchini plant, supplied by a food pantry or a community garden. Every line gets all of it.

I ask people in our winter workshops to do this, and the first responses are always the same shape. Blank faces, then a guess. Most people, when asked what vegetables they eat, describe an aspiration. They say "a lot of greens," which turns out on paper to mean one bag of spinach a month, two-thirds of which goes brown in the drawer. Or they say "we eat everything," by which they mean they are polite at other people's tables. The record is humbler than the self-image. That is not a flaw in the household. It is the whole point of the record. You are not auditing your virtue. You are taking inventory of demand, and demand does not care what you meant.

Here is a real composite of what a week looks like when someone actually writes it down, drawn from the kinds of logs people bring back to me in January. Sunday, a pot of soup with onions, carrots, celery, canned tomatoes, all from the grocery. Monday, a stir-fry with a bag of frozen broccoli and a fresh onion. Tuesday, tacos with shredded lettuce and jarred salsa. Wednesday, leftovers. Thursday, pasta with frozen peas and garlic. Friday, a salad eaten by one member of the household while the others had something else, and the leftover salad greens in the bag going soft by the weekend. Saturday, roasted potatoes and frozen green beans. One teenager ate a raw carrot every school day. Onions appeared five times. Fresh greens appeared once, and spoiled once.

That log is more valuable than any catalog, because now the numbers can argue with the fantasy. This household does not need a garden that supplies fifty kinds of produce. It needs onions, carrots, something leafy in a quantity that matches how fast it actually gets eaten, and possibly potatoes and green beans. The eggplant that looks so stately in the photograph has no entry in the log at all, because nobody in this house has ever cooked one on a Tuesday. That is not a reason to never grow it. It is a reason not to give it prime space in the first year.

A few cautions before you trust your own week. Pick an ordinary one. If you were traveling, or sick, or hosting your in-laws, the log will mislead you, and you should run it again. One week is an estimate, not a contract. I had a woman in a workshop realize, midway through, that her chosen week included a holiday and a funeral, and her vegetables that week were entirely potatoes and one heroic casserole. She did the log again the next week and got a completely different list, with greens in it. If your household changes a lot with the seasons, note that too. Winter logs understate fresh tomatoes because nobody decent is selling them in December, and if your household eats tomatoes all summer, that preference is real even if it does not show up in a January week. Ask. Ask the people who eat with you what they would actually use, and when they say "salad," ask what is in the salad, because "salad" is the single most common way a household lies to itself about greens.

You also need to be honest about the source column, and this is where I watch beginners trip most often. Food you already have dependable access to is not unmet demand, and a garden does not earn its keep by replacing supply lines that work. I worked for years with families who received weekly produce through our food-access program and through a church distribution, and some of them felt they ought to grow everything anyway, as if the garden were an apology for needing help. It is not. If your freezer is already full of peas from your mother's garden or from a good sale, peas are a poor use of your first bed, no matter how easy they are to grow. Grow what you cannot reliably get, or what costs more than you want to pay, or what tastes so much better fresh that the store version stops counting as the same food. That last category is smaller than the catalogs claim and realer than skeptics think. Nearly everyone who has eaten a homegrown tomato in season puts tomatoes in it.

Once you have the log, you can build the short list, and I mean short. Take every vegetable that appeared more than twice in your week, plus at most two that you eat less often but love when you do. For each one, write a single line in a notebook: the vegetable, the meal or recipe it belongs to, how often that meal happens, whether it is eaten fresh or needs freezing, canning, drying, or root-cellar storage, and how much work it is at harvest. Then mark each one keep, trial, or defer. Keep means it goes in the main beds. Trial means it gets a deliberately small patch, a corner or one bed end, because you have never grown it and one season should not bet the garden on it. Defer means not this year, and no guilt attaches. The defer pile is a sign of good planning, not cowardice.

That harvest column matters more than beginners expect, because it is where the plate meets the calendar. A fresh-use crop and a storage crop are not the same commitment. Cut-and-come-again greens give you something to pick twice a week and eat that night, and if you skip picking for ten days because work was heavy, you lose some quality but the system survives. A crop meant for freezing or canning is different. The peas all come in a window of about two weeks, and every pound you do not shell and blanch and bag in that window is compost. Last summer a renter I know, two raised beds and a demanding job, grew a beautiful row of shell peas with no processing session on the calendar. Her freezer was small, her evenings were short, and the peas went from prize to problem in about nine days. The garden did not fail. The plan did, by asking for kitchen labor that the household had not actually scheduled.

For harvest timing and spacing, find the extension planting guide for your region rather than trusting a number printed on a national seed packet. Most states and many counties publish one, and the good ones give planting windows and days-to-harvest figures tied to their own climate, which you should read as estimates, not promises. A radish listed around thirty days and a potato around a hundred and twenty five are in different categories of commitment, and a first-year gardener should know that before drawing the bed. Your local figures will differ from your neighbor's and even from one end of your yard to the other.

One more thing, and it is the part people want to skip. Start a second page in the same notebook now, before any seed arrives: what you planted, and then, all season, what got eaten, what got given away, what got lost, what got stored, and what you still bought anyway. Simple counts, not a weighed and costed ledger, unless you enjoy that sort of thing. I have seen a lot of first gardens end in a November shrug, and the shrug is usually a failure of records rather than a failure of the garden. The zucchini that everyone took from you by the bag was a success, and without the page you will remember only the mildew.

Here is my working definition, and you can adopt it or argue with it. A first garden succeeds if, by the following December, you can name the meals it supplied, the purchases it replaced or reduced, and one thing you learned about how your particular plot behaves. Not self-sufficiency. Not a grocery bill of zero. Most first gardens, even good ones, will not come close to replacing the vegetable aisle, and the ones that claim to usually have a hidden cost in hours that nobody printed. Your log from this December is the demand side of a small production system. Read it again before you circle anything in the catalog, and check the drawer before you order the greens.

The seed catalogs arrive in December because December is when hope is cheapest. A catalog page can put kohlrabi, bok choy, and four kinds of escarole in front of a person who has eaten none of them since the Clinton administration, and by the fire, in the dark, ordering feels like competence. I have watched this happen at kitchen tables. I have done it at my own. The order arrives in March, the packets go in a shoebox, and by July the escarole has bolted into something bitter that nobody in the house will touch. The money lost is small. The bed space is not.

So before you circle anything, take the demand log you wrote last week and do something unglamorous with it: cut it down. A first-year crop list should be short enough that you can name every crop on it without looking, and specific enough that each one has a meal attached. I will not give you a magic number of crops, because there is no research that supports one and because the honest answer depends on your plot, your schedule, and how many evenings you actually have. What I can tell you is where beginners go wrong. They choose too many crops, and then in July, when the tomatoes need tying and the green beans need picking and something is eating the cabbage, they cannot give each crop the ten minutes it needs. The garden does not fail from ignorance. It fails from a July that was planned in December by a person who had not yet met July.

Here is the method I teach, and it fits on one notebook page. For each candidate crop, write a single line with five things on it. First, the meal or recipe that uses it, named specifically, not "salads" in general but "the Tuesday salad" or "the soup we make when the carrots run out." Second, how often that meal happens in an ordinary week, using your log, not your intentions. Third, roughly how much bed space it would need, which you will get from your regional extension planting guide, since spacing is local business and a Virginia figure will lie to you in Colorado. Fourth, whether it is a fresh-eating crop or a storage-and-processing crop, a distinction I will come back to because it carries more weight than people expect. Fifth, the work it demands at harvest, which includes picking frequency and anything that happens after picking. Then, at the end of the line, one word: keep, trial, or defer.

Keep means the household eats it regularly, you have some idea how to cook it, and it fits the space and time you have. Trial means you want to learn it, and you plant a deliberately small amount, enough to judge but not enough to be buried by. Defer means it goes back on the shelf for a year or two, with no shame attached. Defer is not a rejection of the crop. It is a scheduling decision, the same one a competent manager makes when the work order has more jobs than the crew.

*Figure 1.1. A crop earns its place by fitting both the household and the season. When the answer is uncertain, make the commitment smaller.* Let me show you the arithmetic with a household I know through the food-access program, a renter with two raised beds, a job with fixed weekday hours, and a freezer she stocked with peas in a good sale last June. Her demand log showed fresh tomatoes in some form nearly every summer week, salad greens bought most weeks and often spoiled before they were finished, and carrots appearing in soup twice. The peas she already owned were not garden demand. They were supply, the same as if a neighbor had given them to her, and planting peas would have meant producing a vegetable she had already paid for. Her keep list came out to tomatoes, salad greens, and carrots. Her trial was one hill of zucchini, which is the classic beginner's first humbling crop and cheap to learn from. Everything else, including the peppers she half-wanted, got deferred. That is a first-year range: three keeps, one trial, in two beds. If that sounds stingy, remember that each crop adds a separate set of unfamiliar decisions, and unfamiliar decisions are slow. The zucchini alone taught her about squash bugs, harvesting young, and what to do with a vegetable that produces faster than one person can eat it. A fifth and sixth crop would have taught her less about each and more about her own fatigue.

Notice that the peas got left off, and notice why. Food you already have from the freezer, the pantry, a community garden, a farmers market, or an assistance program is dependable supply. It is not evidence that you are wasting garden space by failing to grow it. I have watched people apologize for buying winter squash at the market while standing next to a garden that produced their entire tomato supply. The garden does not have to do everything to be doing its job. It has to cover the things you actually use and cannot easily get, or cannot get at a quality worth the price.

Now the distinction I promised, because it decides more first gardens than any growing technique. Some crops are eaten fresh, close to the moment of picking, and their only after-harvest work is a rinse. Lettuce is the pure example. Some crops are storage or processing crops: their value depends on keeping them, freezing them, drying them, or standing over a canner with them. Onions, garlic, winter squash, potatoes, drying beans, and paste tomatoes all live in this second country, and the second country bills you later.

The bill is not the same for everyone, which is why I cannot tell you one category is easier. A household with a big chest freezer, an August Saturday it can plan in advance, and a tolerance for batch work will find freezing chopped peppers to be an ordinary chore. A household with an apartment fridge's small freezer compartment and two young children will find the same harvest sitting in the crisper drawer turning to leather. Canning is a further step, and it is the one place where I draw a hard line: use only a tested recipe from a current, reputable source, and do not accept a neighbor's shortcut as heritage. Botulism does not care about anyone's grandmother. If a storage or processing crop makes your list, the processing session has to be on the calendar the way the planting is, because a fifty-pound squash harvest with no plan is not a yield. It is a chore with a deadline.

So when you write your one line per crop, be honest in that fifth column. A paste tomato is not one decision. It is two: grow it, and then spend an August afternoon turning it into sauce. If the second decision has no realistic answer, the crop is deferred regardless of how well it grows, and here is the uncomfortable part. It might grow beautifully. A high yield per square foot is worthless to a household that cannot or will not use it when it arrives. The seed catalog never prints this. The seed catalog prints weight.

On the subject of trials, keep them small and keep them defined. I mean a specific area, written down, that you are willing to lose entirely. One hill of something, or a short row, or a square meter. There is a real chance a trial produces nothing worth judging, too little to eat and too little to learn from, and if that happens, write down what the conditions were before you conclude anything about the crop. One bad season in one bed is not a verdict. It is one data point with weather attached. I once wrote off rutabaga for six years because of a trial I later realized had been planted in the shadiest corner of a community plot, next to a fence, in a summer with a long dry spell. The rutabaga did not fail. I had failed to give it a fair trial and then blamed it for my site.

For your space and timing figures, go to your local extension service or your regional equivalent, and use its numbers as estimates, not promises. Guides typically list something like thirty days to harvest for radishes, sixty for beets, well over a hundred for potatoes, but those figures describe the guide's growing context, and your variety, your weather, and your soil will move them. I have had the same beet variety take seven weeks in one bed and ten in another, in the same yard. The point of looking up timing is not prediction. It is comparison, so that you can see which crops will occupy a bed all season and which will clear out in time for something else, and so that you do not plant your whole range of one long-season crop and find yourself with nothing to eat in June.

Draw the keep line where the honest numbers put it, not where ambition does. If your list runs to eight keeps, ask which three or four supply the most meals and defer the rest; a second year is a real thing, and it is easier to add crops than to recover from a season that got away from you. Leave a defined trial patch, size it to what you can afford to lose, and treat its results as provisional. And write keep, trial, or defer in the notebook itself, not in your head, because by February you will have forgotten your reasons and the catalog will still be on the table, still cheap, still selling July to a person sitting in the dark.

The question that undoes more first gardens than any pest is deceptively simple: how will you know whether this worked? Most beginners cannot answer it, because the answer they are carrying around was never theirs to begin with. It came from a seed catalog cover, or a magazine photograph of a cellar stacked with jars, or a relative who gardened in a different decade on different land with a spouse home all afternoon. The inherited answer is self-sufficiency. Grow enough to stop buying vegetables. Fill the freezer, stock the shelf, get ahead of the grocery store. It sounds modest when you say it fast. It is not modest. It is a production target that a quarter-acre of borrowed yard, a person with a job, and one growing season cannot reasonably hit, and the failure is then billed to the gardener rather than to the target.

I want to talk you out of that number and give you a better one.

Here is the arithmetic that self-sufficiency quietly assumes. A household of two or three adults eating vegetables at ordinary rates goes through a substantial quantity across a year, far more than most people estimate, because the estimate is usually made in January when the memory of a full summer garden is vivid and the memory of a full winter grocery cart is not. Covering that demand from your own plot means producing volume through the whole season, which requires successions, storage crops, and preservation work in August, which is also when vacations happen, when zucchini needs picking every other day, and when the tomatoes you planned to can all arrive in the same ten days whether or not you have those days. Then you need storage that actually works: a cool dry place for onions and winter squash, a freezer with spare capacity, jars, lids, a pressure canner if low-acid vegetables are on the list, and the knowledge to use all of it safely. Each of those carries a real cost, whether the bill comes in dollars or in hours, and none of it shows up in the photograph of the finished pantry.

I am not saying storage and preserving are a bad idea. Later chapters treat freezing and canning as real skills with real rules, and I will tell you plainly when a shortcut is unsafe. I am saying that a first season is the wrong place to attempt the whole chain. The chain has too many links that can fail independently: the crop has to grow, has to arrive when you have time, has to survive the harvest in usable condition, and has to be processed correctly enough that it is still food in February. A beginner who succeeds at three of those four has done well. A beginner who was promised all four and got three will read the season as a failure, stop keeping records, and buy tomatoes at the store forever with a story about how gardening did not work out. The story is wrong. The measuring stick was.

So set the stick before you order seeds, in December or early January, while the plan is still pencil.

The measure I recommend is meals. Not pounds, not dollars saved, not jars lined up on a shelf for a photograph. Meals. Pick a number that would satisfy you and write it down with the date beside it. For a first garden with a small plot, the honest range is something like ten to thirty meals over the season that include vegetables you grew, cooked the way your household actually cooks. That is a modest number. It is also reachable, and a reached target teaches you more than a missed one, because you will finish the season with a record you trust instead of a story you are defending.

Ten meals might sound small enough to be pointless. Run it against the plate. A dinner with your own lettuce, the first radishes, and a side of roasted beets is one meal. A September pasta sauce made from your tomatoes, even if the onions came from the store, is one meal. A stir-fry built around your snap peas in June is one. Thirty such meals across a season is a vegetable at your table roughly twice a week from June through October, which is, incidentally, close to what most small plots can supply well without becoming a second job. The number is not a concession to weakness. It is a description of what a bed or two actually produces when the harvest windows are honest.

Some households will want a second measure, and a good one exists: purchases reduced. Not eliminated, reduced. If your audit from earlier in this chapter showed salad greens bought most weeks and often spoiling in the drawer, then a bed of cut-and-come-again lettuce that replaces even half those purchases from May through July is a real result you can point to. If you bought tomatoes every week of August last year and grow enough this year to buy them every other week, that is a result. I would rather you count that than pretend the garden covered the produce aisle.

A third measure belongs to the trial patch, and it is different in kind: a crop learned. The point of the small trial area was never to feed anyone. It was to find out whether a particular vegetable fits your ground, your schedule, and your kitchen. A trial that yields two puny heads of something is not a failed trial if the record tells you why. Maybe the variety wanted more heat than your site gives it. Maybe it needed a harvest window you do not have on Tuesdays. Maybe nobody in the house wanted to eat it twice, which is a kitchen result, not a garden result, and it is worth exactly as much as a good yield. Write the outcome and the conditions down. One bad season is not a verdict on a crop; it is one data point, and next year it makes you a better planner.

What I want you to refuse is the word "enough," used without a referent. Enough food for what? I have sat in a lot of county workshops, and when I ask a new gardener what success looks like, that word comes up constantly, and it always means the photograph. Enough to not need the store. Enough to be secure. There is real feeling behind it, especially in households where the grocery bill is the flexible one, the one that bends when the rent does not. I take that feeling seriously. But the feeling does the household no favors when it is converted into a plan that cannot survive contact with a job, a heat wave, or a week of rain that splits the tomatoes. A garden that reliably puts a vegetable on the table twice a week through the summer, and teaches you two crops you will grow better next year, is doing work for that household. It is not doing all the work, and nothing about a raised bed obliges it to.

There is a trap on the other side too, and I should name it. A modest target can become an excuse for a garden nobody plans at all, the kind that gets planted in May from whatever the hardware store had left, weeded twice, and abandoned in July. The measure is not a way to lower the bar. It is a way to aim. Ten meals do not happen by accident; they happen because in January you chose crops the household eats, matched them to the space and the hours you actually have, and put the harvest work on the calendar next to the growing work. The number is small. The decisions behind it are not.

Write the target in the notebook now, in December, with the meal audit beside it. Something like: "This year counts if we eat thirty meals with our own vegetables, cut our salad purchases in half through June and July, and learn whether endive belongs on next year's list." Then add the second half of the measure, which most people skip: record what actually happens, all season, in the same notebook. Simple counts, not a scale. Meals with garden vegetables, tick marks. Bags of greens given to the neighbor, noted. The row of beans that got away from you during the week your mother was in the hospital, written down as lost with the reason, because that reason matters more than the loss. What you still bought, noted when you notice it. What came out of the freezer versus what went in.

That record is the only honest way to answer the question you will ask yourself next November, which is whether the garden was worth it. If you wait until November to reconstruct the answer from memory, you will get the photograph again: the one good tomato sandwich, the day the sun came out. The notebook gives you the ledger instead, and the ledger is almost always kinder and more useful. It shows the twenty-two meals, not the imagined fifty. It shows that the lettuce worked and the broccoli did not, and that the broccoli did not because of shade from the neighbor's maple, which is a fact you can act on. It shows that you gave away more zucchini than you ate, which next year becomes a decision to plant one hill instead of three. Self-sufficiency is judged on a scale you did not build, and it usually fails. A ledger is judged against your own declared target, and it gives you something better than a pass or fail. It gives you next year's plan, already half written, sitting there in a notebook that cost less than a packet of seed.

So this is where the planning ends and the waiting begins. You have a week of meals on paper, a short list marked keep, trial, and defer, a trial patch sized to what you can lose without resentment, and a number of meals written at the top of a page. Put the notebook somewhere you will find it in March, when the catalogs arrive glossy and confident and full of vegetables nobody in your house has eaten since 2019. The catalog is selling July. You are buying a season. They are not the same product, and by next winter you will know exactly what you paid for.