This was originally an email sent to the Ops Stories Google Group on the 21st of July 2020. The text was slightly adapted to work better in Notion, mainly formatting.
We wanted to share something that's going on in the background of Ops Stories with you today.
We have quarterly board meetings.
Okay, this is probably not what you expected us to tell you. But we're really proud of it and wanted to share a couple of things with you. Mainly because sharing is fun, and hopefully adding transparency to how we run this community. The idea is that from now, after each board meeting, we keep you all updated with our agenda, topics discussed, and goals set for the next quarter.
Why organise a quarterly meeting?
We (Aušrinė and I) have a vision for Ops Stories, but sometimes we need a hand. As much as we know why we created Ops Stories and what we want to achieve with it, being to close to it daily makes it hard to see the bigger picture. Organising these board meetings allows us to bring clarity to our dreams and how to achieve them. We get the opportunity to ask questions, get honest feedback and help set targets for the next quarter.
Who's helping us?
Our Core Team, a.k.a. the people who took initiatives within Ops Stories to help enhance the experience. Here are a few words from them all on why they're getting involved and giving time to Ops Stories.
Laura Parker I am a big fan of Ops Stories as it is an amazingly open, humble and supportive community that saved my bacon numerous times when I was dealing with the challenges of being the sole-operations person in a high-growth tech start-up. It is great to chat to people who understand the highs and lows of an Ops role, which can be quite lonely within a start-up full of developers and sometimes it is good just to vent over a glass of ! I run the bookclub as I had tonnes of highly recommended business books on my shelf which I never got round to reading and when I did, I wanted to talk to people about how to implement all the techniques I was learning about.I started the compensation survey as I couldn't find a lot of data on Ops compensation and wanted the ability to benchmark Ops salaries, have a reference point for salary negotiations and help people get the they deserve!
Penny Penatti Ops Stories has helped me a lot in the past 3 (has it been 3?!) years that I've been part of the community. Therefore spearheading the blog was a little way to say thank you to Ops Stories by increasing their presence and making people aware of what a great community it is.I remember writing down this initiative at 10 pm on a Friday night (I'm that cool). My idea behind it was the following:1. There are so many reading materials on what Operations Roles look like, and what the role consists of. But, I believe that the most beautiful thing about operations is that if you ask ops people about their role, there will always be variances depending on the industry, team size, and their own personal journey.2. Ops Stories consists of fantastic members and why not let them shine through blog interviews.3. These blog interviews have the following purpose: a) showcase Ops Stories awesome members b) a great way to enhance members personal brand and added bonus c) great PR for their startup
Ania Futrzyk I have always been passionate about delivering the best experience to customers and driving organisations to be customer-centric. Working as an Ops person and wearing many hats, I had the opportunity to combine my passion with operations and focus my work around Customer Operations. I was really surprised to find that there are so many Ops people working in Customer Operations roles and not being aware of it. I want to embrace the role of Customer Ops, understand how it differentiates from Customer Success, what is a career path for Customer Operations role and how we can support each other as a community to use the right tools and metrics to set companies up for success via Customer Operations.
Why is this important?
Every time we organise this meeting, we realise a couple of new things, we see how we can do it better. We currently have two things we want to improve on:
- Get more people in the board meeting, have them help us answer the crucial questions and contribute with feedback.
- Give our Core Team more power in the community. I'm sure you're all aware of how much Laura, Penny and Ania have worked to help bring Ops Stories to the next level, we haven't been giving them enough support.But we will, here are some of the changes you can expect to see in the future:
- Our Core Team members will have the Ops Stories logo emoji after their name on Slack so that when they ask you for your cooperation, you know where it's coming from, and it's with Ops Stories interest at heart that they ask you to help them out.
- We're going to be pushing their messages more actively.
- Give them more exposure in general.
What is our next priority?
Improve engagement, we've grown and with that growth, it's hard to keep the conversation going. Even if we're all in this together, being ops people in start-ups, it's sometimes difficult to know who to ask the question to. That's why we're coming up with a couple of initiatives that will hopefully make you all feel better about sharing your questions, experiences, wins, ... Watch some of our efforts deployed over the next couple of months.
How can you get involved?
- Organise something for Ops Stories, we'd love to help you kick off your project
- Share your feedback with us at any time of the day or night. It's incredibly precious to us and we want to hear from you
- Volunteer to join in with our next board meeting as a guest. It will require some prep work and involvement on your end, but we'd love to expand the number of voices in our meeting.
Looking forward to keeping building a strong community,
Aušrinė and Astrid