"Kanban isn't relevant to me because I don't run a development team."
I've heard this sentiment a few times of late, and I guess it's understandable - 'Kanban' is often spoken of in the same breath as 'Scrum', but they do not do the same job.
If your team takes work items (of any nature) through a series of stages, Kanban is relevant to you!
Kanban is about identifying waste and optimising the flow of work through your system. It originated in automobile manufacture, and has found itself (approximately) at home in software development. In this new domain almost all of the analogues are strained, and yet it remains a very valuable tool.
tl;dr - don't write off Kanban just because you're not shipping software (or cars).