When Loyalty Is Not Reflected in Your KPI

There is one career lesson I only fully understood much later:

Not every meaningful contribution will show up in your KPI. And not every decision framed as teamwork is equally fair to everyone involved.

Around May or June 2025, I went through one of the most expensive lessons in my professional journey.

At that time, I was in Jakarta. Through a verbal discussion, two major project opportunities were redirected — one from the automotive sector and one from the FMCG sector. The explanation sounded simple: it was a “project swap.”

I treated it as part of teamwork.

There was a situation to support. There was a business interest to protect. There was a team dynamic to manage. And I chose to trust the process.

But the real problem was this:

A decision that had a direct impact on my KPI was never properly documented.

There was no formal record of how the project transfer would affect my personal target. There was no clear agreement on how my contribution would be recognized. There was no protection if the replacement project failed to move forward. There was no written accountability on who owned what after the swap.

And eventually, that risk became real.

Based on the original project potential, I could have achieved at least around 8 MWp in PSC points. In business development, that number is not small. It can be the difference between a strong performance year and a year that looks disappointing on paper.

But after the project transfer, my achievement was significantly affected.

I did not reach the number I should have been able to reach.

What made it worse was that the project exchanged in return also failed.

And at some point, I was not even properly involved in the replacement of that project.

At first, I thought this was simply the consequence of a messy business decision. Maybe it was just the cost of helping others. Maybe it was part of being a team player. Maybe it was the risk of trusting a verbal arrangement.

But later, I began to understand the bigger picture.

The situation was not as simple as a project swap.

There were other interests that were never transparently explained to me. There were internal dynamics behind the decision. There were parties being protected. There were processes happening in the background, including issues related to broker-fee arrangements, which made the whole situation feel even less transparent.

I am not writing this to attack anyone.

I am writing this so I do not forget the lesson.

Because the most painful part was not only the missed KPI. It was not only the lower bonus. It was not only the lost momentum in performance review.

The most painful part was realizing that I trusted a decision, acted in good faith, supported the situation, and ended up carrying the consequences almost alone.

In the workplace, we are often taught to be loyal.

To help the team. To support colleagues. To not be too transactional. To put the organization’s interest above personal interest.

And to some extent, all of that is true.

But there is one boundary people rarely talk about:

Loyalty without clarity can become one-sided sacrifice.

Teamwork without documentation can become invisible contribution.

Trust without accountability can become regret.

And verbal decisions that affect someone’s KPI should never be treated as minor.

This experience taught me that good intentions are not enough in a professional environment.

We need documentation. We need clarity. We need ownership. We need a clear record of contribution, especially when a decision changes someone’s target, incentive, and performance narrative.

Not because we should stop trusting people.

But because a healthy system should not depend only on memory, personal relationships, or one-sided interpretations.

Since then, the way I see leadership has changed.

For me, a good leader is not only someone who can protect the team’s target. Not only someone who can manage strategy. Not only someone who can keep things looking stable from the outside.

A good leader is someone who protects fairness inside the team.

Especially when one person is asked to support another.

Especially when contribution does not appear directly on the dashboard.

Especially when a difficult decision affects someone’s bonus, KPI, and professional reputation.

Because numbers can explain performance.

But numbers do not always explain context.

And sometimes, behind one disappointing KPI result, there is a long story of undocumented decisions, unrecognized contribution, and trust that turned out to be very expensive.

I do not want to carry this experience as resentment.

I want to carry it as a lesson.

I will still help people. I will still support the team. I will still believe in collaboration.

But I will also be more disciplined in protecting accountability.

If there is a project transfer, the ownership must be clear.

If there is a project swap, the risk must be clear.

If there is a contribution that affects KPI, the recognition mechanism must be clear.

And if there is a decision that can affect someone’s bonus, career, and reputation, that decision should not live only in a verbal conversation.

The biggest lesson is simple:

Never let a major contribution exist only as an oral story.

Because when the year ends, the system does not measure your good intentions.

It measures your numbers.

And if those numbers do not carry the right context, you may be the one left carrying a story that nobody else remembers.