There are only two kinds of creative problems, and almost every frustrating meeting comes from confusing them.
Polish problems mean the thing is right but rough: correct message, right audience, weak execution. Change problems mean the thing itself is wrong: the strategy, the assumption, the offering. Polish problems are solved with craft. Change problems are solved with decisions. And each one is immune to the other's medicine.
Misdiagnosis, both directions
Apply polish to a change problem and you get the church that redesigns its ministry brochure every year while the ministry it describes quietly stopped working in 2019. The brochure gets better. The problem stays fed and warm underneath it.
Apply change to a polish problem and you get the opposite failure: the team that scraps a working strategy because the last two executions were sloppy. That's amputating a limb that needed a splint. Strategy takes the blame for what craft should have caught.
The diagnostic
When something isn't working, ask one question before anything else: if this exact idea were executed flawlessly, would it work?
If yes — the sermon series is right but the graphics are muddy, the event is right but the signage failed — you have a polish problem. Hand it to craft. Protect the strategy from the room's panic.
If no — flawless execution would still land on people who aren't listening, or say something that's no longer true — you have a change problem. No designer can help you yet. It has to go back to leadership, and going back is the win, not the failure.
Why this is a leadership skill
Teams under pressure default to polish, because polish is visible effort and change is visible risk. Somebody has to be willing to say "this isn't a design problem" in a room that would rather order another revision. That somebody is a leader — whatever their title says.
