Assuming Past Alignment = Present Priority
Utpal Vaishnav
Upsquare
What I was building
A single operational head to run point across a portfolio of ventures.
I believed in it because I had a proven data point.
We had worked together 15 years ago, and back then he went deep, worked hard, carried real ownership.
I was not hiring a stranger. I was re-hiring a track record.
What happened
The track record was real.
It had just expired.
His priorities had moved.
He now wanted a calmer, lower-intensity work life, and he did not want the upside badly enough to trade peace for it.
I diagnosed the symptom, not the system.
So I ran my usual all-in playbook on it.
More clarity. More push. More problem-solving.
None of it landed, because the gap was never capability ... it was something else.
It was a priority mismatch I never checked for.
I failed to reference-check his current hunger.
What I learned
- Past alignment is not present alignment. People change, priorities change, and a relationship that worked at one life stage is not a guarantee at another.
- When something is "not working," interrogate the diagnosis before scaling the effort. Pushing harder on the wrong problem just compounds the wrong problem.
- For high-ownership roles, capability is the entry ticket, not the decision. The real screen is current hunger, life priority, and willingness to carry the weight.
Outcome: The failure was mine, not his. My ego-system wanted to ask "how did I misjudge this?" The honest answer was quieter. I did not misjudge the person. I judged an old version of him and assumed it still shipped. Now, before assigning weight to anyone, I check the present, not the memory. #DhandheKaFunda: Misalignment is not always a people problem. Sometimes it is an unspoken priority problem.