The Baseflower role functions like an abstract class in —it provides a shared foundation that applies to everyone in the organization but isn’t a fully defined, individual role on its own.
How Baseflower is like an abstract class you ask?::
- It’s not a standalone role – Just like an abstract class cannot be instantiated, the Baseflower role isn’t meant to cover all responsibilities by itself.
- It defines shared expectations – It sets the common values, principles, and behaviors that everyone upholds.
- It can be extended – Each person has specific roles (like Developer, Product Owner, or Designer) that inherit from and add to the Baseflower role.
- Some elements are enforced, others are flexible – Just like an abstract class can have both concrete and abstract methods, Baseflower includes shared commitments while allowing individuals to define their own responsibilities within their roles.
Yeah, yeah, so what does that mean?
Rights – What you are entitled to
- Freedom in how you work
- Autonomy and decision-making power
- Being heard and feeling safe
- The right to grow and develop
- Space to think, act, and experiment
- 10% time for self-directed projects
Accountabilities – What you are responsible for
- Collaborating and actively supporting each other
- Creating an inclusive and respectful environment
- Taking responsibility for your work and impact
- Helping when asked and offering support proactively
- Speak up, don’t hide your thoughts