Okay, so what is a role? A role in Baseflow is:

• Driven by purpose – Every role exists to fulfill a specific goal or need within the organization.
• Defined by accountabilities – Clear responsibilities outline what the role is expected to deliver.
• Empowered by rights – The role comes with decision-making authority within its scope.
• Not limited by skills – Certain skills may be useful, but they are not a barrier—people can develop them over time.

This keeps governance flexible, inclusive, and focused on growth, ensuring that roles evolve as the organization does.

<nerd> intermezzo

In object-oriented programming, an abstract class is a class that cannot be instantiated on its own and is meant to be extended by other classes. It typically serves as a blueprint for derived (sub)classes, defining common attributes and behaviors that subclasses must implement or override.

So, before we pull out the UML editor, what does that mean for roles in Baseflow? Well, you can find out about that and the other more common roles in the sub pages.

</nerd>

Role definitions

Baseflower

Circle lead

Facilitator