This is something that we've slowly been getting better at, and we're trying to stay thoughtful about it while we do it.
So about 5 years ago, I started this by trying to write down the fundamentals about how
I make decisions, so that our community could better understand why things work. The result has been
live on our public website for quite a while, broken down into a sort of "plinko board" of actions that we always strive for, and actions we try to avoid. It's sort of like a hybrid of a SOP and a living breathing action-oriented version of our community values, documented:
We always:
...help unlikely groups of likeminded people form relationships.
...focus on people and their interactions, and the formation of relationships.
...help people tell the stories of the experiences they have in Philadelphia.
...trust people to do the right thing.
...guide people to being good citizens of Indy Hall and of Philadelphia.
...support people in their goals of building businesses to last, in Philadelphia and for Philadelphia.
We never:
...do anything against our community’s interest.
...focus on desks or square footage.
...create something only because we think we’re supposed to.
...accept the status quo.
...accept a "no" at face value.
...compromise our core values.
...prioritize a transaction before a relationship.
Every day, we:
...keep people at the center of every action, interaction, and decision.
...welcome new community members, and make it clear that Indy Hall is theirs, not just ours.
...always look for a way to say yes.
...teach others in our immediate and neighboring communities how we operate.
I literally use these guidelines for decision making 100x a day, and it's awesome to watch my team and even members use and reference this when figuring out how to make things work.
A simpler version that we put on our welcome one-pagers, and include as a major part of our tour, is to:
- Look after yourself
- Look after each other
- Look after this place
In all cases, we're SUPER careful in our language choice to make it clear, before providing SOP documentation, that anything documented is meant to help, but not constrain. Any "rule" is open to being adjusted, adapted, or rewritten to help us better achieve our goals working together.
I'm curious how others have found balance between SOP and handbook-style documentation, and still allowing/encouraging people to "color outside of the lines" and trusting people to do what's right?
-Alex