mid-year review – Gen’s input

Remember the feedback is constructive feedback, which can help you improve as a professional wherever you go.

Be humble with the constructive feedback. Don’t be bitter or resentful.

Make sure your own performance improvement plan is honest and feasible. Once agreed, they will use it to measure your  improvement.

Key SMS: “Leave the rest to them” — if they stick to the high expectation in terms of “lead role” etc then they will conclude I’m not fit for the role. If their business objective dictates a replacement, then they will have to do it. But still I want to be remembered as an honest, diligent, albeit less competent professional.

If you need more time to take on the lead role, then ask manager for help and ask for a longer time frame.

Unless there’s someone internal, it will take a long time to hire a replacement. So they probably won’t take that decision lightly.

If they let you go before hiring, then in the interim manager would have to do 1.5 person’s job so his own quant work would suffer.

mid-year review 2016

I can understand most of the negative feedback. Some of them are within my capabilities but some aren’t.

Refuse to feel weak, inadequate, inferior, or old. Some past jobs are also too demanding — part of the GS job, part of the Citi-muni job.

Welcome the opportunity to start again somewhere else, though I will not give up improving myself on this job. The effort and attitude to keep improving myself is good for my spirit, my image, my self-image

It’s possible that managers may have already concluded I am not fit for the job (I won’t speculate) but that would be understandable and I will handle that situation well.

It’s painful but we can convert that to less hazardous energy, with a mental shift.

Some may say the situation is painful, but I will be kind, supportive to myself just as I am to my wife or my son. I won’t beat myself.

I like the let-go tips in https://btv-open.dreamhosters.com/2009/12/13/avoid-the-pain-in-this-tough-situation-and-live-with-peace-of-mind/ so I added a few:

  • I need (and have) the serenity to accept the things I can’t change.
  • Yes we CAN live through this tough situation with peace. Much less severe than health issues
  • put in 80% effort rather than straining myself with 100% effort, which may not help a lot but puts too much strain on self and family
  • don’t worry if manager still complains about efficiency — i have done my best so nothing more to strive for.
  • Do what I can and leave the rest to God
  • layoff is not bad for me and family, seriously
  • Xia Rong’s suggestion — separate my effort. On work projects, set a clear goal to keep the job; Outside the office, work on the US relocation. If unable to keep the job then it’s fine.

so afraid of losing the GS job in early 2010

Looking back at the last 3 months since my disappointing review and bonus, i am trying to understand why i had no choice but resigning on my own. I seriously considered 3 options

* if possible and lucky, find a financial developer job anywhere in NY, big or small companies
* otherwise, resign and return to S’pore.
* otherwise, resign and take a pay cut anywhere in NY/NJ in any no-name small software company or web shop

Many friends and my family repeatedly recommend that I put in the minimum effort on my current job and wait for layoff, so I can get a severance package.

I think this experience is one of the most bitter and painful during my entire working life. This is why I tried so hard to hold on to the job offers I received. Losing them, i go back to job-hunting mode and if not lucky i go back to S’pore.

autonomy, productivity, high-maintenance

Communications and efficiency are the 2 root causes, as identified by my senior manager.

For the initial 2 months i operated as a senior developer, in a self-directed mode. For example, i gave only high level updates to managers, on a weekly basis. I made decisions on implementation or how to communicate with users or external teams. However, As managers inquire about details, they see many things not done “right”. My supervisor explained a few times “we will give you more freedom and leeway once we have confidence in you”.

For a long time i felt extremely micro-managed. My supervisor was so busy (almost a bottleneck) i didn’t want to ask him at every right turn and left turn. But feedback was i should communicate more with managers. I shifted gear to operate as a junior developer, requiring lots of hand-holding — “high-maintenance”, my senior manager said. For example, i decided to give daily updates and discuss many implementation details with managers.

My communications with users was more problematic than my technical, so i needed even more hand-holding. In my 2nd year’s review this improved so much that i received top rating on client service, but still some users commented on my communications.

Hand-holding slowed me down. Productivity requires a certain level of autonomy. I didn’t know or attempt to acquire such autonomy. In fact, I avoided increasing responsibility or additional work, driven by the fear of overwhelming workload. It’s a negative feedback cycle — overwhelmed by workload so (subconsciously) i fell into avoidance mode.

Avoiding unfamiliar components of our system, i remained unfamilar with most of our system for a year (until I changed my mind to take up those components.) I also filtered out most email threads, due to information overload and other reasons. Consequently, it was impossible to gain confidence, efficiency or autonomy. So far in 3 sub systems i show confidence, efficiency and autonomy, all because of one reason — system knowledge (implementation, requirement, limitations…) I feel the pattern is the same for all the colleagues too.

Avoidance mode was my choice, a practical, healthy, self-preservation decision. I didn’t feel confident I could handle the increased responsibility, not at that time.

At end of 2008, another career advice was project management — what i call “autonomy”. However, when I tried to operate more independently, i hit resistance. 3 steps up, 2 steps down. I don’t feel managers have confidence in my judgement. Also I wanted protection and proper approval from a control perspective. So i continue to function as a junior developer — high maintenance.

