Getting to know the community
- Currently, the best way to find out who's in the community is by exploring the member directory on Slack. You can also have a browse on the #intros channel on Slack.
- You can find some of Ops Stories members on LinkedIn if they have added the community to their experience. Click here to see everyone who has. Also, please add Ops Stories to your LinkedIn profile! It will make it easier for others to find you. See here how to do that.
- We are working on a proper Members Directory so keep your 👀 peeled, it's coming soon! 🔜
- Go to your LinkedIn profile, scroll down to "Experience" and select the "+" symbol.
- In the pop-up modal, find "Ops Stories" as the Company and "Member" as title, and add the description below: "Ops Stories is a private, invitation-only community of operations folks from startups to scale-ups across different industries."
- To find out the date you joined the community you can search "email@example.com” in your email to find your original Google group invitation. Alternatively, just ping a message to Astrid or Aušrinė on Slack or via email and we'll let you know 🙂
Getting answers that you need
- If possible, ask during working hours. Questions asked on Friday evenings or weekend don't tend to get many responses.
- Be clear, concise and as explicit as possible.
- Using appealing visuals helps too e.g. bolding the main question or adding an emoji for emphasis.
- Use the right channels (e.g. #finance for finance related questions, etc.)
- Give an example of what you're looking for if possible
Spreading the word about Ops Stories
If you'd like to refer someone to join Ops Stories, please send them the Airtable form to fill in and Astrid and Aušrinė will take it from there.
What we're looking for in new members:
- Their main responsibility is operations. It will usually be reflected in the job title (e.g. Head of Operations, Operations Manager, Operations Lead, COO), however, it may sometimes be disguised under titles like Business Change Manager, Special Projects, Head of Supply, etc.
- They will gain value from being part of the community and are also willing to contribute.
- They have 3+ years of work experience. This doesn't have to be in operations.
Our current process is:
- Astrid or Aušrinė jump on a quick phone call with them to align on expectations. We'll tell them more about how Ops Stories work and also ask about their operations journey so far, and their expectations from the community, why they'd like to join and how they're willing to contribute.
- They're welcomed to Ops Stories :)
- Sometimes, however, we have to let people down in this case, we would direct them to a community that would deliver more value for them than Ops Stories. This is usually the case for folks who focus more on one area, e.g. People Operations (>> People Stories), Customer Success (>> Customer Stories), Office Management (>> OMG), Founder/CEO responsibilities (>> Foundrs), etc.
- Please don't add people directly to the Ops Stories Slack. That functionality has been disabled.
- Our roundtable events are normally reserved for Ops Stories community members, however, sometimes we might welcome guests. If you think that the person in question will be able to contribute to the event by actively participating in the discussion, asking insightful questions and/or sharing their knowledge, we don't see why not.
- Please let us know before extending the invitation so we can prepare to properly welcome them!
Our events usually aren't recorded, but we always try to keep notes on the most important things that we discussed. You can find historical events and there notes here
Absolutely, we always encourage our ops members to share our content with their colleagues. Just let us know about it ahead of time and ensure they have rsvp'ed to the event.
Changing your details
Our Slack channels recently got reorganised and we're now working on a proper guide so stay tuned. However, it's really not rocket science - each channel has a description on what it's for. If you're unsure, just chuck it in #general 🙂