“I need each of you to tell every young woman you know to be comfortable with imperfection.”
Reshma Saujani offered this line in her TED2016 talk “Teach girls bravery, not perfection”. Saujani connected gendered expectations of perfection with participation in computing. She argued that avoiding visible mistakes can discourage girls from taking risks, submitting unfinished work, and staying with hard technical problems. Its force comes from experience: the speaker was describing consequences already visible in real systems and institutions.
Comfort with imperfection is not acceptance of low standards. It is permission to enter the learning loop where drafts fail, feedback arrives, and skill grows. Innovation requires exposure to uncertainty before mastery is available. The line asks readers to look past novelty and examine what the technology enables people to do. It directs attention to the work between an appealing idea and a dependable result: defining the problem clearly, exposing assumptions, and learning from evidence instead of relying on reputation or momentum. In practice, that means asking what changed, who gained new capability, and how the result would be checked by someone who did not share the builder’s expectations.
Confidence messages cannot substitute for fair classrooms and workplaces. Biased evaluation, harassment, unequal access, and lack of sponsorship are institutional problems. Individuals should not be asked to become braver while organizations preserve avoidable penalties. That distinction is essential whenever a compact quotation travels farther than the detailed account that produced it. Strong technology reporting must preserve this nuance, because the same words can support very different choices when the original constraints disappear. A responsible reading also separates the speaker’s documented claim from broader promises that admirers may attach to it later. That protects both the historical record and the reader’s ability to disagree intelligently.
Programming makes mistakes visible through errors and broken builds, which can be productive when the environment treats them as information. Teams that normalize questions, prototypes, and revision widen participation and improve the quality of technical decisions. Used this way, the quote becomes a prompt for better practice rather than a decorative line about innovation. For readers, builders, and institutions, the practical question is not whether the quotation sounds true in isolation, but whether current decisions honor the conditions and responsibilities it identifies. Teams can make that test concrete through review, accessible documentation, independent feedback, and measures that include failures as well as successes. Those habits turn a memorable insight into work that others can examine and improve.
Reshma Saujani offered this line in her TED2016 talk “Teach girls bravery, not perfection”. Saujani connected gendered expectations of perfection with participation in computing. She argued that avoiding visible mistakes can discourage girls from taking risks, submitting unfinished work, and staying with hard technical problems. Its force comes from experience: the speaker was describing consequences already visible in real systems and institutions.
The source record connects the wording to her TED2016 talk “Teach girls bravery, not perfection”, which is the context used for this post.
Comfort with imperfection is not acceptance of low standards. It is permission to enter the learning loop where drafts fail, feedback arrives, and skill grows. Innovation requires exposure to uncertainty before mastery is available. The line asks readers to look past novelty and examine what the technology enables people to do. It directs attention to the work between an appealing idea and a dependable result: defining the problem clearly, exposing assumptions, and learning from evidence instead of relying on reputation or momentum. In practice, that means asking what changed, who gained new capability, and how the result would be checked by someone who did not share the builder’s expectations.
The interpretation focuses on a decision or design principle that readers can test against actual systems.
Confidence messages cannot substitute for fair classrooms and workplaces. Biased evaluation, harassment, unequal access, and lack of sponsorship are institutional problems. Individuals should not be asked to become braver while organizations preserve avoidable penalties. That distinction is essential whenever a compact quotation travels farther than the detailed account that produced it. Strong technology reporting must preserve this nuance, because the same words can support very different choices when the original constraints disappear. A responsible reading also separates the speaker’s documented claim from broader promises that admirers may attach to it later. That protects both the historical record and the reader’s ability to disagree intelligently.
Programming makes mistakes visible through errors and broken builds, which can be productive when the environment treats them as information. Teams that normalize questions, prototypes, and revision widen participation and improve the quality of technical decisions. Used this way, the quote becomes a prompt for better practice rather than a decorative line about innovation. For readers, builders, and institutions, the practical question is not whether the quotation sounds true in isolation, but whether current decisions honor the conditions and responsibilities it identifies. Teams can make that test concrete through review, accessible documentation, independent feedback, and measures that include failures as well as successes. Those habits turn a memorable insight into work that others can examine and improve.
Explore more "Quotes of The Day"
Discover more notable quotes from influential voices across politics, science, business, technology, sports, and culture. Each quote offers insight into how ideas, beliefs, and decisions shape the world around us.