All else equal, higher salaries almost always would lead to more candidates, but once you close to a level that is relatively competitive (eg compared to similar roles in other non-profits) and seems generally relatively fair compared to the rest of the organisation, I think other aspects of the role might become more important to candidates (eg the general work environment, how much freedom people get in the role, how much involved they can get in other aspects of the organisation if they want to, etc).
There are a few ways which allow me to get involved in other areas of our organization:
All of our Lead staff have weekly meetings, so in those meetings I can reflect on questions other Leads bring to the group, contribute ideas, etc.
Our whole team tries to allow pretty good visibility of what we’re working on by keeping project- or task-related information in the appropriate place in Asana and by posting brief weekly project updates in Slack.
We have a “reciprocity” Slack channel where we can post if we’d like someone’s help on something, and that can often be someone from a different competency area than the poster’s.
We encourage staff to join projects as Scrum Master, even if the project is outside their competency area
All else equal, higher salaries almost always would lead to more candidates, but once you close to a level that is relatively competitive (eg compared to similar roles in other non-profits) and seems generally relatively fair compared to the rest of the organisation, I think other aspects of the role might become more important to candidates (eg the general work environment, how much freedom people get in the role, how much involved they can get in other aspects of the organisation if they want to, etc).
Thanks! How can an org give ops staff more freedom and involvement-if-they-want-it? What are some classic mistakes to avoid?
There are a few ways which allow me to get involved in other areas of our organization:
All of our Lead staff have weekly meetings, so in those meetings I can reflect on questions other Leads bring to the group, contribute ideas, etc.
Our whole team tries to allow pretty good visibility of what we’re working on by keeping project- or task-related information in the appropriate place in Asana and by posting brief weekly project updates in Slack.
We have a “reciprocity” Slack channel where we can post if we’d like someone’s help on something, and that can often be someone from a different competency area than the poster’s.
We encourage staff to join projects as Scrum Master, even if the project is outside their competency area