How our teams work

This is the company Flagon is built to be, described through the teams that run it: what a team owns, how it spends its days, and how the whole thing stays coherent without much process. Small by design explains why we stay small; this goes a level deeper, into how a team actually works. For the current shape of the company, see the teams page.

Every team is a little startup

The unit here is a small team that owns something whole, and each one runs like its own little startup inside the company. It has a mission, a lot of rope, and the freedom to figure out how to do the work. It isn't handed a backlog and told to burn it down. It's handed a problem worth solving and trusted to solve it.

That framing does real work. A startup owns its outcome, not just its output: it talks to the people it serves, decides what matters and what to ignore, and moves without asking permission for every step. We want each team to feel that way, because that's when people do their best work and care about the result like it's theirs, which it is.

One person or ten, the page stays true

A team here might be a few people, or one person wearing the hat for now, or a group that's still filling out. We're not apologizing for that. It's the plan: we grow into this shape on purpose, adding people to a team when the work clearly needs them and not before.

We describe a team by what it owns and how it works, not by how many sit on it. Engineering ships in the open whether that's one person or a dozen. Design holds the taste bar whether or not the title is on anyone's door yet. Read each page as the design, true whether the team is one person today or ten later.

How a team gets its mandate

A team's mandate is a problem to own, not a list of tickets. Someone can say, in a sentence, what this team is for and how we'll know it's working. That clarity does the work: when a team knows what it owns, it can make its own calls about how to get there, and tell the difference between the work that matters and the work that just looks busy.

Mandates come from the work and the people closest to it, not from a plan handed down and defended. When a team's shape stops matching the problem, we change the shape. See how decisions get made for who makes which call.

Autonomy without drifting apart

Small autonomous teams could easily drift into a dozen companies that happen to share a logo. We keep that from happening without heavy management, mostly by being loud in public. Work happens where people can see it: in GitHub, in Discord, in this handbook. When the reasoning is out in the open, teams stay aligned by reading each other instead of by sitting in a meeting about alignment.

The glue is shared, too. Everyone works from the same values and operating principles, builds on the same product, and holds the same bar for quality. That shared floor is what lets us hand a team the rope and trust it not to wander off. Autonomy isn't isolation; it's freedom inside a set of things we all agree on.

If a team ever feels boxed in, or so loose it's lost the thread, that's a bug. Say so, on GitHub or at hey@flagon.io. The team model is something we keep tuning, not a thing we set once and walk away from.