Skip to content

What is Broccoli?

Broccoli replaces the patchwork an engineering org normally stitches together to run itself — a spreadsheet for 1:1s, a slide deck for quarterly goals, a separate JIRA dashboard, a separate GitHub metrics tool, and an ad-hoc Slack-based access-request process — with one web application, one login, one source of truth.

Success is a manager (and everyone above and around them) never having to open a second tool to know the health of their team.

Who it's for

Ten roles, each scoped to see only the slice of data they're entitled to:

RolePersona
ManagerEngineering Manager — owns a team's roster, 1:1s, goals, quarter and roadmap
Team AccessA team member — read-only view of their team's roadmap and JIRA Live
AI AgentA programmatic, read-only credential scoped to one team
Director / ExecutiveRead-only rollup across every team that's granted them access
Program ManagerCross-team rollup, plus edit rights (status/priority/dates) on granted teams
Product ManagerFull read/write on one or more granted teams' roadmaps
ArchitectSame model as Program Manager, framed around technical rather than delivery oversight
Org AdminOnboards Manager/Director/Executive accounts, reviews the org-wide audit log
Super AdminBootstraps whole companies (workspaces) and their first Org Admin

See Roles & Permissions for the full picture, or jump straight to the guide written for your role:

What you get

  • Team roster & 1:1s — an employee directory with skills, growth areas, communication preferences, and a dated 1:1 notes history per person.
  • Goals & OKRs — per-employee goals rolled up into a team dashboard.
  • Quarterly planning & KPIs — fiscal-quarter planning with a capacity plan and a KPI tracker.
  • Roadmaps, synced to JIRA — Planning vs. Published modes, with automatic ticket-key linking so status flows in live instead of drifting out of date.
  • JIRA Live — search, transition and edit real tickets without leaving Broccoli.
  • GitHub metrics — cycle time, review load, contributor leaderboards, and AI-assisted-code detection, exclude-list driven so everyone shows up by default.
  • Knowledge Graph — a searchable graph of how JIRA issues and roadmap items relate.
  • Multi-tenant administration — an Org Admin / Super Admin hierarchy with a real approval workflow for who gets access to what.

Ready to set one up? See Creating a workspace.