I fear I did a horrible job of describing it in those terms, though. Or perhaps the thoughtful responses like yours have just helped me clarify my thoughts on the topic. Because in reality, I'm a huge proponent of the creative side of development. I think it's often so underrated by many companies and interviewers.
Creativity is absolutely part of the value a good developer provides, and creative developers shouldn't hesitate to discuss that in interviews.
It'll sometimes be the case that the company of person interviewing you won't value creativity. Which is actually super useful to find out, because interviews are a two-way process. If you're a creative developer, and an interviewer makes it clear they don't care about that, they've helped you by letting you know unequivocally that you don't want you work for them.
When interviewing I look for people that just don't sit back and do what they're told. Someone proactive who can think of different ways of doing things. I would like to hear an answer like "Compared to other developers I've worked with in the past, I make more of an effort to talk with end users and try to target the system to make it more usable rather than just getting the functionality done." That shows something that might appeal more than the last guy we just interviewed.
I know other people like predictable developers who can crank out code from a big Jira list. Maybe they would like an answer about productivity over costs.
As you can tell it depends on the people, there is no right answer. :)