isselthal Mission & Values
Mission
We exist to help worthwhile projects succeed and to build digital products that are enjoyable, useful, and respectful of the people who use them.
We understand our role as enabling people through technology. That means support and tools for experts doing difficult work that matters, especially in the public interest. It also means building tools for people to use directly. We do both on the basis of an ethical framework of engineering: technology should serve people and be a useful tool to them. Software plays an important role in public infrastructure and has effects at large scale on society, and that deserves deep respect and careful work. At the same time, an individual user should find that the software they use treats them with respect, wants what is genuinely best for them, and brings them joy.
Values
Builders, not consultants
We deliver products, not spreadsheets. We prioritise building, testing, and improving useful things; processes, meetings, contracts, and documentation should enable the work, not replace it.
Are we creating something, or just talking about it?
We want to be a creating force in the world. Not art, but the same instinct: something exists at the end that did not exist before, and we made it. There is a piece of us in it, and that is worth something to us. A working life is a long time to spend on things that never produce anything. Creation gives you plenty of opportunity to gather scars, and the scars are where the knowledge comes from. You cannot advise on something you have never had to build.
Expertise, not hours
We hold ourselves to being good at what we do. Depth takes work to gain and work to keep, and we would rather turn down a project than build something that could come off an assembly line.
Does this need what we are good at?
Our aim is to be real experts. We think it matters that people strive to be good at what they do and to be the best they can be at it, and we hold ourselves to that. We want the people who work with us to expect it too. For our part that means focus: expertise takes years to build and continuous work to keep. You cannot be sharp at everything, so we choose what we want to be genuinely good at and keep going deeper there. Which means saying no to most things. We think there is an obligation in having built expertise: it is worth pointing at problems that need solving, not spent coasting through work that does not matter.
Improving, not perfect
We believe in deliberate growth and continuously improve how we work. We learn and develop our skills. We also accept that complex work involves mistakes. When they happen, we take responsibility and work through them openly.
Are we better than we were on the last project?
When we get things wrong, do we say so?
We believe perfection is fundamentally unattainable. What we believe in instead is deliberate practice and that small improvements compound over time to make us better in the future. It follows that mistakes are unavoidable. What matters is how you deal with them. We believe you should honestly name them, take responsibility, and work through them even when it is uncomfortable - and that this applies to human errors as much as professional ones. Admitting a mistake and improving from it is a strength, not a weakness, and the right response to someone doing so is to help work through it rather than to assign blame. With that comes the understanding that other people are not perfect either and they deserve the same grace as we do. When others get it wrong we work through it with them instead of judging them blindly.
Honest, not agreeable
We say what we believe is best for the project, even when it’s difficult. We’re clear about what we don’t know.
Are we saying the uncomfortable thing?
Are we clear about what we don’t know?
It is comfortable to agree, and there is a trap in wanting to please everyone. But an expert has a responsibility to give honest answers, not easy ones: what is wrong with a project, what the risks are, what will be difficult, and what should not be built at all. Most importantly, that includes being clear about what they know and what they do not. What should guide the answer is what the project needs, even when that is uncomfortable, goes against what a partner wants to hear, or costs us work.
Craftsmanship, not commodity
We build things carefully, and we choose carefully what to build. We owe that to the people who use or experience what we make, not just to whoever is paying for it.
Would we be proud to have our name on this in public?
Some engineers wear an iron ring: a reminder that the duty is to the public, before the client and before the fee. Doctors take an oath to much the same effect. Software has called itself engineering for decades, often without taking on the same responsibility. However, the stakes are increasingly similar. Software now runs infrastructure people cannot opt out of: how they experience the world and inform themselves, but also how institutions police them, pay them, and insure them. That is public engineering, and it carries the same obligations. Building well and building things worth building are the same duty - a shoddy system fails the people who depend on it, and one that should not exist fails them whether or not it works.