Skip to content
Tiatra, LLCTiatra, LLC
Tiatra, LLC
Information Technology Solutions for Washington, DC Government Agencies
  • Home
  • About Us
  • Services
    • IT Engineering and Support
    • Software Development
    • Information Assurance and Testing
    • Project and Program Management
  • Clients & Partners
  • Careers
  • News
  • Contact
 
  • Home
  • About Us
  • Services
    • IT Engineering and Support
    • Software Development
    • Information Assurance and Testing
    • Project and Program Management
  • Clients & Partners
  • Careers
  • News
  • Contact

Stop telling yourself no: Breaking the cycle of self-imposed limitations

In a recent conversation with an IT leader at Avery Dennison, they shared something that stuck with me. We were discussing a new idea, and I said, “Just tell me what you need.” They paused and said, “I appreciate you saying that. So often, people tell themselves no before they even ask.”

That moment inspired this article and sparked a deeper reflection on one of the most pervasive barriers to innovation and progress in organizations today. As SVP and CIO at Avery Dennison, I’ve witnessed countless brilliant ideas stall not because they lack merit, but because someone assumes they can’t get the time, budget or support to pursue them. They self-censor, convinced they’ll be expected to deliver without any additional resources.

This phenomenon extends far beyond individual conversations. It’s a cultural issue that quietly undermines organizational potential. I’ve seen teams with transformative solutions never voice them because they’ve convinced themselves the answer will be no before they even ask.

The silent killer of innovation

Throughout my career, I’ve observed that great ideas often die in the minds of the people who conceived them. I’ve watched talented professionals dismiss their insights before giving them a chance to be evaluated on their merits. Think about the last time you had what you considered a “crazy” idea. Maybe it was a process improvement that could save your team hours each week, a technology solution that could enhance customer experience or a strategic initiative that could open new markets.

If you’re like most people I work with, you probably ran it through an internal filter first, a mental calculation of feasibility, resources and likelihood of approval. More often than not, that filter convinced you to keep the idea to yourself. I’ve done this myself early in my career, and I’ve seen it happen countless times with my teams.

This self-imposed gatekeeping creates a tragic irony: the very ideas that could transform our organizations never make it past the person who conceived them. We’ve become our own worst enemies when it comes to innovation, creating invisible barriers that are often higher and more impenetrable than any real constraints we might face.

In my experience leading digital transformation initiatives, some of our most successful projects came from ideas that initially seemed impossible or too resource-intensive. The Boston Consulting Group research on innovation barriers confirms what I’ve observed: organizations that encourage idea-sharing at all levels significantly outperform those that rely solely on top-down innovation.

Why we tell ourselves no before anyone else can

I’ve spent considerable time analyzing why talented professionals consistently self-censor their best ideas. The tendency stems from several deeply ingrained psychological patterns that I’ve observed across different organizations and cultures.

Loss aversion plays a significant role. When we consider proposing an idea, we immediately imagine the potential embarrassment, rejection or perceived failure if it’s shot down. I’ve seen brilliant engineers and business analysts hold back game-changing concepts because they fear looking naive or out of touch with practical constraints.

Risk aversion compounds this problem. In many organizational cultures, there’s an unspoken understanding that it’s safer to maintain the status quo than to rock the boat with new proposals. Early in my career, I learned this lesson the hard way when I witnessed colleagues who suggested changes being perceived as dissatisfied or overly ambitious.

There’s also the phenomenon of learned helplessness. Over time, if people have had ideas dismissed or have witnessed others’ proposals rejected, they begin to internalize the belief that their input isn’t valued. I’ve worked with teams where previous leadership changes or budget cuts created an atmosphere where people assumed decision-makers were too busy, too set in their ways or too focused on other priorities to consider new suggestions seriously.

Perhaps most insidiously, we often engage in mind-reading. We assume we know what our leaders are thinking without actually asking them. I’ve caught myself doing this, convincing myself that my boss was too stressed to hear new ideas or that the timing wasn’t right for change. While sometimes based on observable patterns, these assumptions frequently miss the mark entirely.

Harvard Business Review’s research on psychological safety demonstrates that teams where members feel safe to voice ideas and concerns significantly outperform those where people self-censor due to fear of negative consequences.

The hidden costs of silence

When I reflect on my years in leadership, I can trace many missed opportunities back to ideas that were never shared. The most obvious cost is innovation that could have improved efficiency, increased revenue or enhanced competitive advantage. But I’ve learned that the hidden costs run much deeper.

Employee engagement suffers dramatically when people feel their ideas aren’t welcome or valued. I’ve managed teams where creative, strategic thinkers gradually became order-takers rather than problem-solvers because they believed their input wouldn’t be heard. This transformation is painful to watch and devastating to organizational capability.

We also lose valuable intelligence about problems and opportunities that only front-line employees can see. In my role, I regularly discover that the people closest to customers, processes and day-to-day operations have the clearest view of what’s working and what isn’t. When they stop sharing these insights, leadership loses touch with operational reality.

Furthermore, self-censorship creates a vicious cycle that I’ve seen play out repeatedly. When good ideas aren’t surfaced, leaders may assume everything is running smoothly or that their teams aren’t thinking strategically. This can lead to top-down problem-solving that’s less informed and less effective than solutions that might emerge from collaborative ideation.

Creating environments where ideas flourish

I’ve learned that every leader needs to communicate clearly and consistently: We want to hear your ideas and know how we can help make them real. If an idea aligns with our goals and creates value, we’ll figure out how to support it.

