DEV Community: Karl Hill

Performance Feedback Without Politics

Karl Hill — Fri, 07 Aug 2026 14:31:44 +0000

Performance conversations go political when they become vague, late, or surprising.

Engineers can handle hard truth. What they cannot handle is fog: “be more proactive,” “improve communication,” “raise your impact” — with no examples, no path, and no shared definition of success.

Leadership work, whether Staff coaching or EM accountability, is making feedback usable.

Specific beats clever

Good feedback points at work:

“In the last two incident reviews, the postmortem missed the customer-facing impact.”
“Your PRs are strong technically, but reviewers wait days because context is missing in the description.”
“You owned the migration plan end-to-end — that is the bar for senior delivery.”

Personality labels invite defense. Observed behavior invites change.

Timing is part of the craft

Annual reviews should never be the first time someone hears a concern.

The durable pattern is small and frequent:

1:1s that include growth, not only status
Review comments that teach
Praise close to the moment it was earned
Course-correction while the work is still recoverable

Late feedback is not “careful.” It is expensive. It forces managers into documentation theater and engineers into damage control.

Separate support from consequences

People deserve clarity about both:

What “good” looks like in this role
What support is available to get there
What happens if the gap remains after a fair window

Politics thrives when those three stay implied. Teams stabilize when they are explicit.

This is also where Staff leaders practice manager muscles before the title: you may not own formal performance, but you can still coach with evidence, advocate fairly, and refuse hallway narratives.

Write less theater, more signal

When written feedback is needed, keep it boring and true:

Situation
Observed behavior
Impact
Expected change
Support offered

Skip the novel. Skip the score-settling. Skip the vague adjectives that sound sophisticated and mean nothing.

The point is a stronger team

Feedback is not a ritual for HR. It is how you protect the people who are carrying the work — including the person receiving the critique.

A team that cannot talk about performance cannot talk about standards. A team without standards will invent politics to fill the vacuum.

I would rather have the uncomfortable conversation early than manage a surprise later. That preference is not soft. It is operational.

Saying No to Roadmap Pressure Without Losing Trust

Karl Hill — Fri, 07 Aug 2026 14:31:28 +0000

Roadmap pressure is not a villain story.

Product wants progress. Mission owners want outcomes. Engineers want work that is finishable. The conflict is usually real, not political theater.

The leadership failure is pretending everything can fit.

I have watched this pattern across NASA programs, product teams, and aerospace delivery: when engineering cannot say no clearly, the team says no later — through missed dates, fragile releases, and burned people.

Trust is a sequencing skill

Non-technical partners rarely need the stack explained. They need to trust your judgment about capacity and risk.

That trust is built when you:

Name the constraint before the deadline becomes a crisis
Offer options instead of a flat refusal
Protect the commitments you already made
Show working progress on the things that remain

A “no” without alternatives is obstruction. A “yes” without capacity is a lie with a smile.

Make the tradeoff the product

Good pushback sounds like:

“We can ship A this sprint if B slips a cycle.”
“We can hit the date with reduced scope, or full scope with a later date.”
“We can keep quality gates and move slower, or cut gates and accept operational risk — here is what that means.”

Now the decision belongs to the partnership, not to secret heroics in engineering.

Staff and EM leaders earn credibility the same way here: by translating constraints into decisions other people can own.

Protect focus as a team system

Saying no once is easy. Sustaining focus requires operating habits:

A visible priority list the team can recite
Intake rules for interrupt work
Definition of done that resists last-minute scope inflation
Retros that examine broken promises, not only broken tickets

Without those, every “no” becomes a personal confrontation. With them, “no” is the system protecting delivery.

Keep the relationship warmer than the constraint

Tone matters. Stakeholders remember whether you fought them or fought the problem with them.

I aim for:

Early warning over late surprise
Options over absolutes
Written clarity after verbal debate
Follow-through that matches the last agreement

Engineering leadership is not about being the person who always delivers the maximal ask. It is about being the person whose commitments remain true when the roadmap gets crowded.

That is how teams keep trust — and how managers keep seats.

Staff IC to Engineering Manager: What Changes in the First 90 Days

Karl Hill — Fri, 07 Aug 2026 14:30:34 +0000

Moving from Staff IC toward Engineering Manager is often sold as a title change.

It is not.

It is a change in the unit of work. As a Staff engineer, your craft is systems, leverage, and technical judgment. As a manager, your craft is people outcomes — growth, clarity, trust, and a team that ships without depending on one heroic person.

I have spent years practicing the Staff side of that bridge: coaching, operating standards, stakeholder translation, and delivery systems. The first 90 days in an EM seat are where those muscles become the job.

Days 1–30: Learn the real system

The org chart is not the system. The real system is:

Who people trust when something is on fire
Where decisions actually get made
Which rituals create clarity versus theater
What “good” looks like to product, mission, and engineering

Your job early is diagnosis, not reform.

Listen in 1:1s. Watch how work enters the team. Notice who becomes the bottleneck when pressure rises. Map the invisible dependencies before you rearrange them.

Staff engineers are often hired for answers. New managers earn trust by demonstrating they understand the constraints.

Days 31–60: Make ownership explicit

Ambiguity is expensive. In the middle stretch, turn fog into contracts:

Clear priorities for the next quarter
Explicit ownership for services and outcomes
A definition of done the team will actually defend
Feedback loops that catch risk before demos invent optimism

This is not bureaucracy. It is kindness under load.

The Staff mistake is to keep being the glue. The manager job is to make glue unnecessary — by distributing ownership and coaching people into it.

Days 61–90: Raise the bar without becoming it

By the third month, you should be able to point to team outcomes, not personal heroics:

Onboarding that gets someone productive without a tribal guide
Reviews that teach instead of only gate
Roadmap conversations where tradeoffs are visible
A cadence stakeholders can trust even when scope changes

Technical depth still matters. EM candidates from Staff paths win because they can still smell a bad design. What changes is whether you solve it yourself or create the conditions for the team to solve it well.

What does not change

Mission context. Honesty about risk. Respect for craft.

If you strip those out in pursuit of “people management,” you become a status reporter. If you cling only to IC excellence, you become a bottleneck with a new title.

The bridge is both: keep the technical judgment, move the accountability to people and team systems.

That is the work I am building toward — and the standard I already use while shipping as a Staff engineer.