Recognition is the thing most members are actually there for, and it is the one thing your software cannot do on your behalf.
Points, badges and levels are all proxies for it. They are useful proxies. But nobody has ever felt seen by a threshold, and the difference between the proxy and the thing is where most communities quietly lose people.
A badge says the system noticed
Automated recognition and human recognition feel completely different, and members can tell which one they got within a second.
A badge says a counter crossed a line. A sentence from a person says somebody read what you wrote and thought about it afterwards. The first is pleasant and forgettable; the second is the reason people describe a community as somewhere they belong rather than somewhere they subscribe.
This is not an argument against the mechanics. Run them — they do work that you cannot do by hand, and gamification has its own craft. It is an argument against believing they discharge the obligation, because the moment they are the only recognition on offer, members start reading the place as a machine that counts them.
The test: could this have been said to anybody?
Here is the one question that separates recognition from politeness.
"Great post!" is warm and it is not recognition — it could have been left on anybody's post, on any day, without reading it. "The bit about doing it in two stages is what I got wrong last year" proves a specific person read a specific thing. The warmth is identical. The information content is not, and the information is what lands.
If your comment would work unchanged on somebody else's post, it is politeness. That is not a crime — communities need politeness — but it should not be mistaken for the thing that makes people stay, and an owner who leaves forty of them a week can genuinely believe they are recognising people.
Four kinds, and what each one says
All four have a place. Only one of them does the work people remember.
| What they get | What it actually says | When it backfires |
|---|---|---|
| A badge or level | A counter crossed a line | When it is the only recognition on offer |
| A reaction or "great post" | Somebody was being polite | Almost always — it reads as noise at volume |
| A sentence naming what they did | A person read this and thought about it | Rarely. This is the one that works |
| Member of the month | It was your turn | The moment anyone notices it is a rota |
The third row costs about twenty seconds and nobody does enough of it, mostly because it requires having actually read the thing.
Recognise the behaviour, not the outcome
Most owners praise results, and results are the thing members control least.
Praising somebody's impressive launch teaches the room that impressive launches get noticed here, which is useful only to people who already have one. Praising somebody for writing a careful answer to a beginner's question teaches the room that careful answers to beginners get noticed — and that is a behaviour anybody can repeat tomorrow.
Ask what you want more of, then recognise precisely that. It sounds mechanical and it is the single highest-leverage habit available to an owner, because recognition is how norms are actually set — far more than guidelines, which describe the norm you wish you had.
Public makes a norm, private makes a person
The two are not interchangeable and the choice is not about volume.
Public recognition is instruction aimed at everyone who is watching: it says this is what counts here. Private recognition is for the thing you cannot say in public without embarrassing somebody — that you noticed they have been quietly answering every newcomer for a month, or that their post was braver than it looked.
Use public when you want the behaviour copied and private when you want the person to feel it. Getting this backwards is common: owners praise in private out of tact and then wonder why the norm never spreads, or praise in public something that was really a kindness meant for one person.
The one thing that must not become a ritual
Almost everything in a community benefits from being predictable. This is the exception.
A weekly thread works precisely because it is boring and scheduled, and that predictability is the product. Recognition inverts it. "Member of the month" starts as an honour and becomes a rota the moment somebody works out that everyone gets one eventually, and at that point it is not recognition, it is attendance being acknowledged on a timetable.
Recognition has to be earned specifically and given unpredictably or it stops carrying information. If you want a recurring slot, make the slot about members rather than about one member — a wins thread where anybody can be seen — and keep the pointed, individual version unscheduled.
Do not recognise people for agreeing with you
This one is uncomfortable and worth sitting with, because it is almost entirely unconscious.
The people an owner thanks most are the people who are nice to them: the ones who back you up in a tense thread, who like your announcements, who say the community changed their life. Over a year, recognising those people consistently selects for a community of people who are nice to the owner, which is a different and much worse thing than the community you set out to build.
Check whose names you have said out loud this month. If the list is mostly people who agree with you, the room has already noticed and the members with something awkward and useful to say have started keeping it to themselves.
What the software can and cannot notice
It is worth being exact about where the automated half genuinely helps and where it structurally cannot.
Mateflow's badge manager awards against seven thresholds and sorts them into three kinds by itself: Activity (posts, comments, points, login days), Social (likes received) and Monetization (months subscribed, amount spent), with anything mixing them labelled Hybrid. That labelling is worth paying attention to, because it tells you right there in your badge list when what you are rewarding is payment rather than participation — which is sometimes exactly what you want, and should always be a decision.
What matters is that all seven are quantities. The categories tell you which number moved, not what somebody did. Not one of the seven can express that a particular answer was unusually generous, or that somebody said the hard thing in a thread where it cost them something. The system can measure how much; it cannot notice what — and the recognition that makes people stay lives entirely in the what, which is why this stays a job rather than a setting.
Three things not to do
Do not thank people publicly for something they did privately. Somebody who sent you a careful message about a problem did not sign up to be an example, and doing it once teaches everyone to be more careful with you.
Do not recognise only the top contributors. They are already fine. The member whose third-ever post got no replies is the one for whom a single specific sentence changes whether there is a fourth.
Do not batch it. Recognition written in a Friday catch-up block reads exactly like what it is, and the specificity that makes it work is the first thing lost when you are doing eleven of them in a row.
Your ceiling is real, so distribute it
You cannot personally recognise five hundred people, and pretending otherwise is how owners end up leaving forty "great post!" comments a week.
Past a certain size the honest move is to stop being the only source of it. Members recognising each other scales in a way you never will, and it is produced the same way as every other peer behaviour: by doing it visibly and then getting out of the way, and by giving a few people something of their own to run so that standing comes from somewhere other than you.
This is also the real cost of growth, and the reason size is a decision rather than an outcome — the number of people you can genuinely see is the number of people your community can hold at full strength.
The bottom line
Recognition is not a feature you switch on. It is twenty seconds of attention, given specifically, by somebody whose attention means something.
Run the badges and stop believing they finish the job. Say what the person actually did rather than that it was great, recognise the behaviour you want repeated instead of the outcome you admired, use public for norms and private for people, and keep it unscheduled so it keeps meaning something. Then check that the names you say out loud are not just the names of people who agree with you — because the members who go unrecognised do not complain about it, they simply stop arriving, and that reads as churn long after it was really something much easier to have fixed.