Notes from usage analytics work
Practical pieces on extracts, journey mapping, workshops, and post-launch reviews for customer-facing web applications.
What to pull from a cloud bill before an analytics conversation
Billing exports rarely match product language. Here is a practical checklist for preparing usage extracts that an analyst can actually read.
Reading usage against customer journeys, not against servers
Server-level charts answer operations questions. Journey-level reading answers whether your cloud spend follows how people actually use the product.
Five questions Korean product teams ask before commissioning an audit
Teams in Korea often ask about language of deliverables, data residency, and how much internal time an audit will take. These answers help set expectations early.
When a measurement workshop is enough — and when it is not
Workshops create shared definitions. They do not replace a full usage audit when the underlying extracts are messy or incomplete.
Post-launch reviews: capturing expectations before the release ships
Comparing actual cloud usage to memory is unreliable. Write the expected usage story down while the release plan is still fresh.