Growth mindset

Definition
A growth mindset is the belief that ability improves through practice, feedback and repetition, so a setback is information about the next attempt rather than a verdict.

Why it matters

A team that avoids tests likely to fail, or defends a bad number instead of asking why, learns slowly. A team that treats each result as evidence learns faster, and speed of learning is often the only advantage a small company has over a larger one. The practical shift is small: the question moves from whose fault the result was to what it showed and what to try next.

How to apply it

  • Set a learning goal next to every performance target, and count the insight even when the number falls short.
  • Run small, frequent tests instead of waiting for a perfect, fully formed one.
  • Write down what each test found where the whole team can see it.
  • Replace blame-heavy post-mortems with a plain review: what went well, what was surprising, what to try next.
  • Say "not yet" instead of "can't", both to others and when judging your own work.

What it is

The phrase comes from the psychologist Carol Dweck, who contrasted a fixed mindset, in which talent is something you have or lack, with a growth mindset, in which skill is built through effort and good feedback. In business the idea is practical. Writing, selling, optimising and building all get better with repetition, yet plenty of people stop early because they have quietly decided they have reached a ceiling.

It is not positive thinking, and it does not mean working harder at a plan that is not working. It means treating a disappointing result as data.

Common mistakes

Using the phrase as a slogan to ask for more effort, or praising effort when the approach itself is wrong. Effort counts only when it is paired with changing the method.

Worked example

Suppose a small team of five runs its own marketing experiments and keeps hitting the same disappointment: a test misses its target and someone is blamed. The lead changes the habit. Each experiment becomes a card on a Trello board, with its hypothesis in the title, and the card moves from idea to running to done. When a test misses, the team writes what it showed on the card before the next one starts. Within two months the board holds twenty-two finished experiments, eight of which failed, and nobody argues about whose fault it was. A failed test now counts as a finished card with a lesson on it.

Tools in the example

Some links are affiliate links: we may earn a commission at no cost to you. It never decides a ranking. How we work with partners

  1. Article

    Prioritisation

    Deciding which experiment runs next.

  2. Article

    OMTM (One Metric That Matters)

    The number a team's experiments usually aim at.

  3. Article

    Kill criteria

    The rule that stops a test being run forever.