Team Roster & 1:1s
The roster is the spine of a Manager's team — most other features either read from it or roll up into it.
Adding people
For each person, a few fields drive features you'll only notice are missing later:
| Field | Why it matters |
|---|---|
| Identity, and how leadership rollups attribute work | |
| GitHub username | Without it, this person's commits and PRs never appear in any metric |
| 1:1 cadence and last 1:1 | Drives the "who is overdue for a 1:1" prompts |
| Role, level, sub-team | Grouping and filtering across every view |
| Skills, strengths, growth areas | Feeds career development and the Knowledge Graph |
Adding someone to the roster does not give them a login — roster entries and accounts are separate on purpose, so a manager can track someone who isn't a Broccoli user yet.
Team Graph renders the roster as an interactive org chart once it has a few people in it.
Running 1:1s
Open a person to get their full profile: skills, strengths, growth areas, communication preferences, career development notes, goals, collaborations, and private notes.
- Notes are one entry per person per date.
- Goals carry status, priority, milestones, success criteria and target dates — a person's development goals, distinct from roadmap items.
All of this is private to the manager's scope. Directors see a team's roadmap through Portfolio; they never see 1:1 notes, goals, or a manager's private journal.
My Workspace
A manager's own journal, separate from anything attached to a person — reflections, plans, brainstorms, performance drafts. Taggable, pinnable, archivable, and never shared by default.