#5837 - Start tracking and aggressively pushing on key metrics (KPIs)
| Identifier | #5837 |
|---|---|
| Issue type | Feature request or suggestion |
| Title | Start tracking and aggressively pushing on key metrics (KPIs) |
| Status | Open |
| Tags |
Roadmap: Over the horizon (custom) |
| Handling member | Deleted |
| Addon | General / Uncategorised |
| Description | We have always been feature/community/client-led, but since working my new job I've learned the power of aggressively tracking metrics directly from senior people who've worked at FAANG companies.
We should track things like: - Number of signups to the Composr homesite per month - Number of new sites calling home (of those that have that enabled) per month - User testing aggregate user experience rating And most new efforts should be focused on moving those metrics. That might mean implementing new features, that might mean doing more or better marketing. But the point is it forces clarity of purpose and keeps our tasks and tactics accountable to our actual goals. For example, let's say we have some development bandwidth available. Do we implement two-factor authentication, or do we run a user testing workshop to identify stumbling blocks in existing functionality? The typical developer thing is to do the former, but clarity of focus may show we should actually be doing the latter. And with growth, the amount of bandwidth increases, so you can end up doing both. |
| Steps to reproduce | |
| Funded? | No |
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".


Comments
There have been no comments yet