Cooking, commuting, folding laundry: how to pick audio for a hands-busy hour

The dishes take ten minutes. The commute takes forty. Most people queue audio the same way for both: whatever is next in the feed, regardless of how long it runs or how many times a timer, a doorbell, or a dog will interrupt it. That habit formed when podcasts really were mostly commute audio. It doesn't fit as well now that the biggest chunk of listening has moved somewhere else.

The question worth asking before pressing play isn't only "what show." It's "what fits this specific stretch" — a ten-minute dish-washing window, a forty-minute walk, an hour of cooking a real dinner. Those are different containers, and pouring the same long-form queue into all of them is why some episodes get abandoned halfway and others end just as the good part starts.

None of this is really about which topics work best for chores versus commutes. It's about treating length and timing as choices you make on purpose, stretch by stretch, rather than defaults set once when you subscribed to a feed.

Home is now the bigger listening room than the car

The commute earned its reputation honestly: it's a fixed, undistracted block of time, and for a long stretch of podcasting's history it was the easiest place to build a habit. But Edison Research's own tracking shows that reputation has stopped matching the data. In 2019, 48% of weekly podcast consumers said they most often listened to podcasts at home. That share jumped to 58% in 2020, and Edison's most recent estimate, published in a January 2026 research note, puts it at 63%. The shift outlasted the initial pandemic-era spike that caused it, which is its own signal that something durable changed rather than something temporary rebounding.

A separate Edison measurement, its Share of Ear study, backs this up from another angle. Rather than asking where people say they listen most, it tracks where all daily podcast listening time actually goes. At-home listening accounts for 67% of that time. Work takes 16%. The car — the place popular assumption still treats as prime podcast real estate — accounts for 11%. The remaining 6% is everywhere else: gyms, errands, walking.

Neither number claims the commute stopped being a listening occasion. It says home overtook it by a wide enough margin that designing an audio habit only around the drive misses most of the actual listening day.

Chores already outrank the commute as an occasion

Location data answers where people listen. A 2023 YouGov Profiles survey asked something more specific: what situation people were in. Household chores came out on top — 49% of podcast listeners said they listen while doing chores, the single most common occasion in the survey. Commuting came second, at 42%.

The two aren't mutually exclusive; plenty of people do both on the same day. But the ranking is worth sitting with, because it inverts the assumption baked into most podcast habits. The occasion most associated with podcasts in the public imagination isn't even the most frequently reported one. Chores — cooking, cleaning, laundry, the unglamorous maintenance of a home — generate more listening moments than sitting in traffic.

Why "hands-busy" isn't one moment

Grouping cooking, commuting, and folding laundry under one label — "hands-busy" — hides real differences between them, and those differences are exactly what should shape what gets queued.

A commute has a fixed, known endpoint. Outside of unusual delay, you know within a few minutes when it ends, and almost nothing interrupts it along the way. That combination — bounded length, low interruption risk — is what makes a commute genuinely good ground for a long-form episode that needs fifty uninterrupted minutes to land.

Chores don't share that shape. Washing a sink of dishes might take ten minutes on an ordinary weeknight. Cooking an actual meal, from the first chop to plating, can run thirty to forty-five. Folding one load of laundry is closer to fifteen or twenty. A dog walk lands anywhere from fifteen minutes to nearly an hour, and unlike a drive, it can be cut short by the dog, a phone call, or the weather. Each of these is a different container, with a different chance of getting interrupted partway through — and a forty-five-minute episode doesn't fold the same way into all of them.

This is also where audio's advantage over reading is easiest to see and easiest to waste. With wet hands or a chef's knife mid-task, a printed recipe or an article is out of reach; audio is the one medium that keeps working. That's a separate question from length, though — listening vs. reading a long article covers when audio's flow beats a page you can scan and cite, and when it doesn't. This piece assumes the format decision is already made and focuses on what to do once you've made it: matching how long that audio runs to how long you actually have.

Interruption is the part that's easy to underweight. Losing your place in a dense, evidence-heavy episode costs more than losing your place in something lighter, because picking it back up means re-establishing who's talking, what was already established, and what claim is being built toward — work a commuter rarely has to redo, because a commute so rarely gets cut short mid-sentence. A chore that gets interrupted by a phone call, a kid, or a boiling pot doesn't just pause the episode; it taxes the next few minutes of listening with reorientation. That cost is invisible when you're choosing what to queue and very visible once you're standing at the counter trying to remember what the host was in the middle of explaining.

