The accidental profession: Product Manager

I work as a Lead consultant at Thoughtworks and my role is usually called Business Analyst. This post is entirely about hoe I ended up becoming a Product Manager.

Like what Steven Haines tells in this book: “THE PRODUCT MANAGER’S DESK REFERENCE”, Product Manager is an accidental profession.

"You may have backed into Product Management from another field or
business discipline.”

I landed this position because of the following reasons:

We are a services company. No one was interested in a product team.
No one was sure what to do as a Business Analyst in the product team
No one was convinced that this specific product would be successful.

I ended up getting the job and was left to figure out what to do in the team.

I was to be the business analyst trying to line up functional work for the product engineering team
I have to manage the team - with respect to the team members and make sure I plan for the functional work to complete
I was to interact with our current product owner and build the product road map.

What I ended up doing - as the title suggests - was entirely different.

p.s: “The Product Manager’s desk Reference" is a really good book to start learning. You can order it from Amazon here

Comments

Principles for developing systems that are anti-fragile

I have been trying to make sense of what anti-fragility means and how do I use that in my day job. As a Business Principal, I tend to work with the abstract but orchestrate a program of work that needs details. This makes my job a little difficult in the terms of designing for more self-preserving systems that preserve the spirit of the abstracted strategy or vision. I came across an article from Daniel Russo on anti-fragility and his attempt at creating a manifesto similar to the manifesto for agile software development. For more reading on Daniel Russo, here is his profile: http://djrusso.github.io More reading from his paper here: https://www.sciencedirect.com/science/article/pii/S1877050916302290 This post is an attempt for me to understand what goes into developing a program that uses every opportunity to strengthen itself and achieve its objective - the vision. I liked the approach of principles for developing systems that are anti-fragile. It i...

The cost of delayed decisions in Enterprise

Large enterprises have started their IT journey in earnest. However, they are miles behind what is happening. Some of them have been trying to learn faster by creating research programs or separate business unites to try out and learn a few exotic ideas that have not yet gained acceptance in the industry or enterprise. Enterprises have moved record collection and data to IT long back and were pioneers in that. However, since the advent of personal computers, they have been left behind. Internet and mobile have left them far behind. For example, Network security, big data, mobile apps. social applications are solved problems that the enterprise choose to ignore.

My Journey in Inquiry and Advocacy - An experience report

It is recently that I have consciously started practicing Inquiry. Let me explain. I am a consultant who constantly looks at the situation and comes up and implements the solution to progress from there. While I do that, I constantly use Inquiry as a means to progress - one of the key facilitation technique specifically in multiple stakeholder situations.

Life of a Business Principal in Consulting

Search This Blog