Düşün's first month: numbers, errors, lessons

This post is the first run of Düşün's monthly report template. The number fields get updated with real data — no decorating, no hoarding.

Five things are measured: questions asked, completion (was the answer seen through), card downloads, return rate, errors. More than five is showing off; fewer is blindness.

First lesson: the error message is part of the product. "The council couldn't convene right now" loses fewer users than a technical error code.

Second lesson: example prompts really do get clicked — blank-page fear is real. The report promise: same format every month, same honesty. Bad months get reported too.