Photo by Brett Jordan on Unsplash
Observing the Effects of Submitting Work Without Immediate Feedback
The Quiet Execution Principle
There’s a subtle but noticeable difference in my long-term drive when I manage to release projects or finished pieces of work without immediately seeking external validation or even telling people I’ve completed them. It’s not about being secretive, but rather about letting the act of completion and the subsequent quiet reflection be the primary reward, at least for a short while. It feels like this practice helps shield the intrinsic motivation from the potentially corrosive effects of premature praise or criticism.
I’ve noticed this most clearly when working on personal creative projects or difficult analytical tasks. For example, after finishing a particularly dense research summary I’d been wrestling with for weeks, my initial impulse was to share it with a colleague to get their thoughts right away. Instead, I held back, letting it sit for two days, just for myself. The subsequent conversations felt more measured, and I found myself less invested in their immediate reaction and more in the content itself.
Trade-offs and Nuances
The obvious limitation here is social and professional connection. In many collaborative environments, especially early on, showcasing work and seeking input is crucial for visibility and progress. Holding back too much can be misinterpreted as aloofness or a lack of teamwork. Finding the balance is key, and it’s easy to err too far in either direction. There’s also the internal pressure; sometimes, the silence after finishing something important can feel deafening, making the urge to share almost overwhelming.
Counter-Intuitive Insight
What feels counter-intuitive is that intentionally *not* broadcasting achievements, at least temporarily, can actually enhance long-term motivation, rather than diminishing it by lacking external reinforcement. We often associate motivation with positive feedback loops, but this suggests that an internal locus of reward, derived from the work itself, is more robust for sustained effort, particularly on challenging tasks.
Comparison to Performance Metrics
This contrasts with a purely metrics-driven approach to performance, like tracking daily task completion rates or public acknowledgments. While those can be useful for accountability and identifying patterns, they tend to focus on external outputs and quantifiable results. The quiet execution principle, on the other hand, prioritizes the internal psychological state of the doer, emphasizing process and intrinsic satisfaction over immediate performance indicators. It’s less about *how much* is done and more about the *quality of the internal experience* of doing it.
Practical Application
For practical application, I’ve started building in a short ‘quarantine’ period for completed work. It might be 24-48 hours before I send an email, post an update, or discuss it openly. It’s a small buffer, just enough to let the completion settle internally before the external world weighs in. This doesn’t mean abandoning feedback; it means timing it strategically, after the initial intrinsic reward has had a chance to resonate.
Further Reading
Deci, E. L., & Ryan, R. M. (2000). The ‘what’ and ‘why’ of goal pursuits: Human needs and the self-determination of behavior. *Psychological Inquiry*, 11(4), 227-268.
Brown, B. (2018). *Dare to Lead: Brave Work. Tough Conversations. Whole Hearts.* Random House.
Kahneman, D. (2011). *Thinking, Fast and Slow*. Farrar, Straus and Giroux.
