How we work
We take a problem apart until we understand it, shape each part with the next one in mind, and look hardest where the parts meet.
The method
Take the problem apart
Understanding comes before design. We begin by writing down what a product will meet in the world: who will use it, on which device, in which language, over what kind of connection, and what should happen to what they share.
A school gate, a family’s shared phone and a developer’s terminal each ask different questions.
Shape each part to fit
Each part is made with the next one in mind, from what a person sees and touches to the services and safeguards underneath.
Parts that fit do not need forcing, and a system made of them can be explained to the people who rely on it.
Look hardest where the parts meet
Most failures happen at the joins: a message crossing between languages, a phone folding halfway, a school payment waiting for its second signature.
That is where we look hardest, and we keep looking after release.
In our products
Pearl
A translation appears under the original message, never in place of it, so nothing is lost when a conversation changes language.
Brim
No entry reaches a school’s books until a second authorised person signs it.
TillDev
TillForge turns away a push that contains a leaked key or password.