Watch the series →

Stories from the hustle — composite, dramatized, and not financial advice. What this is.

The Meeting Ran Long and the Dash Window Closed

It was a Tuesday, around 4:15 in the afternoon, and I was already in my car. Not driving anywhere — just sitting in the driveway with the DoorDash app open, engine running, watching the little heat-map pulse orange over the dinner rush zone on the east side. I had a window. I had gas. I had exactly the kind of low-stakes momentum that makes you feel like you've got your life organized for once.

Then my laptop pinged. Slack message from Marcus, the team lead: "Hey, can we pull the sprint review up? Product wants to join and they're only free at 4:30." Which — fine, that's how it goes. Except "sprint review" with product in the room is never forty-five minutes. It's a hostage situation with a shared screen.

I cut the engine. Walked back inside. Opened the laptop on the kitchen counter because my desk chair was buried under a pile of clean laundry I'd been meaning to deal with since Saturday. The app stayed open on my phone, face-up on the counter, the orange zone slowly cooling to yellow while I talked about story points.

Find the Right Professional for Your Business

Explore trusted resources and connect with professionals in finance, legal, HR, marketing, technology and other key areas of your business.

Learn more

How a Sprint Review Ended Up on the DoorDash Ledger

The thing about dashing after work hours is that it only really works if you can actually leave at the end of work hours. Remote jobs sell you on flexibility, and that part is real — I'm not commuting, I'm not wearing pants with a button, I ate leftover wings at 2pm and nobody said a word. But the flip side is that the day doesn't have hard edges. A meeting that "shouldn't run long" runs long. A quick Slack thread turns into a voice call. A deploy that was supposed to go out at three is still being argued about at five-thirty.

I've written about a deploy eating a dash window before, and I thought I'd learned something from that. I had a whole theory: only commit to a dash window if you're past the last scheduled meeting of the day. Buffer time. Don't trust "this'll be quick." I was pretty pleased with that theory. I told John about it. He nodded like it was obvious and then told me about a documentary he'd been watching about the Federal Reserve.

The sprint review was the last scheduled meeting. That was the whole plan. Product joining last-minute was the variable I hadn't accounted for, which is either a planning failure or just Tuesday. I genuinely don't know which.

Ninety Minutes of Velocity Discussion While the Orange Zone Went Gray

The meeting went an hour and thirty-two minutes. I know because my phone was face-up on the counter the whole time and I kept glancing at it the way you glance at a parking meter you know has already expired. The DoorDash heat map had gone from orange to yellow to the kind of pale beige that means everyone in that zone has already eaten and gone to bed.

Product had questions about two tickets that weren't even in this sprint. We answered them anyway. Then there was a side conversation about whether the definition of "done" included QA sign-off, which is a real and important question that I did not need answered at 5:47 on a Tuesday while my car sat in the driveway getting cold.

My oldest walked through the kitchen about an hour in, looked at me hunched over the laptop, looked at the phone on the counter, and said:

"I thought you were going to be dashing tonight."

"I am," I said. "In theory."

She gave me the look kids give you when they've caught you in something and are choosing not to press it, and went back to whatever she was doing. I respect that move. I've tried to learn it myself.

By the time the call ended it was 5:53. I'd missed the dinner rush entirely. I opened the app anyway, stared at the gray map for about ninety seconds, and closed it. There's a version of this story where I go out anyway and grind through the slow stretch, but I'd been on calls since nine in the morning and the honest answer is I didn't have it. I heated up some leftover rice and watched something on Netflix that I couldn't describe to you now if you paid me.

Thirty-Eight Dollars I'd Already Spent in My Head

I want to be careful here because I don't actually know what I would have made. The dinner rush on a good Tuesday might run me thirty, thirty-five, maybe thirty-eight dollars over two hours if the orders are stacking and I'm not stuck behind a train on Troy Highway. That's not a guarantee — it's a guess, and I've had Tuesday nights that paid twenty-two dollars for the same stretch of time and left me smelling like a Thai restaurant.

But I'd mentally spent it. I had a specific grocery run in my head. The good ground beef, not the stuff I usually buy. A six-pack of something decent. Maybe the fancy chips. That's the real cost — not the abstract lost revenue, but the moment you realize the grocery list in your head was never funded and you're back to the regular stuff.

The day job paid, obviously. It always pays. The floor is the floor. But the floor doesn't cover the good ground beef, which is the whole reason the dashing exists in the first place. This is the math that doesn't show up in any productivity blog post I've ever read. The overlap between work hours and hustle hours is the thing nobody really talks about — you can optimize all you want, but you can't optimize a product manager who just remembered a question.

I also lost the gas I'd burned idling in the driveway for ten minutes before Marcus messaged me. That's probably a dollar fifty. I'm not above counting a dollar fifty.

The Rule I Rewrote and Will Probably Break Again

The updated theory — which I fully acknowledge is just the same theory with more caveats stapled to it — is that last-scheduled-meeting is not the same as last-possible-meeting. Product can always join. Someone in a European time zone can always have "one quick thing." The meeting is never as done as the calendar says it is.

So now I'm trying to only commit to a window that starts at least thirty minutes after the last calendar block. Not fifteen. Thirty. And even then I hold it loosely, because I've been wrong about rules before — I've been wrong about more of my own rules than I'd like to admit, and the ones about time management are the worst offenders.

The other thing I've started doing, when a meeting runs long and I miss a window, is opening the survey apps instead. It's not the same money — not even close — but it's something to do with the frustration. Sitting there clicking through a ten-minute survey that pays eight dollars while the sprint retro runs over feels appropriately absurd in a way that at least keeps me from just doom-scrolling. Small wins. Tiny ones. Whatever.

I didn't change anything about the day job. I wouldn't. The sprint review process is fine — product should be in those meetings, the questions were legitimate, Marcus was right to move it up. I'm not actually mad about any of it. I'm just a guy who sat in his driveway for ten minutes and then didn't go anywhere.

The good ground beef stayed at the store. I made the regular stuff with some cumin and called it a win. It was fine. Everything was fine. The orange zone will be back Thursday.

Note: Everyday Hustle Jeff is the written side of a digital series. These accounts are composite and dramatized. Any figures are what they were on the day, for one person, and are not a projection, a track record, or advice.

Seven desks, one guy, a lot of things that did not work.

Start from the top