This post continues my 2 "primer" post on product management differences between Enterprise & Desktop Software:
- Differences between Desktop & Enterprise Software
- Product Management of Enterpise V/s Desktop Products
For all the reasons discussed in the previous 2 posts it should be clear that the buying cycle of Enterprise software is longer -- because large parts of organization would get affected by the purchase & use of Enterprise software.
Buying Enterprise Software
Evaluation is done at a broader organizational level. The budget is bigger for enterprise software -- the cost involved is not only buying software but making sure all users affected by the software understand how to work with it. Implemention, Consulting, and Customizations -- all these become important issues in Enterprise software purchases.
Buying Desktop Software
Desktop or Consumer software comes normally as a download or packaged in a box with a CD and user manual. Enterprise software, quite the opposite may have standard "modules" that are customized based on the needs and existing processes of the buying organization. Normally, customization is not done at all in desktop or consumer software.
Customizing Desktop or Enterprise Software
Almost all customizations of popular desktop software happen via 3rd party Extension developers. Desktop software providers primarily focus on providing standard functionality to its core set of customers.
In the Enterprise space 3rd party developers build niche solutions around an enterprise software -- bridging legacy systems, focus on an industry vertical etc. But Enterprise Software providers themselves do a lot of customization via their inhouse consulting teams.
Software Development Process -- differences in Desktop & Enterprise Software
The software development process is therefore impacted by these differences. Desktop or Consumer software is developed in fixed time cycles usually lasting 6 to 18 months. Then bugs are collected and 1 or 2 bug fix packages are released.
In the Enterprise space software development is longer and different. Standard modules are developed by the software vendor and then customized for customers. During the customization process, bugs or requirements may come up that need to fixed "before" the users in the organization could even begin using the software.
Product Management experience in Enterpise v/s Desktop Software
Thus the product management experience in building desktop/consumer software differs quite significantly from building enterprise software. Very often enterprise software products have limited customers that provide the entire revenue and requirements for the product. The product manager has to focus on few such customers, talk to key stakeholders in the customer-enterprises, resolve the problems they face in implementation, customization etc.
But consumer and desktop software Product Managers, have to deal with several thousands, sometimes millions of individual users of their software. Revenue and Requirements get added 1 individual at a time. Standard ways of interacting are focus groups, online forums, email, phone interviews etc.
Keeping the above mentioned differences in mind between Product management of Desktop V/s Enterprise software should help you tackle your next Product Management interview. If it does help, please do leave a note/comment to tell me that how :)
Read More:
- Pragmatic Marketing Inc.'s note Desktop Vs. Enterprise Applications: The Impact on Product Management
- Software Product Management
