Skip to main content

On titles and seniority ranks in an organization

 

I lately was asked to participate into workshopping in creation of "career paths and titles" in a software development organisation.

I have seen a few. Some with a lot of work put to them. And all wrong.

Is it them or me? Definitely me.

That's because I don’t in general like titles, the way are assigned to people. I think it would be more reasonable to discuss the responsibilities a person has and things they do, periodically. And help everyone pick a title that describes this well. And adjust it whenever they want.

Seniority is also a hard concept. Is it about years in field? Or years in life? Or about specific knowledge, or knowledge in general? Or about the successes and mistakes you have been part of? Or on how you treat yourself and other people? Or on how you compare to another random coworker?

I don't know, and maybe I don't care. Why other people do, at least because of the money. And the way salary raise is usually tied up to a promotion.

For that I have been thinking of a model, where you would always negotiate a contract from one to a few years. And then nearing the end of the contract negotiate a new one. Based on your own and the employers evaluations on the value of the work been done. Kind of like they do in sports, with professional contracts. 

Alternatively and preferably, we all get the same base salary, and a similar cut of the profits.

That’s communism and doesn’t work?

Well capitalism has and is screwing up the world, so people should start to get joy out of other things than money and possessions.


Buuut as that is not gonna happen probably ever, I will continue by picking and using my own titles as I go.

And for the request to participate - I think I will pass and use my energy on something else that I care more about. Been doing that quite a lot lately and am feeling pretty good about it.



Comments

Post a Comment

Popular posts from this blog

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.
3 comments
Read more

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...
Post a Comment
Read more

The miseducation of Exploratory Testing

I've been noticing a phenomenon lately, that is the over/misuse of the term Exploratory testing. As many testers seems to have kind of settled for the Exploratory testing paradigm and have moved to new frontiers like checking vs testing , it seems many other parties are really getting into it, and of course understanding it in different ways. Couple of examples of this phenomena: 1. In my final days as a consultant one of our sales people, had visited a customer who had no experiences about testing, but specifically requested the sales man to give a offer on Exploratory testing 2. I just looked at the program of Agile testing days 2013 , and really many of the testing related talks were labeled about Exploratory testing, although to me many seemed to talk/practice testing in generally It's nice that the Exploratory testing is gaining momentum, but I am also a bit worried about it. The examples listed above could be supported by many others, which kind of give me the impr...
2 comments
Read more