Product Management for internal applications
Hey, I'm currently working as a Business Analyst at a company where we have been going through a rather successful Agile transformation (in my opinion). We don't really have a Product Management practice and I'm trying to learn the ropes while trying to build the practice up at our company. I have the support of my manager to experiment and try new things but I'm getting stuck.
Our company is an enterprise level company where the vast majority of our applications are serving internal customers. We have feature requests and new project ideas that I'm sure could keep our current software team busy for the next decade and I'm hoping to build a practice of using Product Management techniques for helping to decide how to prioritize the work.
I've been reading several books and countless articles on Product Management but I haven't been able to find anything discussing managing products where you have a user base that doesn't really have a choice but to use the software your team is developing. Does anybody have any thoughts regarding how Product Management practices that have been developed for externally facing products can be used for internal products?
Posted May 23, 2019, 12:51 AM UTC
I'm a PM on an internal facing product. All the standard product management practices are translatable - there are going to be a few differences here and there of course.
Is there a specific practice that you were thinking about when you wrote this? Prioritizing, user research, writing specs, etc? Definitely can give you any insight if you specify a little bit :)
Thanks for the offer! There is just so much that I'm trying to figure out.
To start, I'm trying to sort out what to start measuring about my products. If this were an external product I'd be starting with Activity, Churn, and Engagement based metrics. However, for situations where your users have the choice of either using your software or quitting their job, it doesn't seem like those kinds of metrics will be telling me much about how effective the software is. Or am I mistaken?
Do you have any recommendations regarding what i should be measuring about my products to start with?
Would help to get a better sense of what your product does in general. You can look at metrics such as quality of task performed (funnel metrics, accuracy, number of mistakes, how often the task need to be redone). Assuming a minimum quality is met you can then look at speed related metrics.
The key thing here is that you cannot treat quality and speed metrics as equal or else you will dig yourself into a hole. Establish clear minimum quality metrics first as a qualifier. Then assuming a minimum quality is met you can then optimize for speed. A good rule of thumb is that quality should be valued at 2x of speed.
Thanks, this is great stuff to start. I'll be looking into ways to figure out how often mistakes are made and rework needs to be done.
My company is a car dealership with branches across the country that does rentals, sales, and leasing. The products I need to support are generally used to generate the legal documents for the sale/lease or to track the rental of a car. On top of that we have some software that supplements our accounting software to track the value of a vehicle as it moves through its life cycle and a custom CRM product because licencing for CRM can get stupid when you need 500 licences for all of your sales staff.
Other than the CRM product where we do see some adoption issues, the users are fairly captive. If they want to get paid their commissions, they need to fill out the paperwork in our tools.
Is there a smart way of figuring out mistakes ?