Ah; I forgot to add the second sentence; roughly what NogDog suggested, but at right angles (in other words, it was exactly the same but completely different): rather than a generic "Manager" class I had a generic "CRUD" class, viewing users from the perspective of what they can do with the information in the system (create/retrieve/update/delete) rather than from their role in the company.
I reckon such a mapping would come in at some point: it would, for example, unify the "Management" roles with the "Report Generation" role (since managers also need to be able to generate reports). Another role would be that of the clerical worker who can edit records but not add or delete them; or the data-entry operator who can only add with only limited scope for editing.
But I think I'm waffling again.