The seeker and the scoreboard

A close friend sent me something yesterday. Buried in it was a line that stopped me mid-scroll: Seek and you will miss it. Don't seek and you will find it.

It reads like spiritual wordplay. Sit with it for a minute and it sharpens. Every time I say "I want peace," I quietly split myself in two. There is the me who lacks it, and the peace waiting somewhere ahead. The seeking is what holds those two apart. Same trap as forcing yourself to fall asleep. The harder you work at it, the wider awake you get.

Which raises the obvious objection. If seeking is the problem, why does every tradition prescribe sadhana? Years of practice, discipline, effort, most of it dull. Is that not seeking?

The old Vedantic answer is the thorn. You use one thorn to remove another, then throw both away. Sadhana is not a machine that manufactures the finding. It exhausts the seeker until the grasping stops on its own. You cannot force muddy water to clear. You stop stirring.

The cleanest version comes from the Gita. Nishkama karma: act fully, drop the claim on the fruit. The seeker does not live in the action. It lives in the expected outcome. Cut the claim on the outcome and you can pour everything into the work while the ego quietly starves. A musician deep inside a phrase is not seeking the music. For those few minutes he is the music.

Fine thing to arrive at on a Sunday morning with coffee. The cushion is not the test. Monday is.

Monday looks like a tender document

Ask me to drop the claim on the fruit while I am running a consulting firm and the idea gets funny very fast.

I carry a number. Diagonal is growing by 2x. DataLumin is chasing 3x. Aryabhat is in pilot, and the whole point of the pilot is to find out whether anyone actually wants it before we build another six months of features into it. Every one of those sentences is a claim on a fruit. I say them out loud in review meetings.

Public sector work makes the attachment even more literal. A tender is 200 pages. You spend six weeks on it. You build the solution architecture, you price it three times, you chase the turnover certificates and the past performance letters, and then you lose because a clause about prior contract value in a similar department was read one way by the evaluation committee and another way by you. Nothing about the technical bid was wrong. The harvest simply went elsewhere.

So "do not seek the outcome" sounds, in that room, like a plan for going out of business.

Look at what the opposite actually does, though.

What attachment costs you in the room

When your identity is riding on a deal closing, the client feels it. Not in your words, in your pacing. You over-answer. You discount before you are asked. You send the follow-up two days early. Buyers read that instantly, and what they read is need. I have watched genuinely better proposals lose to calmer ones for exactly this reason, and I have been the desperate one often enough to recognise the tell in myself.

The damage inside the team is worse and slower. If an engineer believes a slipped launch date will produce an emotional event from leadership, he stops proposing the harder architecture. He picks the option he can defend in a post-mortem. Defensive engineering looks like productivity for about two quarters. Then you notice nobody has suggested anything risky in a year, and your product is a competent copy of what everyone else shipped in 2023.

The seeker is loud. When the seeker is loud, the work gets thin.

Targets as coordinates, not verdicts

Practising nishkama karma in business does not mean abandoning targets. We track win rate, pipeline coverage, margin per consultant, delivery slippage, all of it. The shift is what the number is allowed to mean.

A coordinate tells you where you are. A verdict tells you what you are worth. The same win rate can be either one, and which it becomes is decided by the tone of the room where it gets read out. That tone is set by one person, and if you run the firm, it is you.

The place this gets tested hardest is the post-mortem on a loss. An attached mind spirals. It hunts for a scapegoat, relitigates the pricing call from four weeks ago, or drifts into a long private grief about the lost revenue. None of that produces anything usable for the next bid.

What we run instead is an emotionless autopsy. Not a mood. A process, with the team in the room, in three moves.

Strip the adjectives

Ban the words "disaster," "unfair," "sloppy," and "obviously" from the review. Every claim gets restated as data or it does not get stated. "The client hated our pricing" becomes "our licensing model came in 18% above the budget line they had already locked for the quarter." One of those sentences you can argue with forever. The other one you can fix.

Isolate the controllables

Draw a hard line down the middle of the whiteboard. On the left, what was in our hands: the solution architecture, the clarity of the pitch, whether we identified the actual decision maker, whether our references were relevant to their sector. On the right, what was theirs: a budget freeze, an internal succession fight, a policy change three levels above the buyer.

Forgive the right side instantly and completely. Dissect the left side with the coldness of someone reading a machine log. The discipline is in not letting items migrate across that line, which they will try to do in both directions. Attached teams move their own failures to the right. Anxious teams drag the client's politics to the left and take the blame for weather.

Blame the system, not the seeker

When a deliverable misses, the question is never "who messed this up." It is "where did our process fail to catch this." A senior consultant sent a model with a broken assumption to a client; the useful question is why nothing between his laptop and the client's inbox flagged it.

This is the move that removes the terror of the scoreboard. It tells your engineers and your partners that their worth is not on trial. Only the workflow is. You drop the loss and go back to the craft, and the loss converts into fresh, high-quality input for the next bid.

Where this breaks

I should be straight about the failure mode, because there is a real one.

Detachment makes an excellent alibi for mediocrity. "I did my work, the outcome was not in my hands" is the exact sentence a person uses when they did not, in fact, do the work. The philosophy only holds if the effort side is genuinely maximal. Half-effort plus serenity is not nishkama karma. It is just giving up with better vocabulary.

The second cost lands on the leader personally. Shielding a team from outcome terror does not delete the terror. It relocates it. The pressure of a missed quarter still exists, and if the team is not carrying it, you are. Anyone who tells you that founders who practise this feel lighter is selling something. You feel it. You just do not pass it down the org chart at 11pm on a Thursday.

The weather you set

Your relationship with outcomes becomes the psychological weather of the whole organisation. Nobody reads it off your strategy deck. They read it off your face in the ten seconds after bad news lands.

Which is why the culture has to honour the root over the fruit, and be seen doing it. Celebrate the elegance of the architecture. Celebrate the rigour of the discovery work, the consultant who found the latent pain nobody had articulated yet, the team that killed its own feature because the pilot data said users did not want it. When you hand out an award for excellence, do not hand it to the person who caught a lucky quarter on a large renewal. Hand it to the person who showed the most relentless dedication to the craft, including the one whose deal died on a technicality.

The paradox dissolves the same way whether you are chasing enlightenment or scaling a business. Effort and surrender are not opposites. They work together. You play the game to win, and you stay aware that it is a game.

Plow the field with everything you have. Leave the harvest alone.