Watching people just tells you who is busy. Watching projects tells you what is actually getting built. 🏗️
We recently updated the platform core to map directly to your actual work units. Previously, the system organized insights around teams. We changed this because a single engineering group often splits attention across multiple different initiatives. Measuring a team blends all that context together, making it hard to see the true status of a specific deliverable.
The shift to project-centric tracking
We restructured our database tables, APIs, and schemas to focus entirely on projects instead of teams. This structural change aligns our infrastructure directly with how you actually think about your business goals.
Engineering groups rarely work on just one thing. When you track a team as a single unit, a high velocity score might just mean they closed out dozens of minor bug fixes, while your critical feature remains stalled.
By pinning data directly to the project level, the noise drops away. You stop looking at generic activity metrics and start looking at real progress.
Sharper morning reports
Now, when your morning report arrives, the insights tie directly to the specific deliverables you care about.
You see exactly who drove the work forward and where momentum slowed down for that exact initiative. If a project stalls, you know immediately. You do not have to guess if the team was busy elsewhere or simply blocked. 🎯
This update reinforces our core philosophy: meaning over motion. AI-generated code broke the old metrics, so counting commits tells you nothing. You need to know if the engineering work is actually producing something useful.
It is a deliberate shift that gives non-technical leaders, engineering managers, and investors a clear, credible view into the work. You get the leverage to manage effectively, without needing to dig through a single ticket board. 🚀