no funny hats needed
swarmrise uses simple words and concepts. No esoteric vocabulary or neologisms, no ceremonies, no circles, no personal development gibberish. It's a tool, not a religion.
Simple ideas that guide how swarmrise works.
swarmrise uses simple words and concepts. No esoteric vocabulary or neologisms, no ceremonies, no circles, no personal development gibberish. It's a tool, not a religion.
To draw the organization's big picture is not enough to give someone confidence and direction. swarmrise is centered on you as a member of that organization, highlighting your roles, your teams, your relations, and your decisions. On a daily basis, you just want to know what others expect from you, and how you can help and act.
swarmrise is driven by purpose. The organization must have a global purpose, but every team and every role should start with a clear purpose. People are smart, they can figure out what to do and how to do it when they know why they're doing it.
One big difference with hierarchy is the possibility to get rid of full-time decision-makers. Everybody makes decisions all the time, thus this talent is not that rare. By enabling a decide/commit/execute self-owned scheme for every role, you highlight the much rarer ability of good execution. People who could actually do stuff should feel more empowered and appreciated.
Bad behaviors flourish when either you're not aware of them or you can't do anything about them. Of course, a governance model can't guarantee ethical conduct by itself, but it can encourage it by letting the members know what is happening, and by letting them make decisions accordingly. swarmrise uses transparency, traceability, and memory of information as default mode (when it doesn't contradict personal data rights or sensitive intelligence info), and proposes a decision model which is open to any role.
Org charts and job descriptions are often outdated, partly because modifying them is a pain. swarmrise allows easy modification, by every member, of every piece of the organization. It's not risky because, by letting everybody know who did what, swarmrise forces members to think before they act. And by the way, if you don't trust people, you shouldn't hire them in the first place.
swarmrise proposes a public copyleft template library for teams, roles, and policies, so the innovations from some can be reused freely by others. By authoring and maintaining public templates, you can help other organizations and get useful feedback for you, one stone two birds.
Hierarchy is a very simple concept. That's why it's dominant despite not being the most efficient system. swarmrise tries hard to add as little complexity as possible and to keep things easy to explain and operate. There's a limited set of concepts and rules from which you can grow your governance to fit your organization.
swarmrise is and will stay a work in progress. Feedback and contributions are more than welcome. These principles are just a backbone, let's see where the whole thing will go.
swarmrise is both a governance model and a tool.
By keeping one role per member, you can use it as a simple org-chart tool. By embracing multi-role membership, team autonomy, and consent-based decision-making, you move into a genuinely different way of organizing. The transition is progressive -- adopt at your own pace.
In traditional organizations, one person has one job title. In swarmrise, a member can hold multiple roles across multiple teams. A person might be the Product Lead in the Product team, the Secretary in the Operations team, and a Data Analyst in the Finance team -- simultaneously. This reflects how people actually contribute: across boundaries, wearing different hats depending on context.
Checks and balances within every team.
Every team starts with three special role types as a framework. These three exist by design to create checks and balances. No single person accumulates unchecked authority within a team.
Provides direction and facilitates the team's work. The leader coordinates but does not command. They represent the team in the parent team, creating a natural connection between levels of the organization without creating hierarchy.
Ensures documentation, procedural integrity, and organizational memory. The secretary keeps things honest and traceable.
Mediates conflicts, ensures fair process, and protects minority voices. The referee prevents power grabs.
The triad is a starting point, not a rigid constraint. Organizations may eventually define their own default role types. But the principle of distributed authority within teams is non-negotiable.
Not consensus. Consent.
The decision model follows a three-step process. This is not consensus, where everyone must agree. It is consent, where no one has a principled objection. Silence is consent.
Any role holder can propose a change.
Members ask questions to understand the proposal.
The proposal is accepted unless there are valid, reasoned objections.
The existing decision journal, which records all changes with before-and-after diffs, is the foundation on which the consent process will be built.
A map of connections, not a top-down pyramid.
Teams connect to other teams through their leader roles. A team's leader holds a corresponding role in the parent team, creating a natural link. But this is a connection, not a command chain. The parent team does not dictate to the child team. The leader represents the child team's interests upward and carries context downward.
Messaging where governance is native, not an afterthought.
swarmrise will include a communication layer tightly integrated with the organizational structure. This is not a generic chat tool bolted on -- it is communication that understands teams, roles, and governance.
The building blocks of living governance.
Discussion items that can be addressed synchronously in meetings or asynchronously online. A topic can become a proposition, go through clarification, and reach consent -- all without requiring everyone to be in the same room at the same time. This is essential for distributed and remote organizations.
The permanent rules a team or organization gives itself. Authored by role holders, scoped to teams, versioned, and visible. Unlike decisions which record a single change, policies codify ongoing expectations. They answer: how do we operate here?
A public library where organizations can browse templates for team structures, role missions, duties, and policies. Copy them, adapt them, publish your own. For newcomers, templates lower the barrier to adoption. For veterans, templates are a way to share what works.
Boundaries that are deliberate and defended.
No tasks, no kanban boards, no sprints, no Gantt charts. swarmrise defines who is responsible for what and why. How those people track their work is their choice. swarmrise governs; it does not micromanage.
If a feature makes it easier to concentrate power, it does not belong in swarmrise. The system is designed so that authority is always distributed and accountable.
No esoteric vocabulary. No certification programs. No mandatory ceremonies. swarmrise uses plain language and simple concepts. If someone needs a training course to understand the tool, we have failed.
swarmrise is openly, proudly a work in progress. The commitment is to the principles, not to the current feature set.