As training material writers and designers, we often strive for perfection. This may manifest itself in certain behaviors, such as rewriting the same paragraph multiple times, obsessively adjusting text formatting, and so on. We often interpret these habits as an indication of our dedication, but in fact, they may be impeding our progress.
Perfectionism isn’t really about striving for excellence. It’s about seeing every minor mistake as a sign of failure. It’s about believing that unless something is flawless, it isn’t worth sharing. In our work as material writers, where creativity is key, perfectionism can be the silent thief that steals our time, dampening our creative impulses. It leaves us with complex drafts and unfinished projects. We are frustrated, wondering why we cannot just move on.
Perhaps you’ve been in this bleak place. You’re stuck tweaking a document repeatedly, only to realize that it does not really work after all. You are hesitant to submit your idea, convinced that it is not good enough and that others will judge you for it. These moments can feel isolating, but they’re far from unique. We’ve all faced those inner battles, and it’s time to learn how to challenge them.
Another factor is confirmation bias, which we all suffer from. Many people have a bias that filters out positive feedback, focusing their attention instead on negative feedback, reinforcing their sense of chronic imperfection.
We need to shift our focus. Instead of chasing perfection, we could aim for “good enough.” This is like the concept of an MVP (Minimum Viable Project), the minimum state in which the project is said to fulfill the primary aim. The core idea of an MVP is to create a tangible product or service, even if it’s just a basic version, like a landing page or a manual service disguised as something automated. This allows you to present it to customers and observe how they use it. Actual user behavior provides far more reliable insights than simply asking people what they think something would do for them. This concept is well known in the world of app development, where projects will initially have a minimal level of functionality. The developer will build on this in later reiterations. Good enough is not about settling for something bad; it’s about recognizing when something has achieved enough functionality to serve its core purpose, and then it can be tested and improved in later iterations. This is the basis of good instructional design.
Imagine what might happen if we approached our work with this mindset. Deadlines would feel less daunting. Creativity would flow more freely. Most importantly, we’d be able to see our successes rather than fixating on what could be better. We would stop striving for perfection and start creating for the learner. User feedback would begin to play more of a role in the writing process.
Of course, letting go of perfectionism isn’t easy. It requires us to be kind to ourselves and see mistakes not as failures but as opportunities to grow. It means allowing for imperfection and trusting that our work has value, even when it isn’t flawless. We need to allow ourselves to make mistakes.
What is important when you design learning activities is the question: What will benefit the learner the most? What’s essential, and what can you omit? When you focus on what matters, you’ll discover that “good enough” often turns out to be exactly what’s needed. In the end, the learners don’t need perfection. They need materials that will allow them to reach their learning goals. Good enough isn’t just acceptable; it’s the foundation of good work.
AI-Generated image from Dall-E
No responses yet