I congratulated him.

But there was one thing he didn't know.

𝗛𝗲 𝗵𝗮𝗱 𝘀𝘁𝗼𝗹𝗲𝗻 𝘁𝗵𝗲 𝗽𝗿𝗲𝘀𝗲𝗻𝘁𝗮𝘁𝗶𝗼𝗻. 𝗡𝗼𝘁 𝘁𝗵𝗲 𝗸𝗻𝗼𝘄𝗹𝗲𝗱𝗴𝗲 𝗯𝗲𝗵𝗶𝗻𝗱 𝗶𝘁.

This is a workplace story that every employee should learn from.

For eight months, I had been developing a proposal for a new service that could generate an additional $1.2 million in annual revenue.

I researched the market, interviewed potential customers, studied the competition and built the financial projections.

Most of the work happened after office hours.

I believed that if I delivered something valuable enough, management would eventually recognise me.

Then a colleague I'll call Marcus approached me.

He wanted to see what I was working on.

I trusted him.

I sent him the proposal.

Three weeks later, the CEO called an all-hands meeting.

And there was Marcus, standing in front of everyone, presenting my work.

My research.

My financial model.

My charts.

Even the name I had created for the service.

He had barely changed anything.

At the end of the presentation, the CEO stood up and congratulated him.

Shortly afterwards, Marcus was promoted to director.

𝗜 𝘄𝗮𝘁𝗰𝗵𝗲𝗱 𝘀𝗼𝗺𝗲𝗼𝗻𝗲 𝗲𝗹𝘀𝗲 𝗴𝗲𝘁 𝗿𝗲𝘄𝗮𝗿𝗱𝗲𝗱 𝗳𝗼𝗿 𝗲𝗶𝗴𝗵𝘁 𝗺𝗼𝗻𝘁𝗵𝘀 𝗼𝗳 𝗺𝘆 𝗵𝗮𝗿𝗱 𝘄𝗼𝗿𝗸.

When I confronted him, he said we worked for the same company and it was a team effort.

My manager wasn't helpful either.

He told me not to be emotional.

Imagine being told to control your emotions after someone has taken credit for something you sacrificed your evenings and weekends to build.

I went home that day and opened my original project folder.

Thankfully, I had kept everything.

The dated drafts.

Research notes.

Customer interviews.

Spreadsheet versions.

Every single document.

I didn't know how important those records would become.

Two weeks later, the CEO announced that the new service would launch in 60 days.

Marcus was appointed project lead.

That was when his problems started.

He called me into a meeting and asked for the implementation plan.

I asked him what he needed.

It turned out he had no supplier agreements, no customer acquisition strategy and no approved operational budget.

He had presented the numbers without understanding the assumptions behind them.

I explained that the proposal recommended starting a pilot in 60 days, subject to certain conditions.

He had apparently not read the appendix.

Then he asked me to prepare the entire implementation plan.

I requested formal assignment to the project.

He accused me of being difficult.

𝗧𝗵𝗲 𝘀𝗮𝗺𝗲 𝗺𝗮𝗻 𝘄𝗵𝗼 𝗱𝗶𝗱𝗻'𝘁 𝘄𝗮𝗻𝘁 𝘁𝗼 𝘀𝗵𝗮𝗿𝗲 𝘁𝗵𝗲 𝗰𝗿𝗲𝗱𝗶𝘁 𝗻𝗼𝘄 𝘄𝗮𝗻𝘁𝗲𝗱 𝗺𝗲 𝘁𝗼 𝘀𝗵𝗮𝗿𝗲 𝘁𝗵𝗲 𝗿𝗲𝘀𝗽𝗼𝗻𝘀𝗶𝗯𝗶𝗹𝗶𝘁𝘆.

A few days later, the CEO's office requested the original research because the board wanted to review the financial projections.

I submitted everything, including the assumptions Marcus had omitted.

The following morning, an emergency meeting was called.

The finance director started asking questions.

Had the distribution agreements been signed?

Were the projected margins guaranteed?

Was the implementation budget approved?

Marcus couldn't give satisfactory answers.

Then came the question that changed everything.

"Who developed the original financial model?"

The document history was reviewed.

My name was on the original drafts, spreadsheets and research files.

Marcus had only made edits shortly before his presentation.

The CEO wanted to know why my contributions had never been acknowledged.

Marcus tried to explain it away as teamwork.

But the evidence was there.

Later that day, the CEO invited me into his office and apologised.

I appreciated the apology, but I wanted more than recognition.

I requested formal ownership of the implementation plan, appropriate decision-making authority and a salary review.

Two weeks later, I was appointed project manager with a salary increase.

Marcus was removed as project lead while the company reviewed what had happened.

The service eventually launched four months later and exceeded its first-year revenue target.

At the company celebration, the CEO publicly acknowledged my contribution.

I also received a $22,000 performance bonus.

But the biggest lesson had nothing to do with the money.

𝗬𝗼𝘂 𝗰𝗮𝗻 𝗯𝗲 𝘁𝗵𝗲 𝗺𝗼𝘀𝘁 𝗵𝗮𝗿𝗱𝘄𝗼𝗿𝗸𝗶𝗻𝗴 𝗽𝗲𝗿𝘀𝗼𝗻 𝗶𝗻 𝘆𝗼𝘂𝗿 𝗱𝗲𝗽𝗮𝗿𝘁𝗺𝗲𝗻𝘁 𝗮𝗻𝗱 𝘀𝘁𝗶𝗹𝗹 𝗯𝗲 𝗶𝗻𝘃𝗶𝘀𝗶𝗯𝗹𝗲 𝘁𝗼 𝘁𝗵𝗲 𝗽𝗲𝗼𝗽𝗹𝗲 𝘄𝗵𝗼 𝗱𝗲𝗰𝗶𝗱𝗲 𝘆𝗼𝘂𝗿 𝗰𝗮𝗿𝗲𝗲𝗿.

This is why employees must learn to protect their professional contributions.

Document your work.

Keep dated records of your achievements.

Communicate important decisions in writing.

Make your contributions visible to relevant stakeholders.

And never assume that someone will automatically give you credit because you worked hard.

𝗕𝗲𝗰𝗮𝘂𝘀𝗲 𝘀𝗼𝗺𝗲 𝗽𝗲𝗼𝗽𝗹𝗲 𝘄𝗶𝗹𝗹 𝘂𝘀𝗲 𝘆𝗼𝘂𝗿 𝗵𝗮𝗿𝗱 𝘄𝗼𝗿𝗸 𝘁𝗼 𝗯𝘂𝗶𝗹𝗱 𝘁𝗵𝗲𝗶𝗿 𝗼𝘄𝗻 𝗰𝗮𝗿𝗲𝗲𝗿 𝗮𝗻𝗱 𝘀𝘁𝗶𝗹𝗹 𝗰𝗼𝗻𝘃𝗶𝗻𝗰𝗲 𝘆𝗼𝘂 𝘁𝗵𝗮𝘁 𝗮𝘀𝗸𝗶𝗻𝗴 𝗳𝗼𝗿 𝗿𝗲𝗰𝗼𝗴𝗻𝗶𝘁𝗶𝗼𝗻 𝗶𝘀 𝗯𝗲𝗶𝗻𝗴 𝘀𝗲𝗹𝗳𝗶𝘀𝗵.

Have you ever had a colleague or manager take credit for your work and receive the recognition you deserved? How did you handle it?

Credit - Ella