Who let the product die?

One evening, few products who registered to the Products Anonymous forum met at a local cafe to introduce themselves and share their experiences. They started off in a round robin fashion and we shamelessly listen in…

I died as I arrived as I did not serve any significant purpose for my users. People did not pay for me as they were convinced that I am not good as existing products they were using. Few who dared to risk by buying me but they did not like me. I am result of reactive product manager.

I made good sense to my buyers and they too fell in love with me but none took me home simply because they could not take me home. I did convince them about benefits that I can bring to them and they did agree to most however owning was not so cheap. Their hands did go in their pockets but only few could come out. I wish I could have been better priced but my over confident product manager thought otherwise.

I made success the moment I hit the stores and I was at all the places. I was talk of the town. This was 2 years back, the same people who rushed to shops 2 years back to buy me are the one who hate using me. It is not that I am a bad quality product but like all other products I too need some maintenance which my makers really did not bothered about. My buyers find it hard to repair me or replace my parts, my mechanics are difficult to reach and they simple do not live up to my buyer’s expectations and my product manager believes customer satisfaction is not his responsibility. I am suffering because my product manager never bothered about customer satisfaction.

People liked me and they want me. Few took me home but returned me to the store simply because they find me little too complex to set me up, forget using me. And for those who could configure me correctly found difficult to use me. I know I am a good quality product but at the same time I am difficult to use. My product manager could never appreciate importance of user experience and even though I am efficient I died premature death as I was made me so complex for my users.

I was created so well by makers that I never thought I will spend most of my life in warehouse. Somehow my product manager screwed up big time. He put me in the wrong shelf. He should have put me in the second from right shelf instead he put me in second from left shelf. Pathetic, people who came buying me could not understand my need to be on second from left shelf and those who went to shelf at second from right could never find me. This guy made me nice but could never understand my use. My product manager only had technical sense but marketing sense was missing big time.

I was born with bad luck or shall I say bad timing. The day I hit the shelf I was liked by buyers but most refrained from picking me for simple reason that they knew what my product manager did not knew. There was something new coming in few days and most anticipated that product to be better than me. As a result no one picked me and though I was at par with my competition I did not gain enough word of mouth and eventually lost the batter. My product manager’s ignorance killed me.

All went well for me but I still could not make it big. I was good but business leaders never believed in my potential or success. They always wanted a reason to shut me down and my product manager never bothered to advocate about me to executive team. I died slow with great pain. I could only wish that my product manager should have been stronger in advocating me.

@mathurabhay

3 Key Personality Enhancements from Agile

All over the world, Agile methodologies are changing the ways of working and are leading to faster value realization for both the businesses and customers. The value that Agile methodologies are bringing is evident from the fast paced and the high volume of companies and organizations adopting Agile.

Scrum-personalImpr

However, the angle that we are looking at here are the personality improvements that individuals get from being in an Agile team. These are traits that team members get from working in a self organized Scrum team and will be an asset for life. These traits are visible across most flavours of Agile, but we shall stick to Scrum for the moment.

Small steps with feedback: Scrum advocates frequent small releases to market with valuable content rather than one big release at the end of the project. This way, each time a small release is made, feedback is obtained and is ploughed back into the product to make it better. Scrum teaches you to take small steps towards the goal, not relying on one big jump at a later point of time. Scrum understands that planning is important, but it is more important to get moving. Similarly, with each personal goal, it is good to identify the goal, break it down into smaller parts, implement them one at a time, observe the results and fine tune or change the goal as needed. Many times, the personal goals and resolutions need constant reminding and by making frequent small changes, you are not only keeping the goal alive, you are also taking steady steps towards the final goal. As Ralph Waldo Emerson puts it “An ounce of action is worth a ton of theory”

Effective Improved Communication: Scrum puts power into your hands as a team member. To exercise this power, you have to talk and express yourself in planning and estimation sessions, make your voice heard in daily stand-up meetings and voice your opinions in Retrospectives. Scrum’s rituals are all about being heard without being dominant. Initially, it might be hard for some team members to lose their inhibition, but Scrum’s daily stand-ups, planning meetings and retrospectives urge each one to open up and participate. In a positive way, team members are forced to open up in a trusted team environment and over time, this gives confidence to individuals to be more expressive in bigger groups and forums. Voila, Scrum has made you a better public speaker.

See the other person’s perspective: A team composition in Scrum consists of subject matter experts (SMEs) in Development, Testing, etc. As they plan together and work together Sprint after Sprint, they orient themselves towards the Sprint goal each time. With this, once a person is done with his/her task, he/she is now looking to pick up and contribute towards any other task that needs to be completed to meet the Sprint goal. The team member is picking up new cross functional skills and looking at things in a new perspective along with contributing towards the Sprint goal. Development and testing silos are broken and the team becomes self organized. Each person is able to understand and appreciate the other’s views and experience.
This experience teaches us to think more broadly when we face a situation in life where instead of criticizing a person who holds a different perspective, we try to put ourselves in his/her shoes and think from their perspective. Though this is no rocket science, the experience from working in an Agile cross functional team allows us to pause and listen to a perspective that could be valid and totally different.

Do let us know how your personality has gained by working in an Agile environment.

The Silent Achiever

Here is a good article about the 7 Must Have Project Management skills. I really liked the way that it is laid out and I believe that these skills are Must Haves for a successful Project Manager. However, the skill No. 6 “Recognize and solve problems quickly” rang a bell. I do agree that a Project Manager should be able to see and resolve a problem quickly. However, what I think is a better skill to have is the ability to predict a particular problem or risk before it happens, work on it pro-actively and nip the problem in the bud.

The difference here is between a Hero and a Silent Achiever. Imagine two adjacent fields with dry grass and bushes on a hot summer day. On one, there is a fire caused by the extreme heat while on the other field, there isn’t. A Hero might be seen as one who goes in a helicopter, stoops low and douses the bush fire that is raging. The Silent Achiever is one who realized that the atmosphere is dry and hot, predicted the bush fire and cut the grass or sprinkled enough water on the field to ensure that the bush fire does not occur. So, for the casual observer, it seems to be Business as usual and the effort put in by the Silent Achiever is not usually noticed. Continue reading