Principles for Building

The companies within Heuristiqs operate in different markets and build different technologies. They are not expected to resemble one another. They are expected to share a standard. These principles state that standard and apply to every company Heuristiqs creates or controls, and to every product, system, and service those companies bring into the world.

How each company meets the standard may differ. The standard itself does not.

1. Understand the consequences of what we build

Before a company builds something, it is expected to understand who will be affected by it, how, and what happens when it fails. The weight of that analysis scales with the stakes: a system that touches a person’s finances, identity, health, safety, or legal standing is examined more carefully than one that does not.

Understanding consequences includes asking whether a thing should be built at all. A capability that is technically achievable and commercially attractive can still be the wrong thing to make. Our companies are expected to decline such work, and Heuristiqs will support that decision.

2. Design with care

Care is a property of the work, not a sentiment about it. It shows in products and services that behave as described, fail in ways that protect the people relying on them, and are tested to a level appropriate to the harm a failure could cause. It shows in communication that does not mislead, in choices made on a customer’s behalf that protect rather than exploit them, and in the collection of no more information than a task requires.

Where a company makes or automates decisions that affect people, those decisions are made in a way that can be examined afterward, and a person retains meaningful authority wherever the cost of an error would fall on a person.

3. Make responsibility clear

Every product, service, and significant commitment has a named owner. Every company has a leader who is accountable for it. Heuristiqs is accountable for the standard. When something goes wrong, there is never a question of who answers for it.

Responsibility also runs outward. Our companies state plainly what their products do, what they do not do, and what they are not designed for, and they do not permit a product to be marketed beyond that boundary. When a failure affects the people who rely on us, we tell them, we fix the cause, and we record what we learned.

4. Earn trust through performance rather than promises

Trust is not requested. It is accumulated through products and services that do what they are said to do, over time, under scrutiny. Our companies do not describe a capability they have not built or a safeguard they have not tested. They compete on the quality of what they deliver.

Where a company operates in a regulated domain, compliance is treated as a floor, not a ceiling. Meeting the letter of a requirement is not the same as deserving the confidence of the people it exists to protect.

Application

These principles are considered at the formation of every company, in the review of significant decisions, and whenever a failure would carry material consequences for the people a company serves. A company that cannot meet them does not go to market until it can.

Heuristiqs reviews this document periodically and revises it when experience shows it should be revised. Questions about it may be raised through the channels on the Contact page.