Forem: Ranjit Shah

Early Judgment vs Responsiveness: What Builds Influence

Ranjit Shah — Wed, 08 Apr 2026 13:34:40 +0000

A few years into your career, project meetings start to feel familiar.

You’ve seen initiatives repeat. You’ve watched ideas fail. You’ve learned which proposals tend to collapse once execution begins.

So when someone introduces a new idea, your reaction is quick.

You recognize the pattern. You form a judgment. And internally, the conversation can feel settled before the discussion has really begun.

From your perspective, this feels like experience doing its job.

But sometimes something else is happening. The conversation hasn’t reached a conclusion yet—but you already have.

That moment is easy to miss. It’s a form of premature closure.

It rarely feels like disengagement when it happens. It feels like you’ve simply reached the conclusion faster than everyone else.

But over time, it quietly changes how much influence you have.

How Early Judgment Appears

At this stage of your career, judgment rarely shows up as arrogance.

More often, it shows up as efficiency.

You’ve seen enough projects to recognize familiar patterns. So when someone presents an idea, your mind begins sorting it quickly.

You might find yourself thinking:

this won’t scale
we’ve tried something like this before
execution will probably kill this anyway

None of these reactions are irrational. They’re the result of experience.

But they often arrive earlier than the conversation does.

And when that happens, something subtle shifts.

You stop listening as closely
You wait for the discussion to move on
You mentally file the idea under not worth pursuing

From the outside, you’re still in the meeting. But you’ve already stepped out of the conversation.

Why Reactivity Feels So Natural

By mid-career, your mind has learned to move quickly.

You’ve seen enough systems fail, enough initiatives stall, enough optimistic plans collapse during execution. Patterns start to emerge.

So when a new idea appears, your brain begins evaluating it almost automatically.

You’re not trying to shut the conversation down. You’re trying to save time.

Your experience is telling you:

this has probably been tried before
the real constraints will show up later
execution will be harder than the proposal suggests

None of that reasoning is unreasonable. In fact, it often is.

The problem is timing.

Those judgments arrive before the conversation has revealed what actually matters.

And once your mind settles on a conclusion, it becomes much harder to stay curious about where the discussion might still go.

Judgment or Responsiveness

At this career stage, the real difference isn’t whether you can evaluate ideas. Most experienced engineers can.

The difference is when that evaluation happens.

One posture closes the loop quickly. The other keeps the conversation open a little longer.

Judgment sounds like this:

“This won’t work.”
“We’ve tried this before.”
“The flaw is obvious.”

Responsiveness sounds slightly different:

“What’s different this time?”
“Which constraint matters most here?”
“What are we optimizing for?”

Notice the difference.

Judgment ends the exploration.

Responsiveness keeps it alive just long enough for the important signals to appear.

Both involve intelligence. But only one preserves your ability to shape the direction of the discussion.

Where Influence Actually Happens

The moment when a conversation is still figuring out what matters is exactly where influence tends to appear.

Most meetings aren’t really about solving problems.

They’re about deciding which problems deserve attention.

Before solutions appear, the group begins shaping the situation itself. This is the moment when people are still asking:

What problem are we actually trying to solve?
Which constraint matters most here?
What trade-offs are we willing to accept?

Once those answers begin to settle, the direction of the project usually follows.

And that moment— the framing stage —is where influence is easiest to apply.

If you disengage earlier, you’re not just skipping noise. You’re stepping away from the point where your judgment could have shaped the direction of the work.

By the time the conversation reaches solutions, most of the important decisions have already been made.

The Career Cost of Early Closure

Influence in meetings is easiest during the framing stage.

That’s when the problem is still being defined and the direction of the work is still open.

Once the group begins settling on an approach, momentum builds quickly.

alignment forms
assumptions harden
changing direction becomes more expensive

If you engage only after this point, your options become limited.

You can stay quiet
Or you can object after the conversation has already moved on

Neither position gives you much leverage.

Over time, people begin to adjust to this pattern. They stop expecting your input during the early stages of discussion.

Instead, they involve you once the direction is already clear. Not because your judgment isn’t valued. But because the conversation has learned to move without waiting for it.

This is how influence often shrinks at mid-career—not through failure, but through missed moments of participation.

