Product management – Bibliographic Wilderness




	Skip to content

	
		
			
				
					
												Bibliographic Wilderness

										


				
									
						Menu					
				
			

		
	


				
				About
	Contact


		
	
	
	
	
		

	
		

		
			

			
			Product management
				
			
				jrochkind			
							
					General				
			
			
			
				February 3, 2021			

					

	
	
		
In my career working in the academic sector, I have realized that one thing that is often missing from in-house software development is “product management.”




But what does that mean exactly?  You don’t know it’s missing if you don’t even realize it’s a thing and people can use different terms to mean different roles/responsibilities. 




Basically, deciding what the software should do. This is not about colors on screen or margins (what our stakeholderes often enjoy micro-managing) — I’d consider those still the how of doing it, rather than the what to do. The what is often at a much higher level, about what features or components to develop at all.




When done right, it is going to be based on both knowledge of the end-user’s needs and preferences (user research); but also knowledge of internal stakeholder’s desires and preferences (overall organiational strategy, but also just practically what is going to make the right people happy to keep us resourced). Also knowledge of the local capacity, what pieces do we need to put in place to get these things developed.  When done seriously, it will necessarily involve prioritization — there are many things we could possibly done, some subset of them we very well may do eventually, but which ones should we do now?




My experience tells me it is a very big mistake to try to have a developer doing this kind of product management. Not because a developer can’t have the right skillset to do them. But because having the same person leading development and product management is a mistake. The developer is too close to the development lense, and there’s just a clarification that happens when these roles are separate. 




My experience also tells me that it’s a mistake to have a committee doing these things, much as that is popular in the academic sector. Because, well, just of course it is. 




But okay this is all still pretty abstract. Things might become more clear if we get more specific about the actual tasks and work of this kind of product management role. 




I found Damilola Ajiboye blog post on “Product Manager vs Product Marketing Manager vs Product Owner” very clear and helpful here. While it is written so as to distinguish between three different product management related roles, but Ajiboye also acknowledges that in a smaller organization “a product manager is often tasked with the duty of these 3 roles.




Regardless of if the responsibilities are to be done by one or two or three person, Ajiboye’s post serves as a concise listing of the work to be done in managing a product — deciding the what of the product, in an ongoing iterative and collaborative manner, so that developers and designers can get to the how and to implementation. 




I recommend reading the whole article, and I’ll excerpt much of it here, slightly rearranged. 




The Product Manager
These individuals are often referred to as mini CEOs of a product. They conduct customer surveys to figure out the customer’s pain and build solutions to address it. The PM also prioritizes what features are to be built next and prepares and manages a cohesive and digital product roadmap and strategy.
The Product Manager will interface with the users through user interviews/feedback surveys or other means to hear directly from the users. They will come up with hypotheses alongside the team and validate them through prototyping and user testing. They will then create a strategy on the feature and align the team and stakeholders around it. The PM who is also the chief custodian of the entire product roadmap will, therefore, be tasked with the duty of prioritization. Before going ahead to carry out research and strategy, they will have to convince the stakeholders if it is a good choice to build the feature in context at that particular time or wait a bit longer based on the content of the roadmap.
The Product Marketing Manager
The PMM communicates vital product value — the “why”, “what” and “when” of a product to intending buyers. He manages the go-to-market strategy/roadmap and also oversees the pricing model of the product. The primary goal of a PMM is to create demand for the products through effective messaging and marketing programs so that the product has a shorter sales cycle and higher revenue.
The product marketing manager is tasked with market feasibility and discovering if the features being built align with the company’s sales and revenue plan for the period. They also make research on how sought-after the feature is being anticipated and how it will impact the budget. They communicate the values of the feature; the why, what, and when to potential buyers — In this case users in countries with poor internet connection.
[While expressed in terms of a for-profit enterprise selling something, I think it’s not hard to translate this to a non-profit or academic environment. You still have an audience whose uptake you need to be succesful, whether internal or external. — jrochkind ]
The Product Owner
A product owner (PO) maximizes the value of a product through the creation and management of the product backlog, creation of user stories for the development team. The product owner is the customer’s representative to the development team. He addresses customer’s pain points by managing and prioritizing a visible product backlog. The PO is the first point of call when the development team needs clarity about interpreting a product feature to be implemented.
The product owner will first have to prioritize the backlog to see if there are no important tasks to be executed and if this new feature is worth leaving whatever is being built currently. They will also consider the development effort required to build the feature i.e the time, tools, and skill set that will be required. They will be the one to tell if the expertise of the current developers is enough or if more engineers or designers are needed to be able to deliver at the scheduled time. The product owner is also armed with the task of interpreting the product/feature requirements for the development team. They serve as the interface between the stakeholders and the development team.





