I was sitting in my car in a Target parking lot at two o’clock on a Saturday afternoon, crying.
Not the dignified, single-tear-rolling-down-the-cheek kind of crying. The ugly kind. The kind where you’re grateful for tinted windows and hope no one walking past with their shopping cart notices.
I’d spent the morning writing. Three hours of solid, uninterrupted time—the kind of time I’d been telling myself I needed to make real progress on my manuscript. My family was out. The house was quiet. I had coffee and focus and every condition I’d identified as necessary for good writing.
And I’d written garbage.
Worse than garbage. Forced, lifeless sentences that sounded like a corporate memo had a baby with a self-help book. Nothing I wrote captured what I actually wanted to say. Nothing felt authentic or interesting or worth anyone’s time to read.
After three hours, I had two pages. Two terrible pages that I’d probably delete anyway.
This was month three of working on my first book. I’d started with enthusiasm and a clear vision. I was going to write about productivity and time management for writers, drawing from my corporate experience analyzing processes and systems. It felt like a natural fit. I had expertise. I had a perspective. I had a plan.
But somewhere between the plan and the actual writing, everything had gone wrong.
The writing felt mechanical. I was explaining concepts I understood intellectually, but the words on the page had no life. No personality. No connection to anything real.
And the progress was agonizingly slow. Three months in, I had maybe fifteen thousand words. At this rate, finishing a book would take two years. Maybe more.
I’d left Target without buying anything—I’d gone there just to get out of the house after that brutal writing session—and now I was sitting in my car, having what I can only describe as an existential crisis about writing.
The thought that kept circling was simple and devastating: I don’t think I can do this.
Not “I don’t think I can do this today.” Not “I don’t think I can do this right now.”
I don’t think I can do this at all.
Maybe I wasn’t meant to be a writer. Maybe having expertise in a topic wasn’t enough. Maybe the gap between understanding something and being able to write about it in a way that actually mattered was wider than I could cross.
I sat there for twenty minutes, seriously considering just deleting the entire manuscript and going back to only doing the work I knew I could do well—corporate analysis, process documentation, strategic planning. Work that felt competent and valuable and not like pulling teeth.
Then my phone rang.
The Call That Changed Everything
It was my friend Rachel. We’d worked together years ago, and she’d moved to a different city but we still talked every few weeks.
“Hey, what are you up to?” she asked.
I considered lying. Saying I was running errands, everything was fine. But I was too emotionally raw to manufacture normal conversation.
“I’m sitting in a parking lot questioning all my life choices,” I said.
“Oh good, a normal Saturday. What happened?”
I told her about the morning. The three hours of writing that produced nothing good. The growing sense that I’d made a terrible mistake thinking I could write a book. The feeling that every writing session was getting harder instead of easier.
“How much have you written so far?” she asked.
“About fifteen thousand words over three months.”
“That’s actually pretty good.”
I almost laughed. “Rachel, at this rate, it’ll take me two years to finish a first draft. And it’s all terrible anyway.”
“Okay, two questions,” she said. “First, have you reread any of what you wrote in month one?”
I hadn’t. I’d been pushing forward, trying to generate new content, not looking back.
“Do that,” she said. “I bet it’s better than you think. Second question: do you remember that supply chain analysis project you did for the manufacturing company? The one that took you six months?”
I remembered. It had been a complex, frustrating project analyzing workflow inefficiencies across three facilities.
“How did you feel three months into that project?” Rachel asked.
The memory hit me immediately. Three months into that project, I’d felt completely overwhelmed. The data wasn’t making sense. Every facility had different systems. I couldn’t see the pattern yet, and I’d started wondering if I’d bitten off more than I could handle.
“I felt lost,” I said.
“Right. And what happened?”
“I kept working on it. And around month four, things started clicking. I saw the patterns. The analysis came together.”
“So why,” Rachel asked, “are you expecting your first book to be different? Why are you expecting month three to feel easy and clear when literally every other complex project you’ve done has had a messy middle?”
I sat there in my car, phone pressed to my ear, and realized I’d been applying completely different standards to writing than I applied to any other kind of work.
When corporate projects felt difficult at the three-month mark, I knew that was normal. I trusted the process. I kept working because I understood that complex work requires time to develop clarity.
But with writing, I’d expected immediate competence. I’d expected the work to feel good and flow easily, and when it didn’t, I interpreted that as a sign I wasn’t meant to do it.
“You’re three months into learning how to do something you’ve never done before,” Rachel said. “Of course it feels hard. That doesn’t mean you’re bad at it. It means you’re learning.”
The Realization About Hard Work
After I got off the phone with Rachel, I sat in that parking lot for another ten minutes, thinking about how I’d approached different kinds of difficult work in my life.
In corporate consulting, when I took on a challenging analysis project, I expected the first few months to be difficult. I expected confusion, false starts, dead ends, and gradual clarity. That was just how complex analytical work unfolded.
When I started learning data visualization software a few years earlier, I expected the first three months to be frustrating. I expected to make mistakes, create ugly charts, and slowly improve. That was how learning new technical skills worked.
But with writing, I’d unconsciously expected something different. I’d expected that because I could think clearly and had something to say, the writing would flow naturally. When it didn’t—when it felt hard and clunky and uncertain—I interpreted that difficulty as a sign I lacked talent or wasn’t meant to be a writer.
This was completely irrational, and I hadn’t even noticed I was doing it.
Writing is a skill. Like analysis, like data visualization, like any other complex skill I’d learned. And skills are hard when you’re learning them. That’s not a bug. That’s the process.
The difficulty wasn’t a sign I should quit. It was a sign I was in the learning phase.
That realization shifted something fundamental. The hard feelings—the frustration, the sense that I wasn’t good enough, the doubt about whether I could do this—those weren’t messages from the universe telling me to stop. Those were just the normal, predictable feelings that accompany learning something difficult.
I’d felt those exact same feelings three months into learning data visualization. And I’d pushed through them, and eventually got good at it. Not because I had special talent, but because I kept practicing.
Writing was the same. I just needed to stop treating it differently.
What I Found When I Looked Back
That evening, I followed Rachel’s advice. I opened my manuscript and read what I’d written in the first month.
I expected it to be terrible. I was preparing myself to confirm my worst fear—that all of it was bad and I’d wasted three months.
Instead, I found something surprising. Some of it was rough, yes. But it wasn’t all bad.
There were paragraphs that worked. Sections where my actual voice came through. Moments where I’d explained something clearly or told a story that landed.
It wasn’t polished. It wasn’t ready for publication. But it was better than garbage.
More importantly, when I compared the writing from month one to what I’d written that morning, I could see improvement. The recent writing was rougher in some ways, but also more confident. I was trying harder things—more complex ideas, more personal stories. The writing felt forced because I was pushing beyond my current skill level, not because I was getting worse.
I’d been judging my month-three writing against published books I admired—books that had gone through multiple drafts, professional editing, and years of development.
That comparison was insane. I wasn’t comparing apples to apples. I was comparing my first-draft, still-learning work to other people’s polished final products.
When I compared my writing to itself—month one to month three—I could see growth. Not dramatic transformation, but steady improvement. I was learning.
That evidence mattered more than my feelings about how the work was going.
The Perspective Shift
The next day, I did something I’d been avoiding. I looked at my original timeline for the book.
I’d estimated it would take me six months to write the first draft, working about five hours per week. Simple math: if I could write a thousand words per hour, five hours a week for six months would give me a complete draft.
This timeline had been completely arbitrary. I’d made it up based on nothing—no experience writing books, no understanding of my actual writing pace, no accounting for the learning curve.
But once I’d set that timeline, it became the standard against which I measured my progress. And when my actual progress didn’t match my imaginary timeline, I concluded I was failing.
The timeline was the problem, not my writing.
I opened a spreadsheet—because of course I did—and tracked my actual writing pace over the three months. On average, I was writing about twelve hundred words per week. Some weeks more, some less, but that was the average.
At that pace, a seventy-thousand-word book would take just over a year to draft. Not six months. A year.
That timeline felt long. But it also felt accurate. Based on actual data instead of wishful thinking.
And here’s what changed when I adjusted my expectations: the pressure disappeared.
I wasn’t behind. I wasn’t failing. I was progressing at exactly the rate I was progressing. Judging that rate as too slow was pointless—it was the rate that was happening given my current skill level, available time, and life circumstances.
I could either accept that rate and keep writing, or quit. Those were the only options.
Wishing for a faster rate while beating myself up for not achieving it wasn’t a strategy. It was just self-torture.
The Question That Clarified Everything
A few days later, I was talking to my sister about the parking lot breakdown. She listened to the whole story, then asked a question that cut through everything:
“Do you actually want to write this book, or do you just want to have written it?”
I started to answer automatically—of course I wanted to write it—but she stopped me.
“Really think about it,” she said. “Because those are different things. If you want to have written a book—the finished product, the achievement, the ability to say you’re an author—but you don’t actually want to do the work of writing, then yeah, quit. It’s not worth being miserable for a year to get a result you don’t really care about. But if you actually want to write—if you like the process, even when it’s hard—then keep going.”
I thought about it honestly. Did I like writing?
Not the fantasy version of writing where words flowed effortlessly and every session felt inspired. The actual version. The version where I sat down most mornings and struggled to get words out. Where I wrote things that didn’t work and had to revise them. Where progress was slow and uncertain.
Did I like that?
The answer surprised me. Yes. Even on the hard days, even when nothing I wrote felt good, there was something satisfying about the process. About taking vague ideas and forcing them into concrete sentences. About the puzzle of finding the right words for what I wanted to say.
I liked thinking through writing. I liked the moments when a paragraph suddenly clicked together. I liked having written something—even something rough—more than I liked having an empty page.
I didn’t love every minute of writing. But I liked it enough to keep doing it.
That was the bar. Not “do I love this ecstatically every moment?” Just “do I like it enough to keep showing up?”
Yes.
What Changed After the Parking Lot
I wish I could say that after that day, writing became easy. It didn’t.
I still had hard sessions. I still wrote things that didn’t work. I still had days when I questioned whether anything I was writing mattered.
But I stopped interpreting those hard days as signs I should quit.
Hard days were just hard days. They were part of the process, not evidence that I was on the wrong path.
I adjusted my timeline based on my actual writing pace. I stopped comparing my first draft to published books. I gave myself permission to be exactly as good as I currently was—which was better than I’d been three months earlier but not as good as I’d be three months later.
Most importantly, I separated the question “Is this hard?” from the question “Should I quit?”
Yes, it was hard. That didn’t mean I should quit. It meant I was doing something difficult worth learning.
I kept writing. Some days five hundred words. Some days two thousand. Slow, imperfect progress that accumulated over time.
Eleven months after the parking lot breakdown, I finished the first draft of that book. It wasn’t polished. It needed extensive revision. But it was complete.
I’d written a book. Not because I was talented or because it came naturally. Because I didn’t quit on the day I wanted to.
Why Most People Quit
Looking back, I understand why that moment in the parking lot was so dangerous. It was the perfect storm of conditions that make people quit:
I was far enough in to have invested significant time, but not far enough to see results. Three months of work with no finished product. Just a messy, incomplete draft that didn’t look like anything yet.
I was in the difficult middle where initial enthusiasm had worn off but competence hadn’t developed yet. The gap between my vision for the work and my current ability to execute was painfully obvious.
I was judging my process by arbitrary standards that had nothing to do with reality. The six-month timeline I’d invented. The comparison to published authors. The expectation that it should feel easier by now.
And I was alone with those feelings, interpreting them as unique to me instead of universal to the process.
If Rachel hadn’t called when she did, I might have deleted that manuscript. Not because it was unsalvageable, but because I’d convinced myself that difficulty meant failure.
That’s what makes quitting so seductive in these moments. It promises relief from the discomfort of not being good enough yet. And that relief is real—if you quit, you stop feeling inadequate at writing.
But you also stop writing. And if writing is something you actually want to do, that relief comes at a cost you’ll regret later.
The Difference Between Quitting and Pivoting
I’m not arguing you should never quit anything. Sometimes quitting is the right decision.
If you genuinely don’t enjoy writing—if it feels like obligation with no satisfaction—quit. Life is too short to force yourself through creative work you actively dislike.
If you have concrete evidence that writing isn’t serving your larger goals, pivot to something else.
But most people who quit writing don’t quit because they’ve thoughtfully evaluated their goals and decided writing doesn’t fit. They quit because they hit the hard middle, felt discouraged, and interpreted that discouragement as a sign they shouldn’t continue.
That was almost me. I was about to quit not because writing wasn’t working, but because it was working exactly how learning a new skill works—slowly, imperfectly, with a steep learning curve.
The question isn’t “Is this hard?” The question is “Given that this is hard, do I still want to do it?”
If the answer is yes, the hardness isn’t a problem to solve. It’s just a condition to accept.
What I Learned About Staying
The parking lot moment taught me something crucial about creative work: you don’t quit on your worst day.
On your worst day, everything feels impossible. Your work feels worthless. Your progress feels inadequate. Your doubt feels like truth.
But worst days lie. They’re real in terms of how they feel, but they’re not accurate assessments of your work or your potential.
You make decisions about whether to continue on your average days. Days when you can see both the difficulty and the progress. Days when you’re not in crisis mode.
That Saturday in the parking lot was my worst day. Nothing about my assessment of my writing that day was reliable. I was tired, frustrated, and viewing everything through the lens of discouragement.
The decision to keep writing needed to come from a clearer place. Which is why I’m grateful for Rachel’s call, for the perspective shift that followed, and for the fact that I didn’t act on that worst-day impulse to quit.
I stayed. Not because it was easy or because I was sure it would work out. I stayed because I wanted to write more than I wanted to avoid the discomfort of learning.
That was enough.
Three months into your first manuscript is too early to know if you can do this. Three months is still the learning phase. Still the hard middle. Still the part where it’s supposed to feel difficult.
If you’re there right now—sitting in your metaphorical parking lot, wondering if you should quit—here’s what I’d tell you:
Don’t decide today. Your feelings today are real, but they’re not the whole picture. Look at your actual progress, not your imagined timeline. Compare your work to where you started, not to where you wish you were.
And ask yourself the question my sister asked me: Do you actually want to write, or do you just want to have written?
If you want to write—even when it’s hard, even when it’s slow—then stay.
The parking lot moment passes. The doubt fades. The work continues.
And a year from now, you’ll be grateful you didn’t quit on your worst day.