How Responsiveness Preserves Optionality

Being responsive doesn’t mean agreeing with every idea.

It means staying engaged long enough to understand where the conversation is actually going.

Sometimes that requires a small pause.

A better question.
A surfaced assumption.
A moment of curiosity before evaluation.

That pause keeps the conversation open a little longer.

And that extra space often reveals things that quick judgment misses:

a constraint that wasn’t obvious at first
a goal the group hasn’t fully articulated yet
a trade-off that changes the direction of the discussion

Responsiveness doesn’t slow progress. It helps the group make better directional decisions before momentum builds.

And when you remain engaged during that stage, your influence stays connected to how the work evolves.

That is what optionality means in discussions: the ability to shape the path before it hardens.

A Small but Useful Reframe

When an idea appears in a meeting, the instinctive question is often:
“Is this a good idea or a bad one?”

That question pushes you toward judgment. And judgment encourages you to close the loop quickly.

A more useful question is slightly different:
“Is this a moment where my early input could change the direction?”

This question does something important. It shifts your focus from evaluating the idea to engaging with the conversation.

You’re no longer deciding whether the proposal is correct.

You’re asking whether your participation could help shape how the group understands the problem.

That small shift keeps you present during the part of the discussion where influence is still possible.

You’re not agreeing. You’re staying involved long enough to matter.

Why This Matters at Mid-Career

At this stage of your career, growth begins to depend less on how quickly you execute and more on where you place your attention.

Early judgment narrows that attention too soon.

Responsiveness keeps the conversation open long enough for influence to appear.

When you stay engaged while problems are still being defined, you remain connected to how the work takes shape.

That’s where mid-career influence is built.

Engineers who keep progressing aren’t the ones who judge less.

They’re the ones who judge later—when their judgment can still shape the outcome.

If this resonated, you may also like:

I write about how engineers grow—from early career to senior levels.

The Skill of Switching Between Creation and Execution

Ranjit Shah — Mon, 06 Apr 2026 14:39:33 +0000

A few years into your career, work starts to split in a noticeable way.

Some days you’re designing—thinking through architecture, shaping ideas, seeing connections that weren’t obvious before.

Other days you’re deep in execution—closing tickets, fixing edge cases, pushing changes through pipelines.

Both kinds of days matter. Neither feels complete on its own.

The friction begins when you expect one mode to behave like the other.

When Work Splits Into Two Modes

Early in your career, most work looks similar—you’re learning systems, following patterns, executing tasks. Creativity shows up in small, local ways.

As expectations rise, the shape of work changes.

You’re asked to:

think ahead
make trade-offs
anticipate failure modes

And still deliver consistently.

That means switching between creative design and execution grind, sometimes within the same week, sometimes within the same day.

Why the Switching Feels So Draining

The exhaustion doesn’t come from either mode by itself.

Creative work is energizing in its own way. Execution can be satisfying when things move.

The fatigue comes from transitioning.

Each switch requires a mental reset:

loosening constraints to explore
tightening constraints to deliver
tolerating ambiguity, then eliminating it

That back-and-forth is cognitively expensive, even when you’re good at both.

The Quiet Trap: Wanting One Mode to Win

Many engineers, without realizing it, start favoring one side.

Some want to live in creative mode—designing, improving abstractions, thinking deeply—while resenting the execution grind that follows.

Others retreat into execution, telling themselves they’ll “think more deeply later,” when things slow down. Which, they rarely do.

Growth stalls when you over-identify with one mode and avoid the other.

Creative work without follow-through stays hypothetical.

Execution work without creativity turns into maintenance fatigue.

What the Skill Actually Is

It isn’t about being more creative. And it isn’t about sheer willpower.

It’s a coordination skill, not a personality trait.

The real skill is entering and exiting modes deliberately.

Creative work needs:

openness
slack
tolerance for ambiguity

Execution needs:

constraint
repetition
acceptance of imperfection

Trying to blend both at once usually fails.

Engineers who sustain momentum learn to move between them—again and again—without treating either phase as a mistake.

Why This Never Goes Away

This alternation isn’t a temporary phase.

Projects evolve. Systems age. New ideas surface. Old ones demand upkeep. Every meaningful piece of work passes through creation and execution, often multiple times.

