Skip to content
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

Internal Processes #370

Open
thebestmensch opened this issue Jun 12, 2019 · 8 comments
Open

Internal Processes #370

thebestmensch opened this issue Jun 12, 2019 · 8 comments
Assignees
Labels
operations leadership tasks not specific to any specific team

Comments

@thebestmensch
Copy link
Contributor

thebestmensch commented Jun 12, 2019

Goal:

Define the world of processes folks would like defined. Easy, right :trollface:? But seriously, if we plan to grow (leadership or membership), we need to have how we operate written down somewhere. Consider this issue the place to add anything you ever wish we had documented, or if you ever wanted to do something but didn't know how. I'll keep the "Master List" of requested processes up to date.

PS: what I mean by "process" is a document that anyone can follow and complete the task.

Master List

  • Levels of commitment to OA and respective obligations (e.g. leadership vs general member)
  • How to onboard/offboard a member to a higher level of commitment (e.g. to leadership)
  • How leadership decides to commit to doing something (seems silly, but we don't really have a process for when we have opposing views on proposed work. For example, if Mateo thinks this issue is a bad idea, what do we do? Do we trust that these adhoc conversations are always going to produce the best outcome for our membership? Are we documenting why something was or wasn't done?)
  • how to set an Open Austin project up with cloud hosting
  • how to book meeting rooms through the Austin Public Library
@thebestmensch thebestmensch added the operations leadership tasks not specific to any specific team label Jun 12, 2019
@thebestmensch thebestmensch self-assigned this Jun 12, 2019
@thebestmensch
Copy link
Contributor Author

Things I think we should define:

  • Levels of commitment to OA and respective obligations (e.g. leadership vs general member)
  • How to onboard/offboard a member to a higher level of commitment (e.g. to leadership)
  • How leadership decides to commit to doing something (seems silly, but we don't really have a process for when we have opposing views on proposed work. For example, if Mateo thinks this issue is a bad idea, what do we do? Do we trust that these adhoc conversations are always going to produce the best outcome for our membership? Are we documenting why something was or wasn't done?)

@mscarey
Copy link
Contributor

mscarey commented Jun 12, 2019

how to set an Open Austin project up with cloud hosting

@mateoclarke
Copy link

  • how to book meeting rooms through the Austin Public Library

@thebestmensch
Copy link
Contributor Author

thebestmensch commented Jun 17, 2019

  • process for member input or questions and our response.
  • process for inventory (shirts, stickers, anything we give out)

@mscarey
Copy link
Contributor

mscarey commented Jun 17, 2019

How to book a meeting room for Capital Factory (and who the best contact is).
How a sponsor can make a donation (!)

@thebestmensch
Copy link
Contributor Author

thebestmensch commented Jun 17, 2019

This one is a big one, would love input @open-austin/leadership !

I worry about biweekly checkins becoming more of a problem than a solution as the leadership team expands. I want to be as efficient as possible and process-ize the shit out of this, but I also don't want this to feel like work to anyone. Here's a few road bumps I've experienced when a remote team scaled (not all solvable) that might catalyze a discussion:

  • How do we keep topics relevant to majority? How do we ensure someone isn't frequently in the minority?
  • How do we limit the topic list to things that benefit from in-person discussion?
  • How do we limit friction when adding a next step to task management?
  • How do we decide things (ideally in a timely manner)?
  • How do we politely get back on topic when someone goes on a tangent?

Two big ones for me personally right now:

  • How do we easily know if a time sensitive task is on track?
  • How do we easily know all of OA's ongoing initiatives.

@Kristen5
Copy link

Kristen5 commented Jun 17, 2019

* how to book meeting rooms through the Austin Public Library

@mateoclarke Here is the link! https://library.austintexas.gov/meeting-rooms/how-to-reserve

@avickers
Copy link

avickers commented Jul 6, 2019

Should there maybe be a project champion tier between OA leadership and general member?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
operations leadership tasks not specific to any specific team
Projects
None yet
Development

No branches or pull requests

5 participants