View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005837 | Composr advocacy and funding | [All Projects] General / Uncategorised | public | 2024-08-04 15:59 | 2024-08-04 20:17 |
| Reporter | Chris Graham | Assigned To | |||
| Severity | Feature-request | ||||
| Status | non-assigned | Resolution | open | ||
| Summary | 0005837: Start tracking and aggressively pushing on key metrics (KPIs) | ||||
| 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. | ||||
| Tags | Roadmap: Over the horizon | ||||
| Time estimation (hours) | |||||
| Sponsorship open | |||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-08-04 15:59 | Chris Graham | New Issue | |
| 2024-08-04 16:01 | Chris Graham | Description Updated | View Revisions |
| 2024-08-04 16:01 | Chris Graham | Tag Attached: Roadmap: Over the horizon | |
| 2024-08-04 20:17 | Chris Graham | Description Updated | View Revisions |
