A Tracker Is Not an Operating Model
Organizations love trackers.
When work becomes difficult to manage, the instinctive response is often to create a spreadsheet, a project board, a dashboard, or a new set of status fields.
Sometimes that helps.
Sometimes it creates a beautifully organized representation of the same confusion.
A tracker tells you where information is recorded.
An operating model tells you how the organization works.
The difference became especially clear to me while reviewing cross-functional processes that involved multiple project boards, intake mechanisms, work-management platforms, and reporting tools.
The organization had no shortage of systems.
The challenge was that the systems did not always agree.
A project might begin in one board, generate tasks in several others, move into another platform for execution, and then depend on updates being manually carried back into the original record.
Different teams used different structures.
Some created epics. Others created subtasks. Some worked from formal requests. Others began after being tagged in a message.
The tools reflected the fragmentation of the process.
Adding another tracker would not solve that.
The more important questions were:
Where does work officially begin?
What information is required before it starts?
Who owns the end-to-end outcome?
Which team owns each decision?
What are the standard stages?
When should work move from one function to another?
Where is the official status maintained?
How are risks escalated?
How does leadership see the portfolio?
Those are operating-model questions.
A practical operating model usually defines several interconnected elements.
Governance
Who makes which decisions, and how are unresolved issues escalated?
Roles and ownership
Who owns the overall outcome, individual stages, and key approvals?
Process
How does work move from request through completion?
Information
What data is required, where is it stored, and how is it kept current?
Cadence
Which meetings, reviews, and reporting rhythms keep the work moving?
Measures
How does the organization know whether the process is working?
Technology supports this model.
It does not replace it.
One of the easiest mistakes is allowing tool configuration to become a substitute for process design.
Teams debate fields, statuses, labels, and dashboards before agreeing on what those elements are meant to represent.
The result is often a sophisticated system with low trust.
People create their own spreadsheets because the official data is incomplete. They rely on side conversations because the workflow does not reflect reality. They update several tools because no single system has been designated as authoritative.
A useful tracker should be the visible expression of a clear operating model.
When the model is working:
Teams understand what happens next
Ownership is visible
Status definitions are consistent
Risks appear early
Leadership can see the portfolio without reconstructing it manually
People spend less time asking where the information lives
The solution is not always fewer tools.
But it is always greater clarity about the role each tool plays.
Before creating the next dashboard, ask a more important question:
What decisions and behaviors is this system supposed to enable?
That is where operating design begins.