When you have someone(s) doing these roles well, it ensures that the development team is actually spending time on things that meet user and business needs. I have found that it makes things so much less stressful and more rewarding for everyone involved. 




When you have nobody doing these roles, or someone doing it in a cursory or un-intentional way not recognized as part of their core job responsibilities, or have a lead developer trying to do it on top of develvopment, I find it leads to feelings of: spinning wheels, everything-is-an-emergency, lack of appreciation, miscommunication and lack of shared understanding between stakeholders and developers, general burnout and dissatisfaction — and at the root, a product that is not meeting user or business needs well, leading to these inter-personal and personal problems. 


        
    
			

			
			Share this:
	Twitter
	Facebook
	





	


	
			


	
			
				
					

		
		
			Published by jrochkind

		


		
						
				View all posts by jrochkind			
		

	

		
			Published
			February 3, 2021		

	



			
	
		Post navigation

		Previous Post Rails auto-scaling on Heroku


	
			


	
	
	
		
		Leave a Reply Cancel reply




	Enter your comment here...
	





	
		Fill in your details below or click an icon to log in:

			
				
									
			
	
				
									
			
	
			
			
	
				
									
			
	
				
									
			


	


	
		
			
				
			


				
				
					Email (required) (Address never made public)
					

				

				
					Name (required)
					

				

				
					Website
					

				

			

			
		

	


	
		
			
				
			


				
				
				
				
						
			
			You are commenting using your WordPress.com account.			
				( Log Out / 
				Change )
			
			
		

					

	
		

	


	
		
			
				
			


				
				
				
				
						
			
			You are commenting using your Google account.			
				( Log Out / 
				Change )
			
			
		

					

	
		

	


	
		
			
				
			


				
				
				
				
						
			
			You are commenting using your Twitter account.			
				( Log Out / 
				Change )
			
			
		

					

	
		

	


	
		
			
				
			


				
				
				
				
						
			
			You are commenting using your Facebook account.			
				( Log Out / 
				Change )
			
			
		

					

	
		

	



	
		Cancel

		Connecting to %s

	








	 Notify me of new comments via email.
 Notify me of new posts via email.






 






	

	




		
		
	



	Bibliographic Wilderness is a blog by Jonathan Rochkind about digital library services, ruby, and web development. Contact


				
					Search for:
					
				
				
			
