Your org chart

Structure is how judgment scales. A CodeAF manager can start a sub-team, a new team under its own, run by a new manager conversation, and that manager can do the same. Describe the shape in one sentence and the managers build it, one level at a time.

Try it in CodeAF

How the chart holds together

Every manager below the top is also a member one level up. The platform manager runs platform and also sits in your team, here called shop-api, as one of its members, which is what ties the levels together. It is handed its brief with you were started to manage the team "platform", under "shop-api": you run it and report to the manager who started you.

Orders go one level down and reports go one level up. A manager directs its own members, and a sub-team's manager is one of them, but it never directs that sub-team's members; it may read them. Work still flows through every level without you: a worker two levels down finishes, its manager wakes and posts the result up, and your team manager wakes and tells you.

A sub-team spends from its parent's pool: its daily cap is the parent's cap times sub-team share, 50% unless you change it. Teams nest three levels deep by default (team depth), and a start past that is refused with the reason.

A manager on ◇ asks (Alt+A) shows you a card for each hire, reading @platform: a new team "platform" under yours, managed by it. The managers it starts begin on ◇ YOLO, so their own hires do not ask unless you switch them too.

One manager over everything

On the teams page, All teams has its own + Manager. That global manager's members are the managers of your top-level teams and nobody else: its directives reach them, never their members, and their reports and questions reach it before you. While it exists, the top-level managers are teammates who can post to each other directly. A manager gets its @handle from its first turn, so send each new manager one message before the global manager needs to reach it.

Things to build

• A software company in one message: a global manager starts product, backend and qa teams with their own managers, and brings you one table when all three report. Build a software company
• A platform org: one sentence to a manager gives a platform team whose manager starts an api and an infra sub-team, each with its own manager.
• A spend tree: a daily cap on each top team, half of it for every sub-team, and one card to raise or stop when a pool runs out.
• A three-level relay: a worker in a sub-team counts or checks something, and the answer climbs through its lead and your team manager to you with no message from you.
• A lighter lead: move the testers into a testing sub-team under their own lead, and the parent talks only to that lead. Put a manager over other managers

Go further