How we work
Six things we actually hold each other to. They are here so you can tell whether you would enjoy this before you write to us, and so we can be held to them once you do.
- 01
Ship, then learn
Something in front of a user teaches you more in a day than a month of planning does. We would rather put out a small version that is slightly wrong than hold a perfect one back. The work that counts is the work someone else can open.
- 02
Sit with the person using it
Nobody here builds from a spec they got secondhand. You talk to the person with the problem, watch them try the thing, and let what you see rewrite your plan. Every layer between you and them makes the product a little worse.
- 03
Own the whole thing
There is no ticket queue and no one to hand it to. Find a problem and it is yours, whether or not it sits in the part you were hired for. Some weeks that is heavy. Most weeks it is the best part of the job.
- 04
Say what is broken
We would rather hear the bad number early than a good story late. If the model is wrong, the demo is held together with tape, or the customer said no, say it plainly. Nothing gets fixed while it is still being oversold.
- 05
Depth under the surface
The interface should be simple. What sits under it should not be. There is real research beneath this product and we hold it to a standard that survives someone checking our work. Easy to use is not the same as shallow.
- 06
Change your mind in public
Being wrong quickly is cheap, and we treat it that way. Say what you believe, say what would change it, and when that arrives, change. Nobody loses standing here for dropping a position they argued hard for last month.