Showing posts with label Engineering Manager. Show all posts
Showing posts with label Engineering Manager. Show all posts

Thursday, September 10, 2026

How Trustful is Your Listening as a Manager?

 

One of my mentee wanted to meet.  I thought to meet a mentee and converse as we travel to our work places.  I shared this plan with the mentee to know if she is comfortable.  I said this plan can help her to be in office in working hours and no need to travel on weekend to catch up.  It worked for her!

We traveled in the Namma Metro of Bengaluru and I listened to her.  I listened to all what she had to share.

Later we got down and walked to a point where we have to split and take our paths to workplace.


Listening the Vent Out

She thanked and said, "I came thinking, you would talk all and advise on what to do.  But, you did not speak for 5 minutes in last 45 minutes, and no judgement."

Listening to her I understood, there is no need for me to talk; I should listen quietly.  She was in the loop of anxiety and exhaustion.  Just she wanted someone to vent out what she is going through.

I knew she can handle it better given she understands the anxiety and how it is exhausting and holding her.

I did a good and useful listening, and a very little talk in this travel and walk.

I'm aware, I listened just one side.

Why she chose me to share what's happening in her work? The trust!


Leadership and Listening - The Trust!

I wish, we will have a manger or skip managers who listens for first; then ask why this way, and not the way which is assumed to be the appropriate.

In a place and space where the business is executed, asking for someone to listen and respond is a big ask and expectation.

It is hard to find a manager or senior who listens for first before giving the advise or instructions on what to do, or lists the expectations with no conversations.

If you have one such senior or a manger who listens for first, let know that person.  That person needs to be recognized and appreciated.

Connecting to the people in the team is important before giving the feedback, corrections and instructions.

To connect, listen and go as a team it needs trust.  If there is no trust it won't happen in a meaningful and helpful way.  It won't be felt at all.  

The connecting, listening, sharing, and being a team is an emotion.  Later everything!  If the emotion is not healthy and alike, it won't work for a long run.

This is my experience and consistent learning by being a team with my teams

The engineers know what do most of the times.  The clarity on what is of priority to the business and manager has to be communicated by saying why it matters.  If you analyze, in most cases the clarity on what is priority will be missing.

All the team need is -- a feel that they are listened, and at times someone to vent out what they are going through in the processHaving someone to vent out can happen only if there is a trust between the two.

Ah! Your manager and director also need someone to vent out and heal. Do you expect the healing of your manager's to be like marketed self-healing automation?  If so, it wont help you and your manager!  Where is your manager venting out?

A skilled manager is an exceptionally skilled counselor and listener for first.  You can be one for your team, people, organization and community.  Wouldn't you?

This skilled manager would be consistently building the trust.  When the team as well builds the trust with the manager in an open mind, it helps.  

The trust built from manager does not mean the confirmed promotion or saving the people from layoffs or responsible for the growth of people.  

The trust here means being practical, supportive, listening, emphathetic, convrersing, offering the assistance needed and suggesting what works in the current business.

In the days where an Engineering Manager or Engineering Director runs the teams and its activities, it is [not] hard to get time for conversing with team to know them.  

It is a thin line for the Engineering Managers and Directors to have this caliber.  

Unfortunately, the organization, CxO's, VPs and HR staff ignore to evaluate this caliber and skills in the senior leadership.

If the manager and director are just behind the backlogs and deliveries with the boss attitude, the team will be going through the trauma of life time.  This is not healthy for the organization, business, and for its people.  As a consequence, either or both the business and people gradually move out.  I'm aware that you know this!  Don't you?

You will be remembered for how trustful you are, how you spoke, responded, assisted, and how you solved the problems together with the people of your teams and organization; not for what and how you deliveredIt is forgotten in the next 3rd sprint cycleCheck your sprint history to know what is remembered about you.   

I want to get better each day in the caliber and skills of building the trust.  This does not mean I'm a punch bag or saviour.   It means -- I'm open, trustable, learning, upskilling, practical, human centered and bussines oriented.  The differentiator!




To stop here, 

  • What is trust?
  • How you are building the trust factor with your manager?
  • How you are building the trust with your team as a manager?
  • Are you delivering yourself as a bossy leader for your people?
  • What's the trust equation between you and your teams?
  • How trustful is your listening and practicality?
  • Do you listen? How connecting it is?
  • Are you also one among those task checkers and "yes" sayer to please the people above you and impress them?  

