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

713
ineveg•

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 :)

3
GoetzeriousOP•

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?

2
JoshRTU•

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.

3
GoetzeriousOP•

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.

1
Mustool•

Is there a smart way of figuring out mistakes ?

1
Legrigeois_l•

Hello,
from my perspective as a PM, the fact that you have a "captive" user base doesn't change your product management practices, especially for B2B products. Nevertheless, the mindset can be a little different:

  • or your product business case(s), it might not be as explicit as it would have with external customers (nobody directly pays for it but you have to get budget to develop)
  • you have to onboard your user to use your product nonetheless but will they do it willingly (the product make the situation 10x better that the old one) or will they be forced by their hierarchy. It will probably be a bit of both.

My personal recommendation would be to go & observe some of your users that have a reputation to try new stuff to find out what they consistently believe is their major hurdle (and most importantly, why they believe it is one) & try to find a workaround (which isn't necessarily a product per se). Repeat until you get enough feedback that the situation as significantly improved. With these verbatim, you can now start to go higher in the hierarchy to get more users on board.

For example, they tell you that when they send one of the mandatory document, it often comes back because information is missing/incorrect. You go & see and realise that they fill the document while usually being in front of the customer. To close the deal, they need to interact with the lead which they can't easily do while typing hence typos, inaccuracies, etc. Can you provide a lighter version of the form (like a checklist) so that they can come back later & easily filling the blank? Or if they need to copy ID information, is it possible for them to take a picture & come back at it later? etc.

The way they frame your solution when evangelising it to their colleague is probably using their own words which can make it easier for you to "sell" it and identify what metrics truly matter.

"I've sign more deals..."

"I'm wasting less time filling it..."

"I don't need to ____ anymore, now that I have ___"

"I get the result of my work earlier, as the bureaucracy processes my order faster, etc."

I hope it helps,

3
that_sucks_bro•

sounds like you're a platform PM.

platform revolution would be a good book

1
GoetzeriousOP•

Thanks for the recommendation. I'll add it to my reading list. It's by Geoffrey Parker among others right?

1
Bradmagar•

Great question and highly relevant to me as I'm in a similar situation.

Part of my approach is to make the case to senior management to fund my training PM too.

This gets them interested in you and your endeavours as well as some professional reassurance for you.

1
Tattooie•

There's some good advice here but the big thing that is usually missed when working on internal tools is developing a clear set of goals.

Any tool your company uses is likely there for a purpose, I would suggest you start by trying to organize the various tools being used into logical groupings. This will help you determine which tools have the greatest business impact and should be prioritized higher.

Once you have the products organized you can start to develop a product vision for each of them, it doesn't need to be anything too crazy, just a high level understanding of what success means for each tool and how you'll measure that success. There's almost always a way to associate dollars to improvements on internal tools, which will protect you from stakeholders who just want you to work on their thing.

From there, you'll want to start setting goals and prioritizing those goals one product at a time. Task success is a great metric to start with for internal tools but it's only helpful if you've taken the time to define what success means. Time to complete a task is another great one, you can create a ton of value by automating processes that are highly repeatable and make the end users job easier.

1
Aektann•

Piggybacking on the thread: I did that for a small amount of time and felt like a glorified Business Analyst, just gathering requirements.

IMO, PM is not someone who 'gathers requirements'.

1
[deleted]•

If you know how to build software, just resolve the most important requests and complaints and you'll be fine.

0