A rough guide to matching runtime to the stretch

None of this needs to be precise. It just needs to be a live variable rather than an afterthought.

The point of a table like this isn't to make a rule out of it. It's to notice that "how long is this episode" is a question worth asking before pressing play, not something that only becomes obvious in hindsight when the meal is plated and the host is still three segments from the ending.

The more common mistake runs in the direction of overshooting rather than undershooting. It's easy to start a long episode on a short task because the show looked good and the queue was already there, and much harder to notice in the moment that the runtime and the task are mismatched until the dishwasher is loaded and the argument the host is building hasn't gotten anywhere yet. Undershooting is the safer error — a short piece that ends before the chore does just means picking a second one — while a long piece cut off mid-argument tends to get abandoned rather than resumed.

Publishers already treat cooking as its own occasion

The cooking stretch specifically has already been recognized, by people who curate podcasts for a living, as different enough to warrant its own recommendations. Evergreen Podcasts publishes a roundup of shows picked for time at the stove, and the podcast directory Feedspot maintains a list of 35 shows curated for the same occasion, spanning food history, comedy, culture, and storytelling. The specific picks vary, but the existence of the category is itself the evidence: enough people choose differently for cooking than for other listening moments that it's worth a dedicated list.

What these lists mostly optimize for is tone — something that pairs well with chopping and stirring without demanding total attention. What they don't usually address is runtime. A show can be exactly right in subject and mood for the kitchen and still run twice as long as the meal takes to cook, which lands back on the same point: getting the mood right and getting the length right are two separate jobs.

Duration is a design choice, not a default

Other corners of audio have already built formats around this idea deliberately. A morning news briefing commits to a fixed length — often around ten minutes — precisely because it's built for a bounded moment, while a reported news podcast can run twenty minutes or an hour because it isn't. Audio news briefing vs. news podcast goes through that trade-off in more detail, but the underlying lesson travels beyond news: a format's length is usually a deliberate choice by whoever built it, made for a specific kind of moment. There's no reason the same discipline shouldn't apply to a stretch of cooking or a dog walk — it's just less common for the average podcast queue to think in those terms, because most shows are built once and released at whatever length the story took, for whoever happens to be listening.

Most feeds are still built for the drive

Part of why this mismatch persists is that a lot of podcast apps still default to behavior tuned for the commute: autoplay moves straight into the next episode in a feed, "up next" queues assume you'll keep listening until something external stops you, and a show's length is fixed the moment it's published, for every listener and every occasion at once. None of that is a flaw exactly — it's a reasonable default for the moment podcasting was originally built around. But it does mean the adjustment for a shorter or more interruption-prone stretch has to come from the listener, not the app. Nothing in a typical feed asks how much time you actually have before it starts playing.

Choosing the runtime for the next stretch

Everything above points at the same practical shift: instead of building one long queue and letting whatever's next play regardless of the moment, it helps to ask how much time this specific stretch actually has before deciding what to start. That's a habit change more than a technology problem — most existing shows and feeds were never going to solve it on their own, because they're fixed at publication and built for whoever happens to be listening, not for your specific ten minutes.

Lissin is built around that same idea, but from the other direction. Rather than choosing from episodes someone else already recorded at whatever length they chose, you pick a topic, question, mood, or source yourself, and you also choose how long the show runs and when it arrives. A dish-washing stretch and a real commute don't need to draw from the same queue at the same length; they can each get a show sized for the time you actually have. Explore audio on Lissin and decide what your next stretch should sound like.

Sources

• Edison Research, "At-Home Podcast Listening Continues to Climb" for the 2019–2026 trend in listeners reporting they most often listen to podcasts at home (48% to 58% to an estimated 63%).
• Edison Research, "Most Podcast Listening is At Home" for the Share of Ear breakdown of daily podcast listening time by location (67% home, 16% work, 11% car, 6% other).
• YouGov, "Cleaning, commuting and cooking: when do Americans listen to podcasts?" for the 2023 survey finding that household chores (49%) edge out commuting (42%) as the most common podcast-listening occasion.
• Evergreen Podcasts, "Top Five Podcasts to Listen to While Cooking" as evidence that cooking is treated as its own curated listening occasion.
• Feedspot, "35 Best Podcasts To Listen To While Cooking" as further evidence of cooking-specific podcast curation.