Once you stop resisting that loop, something shifts.

You stop waiting for creative time to last forever. You stop resenting execution as a distraction.

You recognize both as necessary phases of the same process.

A Small Reframe That Helps

Instead of asking:
“Why can’t I stay in the interesting part longer?”

Ask:
“Which mode am I in—and what does this phase require?”

That question replaces frustration with clarity.

The Long View

The goal isn’t to escape the execution grind. Nor to stay creative all the time.

It’s to learn to move between the two phases—without resisting the switch.

It’s to return to creativity with something real to build on.

Again. And again. And again.

If this resonated, you may also like:

I write about how engineers grow—from early career to senior levels.

Why Hard Work Feels Pointless When Time Layers Get Mixed

Ranjit Shah — Fri, 03 Apr 2026 12:40:27 +0000

Early in your career, you’re told to do two things at the same time.

Work hard every day
Think about your future

Both sound reasonable. Both seem important.

What’s rarely explained is that they operate at different layers of time.

When those layers get mixed, something subtle happens.

You work hard... but it feels unclear
You think about the future... but it feels distant

And slowly, effort starts to feel confusing instead of meaningful.

That confusion is not a character flaw. It is a layering problem.

The Quiet Tension Beginners Feel

Most early-career engineers carry a quiet internal split.

During the day, you focus on:

finishing tickets
fixing bugs
shipping features
responding to messages

But in the background, another voice runs:

Am I growing fast enough?
Am I on the right path?
Is this the right tech stack?
Am I falling behind?

You try to manage both at once.

Daily execution
Long-term positioning

Over time, that mental back-and-forth becomes draining.

Some days you work hard but feel unsure where it’s leading. Other days you think about the future but feel stuck about what to do this week.

Effort begins to feel busy, but not directional.

Not All Decisions Live at the Same Time Scale

Here’s the missing distinction.

Different decisions belong to different time horizons.

Goals shape who you want to become. They unfold over years.
Strategy sets direction. It evolves annually.
Tactics decide near-term bets. They change every few months.
Effort is what you do today. It is daily.

Mixing them feels productive. Separating them feels calm.

Each layer has a job. Problems start when you ask one layer to do another layer’s work.

When you ask daily effort to provide long-term meaning, it collapses under pressure. When you ask long-term goals to dictate today’s tasks, they become abstract and overwhelming.

The layers are not competing. They are sequential.

Where Effort Loses Its Power

Most beginners over-invest in effort and under-invest in direction.

They:

stay busy
work longer hours
volunteer for more
say yes quickly
chase visibility

From the outside, this looks admirable. But internally, something feels off.

Goals remain vague—“get really good at tech.”
Strategy remains implicit—“I’ll figure it out later.”

So daily effort has nowhere specific to accumulate. It repeats instead of compounding.

That is the moment when hard work begins to feel hollow.

Not because effort doesn’t matter.

But because effort has no container.

A Simple Example

Consider a junior developer in their second year.

The goal is simple: “grow fast.”

So they:

volunteer for frontend tickets
occasionally help with DevOps
fix backend bugs
experiment with a new framework on weekends

Busy. Visible. Learning.

But there is no clear direction. Six months later, they have touched many things—but deepened nothing.

Now imagine the same developer makes a simple strategic choice:

“For the next year, I’ll go deep into backend systems.”

That single decision changes everything. Frontend tickets become optional, not urgent. Helping DevOps becomes selective. Weekend experiments align with backend architecture.

Daily effort looks similar from the outside. But internally, it compounds. That is the difference a simple strategic choice creates.

What Alignment Actually Changes

When the layers are aligned, many things make subtle shifts.

Your long-term goal does not tell you what to do today.
– It tells you what not to worry about.

Your yearly strategy narrows your options.
– You no longer chase everything.

Your quarterly tactics create temporary focus.
– You know what this phase is about.

And daily effort becomes lighter
– not because it’s easier, but because fewer things compete for it.

You stop asking, “Is this even worth it?”

And start asking, “How well can I do this today?”

That is a very different mental state.

The Real Fix Is Smaller Than You Think

You do not need a perfect ten-year plan. You do not need total clarity about your future. You need separation.

