-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Start adding a few examples to EM roles for Managing Teams #84
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like the concept of adding these examples now and not waiting until we have full coverage. And I think these are good examples.
In the Software Engineering roles we separate examples out into different sections for each of the headings. I think that would be a good pattern to follow here, and some of the examples you've added here might be better off under Managing Individuals.
- I created a space with my team members where they can talk with me about problems they're facing without me having to taking any actions, allowing them a safe space to express what's on their mind without concern of it becoming a larger issue. | ||
- I gave permission to a team member to give me feedback, allowing myself to be vulnerable and open the door to feedback to allow me to improve or change my ways. | ||
- I acknowledged that there is a power dynamic between myself and a junior engineer, but was able to listen to that team member and use my position to advocate for their needs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I love these 💯
💭 I'm not sure if they fit better here, or in Leadership
/ Everyone
? For example, Everyone
has this on feedback.
- I created a space with my team members where they can talk with me about problems they're facing without me having to taking any actions, allowing them a safe space to express what's on their mind without concern of it becoming a larger issue. | ||
- I gave permission to a team member to give me feedback, allowing myself to be vulnerable and open the door to feedback to allow me to improve or change my ways. | ||
- I acknowledged that there is a power dynamic between myself and a junior engineer, but was able to listen to that team member and use my position to advocate for their needs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- I acknowledged that there is a power dynamic between myself and a junior engineer, but was able to listen to that team member and use my position to advocate for their needs.
💭 For this Example
, is there a way we could describe an even more concrete scenario that fits this pattern?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left some minor thoughts/questions, but to me this seems like a valuable addition even as-is ✅
I'd like to start adding some examples of the EM role to help new EMs, weather they're new to Octopus, or new to EM from the IC track at Octopus. As we keep expanding, adding more and more examples will become valuable for helping these new EMs onboard into being an EM the Octopus way.
Earlier in the year a few of us attended a workshop around supporting early career women in male-dominated fields and wrote up some of my learnings here: https://octopusdeploy.slack.com/archives/C01HEHFJKUK/p1713925356117769?thread_ts=1713913920.840279&cid=C01HEHFJKUK
We've added a point around connectedness here from that workshop: #83 now I'm expanding on some examples to help support other pillars of our team around connectedness, belonging and certainty.
These are just a few example for all the capabilities of an EM, but I'd like to keep our scope smaller for this first pass, and continue to add more examples for other capabilities over time rather do an all-in add examples for everything in one go.
I'm looking for all feedback around the new capability and examples :)