Teams
Every team, and what it is actually for.
A team is not just a list of people who share a manager. It has a purpose, a set of responsibilities it owns, objectives it is working towards, and a capacity that changes every time somebody goes away.
Purpose before headcount
A team page opens with what this team exists to do and what it owns. The member list matters, but it is not the answer to "what does Operations actually handle?"
Capacity you can reason about
Who is here this week, what is due, and what that means in practice. Not a productivity score — the arithmetic an owner would do on the back of an envelope, done reliably.
Teams are not the only structure
People sit in a team, report to a manager and own responsibilities that cross both. Orglume keeps those three as separate structures because in a real company they rarely line up.
In this area
5 pages under Teams.
Each one is its own surface in the product, and each one is here because it does something the others do not.
Team pages
Manager, members, purpose, responsibilities, objectives and skills in one view.
ReadTeam capacity
Who is available, what is due, and whether those two numbers work.
ReadPurpose & ownership
What this team is accountable for, written down once.
ReadWork that crosses teams
The responsibilities that do not sit neatly inside one box.
ReadLocations
One workforce, several places, without a separate system per site.
ReadThe rest of Orglume
This is one part of one loop.
Run your team with clarity.
From the moment someone joins to the day their responsibilities are handed over, Orglume keeps your people, their work and your organization connected.
Set up from a spreadsheet · Nothing about the AI is metered · [email protected]