Let goals provide direction.
Let strategy narrow attention.
Let tactics define current bets.
Let effort stay local to today.

When each layer does its own job, something important happens:

Hard work stops feeling random. It starts feeling cumulative.

Progress becomes visible, not because you suddenly feel inspired, but because your actions finally attach to a structure.

Motivation returns quietly. Not as excitement. But as coherence.

The Layering Discipline

Early in your career, the temptation is to solve everything at once. That instinct feels ambitious—but it creates unnecessary friction.

You try to build skill, plan a future, choose a path, and execute perfectly—all in the same mental space.

That creates friction.

The solution is not more effort.

It is cleaner thinking.

When the layers stay in their lanes, your work stops feeling scattered. And when effort accumulates instead of resetting, you finally see what you’ve been building—not just features, but a direction taking shape.

If this resonated, you may also like:

I write about how engineers grow—from early career to senior levels.

Hard Work Alone Isn't What You're Rewarded For

Ranjit Shah — Wed, 01 Apr 2026 15:30:00 +0000

You worked hard. You put in the hours. You did what was expected. And still, the outcome doesn't always match the effort.

You finish a task that took real effort. You stayed late. You worked through uncertainty and kept going until it was done.

Naturally, you expect that effort to matter.

Early in your career, you’re often taught a simple equation:

Work hard → good things happen.

It sounds fair. It sounds motivating. So you do what seems reasonable. You put in hours. You stay busy. You try to be diligent.

But after some time, you start noticing something uncomfortable. Hard work alone doesn’t always produce the rewards you expect.

That happens because most people misunderstand what the world actually responds to.

Why Hard Work Feels Like It Should Be Enough

Hard work is easy to recognize—from the inside.

You feel it in your body and your mind. You know when something demanded real focus and energy. You know when you pushed yourself to finish something difficult.

Because effort is so visible to you, it’s natural to assume effort itself should be rewarded.

After all, effort requires something from you. It takes time. It takes attention. Sometimes it takes sacrifice.

But effort is only the input.

What the world responds to is the output your work creates.

What the World Actually Rewards

You’re not rewarded simply for working hard.

You’re rewarded for the value your work creates for other people.

Work becomes valuable when it’s useful to someone.

It might:

help someone solve a problem
save time
remove friction
make something possible that wasn’t before

When work produces outcomes like these, it creates value.

And value is what the world responds to.

A feature that saves someone thirty minutes every day can be extremely valuable—even if it took you just one afternoon to build.

At the same time, a complex task that took weeks of effort may matter very little if no one ends up using it.

Why Effort Alone Doesn't Decide the Outcome

Two people can work equally hard.

One creates something others rely on. The other creates something that quietly disappears.

From the inside, both work-experiences feel similar. Both required focus, persistence, and effort.

From the outside, the outcomes are very different. The difference isn’t how hard they worked.

The difference is the value their work created.

Effort is the input. Value is the outcome that gets noticed.

Why This Idea Feels Uncomfortable Early in Your Career

This idea can feel discouraging at first. It may sound like hard work doesn’t matter.

But that isn’t the lesson.

Hard work increases the chances of creating value. It just doesn’t guarantee it.

The difficult part is that effort is something you control. Value is not entirely under your control.

You can decide to work harder. But you can’t fully decide how useful the final result will be to others.

That uncertainty is uncomfortable, especially early in your career.

A Healthier Way to Think About Work

Instead of asking:
“How hard am I working?”

Try asking:
“What am I creating, and who does it help?”

That question changes how you approach your work. You start paying attention to which problems actually matter. You look for feedback earlier. You notice what people use and what they ignore.

Gradually, your focus shifts.

Hard work stops being the goal.

It becomes the fuel that helps you create something useful.

What This Means for You Right Now

Early in your career, this perspective can actually be freeing.

Unrecognized hard work doesn’t mean wasted effort. And failure after real effort isn’t useless if it teaches you what creates value and what doesn’t.

You don’t need to prove how hard you’re working.

You need to get better at noticing what matters to other people.

Because in the end, the world rarely rewards effort by itself. It rewards the value your effort creates for other people.

If this resonated, you may also like:

Why Hard Work Feels Pointless When Time Layers Get Mixed

I write about how engineers grow—from early career to senior levels.