The challenge isn’t that leaders don’t want to hear ideas. It’s that we often fail to create environments where people feel safe and encouraged to share them. Creating such an environment requires intentional effort from leadership, and I’ve had to learn this through trial and error.

I start by explicitly inviting input and making it clear that idea-sharing is not just welcomed but expected. In my team meetings, I regularly communicate that I view my role as removing obstacles and providing resources to help good ideas flourish, not as a gatekeeper who protects the status quo.

This means establishing regular forums for idea-sharing, whether through innovation sessions, town halls or simply encouraging direct communication. When someone brings me an idea, I’ve trained myself to respond with curiosity rather than immediate judgment, asking questions like “How might this work?” and “What would you need to test this?” instead of “Why haven’t we done this before?” or “Do you know how much that would cost?”

I’ve also learned the importance of transparency about decision-making criteria. When people understand what factors influence an idea’s approval (strategic alignment, resource requirements, timing, impact potential), they can better prepare their proposals and understand outcomes, even when the answer is no.

The results have been remarkable. Teams that once seemed quiet and execution-focused have become hotbeds of innovation when given permission and encouragement to think creatively about solutions.

Moving forward, I challenge every reader to examine their relationship with idea-sharing. The next time you find yourself dismissing an idea before you’ve shared it, pause and ask yourself: What if I’m wrong about the barriers? What if there’s more support available than I think? What if this idea could make a real difference?

Stop telling yourself no. You might be surprised how often the answer is yes. And even when it’s not, you might be surprised by the conversation that follows and the opportunities it creates. The cost of not asking is often much higher than the cost of asking and being told no. 

This article is published as part of the Foundry Expert Contributor Network.
Want to join?


Read More from This Article: Stop telling yourself no: Breaking the cycle of self-imposed limitations
Source: News

Category: NewsAugust 11, 2025
Tags: art

Post navigation

PreviousPrevious post:INE Named to Training Industry’s 2025 Top 20 Online Learning Library ListNextNext post:Report Reveals Tool Overload Driving Fatigue and Missed Threats in MSPs

Related posts

Analytics capability: The new differentiator for modern CIOs
December 12, 2025
Stop running two architectures
December 12, 2025
法令だけでは足りない―医療情報ガイドラインと医療DXのリアル
December 12, 2025
SaaS price hikes put CIOs’ budgets in a bind
December 12, 2025
Don’t blame AI if the data doesn’t stack up
December 12, 2025
DigitalES alerta de la escalada de riesgos en IA y propone un marco para una adopción empresarial segura
December 12, 2025
Recent Posts
  • Analytics capability: The new differentiator for modern CIOs
  • Stop running two architectures
  • 法令だけでは足りない―医療情報ガイドラインと医療DXのリアル
  • SaaS price hikes put CIOs’ budgets in a bind
  • Don’t blame AI if the data doesn’t stack up
Recent Comments
    Archives
    • December 2025
    • November 2025
    • October 2025
    • September 2025
    • August 2025
    • July 2025
    • June 2025
    • May 2025
    • April 2025
    • March 2025
    • February 2025
    • January 2025
    • December 2024
    • November 2024
    • October 2024
    • September 2024
    • August 2024
    • July 2024
    • June 2024
    • May 2024
    • April 2024
    • March 2024
    • February 2024
    • January 2024
    • December 2023
    • November 2023
    • October 2023
    • September 2023
    • August 2023
    • July 2023
    • June 2023
    • May 2023
    • April 2023
    • March 2023
    • February 2023
    • January 2023
    • December 2022
    • November 2022
    • October 2022
    • September 2022
    • August 2022
    • July 2022
    • June 2022
    • May 2022
    • April 2022
    • March 2022
    • February 2022
    • January 2022
    • December 2021
    • November 2021
    • October 2021
    • September 2021
    • August 2021
    • July 2021
    • June 2021
    • May 2021
    • April 2021
    • March 2021
    • February 2021
    • January 2021
    • December 2020
    • November 2020
    • October 2020
    • September 2020
    • August 2020
    • July 2020
    • June 2020
    • May 2020
    • April 2020
    • January 2020
    • December 2019
    • November 2019
    • October 2019
    • September 2019
    • August 2019
    • July 2019
    • June 2019
    • May 2019
    • April 2019
    • March 2019
    • February 2019
    • January 2019
    • December 2018
    • November 2018
    • October 2018
    • September 2018
    • August 2018
    • July 2018
    • June 2018
    • May 2018
    • April 2018
    • March 2018
    • February 2018
    • January 2018
    • December 2017
    • November 2017
    • October 2017
    • September 2017
    • August 2017
    • July 2017
    • June 2017
    • May 2017
    • April 2017
    • March 2017
    • February 2017
    • January 2017
    Categories
    • News
    Meta
    • Log in
    • Entries feed
    • Comments feed
    • WordPress.org
    Tiatra LLC.

    Tiatra, LLC, based in the Washington, DC metropolitan area, proudly serves federal government agencies, organizations that work with the government and other commercial businesses and organizations. Tiatra specializes in a broad range of information technology (IT) development and management services incorporating solid engineering, attention to client needs, and meeting or exceeding any security parameters required. Our small yet innovative company is structured with a full complement of the necessary technical experts, working with hands-on management, to provide a high level of service and competitive pricing for your systems and engineering requirements.

    Find us on:

    FacebookTwitterLinkedin

    Submitclear

    Tiatra, LLC
    Copyright 2016. All rights reserved.