In partnership with

The assignment I was not supposed to get

I was a software person. That was the box I had put myself in, and as far as I could tell, it was the right one. I knew systems and implementation. I didn’t know HVAC. I didn’t know building management systems. I didn’t know clean room regulatory compliance or the kind of hardware that keeps a pharmaceutical manufacturing site running within compliance.

So when I got assigned to lead the remediation project for the clean rooms at the manufacturing site, my first thought was that someone had made a mistake.

They needed someone to connect the dots

The project sat at the intersection of technology, quality, regulatory, and facilities. Nobody owned all of it. Nobody was supposed to. And yet someone had to walk into that space with people from multiple functions, understand enough of each world to ask the right questions, and come with a blueprint that worked.

That someone turned out to be me. Not because I had the deepest expertise in any one area. Because I could move between all of them without missing a beat. I could sit with the engineers and understand the BMS components, then turn around and translate that into what the quality team needed to hear, then figure out what hardware installation actually required from a project management standpoint.

I did not have a word for what I was doing. I just did it.

A few years later, something similar happened. I was in procurement, supporting R&D, when a program manager went on leave unexpectedly. Someone needed to step in and lead the NPI project, new product introduction for a medical device. This was not procurement work. This was product development and commercialization, transitioning a prototype to manufacturing. It was R&D territory and I was an ex-IT, now procurement person sitting in the middle of it.

They asked me and I said yes. I led the project for a couple of months. When the program manager came back, the project had not missed a beat. They even asked if I wanted to join the team permanently.

Both times, I walked out thinking I had gotten lucky. That I had managed to hold something together that I had no business holding. It took me years to understand what was actually happening. Someone had looked at a complex, messy problem and decided that what it needed was not a deeper specialist. It needed someone who could connect things that did not obviously belong together.

They saw it before I did. I was too busy wishing I had my one thing.

Peter didn’t say much. Until he did.

There was a leader, we’ll call him Peter. He did not believe his presence was commanding his meetings or team. He was introverted and reflective, not the life of the party. By the standard scorecard of his peers( confidence, volume, and command) he scored somewhere in the middle to low.

I watched what happened one day when we had a hard decision to make. A major implementation had been on life support for months past the point where it should have been called. The team gathered for yet another alignment meeting, trying to find a path forward on a project that was a pet initiative of a key leader in the organization. Nobody wanted to be the one to say what everyone already knew.

Peter said it. We are killing this project and here are the reasons why. He even volunteered to deliver the news to the project sponsor.

The team was relieved. Peter had nothing to protect. He was not managing a relationship with the project sponsor. He was not calculating how it would affect his next review. He had been watching the whole situation carefully and knew what was at stake.

The trait Peter had been measuring as a weakness, the watching without trying to fill the silence, was exactly what the moment required. Peter just could not see it. He was too busy measuring himself against the people who were louder.

The trait you have been filing under weakness is your superpower.

The scorecard was wrong the whole time

Like Peter, I called my learning agility scattered for years. I told myself I was a generalist in a world that rewarded specialists. I assumed because I could do a lot of things I was probably not exceptional at any of them. I thought if I could just find my one thing, I would finally feel like I belonged in the spaces I kept getting asked to lead.

Those spaces kept asking anyway. Because what they needed was not a specialist. They needed someone who could hold complexity without losing the thread. Someone who could sit with the engineers and the quality team and the supply chain people and understand enough of each world to connect them. Someone who was not protecting one domain, so they could see across all of them.

That was never scattered. That was the point.

There is research that supports this. Organizational psychologists call it cognitive flexibility. The ability to easily shift between different concepts and perspectives and apply knowledge across domains. It is one of the most consistent predictors of performance in complex, ambiguous environments. The people who have it often do not know they have it because they have spent years trying to trade it in for something that looks more like expertise.

Name the trait. Then find the proof.

You already know what you're good at. You've just been calling it the wrong thing. Filing it under the wrong category. A misfiled asset is the same as a missing one.

Write down the trait you have been trying to get rid of. The one you called hard to categorize. The one that doesn’t fit cleanly on a resume or a LinkedIn headline.


Then write down one time that trait solved something nobody else could solve.

That is your answer.

You are not here to blend in.
You are here to bring the skills that only you can bring.
If you do not bring them, they are missing from the conversation.

Until next Tuesday.
Ceaneh

Keep Reading