When we began building the company, my role was clear.
I was the Medical Director.
My responsibility was expected to center on the clinical side of the organization: standards of care, professional oversight, regulatory requirements, and the quality of the medical operation we were creating.
But the company was still under construction, both literally and organizationally.
There were decisions that needed to be made, problems that did not yet have owners, and parts of the business that had not been properly structured.
I began stepping into them.
At first, much of this involved facility management. During construction, I found myself becoming involved in matters well beyond the conventional boundaries of medical direction.
That felt natural. Early-stage organizations rarely operate according to perfectly defined job descriptions. Everyone capable of moving the work forward contributes wherever necessary.
But temporary involvement has a way of becoming permanent responsibility.
The work expanded before the title did
As the company developed, my involvement moved beyond the facility itself.
I began taking a major role in structuring the organization and developing its policies.
Then came decisions about hiring.
Then company standards.
Then brand identity.
Then the broader vision of what we were building and how the organization should position itself.
None of these responsibilities arrived through one formal announcement.
There was no single morning when someone informed me that my role had changed.
The change happened gradually.
One unanswered question at a time.
One decision that needed an owner.
One problem that crossed departmental boundaries.
One area where the company required a clearer position.
Eventually, the pattern became impossible to ignore.
I was no longer contributing to selected issues outside my role as Medical Director.
I was helping direct the business as a whole.
Titles usually describe yesterday’s organization
Job titles are created at a particular moment.
They reflect what an organization believes it needs when the role is defined.
But companies evolve faster than their organizational charts.
A person may be hired to manage a department, then gradually become responsible for decisions affecting multiple departments.
A specialist may begin shaping commercial strategy.
An operational leader may become the person defining culture, standards, and organizational priorities.
A founder may remain formally responsible for everything while, in practice, another executive has become the organization’s central coordinating force.
The title remains unchanged because the shift rarely happens through one dramatic event.
It happens through accumulated reliance.
People begin asking for your judgment outside your original area.
Important decisions increasingly pass through you.
Problems that affect the entire organization become yours to resolve.
You start thinking beyond your function and considering how individual decisions affect the whole business.
The role has changed.
The organization simply has not named it yet.
Increased workload is not necessarily an expanded role
There is an important distinction here.
Being given more work does not automatically mean you are operating at a higher level.
Sometimes it simply means the organization has become comfortable placing additional tasks on a capable person.
The real evidence of an expanded role is not volume.
It is the level and consequence of the decisions you are making.
Ask:
- Has your attention moved from one function to the organization as a whole?
- Are you shaping policies rather than merely applying them?
- Do your decisions affect several departments?
- Are you influencing hiring, investment, positioning, or organizational direction?
- Do senior stakeholders increasingly rely on your judgment?
- Would important parts of the business lose coordination if you withdrew?
These are not signs that you are simply busy.
They are signs that the organization may already be using you in a different capacity.
I eventually recognized what had already happened
After our first year, I understood that I was no longer functioning primarily as a Medical Director.
My actual responsibilities had moved toward general management.
That recognition changed how I viewed my position.
Until then, it was possible to interpret each additional responsibility as another instance of helping the company.
But once the pattern became clear, continuing indefinitely without formal alignment would have created a structural problem.
I would have been accountable for organization-wide outcomes without having an organization-wide role clearly recognized.
That is not humility.
It is weak governance.
When someone is expected to make major decisions, shape direction, and carry broad organizational responsibility, their formal mandate should reflect that reality.
Otherwise, the business creates ambiguity around who leads, who decides, and who is accountable when interests or opinions conflict.
Contribution should come before negotiation
I do not believe the answer is to demand a new title every time your responsibilities increase.
A title claimed before the work exists is ambition without evidence.
The stronger sequence is:
- Demonstrate that you can operate at the required level.
- Establish a consistent pattern of contribution.
- Understand the value and consequences of what you are carrying.
- Formalize the position.
By the time I addressed my own role, I was not presenting a hypothetical case about what I might contribute in the future.
The work already existed.
The decisions had already been made.
The organizational reliance was already visible.
The conversation was about bringing the formal structure into alignment with the operating reality.
That ultimately meant recognizing my position in general management and within the governance of the company.
The title did not create the role.
It acknowledged the role I had already grown into.
Do not confuse delayed recognition with permanent permission
There can be value in allowing your contribution to develop before insisting that it be formally recognized.
It gives you evidence.
It shows whether the expanded responsibility is temporary or whether the organization has genuinely begun depending on you at another level.
But this period should not continue indefinitely.
Responsibility without authority eventually becomes dangerous.
You may be expected to deliver an outcome while lacking the mandate to make the decisions required to produce it.
Authority without formal accountability is equally dangerous.
You may influence major decisions while the organization remains unclear about who ultimately owns their consequences.
And when the title, authority, and actual work describe three different roles, conflict becomes almost inevitable.
The objective is not recognition for its own sake.
It is alignment between:
- The outcomes you are expected to deliver
- The decisions you are authorized to make
- The responsibility you carry when those decisions succeed or fail
- The position the organization formally recognizes
When these elements match, leadership becomes clearer for everyone—not only for the person whose role has expanded.
Name the role the organization is already using
Today, my position is clear.
I serve as Co-Founder & General Manager.
Looking back, that transition did not begin when the title changed.
It began much earlier, during construction, when I started taking responsibility for problems outside the original boundaries of medical direction.
The formal recognition came later.
The role changed first.
That is often how leadership develops inside growing organizations.
You begin by helping.
Then people begin relying on you.
Your decisions expand in scope.
Your perspective shifts from one department to the whole business.
Eventually, you must recognize that you are no longer merely supporting the organization from your original position.
You are occupying a different one.
The title should not lead the work.
But it should not remain permanently behind it either.