Endurance · Core Values
Three values, said plainly.
These values guide how we learn a business, work with its people, and see a project through to daily use.
01 · Core value
Always learning.
Humility and curiosity, every day.
A freight desk, a law firm, and a kitchen each have rules that are easy to miss from the outside. We begin by listening to the people who work there. Their explanations, and especially their corrections, tell us what the software needs to do.
We want to leave each conversation understanding something we did not understand before. The systems we build should make that learning useful: a documented rule or a corrected answer can help the next person who encounters the same problem.
- In practice
- Ask more questions than you answer — a great second meeting is earned by the questions asked in the first.
- “I don't know yet” is a complete sentence — followed by going and finding out.
- Listen before you build — what the operator says shapes the system.
02 · Core value
Be of service.
Jump in. Make it happen.
Service begins with noticing what someone needs and taking responsibility for helping. Within the team, that means direct access to one another and a clear owner for the work.
For a customer, it means knowing who is working on the problem, what happens next, and when they will hear from us. We aim to make those things clear, even while the answer is still taking shape.
- In practice
- See it, own it — jump in without waiting to be asked.
- Direct access, no layers — when a teammate needs you, they get you.
- Acknowledge a partner’s question promptly, take ownership, and agree on the next update.
03 · Core value
Finish the job.
Shipped isn't finished. Used is.
A demo shows what is possible. Daily use reveals what still needs work: messy data, an exception nobody mentioned, a report that almost fits. We keep working toward a system the operator can run their morning on without us in the room.
That means reconciling the numbers, handling the exceptions, and finding the cause of a recurring problem. Our name recalls the Endurance expedition and the effort to bring its crew home. It is a reminder to keep responsibility for the people who depend on the work.
- In practice
- Launch is the midpoint — we stay until the system runs the client's day without us.
- The last 5% — edge cases, empty states, the awkward export — is the job, not extra credit.
- Reconcile to zero and fix the root cause — a patch that hides a problem is a debt, not a fix.