Skip to main content

Honesty pays

I share this story every once and then when talking to people, so thought to write it here too.

About 8 years ago I had got my second consulting gig, working on a big company and on a huge project. And as huge projects normally go it was already very late and presumably very over budget. This had caused a pretty tense atmosphere around the project and things that delayed it further were not looked very fondly on.  And so it happened that I made a mistake of that sort. It was kind of done by a person I was "coordinating", failing to provide a complete set of specifications we had worked on to a vendor, resulting in a release missing a lot of important stuff.

I was very stressed being a pretty new kid on the block and considering my options, whether to lay low, blame the coordinate or the vendor, quit, etc. But in the end decided that I would go for admittance. So I walked to the office of the rather intimidating program manager, knocked, went in and said that "I messed up" explaining what had went wrong. I still remember the angered face, the way the PM inhaled and did not breath out for a while. But then his face softened a bit, and he asked that what could we do about it. So we discussed about our options a bit, came up with a certain one, and then I left feeling still a bit stressed about the next consulting contract renewal occasion, but very relieved about being able to spill the problem out. And thinking that no matter what would happen, honesty had paid off.

A few days after this I was in a reoccurring program status meeting, and the matter of the delay came into the discussion. One member started asking about this in a pretty tight voice, but was cut off by the PM who said that this has been already discussed with me and is under control. So the topic was switched and I was feeling that honesty had really paid off.

Going about a year after this I was talking with a sales rep from our consulting company and she told me quite a nice thing. She had had a meeting with the program manager in an effort to sell some more people into the company and he had simply said, "What we need is more people like Anssi, so if you got some then I am buying."

Honesty pays :)

p.s. This is the first post out of 26 I will be publishing in the year 2018, after a bet made with a colleague to publish one in turns every week during the year. Off to you Mili ;)

Comments

Popular posts from this blog

Periodical retrospectives are lame

  "You got nothing, not a single thing?! Well lets just end this here then." I remember well when I said this, being very frustrated. About ten years ago I had been working as a Scrum master for a team some months, and putting quite a lot of effort into planning our scrum teams sprint retrospectives. Lot of work also because I felt we were not getting too much out from them; not very good discussions, very few actions, and even the few actions we did come up with did not stick.  And then it happened: a retro where none of the participants came up with anything to say about the sprint. Regardless of the retro topic boxes, reading of books on retrospectives, getting inspiration from tools like retromat.org, having them in different places, using all kinds of different formats and rainbow coloured post-it notes. Not a single thing. Blank.  So then I said the words, out of frustration, mainly to myself. Why couldn't I get this thing everyone is so hyped about to work? Af...

Testers doing test automation - is that the most important thing for you to do right now?

I've been thinking quite a lot about tester's moving to do test automation.  Lately beause of these three things: 1.  European testing conference , a great testing conference I attended couple of weeks ago. It is very cool due to many things; the way the speakers get compensated, the focus on the conferring side of conferences making it very easy for people to discuss stuff, the way the talks are chosen, and because there are also a lot of developers joining. So anyway when I was talking with several of the attendees, it was a bit strange how it was easier for me to talk about the product development as a whole with the developers, where as with the testers it more naturally moved into talk of automation and tools. Also on the open space, I think the majority of the topics pitched was automation or tool related. And quite little on the process or on the customer facing side of product development.  2. In my company there are a lot of different products and...

Testing drunk

(My first blog writing ever.) I've been thinking a long time that it's funny how many bugs I find by accident. Try to do something, make a mistake and boom - a bug is found.  Making the mistakes intentionally doesn't quite work - that's why they are called accidents I guess.. So I've thought of ways to make myself more prone to accidents, coming up with an apparent one; testing drunk. TUI (testing under the influence). So this I gotta try. More to come on that later.