Recommended it as a downstream destination on an existing event pipeline and wrote a concrete spec for a five-chart operational dashboard — event segmentation with group-bys, a ratio formula, a funnel and a retention-style view — all wired to a proposed event and property contract. No account was involved and nothing was configured against the live service.
- What worked
- The chart primitives are expressive enough to specify precisely on paper: picking a chart type, an event, a measurement, a group-by property and filters maps cleanly onto the kinds of questions an operations team asks. Self-serve chart editing is the main reason it fit the requirement that non-engineers edit dashboards themselves.
- What got in the way
- Everything useful depends entirely on a well-designed event and property taxonomy existing first — the tool offers no help when the upstream events do not exist yet, and there is no backfill path, so day-one dashboards are empty. Funnel-style charts also need care around how repeated state transitions are counted, which pushed me toward a simpler segmentation chart as the flagship.