Email Subscription

			
									Enter your email address to subscribe to this blog and receive notifications of new posts by email.

						
							
							Join 215 other followers							

						

											
						
							Email Address:						

											

				
				
                    
                    
                    
                    
                    
					                    
	                    Subscribe                    
                

            

			

		
		Recent Posts

			
					Product management
											February 3, 2021
									
	
					Rails auto-scaling on Heroku
											January 27, 2021
									
	
					Managed Solr SaaS Options
											January 12, 2021
									
	
					Gem authors, check your release sizes
											January 11, 2021
									
	
					Every time you decide to solve a problem with code…
											January 10, 2021
									



		Archives
		Archives
		Select Month
 February 2021  (1)
 January 2021  (4)
 December 2020  (1)
 November 2020  (3)
 October 2020  (2)
 September 2020  (3)
 August 2020  (2)
 April 2020  (1)
 March 2020  (1)
 December 2019  (1)
 October 2019  (1)
 September 2019  (1)
 August 2019  (2)
 June 2019  (2)
 April 2019  (3)
 March 2019  (3)
 February 2019  (1)
 December 2018  (1)
 November 2018  (1)
 October 2018  (2)
 September 2018  (4)
 August 2018  (1)
 June 2018  (2)
 May 2018  (1)
 April 2018  (1)
 March 2018  (3)
 February 2018  (1)
 January 2018  (1)
 November 2017  (1)
 October 2017  (1)
 September 2017  (1)
 August 2017  (3)
 July 2017  (1)
 May 2017  (4)
 April 2017  (2)
 March 2017  (9)
 February 2017  (5)
 January 2017  (1)
 December 2016  (7)
 November 2016  (4)
 September 2016  (1)
 August 2016  (4)
 June 2016  (2)
 May 2016  (4)
 March 2016  (2)
 February 2016  (1)
 January 2016  (2)
 November 2015  (2)
 October 2015  (5)
 September 2015  (7)
 August 2015  (5)
 July 2015  (4)
 May 2015  (3)
 April 2015  (5)
 March 2015  (2)
 February 2015  (2)
 January 2015  (4)
 December 2014  (2)
 November 2014  (2)
 October 2014  (6)
 September 2014  (5)
 August 2014  (3)
 July 2014  (3)
 June 2014  (1)
 May 2014  (3)
 April 2014  (5)
 March 2014  (9)
 February 2014  (4)
 January 2014  (5)
 December 2013  (5)
 November 2013  (14)
 October 2013  (4)
 September 2013  (6)
 August 2013  (2)
 July 2013  (7)
 June 2013  (10)
 May 2013  (4)
 April 2013  (5)
 March 2013  (8)
 February 2013  (6)
 January 2013  (16)
 December 2012  (8)
 November 2012  (14)
 October 2012  (6)
 September 2012  (6)
 August 2012  (2)
 July 2012  (5)
 June 2012  (5)
 May 2012  (7)
 April 2012  (12)
 March 2012  (6)
 February 2012  (7)
 January 2012  (6)
 December 2011  (5)
 November 2011  (7)
 October 2011  (5)
 September 2011  (10)
 August 2011  (4)
 July 2011  (5)
 June 2011  (7)
 May 2011  (8)
 April 2011  (5)
 March 2011  (13)
 February 2011  (4)
 January 2011  (12)
 December 2010  (7)
 November 2010  (5)
 October 2010  (5)
 September 2010  (10)
 August 2010  (6)
 July 2010  (7)
 June 2010  (5)
 May 2010  (8)
 April 2010  (8)
 March 2010  (14)
 February 2010  (3)
 January 2010  (3)
 December 2009  (4)
 November 2009  (2)
 October 2009  (3)
 September 2009  (9)
 August 2009  (1)
 July 2009  (4)
 June 2009  (7)
 May 2009  (14)
 April 2009  (17)
 March 2009  (21)
 February 2009  (11)
 January 2009  (16)
 December 2008  (12)
 November 2008  (30)
 October 2008  (12)
 September 2008  (3)
 July 2008  (4)
 June 2008  (2)
 May 2008  (11)
 April 2008  (3)
 March 2008  (4)
 February 2008  (10)
 January 2008  (7)
 December 2007  (4)
 November 2007  (4)
 September 2007  (1)
 August 2007  (3)
 June 2007  (6)
 May 2007  (12)
 April 2007  (11)
 March 2007  (9)




			Feeds
 RSS - Posts
 RSS - Comments

Recent Comments
					
							jrochkind on Rails auto-scaling on Heroku						
	
							Adam (Rails Autoscale) on Rails auto-scaling on Heroku						
	
							On catalogers, programmers, and user tasks – Gavia Libraria on Broad categories from class numbers						
	
							Replacing MARC – Gavia Libraria on Linked Data Caution						
	
							jrochkind on Deep Dive: Moving ruby projects from Travis to Github Actions for CI						
	
							jrochkind on Deep Dive: Moving ruby projects from Travis to Github Actions for CI						
	
							jrochkind on Deep Dive: Moving ruby projects from Travis to Github Actions for CI						
	
							eregontp on Deep Dive: Moving ruby projects from Travis to Github Actions for CI						


				Top Posts
	
					yes, product owner and technical lead need to be different people					
	
					Bootstrap 3 to 4: Changes in how font size, line-height, and spacing is done. Or "what happened to $line-height-computed."					
	
					Dealing with legacy and externally loaded code in webpack(er)					
	
					ActiveRecord: Atomic check-and-update through optimistic locking					
	
					Are you talking to Heroku redis in cleartext or SSL?					

Top Clicks
	bibwild.files.wordpress.c…
	apidock.com/rails/ActiveR…
	github.com/mperham/sideki…
	bibwild.files.wordpress.c…
	opensolr.com

			

			
			


		


		
							
					
						
													
											A blog by Jonathan Rochkind.  All original content licensed CC-BY. 



									

						
											

				

						
				
				Create a website or blog at WordPress.com
				
			
				
							

		
	





	
	



		
		

		
					


	
	
				

	
		

		Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use. 

To find out more, including how to control cookies, see here:
				
			Cookie Policy