It’s a great mantra in the professional realm. The problem still emerges when an ill-defined “good” becomes some version of the new perfect. Sometimes, a person’s or team’s capabilities just aren’t at the place where they can make something good yet. The relationships, chemistry, and balances in talent aren’t there, and aiming for “good” at the first swing isn’t even possible yet. “Good” ideas end up being scarce, a “good” plan is non-existent, and morale ends up really really far away from “good.”

We probably hope that our expectations of making something “good” will turn into an actuality, like a self-fulfilling prophecy. That’s not going to happen though. For every group of people who deal with the pressure to meet this unrealistic expectation, there are dozens that struggle. People are fearful because they know they won’t make something “good” with the time and resources given.

THINGS MAY START OFF “BAD” AT THE BEGINNING

The natural principle here is not to aim for “perfect” or “good,” but always to lower standards at the beginning—even aiming for “bad,” to start with. Perfect things come from good things, and good things come from bad things. I’m definitely not saying to go all in on a bad idea—however, it’s very possible that a good idea could emerge from putting forward 100 bad ideas. (Rather it’s just unlikely that anyone can make 100 bad ideas without 1 of them being accidentally good.)

Sometimes—and I daresay, a lot of times—”good” things start out “bad.” A “good” feature emerges from a really terrible product. A “good” opportunity for skill development emerges from a really “bad” attempt at a project. A “good” book emerges from a “bad” initial draft.

DOING SOMETHING “BAD” FREES YOU UP TO DO SOMETHING “GOOD”

Also, knowing when to slack off and ship “bad” work is another skill altogether, because that frees up your energy to do “good” work—or even to focus on trying to make something “perfect.” That’s a whole other topic altogether, one that startup advisor Shreyas Doshi does a great job explaining. (When he realizes a task is unimportant and will not make an impact, and he still can’t put it off, he deliberately decides to do it badly, watching TV in the background.)

Doing something “bad” can be an awful experience and lead to a complete dead end. Sure. More often than not though, I’ve found that taking it one step further—treating it like the preparation phase of a creative process—can squeeze the most out of an otherwise painful, and fruitless, experience. Thinking about it, getting feedback, looking for a next step, or deciding that you’re better off doing something else—all “good” results from a “bad” project.

“BAD” CAN BE THE FIRST STEP TO “GOOD”

There’s a popular—and controversial—saying in software development, “Worse is better.” This post is not a call to make something “bad” on purpose or to ship incomplete work. It is another way of phrasing Anne Lamott’s powerful writing advice, to give yourself permission to write shitty first drafts. Permission to make something “Bad” is the first step to being more creative. “Bad” isn’t the enemy of “good,” it’s merely the first step to making something good.

If we decide to take that more forgiving approach to “Bad” work, we can start looking at every piece of work as a first draft, as DJ Dahi recommended to me in an interview.

“Good” and “bad” are not always diametrically opposed. “Bad” is often how projects start. We don’t need to pretend otherwise. “Good” is how projects appear when they are closer to complete, if we stay present when we make it. And if we’re lucky, “perfect,” takes place when we make something “good” and it matches up with timing and support. But “perfect” is not in our control.

Once we decide to let go of “perfect” and our fears of making something “bad,” our expectations fall behind and we’re free to focus what’s in front of us: the actual work itself.

This article originally appeared on Herbert Lui’s blog and is reprinted with permission.