How we set and track goals

The failure mode of most organizations is not a lack of effort but a confusion between activity and progress. We measure what shipped, not what was attempted. We define goals as outcomes, not as tasks, because the difference between the two is the difference between building something real and staying busy.

Outcomes over output

“Worked on the onboarding flow” is not a goal. “New users reach their first design output in under three minutes” is. At Nexma, we define goals as measurable end states because tasks are merely the means of arrival. Confusing the two is how companies sustain the appearance of progress for months without producing anything of consequence. And we refuse to tolerate that confusion, because in the domains we serve — defense, infrastructure, logistics — the cost of building the wrong thing is not an abstraction. It is measured in failed deployments and wasted capital.

Weekly shipping cadence

Every week, something ships to production. Not every week produces a major feature. Some weeks are infrastructure work, refactoring, or the repair of defects. But the cadence of shipping is non-negotiable because a week without a deployment is a week without learning. This discipline keeps the feedback loop tight. Ship, measure, adjust. The alternative — long planning cycles followed by large releases — is how startups build the wrong thing for months before anyone notices. We have seen this pattern destroy companies, and we will not repeat it.

Public accountability

Goals are visible to the entire team. Progress is tracked in shared documents, not private notebooks. When you commit to an outcome, everyone can see whether you achieved it. This is not about pressure. It is about clarity. When goals are public, misalignment surfaces early instead of festering into something far more costly. The Nexma team treats transparency in goal-setting as a structural safeguard against drift.

What we refuse

We do not engage in OKR theater. We do not conduct quarterly goal-setting workshops that produce forty objectives no one remembers by the following month. We keep the list short: two or three things that matter right now. If you are working on something not on that list, either the list is wrong or your priorities are. And we have the honesty to determine which.

Was this page useful?