I Was Asked to Enter a New Commodity Market My Organization Had Never Operated In—With No Playbook

I was asked to enter a new commodity market my organization had never operated in—with no playbook.

It sounded like a straightforward ask.

Until I realized it meant stepping into a system where nothing I knew fully applied—
new procurement structures, unfamiliar quality frameworks, and a pricing logic built on entirely different rules.

This wasn’t about executing a transaction.
It was about understanding a system I had never operated in—and building a way to navigate it from scratch.

 “Can Iprocure and sell this?”

A simple question.

Except—it wasn’t.

In over four decades of our organization’s existence,
I had never handled anything like it—nor had anyone else.

What was really being asked

On the surface, it looked like a sourcing question.

• Can I find suppliers?
• Can I understand pricing?
• Can I execute transactions?

But that wasn’t the real question.

I was being asked to operate outside our historical system.

This wasn’t just a new product.

It was a completely different market architecture:

• Procurement flowed through farmer collectives
• Quality existed across multiple graded layers
• Pricing was anchored to a benchmark grade, with variations around it

Everything I knew… needed to be reinterpreted.

Where the real complexity sat

At first glance, it seems manageable:

“Understand the grades, track the price, buy accordingly.”

But in reality:

• Misreading grades → mispricing instantly
• Mispricing → margin disappears
• Misunderstanding the benchmark → pricing logic breaks
• Ignoring procurement structure → execution fails

This was not a transaction problem.
It was a system understanding problem.

The moment of ownership

What made this harder:

There was no playbook.
No prior experience.
No structured guidance from above.

The problem didn’t come with a solution.
It came with expectation.

At that point, I had two choices:

• Escalate the uncertainty
• Or take ownership of building clarity

The shift that changed everything

Instead of asking:

“Can I handle this?”

I reframed the problem:

“What is the minimum system I need to build to participate safely?”

That shift moved me from hesitation → to design.

Building a system from scratch

To move forward, I focused not on speed—but on structure.

What followed

With a structured approach:

• The unknown became understandable
• The risk became manageable
• The execution became repeatable

The initiative translated into profitable transactions
and contributed incrementally to overall turnover.

What this experience reinforced

Organizations don’t get stuck because they lack capability.

They get stuck because:

They wait for clarity instead of building it.

The larger insight

Every new opportunity comes with incomplete information.

The difference is:

• Some wait for direction
• Others create a way forward

Growth doesn’t come from having all the answers.

It comes from:

the ability to design a system when none exists.

Closing thought

The real question is not:

“Has this been done before?”

It is:

“Can I build a way to understand and enter what organisation hasn’t done before?”

Because in the end,

Opportunities don’t expand organizations.
Ownership does.

Because growth doesn’t come from doing more of the same.

It comes from:

learning how to operate when the system changes.

Explore more resources on business bottlenecks.

Explore more insights in the Knowledge Hub.