Introduction
Evaluating the success of Harris Computer's iCity property tax management system requires a comprehensive approach to product metrics. To address this product success metrics challenge effectively, I'll follow a structured framework that covers core metrics, supporting indicators, and risk factors while considering all key stakeholders.
I'll follow a simple success metrics framework covering product context, success metrics hierarchy.
Step 1
Product Context
iCity is a property tax management system designed for local governments to streamline tax assessment, billing, and collection processes. Key stakeholders include:
- Municipal finance departments
- Property owners
- Tax assessors
- IT administrators
The user flow typically involves:
- Data import/entry: Tax assessors input property data and valuations.
- Assessment calculation: The system applies tax rates and calculates bills.
- Billing and notification: Finance departments generate and send tax bills.
- Payment processing: Property owners make payments through various channels.
- Reporting and reconciliation: Finance staff generate reports and reconcile accounts.
iCity fits into Harris Computer's broader strategy of providing specialized software solutions for local governments. It competes with other municipal software providers like Tyler Technologies and Accela, differentiating through its focus on property tax management and integration with other Harris products.
The product is in the growth stage of its lifecycle, with an established user base but ongoing opportunities for feature expansion and market penetration.
Software-specific considerations:
- Cloud-based deployment with on-premises options
- Integration with GIS systems and financial management software
- Regular updates to comply with changing tax regulations
Practice similar questions
Subscribe to access the full answer