Education — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 10 September 2026 and assigned it the closest of 31 fixed categories, at 89% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.
Growth
59 measurements spanning 103 days, net -147. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 13,977–14,177 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 59
Measured (UTC)
Subscribers
Change
16 Nov 2026, 18:10
14,000
-7
13 Nov 2026, 10:05
14,007
-1
11 Nov 2026, 00:54
14,008
-3
9 Nov 2026, 09:31
14,011
+3
7 Nov 2026, 21:19
14,008
-4
6 Nov 2026, 20:26
14,012
-1
5 Nov 2026, 20:24
14,013
-2
3 Nov 2026, 15:58
14,015
-3
2 Nov 2026, 12:47
14,018
-3
1 Nov 2026, 11:18
14,021
+2
31 Oct 2026, 08:06
14,019
-1
30 Oct 2026, 11:19
14,020
-4
29 Oct 2026, 11:38
14,024
-16
28 Oct 2026, 09:36
14,040
+2
27 Oct 2026, 06:18
14,038
-2
26 Oct 2026, 02:58
14,040
+2
25 Oct 2026, 03:10
14,038
+1
24 Oct 2026, 01:49
14,037
-1
23 Oct 2026, 05:01
14,038
-5
22 Oct 2026, 06:10
14,043
first reading
Engagement
29 posts held, back to 13 May 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 81 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
23.6%
avg views ÷ 14,000 subscribers
Avg views / post
3,300
1 post measured
Reaction rate
0.455%
reactions ÷ views · ER floor
Posts in window
1
of 29 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
What these figures were computed from
Window
Rolling 30 days · latest post in window 28 October 2026
Posts held
29 (13 May 2026 – 28 October 2026)
Views total
3,300
Reactions total
15
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
17 Nov 2026, 20:38 UTC
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
What this channel posts
Photos
160
Videos
3
Links
423
Lifetime counters from Telegram’s own channel header, read 17 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Video runtime
1m 00s
Average length
1m 00s
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Reaction mix
649 reactions across 28 posts, in 10 distinct kinds. The most used accounts for 28.2% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👍
183
28.2%
❤
176
27.1%
🔥
174
26.8%
😁
68
10.5%
🦄
20
3.08%
🤔
18
2.77%
👎
4
0.616%
👏
4
0.616%
🎉
1
0.154%
🤯
1
0.154%
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 28 of the 29 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 649 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 29 most recent posts we hold, published 13 May 2026 to 28 October 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Telegram Stars
Stars received
6
across the posts below
Posts paid on
4
of 29 we hold a reading for · 14%
Most on one post
2
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @productclub. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 29 most recent posts we hold for this entry, published 13 May 2026 to 28 October 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Recent posts
Telegram’s own ‘edited’ marker: 0 of 1 post held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
Всем привет. С вами на связи Грачи с новым выпуском подкаста #РАЗБЕРЁМСЯ, в котором мы исследуем, как меняется управление продуктами в эпоху экономических потрясений и ИИ. Этот подкаст мы записали ещё в начале июля. Однако, потом погрязли в делах и потому до продакшна он выходит только сейчас. За что мне очень стыдно, ведь его тема проливает свет на поведение менеджеров в России. Причём не только менеджеров продуктов…
В кулуарах Product Sense мы даже шутили, что если негласная тема по количеству докладов конференции звучала как "Как мы внедрили у себя ИИ (но не увидели пока эффекта)", то тема следующей конференции будет "Мы увидели эффект и отказались от ИИ". Мы стремительно падаем в пропасть разочарований, связанную с нашими завышенными ожиданиями от ИИ и паническим хайпом "нас всех заменят машины".
Для борьбы со всеми теми нега…
Недавно случились два несвязанных друг с другом события, но объединенные общими переживаниями. Во-первых, Грачи прилетели на Product Sense, выступив там с мастер-классом (о нём - в следующих сериях). Во-вторых, Ravi Mehta, широко известный в узких кругах продуктовый специалист, написал очередной пост про шринкфляцию продуктовой культуры.
На Сенсе я был очень рад увидеться со всеми знакомыми и друзьями и пообщаться …
Я нашел три исследования за последние три года, которые частично могут пролить свет на эффект шринкфляции продуктового мышления. Здесь я приведу только ключевые тезисы, сами исследования вы можете почитать по ссылке.
1. Качество результатов НЕ увеличивается, если вы не обладаете знаниями и опытом для верификации результата.
В 2024 году компания McKinsey провела эмпирическое исследование 40 менеджеров продуктов из р…
Привет, это Олег.
Сегодня немного личный анонс.
Последний год мы с небольшой командой исследовали, как применять AI-агентов для прикладных задач.
В процессе появился Unreal Agent — харнесс или обвязка, которая управляет работой агента, позволяющая существенно снизить стоимость решения задач без потери качества.
На бенчмарке Terminal-Bench 4.0 наше решение показывает результат на том же уровне, что Codex + Astra, …
Оказывается, существуют не только тизеры фильма, но и тизеры статьи. В частности, моей второй статьи из цикла про экосистемы https://dzen.ru/a/aqF5Viqc120IU1TZ
Поначалу, она выйдет в "Дайджесте" издательства "Олимп-Бизнес", а через месяц после этого на сайте PAF. В ней я привожу примеры практического использования Product Ecosystem Map - как эта модель применяется для проектирования новых продуктов и офферов.
С пер…
Во-вторых, продуктовое мышление все-таки не мета-навык. В том смысле, что подразумевает не только наличие знаний о мире, как категорий мышления, в рамках которых можно думать, но умений и навыков, через которые эти знания воплощаются в принятие решений. Например, JTBD это не только мышление о продукте в категории "работы потребителя", но и набор конкретных механик исследования этих потребителей и формирование концепц…
Интересным вопросом на подумать стал "Что произойдет с продуктовым мышлением как навыком к концу 2027 года?" Большинство отвечает, что мышление либо превратится в мета-навык, либо станет обязательным для всех руководителей. Несмотря на важность и продвижение продуктового мышления, я не соглашусь ни с первыми, ни со вторыми. И вот почему. Любое мышление - это мышление определенными категориями (объектами). Разные типы…
Я наконец-то дошел до нормального знакомства с результатами исследования Product Sense за прошлый год, хотя мы даже в подкасте с Юрой Агеевым и Олей Стратанович, когда оно ещё не вышло, затронули пару важных тем из него.
Самый заметный слон в нашей продуктовой комнате это ИИ, который вкрячился настолько сильно, что подвинул фокус развития менеджеров по управленческим навыкам с топ-1 в 2024 году (39%) на четвертое ме…
Ура! Делюсь событием. На курсе "Директор по продукту: управление продуктовой стратегией" мы выпустили 10 юбилейную когорту, а среди студентов были руководители и собственники из Ростелекома, Альфа Банка, Петровакса, департамента Москвы, Lindaily, Ikon Tyres, владелец брендов шоколада RED и Nature, Wink Музыка, Conte, Сбера и других компаний. Вообще, с каждым годом мы видим, что методики управления продуктами всё боль…
Грачи на Product Sense 2026
Не так давно я написал заметку на тему, туда ли мы свернули с приходом ИИ, где разобрал два подхода к изменению менеджерской функции:
1. Менеджер продукта как вайбкодер, который использует ИИ для того, чтобы самому запилить продукт с 0 до 1. Человек-команда, который сам и задискаверит, и задеплоит. Его функция – сокращение PDLC (Product Development Life Cycle). Ключевое слово здесь “devel…
👍9🦄5❤2🤔2
Showing the 12 most recent of 29 posts we hold for @productclub. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Mentions
Named by 3 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
ProductDo: практика продакта @productdo · 25,154 Telegram ranks this channel #60 of 97 here — alongside 96 others — read 17 September 2026
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
Cite this entry
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 16 November 2026 — this
entry's latest reading, not the date you are reading this.
“Борода продакта” (@productclub), 14,000 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/productclub.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.