[21723]

> In my ~20-year career I have never once been in a workplace setting where creativity wasn't valued.

Mayhaps, but if true this is atypical and fortunate. Ninety-nine percent of people get shunted into subordinate labor with no creative meat, in which their job is to support the manager's career and that it all that matters--and this is also true in software, now that the Jira jockeys have taken over and turned it into ticket-shop day labor. Congrats if you've escaped the sprint work, but most people can't.

[wdrw]

I disagree that "supporting the manager's career" is necessarily at odds with creativity. Once you reach a certain level of knowledge in a workplace (problem domain knowledge, codebase knowledge, etc), different options appear to deal with each incoming Jira. You can solve them naively, or you can solve them creatively to produce better results and set up the codebase for more success in the future, or you can even (surprisingly often!) question some assumptions and find a way to not even do the work as-originally-specced but rather substitute some simpler version. These latter options make your team (and thus your manager) look even better, there's no conflict of interest here. Sure, this doesn't work with grunt-level "move this button over here" tasks, but presumably after you've actually built up the knowledge I was talking about earlier, you're assigned more interesting and challenging tasks (which are never in short supply).

[nicoburns]

> Congrats if you've escaped the sprint work, but most people can't.

Are you not involved in designing the solutions and the tickets too? And is that process not creative?