--- title: "Is grit the same as resilience for founders? | Len P. van der Hof" description: Grit is sustained commitment. Founder resilience also requires adaptation and recovery. Compare them, then check what you restored after your last hard push. image: "https://lenvanderhof.com/media/generated/blog-hero-resilient-vs-grit.e12bb7f79b2d.wide.webp" --- [Founder Performance](https://lenvanderhof.com/en/blog/category/founder-performance/) Research guide # Resilience vs grit: what founders need beyond persistence Finishing the work shows that you persisted. Before the next promise, check what the push spent, whether the approach still fits, and what you restored. Len P. van der HofPublished 7 November 20269 min read A willow bends towards the river; the branch in front of it has snapped. Direct answer No. Grit concerns sustained interest and perseverance towards long-term goals. In The Psychology of Founder Resilience, founder resilience is an active process of adapting to pressure and restoring the capacity the work spends. Persistence can be part of that process, but continued effort alone shows neither that the approach still fits nor that recovery has happened. ## Key takeaways - Grit concerns commitment over time. The book's founder resilience model also asks how you adapt and what you restore. - Give continued effort a purpose and a boundary: what should another attempt change, and what would make you revise the approach? - Record delivery, adaptation and restoration separately. Finishing the work does not establish all three. - A recovery plan, a completed recovery action and an observed return of capacity are different entries. Write down which one you have. - Audit one hard push and act on the gap today. The exercise reviews one episode; it does not measure your personality or prove a business benefit. **Grit describes sustained commitment to a goal; founder resilience also requires adaptation and restoration.** Finishing difficult work shows that you persisted. It leaves two questions open: does the approach deserve another attempt, and what condition are you in for the decisions that follow? Chapter 2 of [The Psychology of Founder Resilience](https://lenvanderhof.com/books/psychology-of-founder-resilience/) makes those questions central. Its model treats resilience as an active process: read the load, change an approach that no longer fits, and restore the capacity the work spends. The practical test comes after the achievement. Write down what changed and what returned before you promise the same push again. ## Is grit the same as resilience for founders? No. Grit concerns sustained interest and perseverance towards long-term goals. The book’s founder resilience model concerns adaptation and restoration under pressure. Persistence can contribute to that process. By itself, it cannot tell you whether your current method is sound or whether your capacity has returned. Chapter 2 compresses the point into one line: “Persistence without recovery is not resilience.” Its quarrel is not with the grit research but with persistence treated as the whole answer. Popular accounts often turn the research finding into a fixed verdict on who you are, the chapter notes. Persistence does matter: quit at the first resistance and you build nothing. But founder culture, in the chapter’s account, has tied that true point to a dangerous omission, and the omission is recovery. Keep the time scale clear as well. Working late once shows persistence in that episode. It does not show whether you have grit, and no label obliges you to ignore fatigue or refuse help. When reviewing a hard pushWhat persistence showsWhat the book’s resilience model asksYou kept working despite difficulty.Effort continued.Did the effort still serve the goal?You completed the task.The immediate work got done.What did it cost, and should the method change?You are about to make the next commitment.You were willing to keep going last time.What has been restored, and what remains strained? These are questions about how you work. The broader [founder resilience definition](https://lenvanderhof.com/en/blog/what-is-founder-resilience/) introduces the model; this page uses the distinction to review one push. ## What does the grit evidence establish? Chapter 2 cites [Duckworth and colleagues’ 2007 paper](https://doi.org/10.1037/0022-3514.92.6.1087) for a bounded claim: sustained interest and perseverance are linked to some long-term outcomes. The book’s evidence ledger confines the source to that construct and those associations. It does not make grit a complete model of success or a substitute for recovery. That leaves the next decision open. Some problems need more pushing; others need a different approach. Grit taken as a master virtue cannot tell them apart, the chapter argues, while a resilient founder can keep persisting and still notice when persistence has become the wrong instrument. Chapter 2 is candid about its own evidence here too. Founders who sustain strong performance often report being strategic about rest and protective of recovery, but systematic study of that pattern in founder populations remains limited. The word *resilience* needs one qualification. [Bonanno’s 2004 review](https://doi.org/10.1037/0003-066X.59.1.20) treats resilience after loss or potential trauma as a trajectory distinct from the process of recovery. Restoring founder capacity is the book’s operating language; it does not erase that research distinction. [What resilience research found](https://lenvanderhof.com/en/blog/resilience-research-findings/) covers it in detail. For this page, both papers were checked through bibliographic records and abstracts in the book’s source cache. Neither full paper was reviewed. The exercise below applies Chapter 2; it is not a tested intervention from either paper. ## When should you persist, and when should you change the approach? Before extending a push, write what the next attempt is meant to accomplish. Finishing a defined task, collecting missing evidence and repeating an unsuccessful method are different reasons to continue. Give yours a specific result you can inspect. Then name a condition that would change the plan. For a customer pilot, that might be discovering that each new customer needs unpriced manual preparation. More hours could complete the next onboarding while leaving the commercial problem untouched. Continuing to serve the customer and changing what you offer can belong in the same decision. Chapter 2 makes room for that combination: “Admitting a strategy is dead, or taking a day off, is often the resilient act.” You can stay committed to the problem while revising how you solve it. Also write what the extra effort displaces. If the same recovery block moves behind every new request, it has no protected place in the plan. Identify the demand you can remove, the commitment you can renegotiate, or the person whose agreement you need. For the longer-term planning question, [A holiday is not a refill protocol](https://lenvanderhof.com/en/blog/founder-capacity-is-infrastructure/) treats capacity as infrastructure you train and budget. For the immediate decision, give continued effort a purpose, a boundary and a recovery opportunity. Discomfort alone does not settle whether to proceed. Neither does pride in your ability to endure it. ## A worked example: the pilot that hides the cost of the next one **Hypothetical example.** A founder promises a pilot customer an onboarding session on Friday. On Thursday, she discovers that the customer’s data needs five hours of manual cleaning. She cancels that evening’s call with a friend, works until 23:00, and gets the customer started on Friday. Over lunch that day she keeps rehearsing the cleanup problem and loses the thread of the conversation. A second prospect now wants the same pilot. If she records only “pilot delivered,” she has a reason to celebrate but an incomplete basis for the next promise. The cleaning still needs an owner and a price. The cancelled call, the late night and the lost thread at lunch are missing from the delivery record too. A response based only on persistence repeats the offer and assumes she will find the hours again. Applying the book’s resilience model adds two decisions. First, she changes the offer. She will inspect a sample of each prospect’s data and quote preparation separately before committing to a start date. She keeps the goal of serving customers while making the hidden work explicit. Second, she makes room for recovery, matched to what the push drained. Her co-founder agrees to cover routine customer questions over the weekend, with a phone call only for an urgent issue. She stops work at 18:00 on Friday and moves the cancelled call with her friend to Sunday. The cover gives her decision-free hours, which Chapter 2 pairs with executive function. The Sunday call gives her what the chapter says interpersonal support needs: an actual conversation with someone who knows her. On Monday, her review reads: Review lineEntry in this hypothetical caseDeliveredThe first customer started the pilot on Friday.ChangedNo next start date until the data sample is checked; preparation gets a separate scope and price.Recovery actions completedWeekend cover held, Friday work stopped at 18:00, and the Sunday call happened.Return noticed“On Sunday’s call I could follow the conversation without rehearsing the pilot problem. I still feel tired.”Still unresolvedThe next customer’s preparation effort is unknown. Full restoration is not established. That last line matters as much as the first. She has one observation of attention returning during one conversation, alongside a remaining difficulty. She has not proved that the weekend caused a recovery, or that the revised offer will succeed. The example’s hours and days are planning choices. What makes the record useful is that delivery, adaptation and restoration can each be examined. A successful pilot no longer answers for all three. ## What counts as evidence that capacity returned? Start with what you noticed becoming harder. Chapter 2 asks you to match recovery to the capacity under strain, because one input does not restore every reserve. Sleep and movement mainly refill somatic regulation. Interpersonal support needs an actual conversation with someone who knows you. Executive function needs decision-free hours. The book uses refillable reserves as a metaphor, so keep the observation concrete. Keep three entries separate. A booked call is a plan. A completed call is an action. Being able to follow the conversation again is an observation about your experience. Recording all three prevents an intention from becoming a result on paper. For choosing a recovery activity, [Recovery is not a day off](https://lenvanderhof.com/en/blog/recovery-is-not-a-day-off/) develops the matching question. Here, stay with the review: what happened, what seemed to return, and what still feels difficult? A personal observation can guide your next action without proving a cause. “I do not know yet” is a sound entry. So is “the break happened, but I still feel depleted.” Keep the uncertainty visible instead of awarding yourself a resilience score. ## What if recovery is difficult to arrange? Then record the constraint as part of the work. In the pilot example, weekend cover depends on another person having time and agreeing to take it. A solo founder cannot create that cover by putting it in a worksheet. Choose the smallest feasible change: defer an avoidable commitment, reduce the scope of the next promise, or ask for specific help. If agreement is still pending, record it that way. A request for cover is not cover. If nothing can move today, name what prevents it and who can help change it. Keep the recovery need open when you make the next commitment; completing the customer work does not remove it. If executive function or somatic regulation reads empty, Chapter 2’s dashboard rule applies: make no irreversible decisions that day. Chapter 2 explicitly keeps its dashboard outside self-diagnosis and warns against using it to avoid professional support. The same boundary applies here. This review can identify an unmet need or an untested assumption; it cannot diagnose persistent difficulty or certify that another push is safe. ## Try this today Choose the last episode you described as “pushing through.” Give yourself ten minutes, with your calendar or notes beside you. The time limit is a practical choice; the output is one account of the push and one next action. 1. **Name the result.** Write what you completed and when the push ended. “The pilot started on Friday” is more useful than “I was resilient.” 2. **Name one cost you observed.** What got displaced or became harder? Use something specific, such as a cancelled call, a shorter night, or an unresolved decision that occupied your evening. 3. **Check the approach.** Write what you changed afterwards, or why repeating it still makes sense. If another push would reproduce the same hidden work, name the condition that must change before you promise it again. 4. **Write what you restored afterwards.** Record the recovery action that happened, then what you noticed returning. “I planned a break,” “I took the break” and “I could concentrate again” are separate entries. Use “not yet established” where that is the honest answer. 5. **Act on the gap today.** Protect a feasible recovery opportunity, change one avoidable demand, or ask a named person for help. Set a time to check what happened. Until then, leave the result open. Copy these lines into the note: ``` The push achieved: It cost or displaced: Before repeating it, I will change or check: Afterwards, I restored: What remains difficult or unknown: My action today, and when I will check it: ``` If the restoration line stays empty, write “persistence shown; restoration not established.” That push was persistence spending capacity, not resilience restoring it: the gap Chapter 2 warns about. It describes this episode, not your character. Put today’s action beside it. Cite this:Resilience vs grit: what founders need beyond persistence.Len P. van der Hof. [https://lenvanderhof.com/en/blog/resilient-vs-grit/](https://lenvanderhof.com/en/blog/resilient-vs-grit/) · Published 7 November 2026. ## Sources 1. [The Psychology of Founder Resilience](https://lenvanderhof.com/books/psychology-of-founder-resilience/) 2. [Duckworth et al. (2007), Grit: Perseverance and passion for long-term goals, Journal of Personality and Social Psychology 92(6), 1087-1101](https://doi.org/10.1037/0022-3514.92.6.1087) · American Psychological Association (cached metadata and abstract) 3. [Bonanno (2004), Loss, trauma, and human resilience: Have we underestimated the human capacity to thrive after extremely aversive events?, American Psychologist 59(1), 20-28](https://doi.org/10.1037/0003-066X.59.1.20) · American Psychological Association (cached metadata and abstract) ## Further reading - [What is founder resilience? Capacity, not a mood](https://lenvanderhof.com/en/blog/what-is-founder-resilience/) - [What resilience research found: staying level is not bouncing back](https://lenvanderhof.com/en/blog/resilience-research-findings/) - [Recovery is not a day off: match the break to the load](https://lenvanderhof.com/en/blog/recovery-is-not-a-day-off/) - [A holiday is not a refill protocol](https://lenvanderhof.com/en/blog/founder-capacity-is-infrastructure/) - [The Psychology of Founder Resilience](https://lenvanderhof.com/books/psychology-of-founder-resilience/) About the author ## [Len P. van der Hof](https://lenvanderhof.com/en/authors/len-p-van-der-hof/) Entrepreneur, AI Innovator and Venture Builder Len P. van der Hof builds practical AI systems, digital ventures and evidence-informed tools for founders. ```json { "@context": "https://schema.org", "@graph": [ { "@type": "Person", "@id": "https://lenvanderhof.com/#person", "name": "Len P. van der Hof", "alternateName": [ "Len van der Hof", "L.P. van der Hof", "Leendert Pieter van der Hof" ], "honorificSuffix": "MSc", "url": "https://lenvanderhof.com/", "image": [ "https://lenvanderhof.com/photos/len-portrait-1.jpg", "https://lenvanderhof.com/photos/len-portrait-2.jpg", "https://lenvanderhof.com/photos/len-portrait-3.jpg", "https://lenvanderhof.com/photos/len-portrait-4.jpg", "https://lenvanderhof.com/photos/len-speaking.jpg", "https://lenvanderhof.com/photos/len-hero.jpg" ], "jobTitle": "Entrepreneur, AI Innovator and Venture Builder", "description": "Len P. van der Hof, MSc, is a Dutch entrepreneur and AI innovator in Zwijndrecht. He builds ReasonKit, MindSesh, Undominated.ai, books under his name, the fiction imprint LPH98.lifestyle, and technology ventures through LPH98.ventures. Eleven titles in Systems for the Strategic Self are available now, in English and Dutch.", "address": { "@type": "PostalAddress", "addressLocality": "Zwijndrecht", "addressCountry": "NL" }, "alumniOf": { "@type": "CollegeOrUniversity", "name": "Rotterdam School of Management, Erasmus University" }, "knowsAbout": [ "Artificial intelligence", "AI agents", "Agentic AI systems", "LLM routing", "SEO", "Generative engine optimization", "Answer engine optimization", "Venture building", "Founder performance", "Founder psychology", "Evidence-based decision-making" ], "sameAs": [ "https://www.linkedin.com/in/lenvanderhof/", "https://x.com/LenvanderHof", "https://www.youtube.com/channel/UCTG20buKqYYbitqqf7l3zJA", "https://www.instagram.com/Lenvanderhof/", "https://www.threads.com/@lenvanderhof", "https://github.com/Lenvanderhof", "https://huggingface.co/LPH98", "https://www.npmjs.com/~lenvanderhof", "https://www.goodreads.com/author/show/70983905.Len_P_van_der_Hof", "https://www.amazon.com/author/lenvanderhof", "https://www.bol.com/nl/nl/b/len-p-van-der-hof-msc/609879394/", "https://bsky.app/profile/lenvanderhof.com", "https://mastodon.social/@Lenvanderhof", "https://crates.io/users/Lenvanderhof", "https://cursor.com/@Lenvanderhof", "https://medium.com/@Lenvanderhof", "https://gitlab.com/Lenvanderhof", "https://hub.docker.com/u/lenvanderhof/", "https://dev.to/lenvanderhof", "https://www.facebook.com/Lenvanderhof", "https://soundcloud.com/Lenvanderhof" ], "affiliation": [ { "@id": "https://lenvanderhof.com/#publisher" }, { "@id": "https://lenvanderhof.com/#mindsesh" }, { "@id": "https://lenvanderhof.com/#lifestyle" } ] }, { "@type": "WebSite", "@id": "https://lenvanderhof.com/#website", "url": "https://lenvanderhof.com/", "name": "Len P. van der Hof", "description": "Len P. van der Hof, MSc, is a Dutch entrepreneur and AI innovator in Zwijndrecht. He builds ReasonKit, MindSesh, Undominated.ai, books under his name, the fiction imprint LPH98.lifestyle, and technology ventures through LPH98.ventures. Eleven titles in Systems for the Strategic Self are available now, in English and Dutch.", "inLanguage": [ "en", "nl" ], "publisher": { "@id": "https://lenvanderhof.com/#person" } }, { "@type": "Organization", "@id": "https://lenvanderhof.com/#publisher", "name": "LPH98.ventures", "url": "https://lph98.ventures", "founder": { "@id": "https://lenvanderhof.com/#person" } }, { "@type": "Organization", "@id": "https://lenvanderhof.com/#mindsesh", "name": "MindSesh", "url": "https://mindsesh.net", "founder": { "@id": "https://lenvanderhof.com/#person" } }, { "@type": "SoftwareApplication", "@id": "https://lenvanderhof.com/#reasonkit", "name": "ReasonKit", "url": "https://reasonkit.sh", "creator": { "@id": "https://lenvanderhof.com/#person" } }, { "@type": "SoftwareApplication", "@id": "https://lenvanderhof.com/#undominated", "name": "Undominated.ai", "url": "https://undominated.ai", "creator": { "@id": "https://lenvanderhof.com/#person" } }, { "@type": "Organization", "@id": "https://lenvanderhof.com/#lifestyle", "name": "LPH98.lifestyle", "url": "https://lph98.lifestyle", "founder": { "@id": "https://lenvanderhof.com/#person" } }, { "@type": "ImageObject", "@id": "https://lenvanderhof.com/en/blog/resilient-vs-grit/#primaryimage", "url": "https://lenvanderhof.com/media/generated/blog-hero-resilient-vs-grit.e12bb7f79b2d.wide.webp", "contentUrl": "https://lenvanderhof.com/media/generated/blog-hero-resilient-vs-grit.e12bb7f79b2d.wide.webp", "representativeOfPage": true }, { "@type": "BreadcrumbList", "@id": "https://lenvanderhof.com/en/blog/resilient-vs-grit/#breadcrumb", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://lenvanderhof.com/" }, { "@type": "ListItem", "position": 2, "name": "Blog", "item": "https://lenvanderhof.com/en/blog/" }, { "@type": "ListItem", "position": 3, "name": "Founder Performance", "item": "https://lenvanderhof.com/en/blog/category/founder-performance/" }, { "@type": "ListItem", "position": 4, "name": "Resilience vs grit: what founders need beyond persistence", "item": "https://lenvanderhof.com/en/blog/resilient-vs-grit/" } ] }, { "@type": "WebPage", "@id": "https://lenvanderhof.com/en/blog/resilient-vs-grit/#webpage", "url": "https://lenvanderhof.com/en/blog/resilient-vs-grit/", "name": "Resilience vs grit: what founders need beyond persistence", "description": "Grit is sustained commitment. Founder resilience also requires adaptation and recovery. Compare them, then check what you restored after your last hard push.", "isPartOf": { "@id": "https://lenvanderhof.com/#website" }, "primaryImageOfPage": { "@id": "https://lenvanderhof.com/en/blog/resilient-vs-grit/#primaryimage" }, "breadcrumb": { "@id": "https://lenvanderhof.com/en/blog/resilient-vs-grit/#breadcrumb" }, "inLanguage": "en-GB" }, { "@type": "BlogPosting", "@id": "https://lenvanderhof.com/en/blog/resilient-vs-grit/#article", "mainEntityOfPage": { "@id": "https://lenvanderhof.com/en/blog/resilient-vs-grit/#webpage" }, "headline": "Resilience vs grit: what founders need beyond persistence", "description": "Grit is sustained commitment. Founder resilience also requires adaptation and recovery. Compare them, then check what you restored after your last hard push.", "datePublished": "2026-11-07T20:00:00.000Z", "author": { "@id": "https://lenvanderhof.com/#person" }, "publisher": { "@id": "https://lenvanderhof.com/#person" }, "image": [ "https://lenvanderhof.com/media/generated/blog-hero-resilient-vs-grit.e12bb7f79b2d.square.webp", "https://lenvanderhof.com/media/generated/blog-hero-resilient-vs-grit.e12bb7f79b2d.landscape.webp", "https://lenvanderhof.com/media/generated/blog-hero-resilient-vs-grit.e12bb7f79b2d.wide.webp" ], "articleSection": "Founder Performance", "inLanguage": "en-GB" } ] } ```