Impressing should also be to your team members and not just the people above you.  

Don't please be it to your team or people above you! It won't work and help with anyone in longer run.

Impressing and pleasing are not the same.  Whis is more trustable?



Monday, March 23, 2026

In Software Engineering The Numbers Do Not Mean Direction With Clarity

 

I came across a post where a person from community said, he is making 40 PRs a day.  Further, he said, the long standing architects there could not keep up with that pace.  It sounds impressive to one listening it.

Wait!  This put me into a thought.

I'm writing 100+ test cases and executing the 100+ test cases reading line by line.  How should I consider and interpret this?  How do my reporting manager look at this and interpret my contribution and value add?  Do I get the big hike and promotion in each cycle?


Why I say this?

  • Making 40 PRs in a day is as good as writing 100+ test cases and executing it -- when the number is expected and rated.

In a day, what can one push in 40 PRs?  Is this in a same repository or to the different projects repositories?  I have no idea.  But, as a engineer, I have a concern when I see that number -- 40 PRs or 100+ test cases by a person.  What are the review guidelines?  Who is reviewing it?  What is evaluated in the review before the merge is approved?


Engineering Manager, Numbers And Direction With Clarity


While one is on a intended direction with clarity the numbers make a better story.  If not, can it still make a story what is expected?

As an engineer, I see the numbers in everything and whatever I do.  The numbers help to represent, describe and communicate.

When the focus is on the numbers, it does not mean one is having the clarity.  

For example, I'm executing 50 test cases and 100+ in an automation run.  Does the organization, business and my peer programmers get anything from this number?  Will it be counted in as my value addition and contribution?

If we engineers are evaluated on numbers, I have seen the engineers running with the spreadsheet, number of PRs, test cases, product stories, the tickets marked as 'done', instances created and orchestrated.  Isn't it?  Do you see this at your work?

Engineering and Numbers

I learn, when we engineer a solution the goal is to have the clarity on what we are going to do, why and how.

Having the clarity means removing the ambiguities and being aware of it.  This is a major part of the solving in an engineering.

When the clarity is established with no confusions it sets a direction.  This direction is important with a clarity; it tells where we are heading, why and how.

Implementation is one part of the big engineering.

Do numbers remove the direction and clarity?  If one is obsessed with numbers and biased to it, it can derail the efforts.

When we are biased and acknowledge one's voice and thought in an engineering, we are not solving.  We are setting an example of Factory Pattern which the software engineering is not all about.

Engineering Manager, Numbers, Clarity and Direction

I as an Engineering Manager, my primary goal will be to set the direction to team with clarity.  If I do no set a direction and why we want to accomplish it, the team and delivery will be in chaos.

If anyone in my team is behind the numbers for showing PRs, test cases and stories, I will assist them to build the clarity and see it.

I will help them in knowing what the management sees and how to show one's delivery as an impact in conversion and numbers.  

Why this impact conversion matter -- I will talk about it and help to visualize it.  I did not get this from my engineering managers.  It has costed me and the team though delivery went on time sprint on sprint and KPIs looked as set and expected.

A person making 40 PRs and 100+ test cases in a day, is a smoke which indicates something is not right!



To end here, here is the sum up
  • The number of PRs in a day and test cases written and executed by a person looks impressive, but it is not a impact and conversion.
  • Remove the ambiguities, establish the clarity, set the direction and evaluate it consistently.
  • Software Engineering is not all about the numbers, PRs, stories, tests, instances, pipelines and orchestration.
  • Engineering Manager is critical role in the Software Engineering -- this is a role which sets the direction to the development teams with clarity by resolving the ambiguities to deliver with the velocity.
  • The management wanting the numbers and asking for it can mislead the effective and skilled Engineering Manager.
  • This two not the same -- 'the numbers' and 'the conversion and impact'; these two are numbers with different stories.
  • 40 PRs and 100+ tests by a person in a day does not mean she or he has clarity and direction.

In today's timeline of AI and LLM, it is the number of tokens.  Someone saying I used less number of token is a value add?

Then, what is clarity with direction in the Software Engineering?  What it is to your reporting manager?  What it is to the business and management who decides on your employment, hike, promotion, benefits and growth?

Ask your Engineering Manager.  It is not too late.