How the Rust project organizes, tracks and reviews its goals

What happened and what to do

According to the account by Tomáš Šedovič, program manager at the Rust Foundation and co-lead of the goals team, his talk at Kangrejos 2026 presented how the Rust project organizes its overall goals, tracks progress and changes them over time. One aim is to ensure that people who take on a goal have the support they need. The talk was motivated by the fact that the Rust for Linux project inspired several current project goals, so the internal process was explained to those developers.

For a company that maintains technical initiatives with many contributors, the case shows the need for an explicit goals process: defined owners, traceable milestones and periodic reviews. In practice this can be implemented with a dashboard of initiatives showing status, dependencies and recorded scope changes, plus automated routines that alert when a goal stalls or loses support. When part of the work depends on external projects, it is worth mapping those dependencies and monitoring the changes that affect them.

How the consultancy can help

We can diagnose how your team defines, tracks and reviews technical initiatives and propose a goals governance model with owners, milestones and review criteria. Implementation includes a tracking dashboard with automatic alerts for stalled goals or dependencies at risk.

Next step

If your team runs several technical initiatives and struggles to know the progress of each one, send a short description of your case. We will reply with a scoped proposal for diagnosis and implementation.