What we're building

One of the principles we try to hold ourselves to is transparency: not just in the framework content, but in how we develop it. That means sharing direction early, being clear about what we're prioritising and why, and letting the needs of real CS teams drive what comes next.

Re-assessment reminder

Planned

Download a calendar invite to re-take the assessment in 90 days and keep the improvement loop moving.

Resume an in-progress assessment

Planned

Pick up where you left off instead of starting the questionnaire over.

Gap-to-next-stage view

Exploring

A visual map of the capability gaps between your current stage and the next, and the playbooks that close them.

Concept stage

Anonymous CS score submission

Planned

Optionally share your maturity score, industry, and company type to contribute to aggregate industry benchmark data.

What we've recently shipped

Items that have moved from the plan into the live framework. We keep them here so the history of the framework stays visible.

Site-wide search

Shipped

Find any metric, playbook, principle, or glossary term from a single search box.

How we decide what to build

Every addition to Distilled CS starts with the same question: does this help a CS team do their job better? Not more comprehensively, not more impressively, but more usefully. We weigh that against the stage the team is at and the constraints they're actually working under.

If you have something specific you'd like to see, or want to help build, document, or fix something on the framework, the contribute page walks through how to get started on GitHub. You can also reach out via the contact page.

Start typing to search the framework.