Back to blog
Product•June 19, 2026•4 min read

Meet users in the workflow they already have

The surest way to get a tool ignored is to make people change how they work to use it. BUC Populi does the opposite - it meets staff inside the system they already live in and asks them to learn almost nothing.

Fit the product to the need, not the reverse

There's no new database and no second source of truth: Populi stays the system of record, and the tool reads from it, drafts into it, and stops. It ships as a handful of scripts, a Streamlit dashboard, and cron - shapes that fit a lean academic-ops reality. The most valuable piece, a weekly compliance audit, is something nobody filed a ticket for - but it met a need they all had once it existed.

A tool that demands a new workflow competes with the old one. A tool that fits the old workflow just gets used.

Solve for needs, not for novelty

Designing around the existing workflow shaped every call:

  • No app to adopt - the dashboard and cron meet staff where they already are.
  • Populi remains canonical, so nobody fears the tool corrupting their records.
  • The unrequested compliance audit shipped because it served a real need, not because it was askable.