How We Work at Conduction
Conduction's mission, vision, and core values live on identity.conduction.nl. One of those values is being open. This handbook is part of putting that into practice: a public record of how we operate, how we manage what we do, and how we measure ourselves.
Being Open
Conduction is an open company. Being open is about more than open-source code. It also means being open about how we work and how we manage what we do. That's why this handbook exists, and it's why it lives on a public site instead of an internal wiki.
In practice:
- Our handbook is public. You're reading it. The source lives in ConductionNL/.github.
- Our roadmap is public. GitHub Projects shows what's next, what's in flight, and what's shipped.
- Our specs and decisions are public. Every change starts as an OpenSpec proposal and lands as a reviewed pull request. The reasoning lives in the issue and the PR, not in private channels.
- Our pipeline is public. Hydra, the agentic CI/CD that builds our apps, is itself open source.
- Our identity is public. Brand, voice, and visual identity live on identity.conduction.nl.
If you can't find something, that's a documentation gap, not a privacy boundary. Ask, and we'll publish.
How We Operate
We work in small, self-directed teams using agile methods. We prefer GitHub Issues over lengthy emails, working software over documentation, and concrete results over process theatre.
- Our work lives on GitHub — github.com/ConductionNL
- We build on Common Ground — open standards for Dutch government software
- We eat our own dog food — we use the products we build
KPIs and Goals
We set yearly Key Performance Indicators to know if we're on track. KPIs may shift year to year, but the aim is steady improvement. Everyone should be aware of the current goals and KPIs — ask your team lead for the latest version.
What we measure ties directly back to our identity: publishing code that's actually used, building accessible software, and making customers happy.
Project Management
Every project starts with a kick-off. If you haven't had one, ask for it — never work on assumptions.
- Scope, budget and planning are defined in the quotation
- Anything outside the quotation scope: discuss with your supervisor first
- All work must be traceable to issues
Further Reading
- About this manual — meta-overview of the handbook itself
- Organizational structure — roles, responsibilities, team structure
- Way of working — sprints, issue flow, code standards
- Release process — branch model, versioning, deployment
- Onboarding — buddy system and getting started
- Customer support — support flow and complaints