OKRs Feel New. Our Capability Isn’t.

In recent years, OKRs (Objectives and Key Results) have become a widely adopted framework for strategy execution. Popularized in Silicon Valley and formalized at companies like Intel and Google, OKRs are often presented as a modern breakthrough in focus and alignment.

For Sente, however, the underlying logic is not new.

Long before OKRs became mainstream, we were operating from a discipline of intentional management — declaring clear outcomes, aligning capabilities to produce them, learning from gaps, and refining our approach through structured feedback loops. In other words, we have always managed by intention.

What OKRs provide is language and structure for something we have practiced for decades.

Intentions Produce Results — Not Hope

From the beginning, our work in Test Resource Management (TRM) and Lab Management has been driven by declared intentions — not vague aspirations.

We did not set out merely to “improve efficiency.”
We declared intentions around:

• Speed — accelerating time-to-market in environments where delay destroys competitive advantage.
• Autonomy — enabling labs and engineering teams to operate as accountable, self-directed systems rather than reactive service centers.
• Capability maturity — building systems that could learn, adapt, and improve over time.
• Competitive advantage — helping our customers outperform alternatives through disciplined coordination of shared test resources.

These are not accidental outcomes. They are the result of sustained intention.

Cost savings were often achieved — and frequently exceeded expectations — but they were rarely the primary aim. Speed, utilization, coordination, and capability came first. Cost improvements followed as a consequence of superior system performance.

That is fundamentally how strong OKRs work as well:
You aim at strategic leverage, not just expense reduction.

Essential Complexity vs. Accidental Complexity

One of our long-standing intentions has been to understand the essential complexity required to produce breakthrough results.

In capital-intensive test environments — aerospace, defense, automotive, medical — the systems are inherently complex. Equipment is shared. Schedules are dynamic. Programs compete for constrained resources. Compliance requirements are real.

You cannot eliminate that complexity.

But you can eliminate accidental complexity — the friction created by misalignment, poor coordination, missing data, and lack of shared visibility.

Our intention was never to make things superficially simple.
It was to design systems capable of managing essential complexity well.

That required:

• Study
• Experimentation
• Iteration
• Learning from failure
• Accumulating operational knowledge over years

In OKR language, you might say we have always treated objectives as hypotheses about what will create leverage — and key results as measurable signals of whether our understanding was correct.

We did not assume we knew everything.
We declared what we intended to produce, measured what happened, studied the gaps, and improved.

Intentions Cascade — Vertically and Horizontally

Over time, we learned something critical:
Intentions do not live at one level of an organization.

They cascade.

An executive may declare an intention to improve time-to-market.
A director may declare an intention to increase equipment utilization.
A lab manager may declare an intention to reduce scheduling conflict.
An engineer may declare an intention to complete validation without delay.

If these intentions are not aligned — vertically and cross-functionally — the organization fractures.

One of the most powerful intentions we ever added was this:

Build trust across the organization.

At first glance, that may not look like an operational objective. But it was decisive.

Trust is not sentiment.
It is confidence that:

• Information is accurate.
• Commitments are honored.
• Decisions are transparent.
• Shared resources are governed fairly.

Declaring the intention to build trust changed behavior. But more importantly, we studied what trust required operationally — clear intention, complete data, shared metrics, visible capacity, shared explanations with complete narratives, and structured collaboration.

The result?

Weekly coordination meetings that once had 5–6 participants grew to more than 50 engaged contributors across functions — not because they were mandated to attend, but because they saw value. They were inventing together. Solving together. Improving together.

That is what aligned OKRs are meant to produce:
Shared clarity around intentions that drives cross-functional collaboration.

Learning What to Intend

Another lesson:
The right intentions are not always obvious.

Early in our journey, we thought the primary intention might be asset tracking. Or reporting. Or compliance documentation.

Through experience, we learned that those were secondary.

The higher-leverage intentions were:

• Increasing throughput without capital expansion
• Improving utilization of constrained resources
• Creating shared visibility across programs
• Enabling proactive scheduling instead of reactive firefighting
• Building operational maturity that compounds over time
• Establish robust governance: with clarity about what is required, forbidden and allowed.

In OKR language, this is the difference between surface objectives and strategic objectives.

It requires background.
It requires pattern recognition.
It requires accumulated knowledge across industries and environments.

Intentions improve when they are informed by experience.

OKRs and the Discipline of Intentional Practice

At its core, OKRs formalize three practices:

1. Declare what matters.
2. Define how you will know if you are succeeding.
3. Review, learn, and adjust.

This is entirely consistent with how we have operated for years.

Our internal discipline — sometimes expressed through what we call the Speed Algorithm — has always required:

• Clear ultimate intentions
• Strategic intentions aligned to them
• Tactics aligned to strategy
• Measurement of outcomes
• Analysis of gaps
• Refinement of intentions and tactics to produce desired outcomes

OKRs provide a common language for this cycle across an organization.

What excites us is not the novelty of OKRs —
but the opportunity to help organizations execute them at a deeper level.

Accelerating Outcomes with Experience

Many companies adopt OKRs and struggle. Not because the framework is flawed, but because:

• Intentions are poorly formed.
• Key results measure activity instead of value.
• Cross-functional alignment is weak.
• Review cycles lack disciplined learning.

We have lived through these challenges in real operational environments for decades.

We understand:

• How intentions cascade.
• How to align shared capabilities across silos.
• How to distinguish essential from accidental complexity.
• How to build trust as an operational objective.
• How to measure what truly matters.

As our customers increasingly adopt OKRs and strategy execution tools, we look forward to accelerating their success — not by introducing something foreign to us, but by applying a discipline we have practiced for years and enabling us to align more tightly with their intentions.

Intentional organizations outperform reactive ones.

OKRs are one way to express that discipline.

For Sente, managing by intention is not a trend.

It is who we have always been.