##significantly better than 2005

It’s easy to fall into a hole of self-pity and fail to raise your head and see …

* better than 2005 — didn’t have a wife
* better than 2006 — didn’t have brank
* better than 2006 when trying US jobs from S’pore. now I’m in such a strong position.

* better than 2007, facing difficulty conceiving.
* better than early 2007. unable to get out of Polaris and break into a good company
* better than 2008. Hoping to stay for 12 months
* better than those 25% laid off

* better than months ago. There’s a clearer path ahead. (Good I planned my sg strategy in Nov.)

code quality unrecognized

I wonder why higher quality in my code is not recognized by my managers. From my first project till my 4th project (mid 2008), i spent 50-100% additional time
 
* adding ground-breaking email alerts
* checking nulls in more places than others
* checking missing data in more places
* adding table constraints
* adding automated tests covering 100% of possible scenarios in some cases
* adding other automated tests usinbg junit, fitness and mocks
 
(If you have time i can bring some code to show you the numerous extra control i added after my code became “good enough” by my colleage's standard.)
 
To my surprise, now i think my managers do not really consider my code quality higher than my colleagues'. They saw my code sent unusual email alerts to report suspicious data (that my colleagues ignore!). They heard i wrote automated tests. They saw the full matrix of scenarios i cover…. Undisputable evidence of higher code quality in my opinion. However, in the end, I was “influcenced” to stop these because i was consistently advised on efficiency and a little “too much” attention to details.
 
In many cases, my email alerts and table constraints uncovered data issues ignored by upstream and downstream. I thought these are proof of my higher code quality but my managers didn't recognize.
 
in early Nov 2009, there was a bug discovered in a project co-developed by me and Colleague A. In Aug, we faced a tricky timing issue between my batch and A's batch. Team lead made a simple design decision that appeared water proof, but now we know he missed a special scenario. People ask why i didn't test that. I didn't know team lead's assumption was only 99% correct. I feel this bug should not affect my reputation, but i think people see it as bug in *my* code, because i'm the main developer and it's my project.

will i get into the same problem again in another company?

Zofia,
 
(Even if you don't reply to me, i won't and have no right to blame you.)
 
You asked me “will you get into the same problem again in another company?”
 
I think in some companies i didn't have such a problem. In other companies i did have problems with my boss. Short answer to your question is “maybe”.
 
I can think of a few past jobs where I had problems with my manager. In most cases, I was not the only employee having difficulties, so problem seems to be partly in the boss. There seems to be a pattern where I often end up working under a less than reasonable manager. You can almost conclude that I was unlucky again and again looking for a suitable job, so maybe i should keep searching?
 
I can think of at least 3 managers I had no problem with
* May 1998 -> Dec 1999 (Chartered)
* Jan 2001 -> Jul 2002 (Zed)
* Jul 2003 -> Jul 2004 (Spherion)
 
These were relatively long jobs. There are other jobs where my bosses didn't complain about me
* Jan 2000 -> Aug 2000
* Aug 2000 -> Dec 2000
 
Measured by duration, in about 60% of my jobs i had no problem with my boss at all. Among the problematic jobs, at least one manager was obviously incompetent as everyone complained about him.
 
In conclusion,
* if i find one of the nicer managers, i will not get into the same problems again
* otherwise, i will do better than this time, as i keep learning on workplace relationships
 
I'm a positive, adaptable person. I am open to change. I am changing for the better…

selective and superficial listening

Thanks so much. Allow me to focus on your tip for me (Will reply to other parts of your email another day.)

“Pay attention to what your managers wants, and you should be able to handle it very well” — i will print this out and paste on my wall. I failed to really really get what my manager wants.

I often feel justified to concentrate on presenting my counter-arguments, but such concentration could affect the level of attention on listening. Perhaps as a result, i listen selectively and superficially.

Perhaps I listen selectively and superfically to most friends, family, users and colleagues.

That’s bad, but it’s worse when it’s with boss.

Action points:
* I will build up a reputation as a “good listener”, first with colleagues then with family.
* I will become a better listening boss for my future subordinates, than my boss is for me.
* I will speak less when talking to boss
* I will take more notes when talking to boss
* I will become a better listening husband for my wife, than my dad was for my mom
* One day I will become a better listening dad for my son, than my dad was for me
(My dad is a good listening husband and father.)

Oct09 avoid the pain in this “tough situation” and live with peace of mind

(A plan as of Oct 2009. Background: A GS colleague told me I am in a “tough situation”. He may feel the distress and pain is inevitable.)

Yes It’s possible.

* do what u can with 80% effort — a reasonable and vigorous effort. I used to push myself to 100% – 120% and put off family commitments
* work 8.30 -> 6.30
* don’t worry about big prj going to others
* dont’ worry if u have just one prj while other have multiple
* don’t worry if your prj take twice longer than a comparable prj by a colleague
* don’t worry if they start transferring knowledge from you
* focus on today. Guard against the habitual worry about tomorrow.
** stop ‘managing’ career
** in other words, focus on doing a good job and leave the rest to God.
*** That’s my attitude about green card, bonus and promotion. This attitude proved effective.
* go out on weekends.