Every framework begins with an answer.Compass began with a question.
The Story of CompassA navigation system wasn't born from a company.
In that Christmas break, I discovered the question that would eventually become Compass.
Every Christmas, I try to learn something completely new.
Not because I have to.
Because I believe the best ideas often come from exploring outside your own field.
One Christmas, I decided to dive into a subject I knew almost nothing about.
I bought books.
I bookmarked articles.
I enrolled in courses.
Every morning I couldn't wait to continue.
And yet, after several days, something felt deeply wrong.
At the end of every day, I asked myself the same question.
What did I actually accomplish today?
I had spent hours reading.
Hours taking notes.
Hours connecting ideas.
But I had nothing tangible to point to.
No finished project. No feature. Nothing I could hold up and say:
This is what I delivered today.
It felt like failure.
Looking back, I wasn't failing at all. I was simply judging today's work using tomorrow's definition of success.
That realization changed everything.
I wasn't doing delivery work.
I was doing research.
Research doesn't produce features.
It produces understanding.
A great day in research isn't measured by what you ship.
It's measured by what you discover.
The problem wasn't my effort.
The problem wasn't my discipline.
The problem wasn't the work.
The problem was the map I was using to judge it.
Same ocean. Different mission. Different definition of success.
One realization changed everything.
I realized that I wasn't the only one using the wrong definition of success.
Organizations do it every day.
They measure research teams like delivery teams.
Platform teams like product teams.
Stability teams like innovation teams.
They don't notice it immediately.
They simply start feeling slower every year.
It began as a question.
What if the problem isn't the people?
What if the problem isn't Agile?
What if the problem isn't execution?
What if the real problem is that we expect fundamentally different kinds of work to succeed in exactly the same way?
That single question eventually became Compass.
Every unclear decision leaves a trace.
In software, we talk about Technical Debt.
But before software accumulates Technical Debt...
Organizations often accumulate something else.
Navigation Debt.
It grows every time people move without enough clarity about context, direction or success.
Compass exists to reduce Navigation Debt before it becomes visible.
A navigation instrument, not a process diagram.
Organizations are fleets.
Context beats methodology.
Clarity comes before execution.
Different work deserves different leadership.
Success should be defined before the work begins.
Navigation is everyone's responsibility.
Compass exists to help organizations see the work clearly enough to navigate it.
Not to make every team the same.
Not to force one definition of success onto every kind of work.
But to help leaders, managers, and teams understand where they are, what kind of work they are doing, and what success should mean before the work begins.
Meet the Navigator
Compass began with a question. But every question has a person behind it.
Teofil Lucaci created Compass after years of working with software teams, engineering leaders and complex delivery environments where effort was high, but clarity was often missing.
Compass began with one question.
What kind of work am I actually navigating?
The Compass Navigation Diagnostic helps you answer that question for your current season.