Review your hands, not a company dashboard

There is no company DAU dashboard.

Nothing rolls every teammate’s expands onto one chart. Nothing prints “hours saved this month” for a manager. CodeExpander’s statistics and search live on this computer: which abbreviations your hands actually type, which few fire every week, which you created once and never touched again.

You are reviewing your hands. You are not reviewing the company.

Friday, open the main window once. Not to “manage a knowledge base.” To see whether your hands still recognize these abbreviations. The signature loop did not change: focused field, abbreviation, trigger. Stats only tell you which rows actually entered that loop.

What the numbers are for

Open Usage statistics (same place in Settings; the write-up is Stats and search). Pro shows cumulative expands, characters saved, time estimated from a typing speed, a streak, today / this week / this month, a daily goal you can set, a top-snippet list, and 7-day / 30-day trends. Achievements unlock from counts, streak, and characters. You can export CSV. You can reset — decide first, because the curve and the ranking both go away.

The time figure is local arithmetic, not a KPI. Do not rewrite it as per-person hours for a manager. The ranking is the useful part. Three snippets that expand every day — a signature, a returns reply — beat fifty quotations you built for a library that looks complete.

If the top row is a test abbreviation from last year, delete or rename it. If a whole group never appears, it is occupying a free-tier slot and the attention you spend scanning the library. Move it, merge it, or admit it is not in rotation. A streak only means this machine’s hands still expand. It does not mean the team is diligent.

Free already closes the expand loop. The statistics page is Pro, for review, not a gate on typing. Leave it closed and abbreviations still replace.

A Friday pass is enough. Open the ranking. If the top five are the sentences you still hate typing by hand, the library is doing its job. If the top slot is an old test abbreviation, delete or rename it. If a whole group never appears, it is occupying a free-tier slot or your attention. Move it, merge it, or stop pretending it is in rotation.

Search is the other half

When you forget an abbreviation, do not invent a shorter one that will collide. Type // for inline search, or open the search window. Name, abbreviation, and body text are all searchable. Enter expands. A click can jump to edit.

Once the library is large, review often looks like this: search one word and find the same sentence built twice, or notice a group prefix already separates support from code. Nesting and version history live in the same doc. Day to day, fix “I cannot find it” first.

Search is not a second product. It is how you return to a body without keeping every abbreviation in working memory. The signature loop stays the same: focused field, abbreviation, trigger. Search is what you use when the abbreviation is the part that slipped.

Do not

• Do not treat local stats as an org report. Coworkers’ hands are not on this chart. Shared copy is a different article: Team copy.
• Do not title a week around hours saved. If a number is not wired to a company dashboard, do not invent one.
• Do not fire empty abbreviations to hit a daily goal. The goal reminds your hands. It is not a score.
• Do not reset stats to make the chart look clean.

Next: take the three snippets at the top of the ranking and check their abbreviations. Hygiene.