Telegram RegisterThe public register of Telegram
Telegram profile photo for Управление проектами и продуктами в IT | Project & Product Management

Channel

Управление проектами и продуктами в IT | Project & Product Management

@product_and_project

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Advertising · Posts · Posts recorded as deleted · Citations · Telegram's recommendations · Cite this entry

16,578subscribers

-71 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1001632700048
TypeChannel
Username@product_and_project
DescriptionВсё о Project и Product менеджменте простым языком. Сотрудничество: @max_excel РКН: vk.cc/cHiCP2
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live14 November 2026
Measurements held65
Confirmed unchanged1 time, most recently 14 November 2026
On Telegramt.me/product_and_project

Topic

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 88% 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

16,44316,85216,647.516,5787 August 202614 November 2026
65 measurements spanning 99 days, net -71. 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 16,382–16,913 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 65
Measured (UTC)SubscribersChange
14 Nov 2026, 06:5616,578-3
11 Nov 2026, 12:5816,581-20
9 Nov 2026, 19:5016,601-1
8 Nov 2026, 14:3616,602-12
7 Nov 2026, 06:0916,614-5
6 Nov 2026, 06:5716,619-15
5 Nov 2026, 05:4916,634-6
4 Nov 2026, 08:3916,640-6
3 Nov 2026, 10:5916,646-4
2 Nov 2026, 10:2816,650-4
1 Nov 2026, 12:3816,654-6
31 Oct 2026, 15:0916,660+4
30 Oct 2026, 18:0816,656-6
29 Oct 2026, 20:2716,662-7
28 Oct 2026, 22:0016,669-10
27 Oct 2026, 19:2716,679-3
26 Oct 2026, 15:3016,682-8
25 Oct 2026, 15:4616,690-14
24 Oct 2026, 16:4016,704-8
23 Oct 2026, 15:4916,712first reading

Engagement

145 posts held, back to 30 July 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 102 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
4.73%
avg views ÷ 16,578 subscribers
Avg views / post
784
45 posts measured
Reaction rate
0.195%
reactions ÷ views · ER floor
Posts in window
45
of 145 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. It is computed over the 16 of 45 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 16 November 2026
Posts held145 (30 July 2026 – 16 November 2026)
Views total35,288
Reactions total26
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken16 Nov 2026, 23:35 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
578
Videos
51
Links
629

Lifetime counters from Telegram’s own channel header, read 16 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
8h 55m
Average length
29m 46s

Measured directly from 18 videos 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

94 reactions across 58 posts, in 5 distinct kinds. The most used accounts for 51.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤4851.1%
👍2324.5%
🤔1313.8%
👎66.38%
🤯44.26%

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 66 of the 145 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 94 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 145 most recent posts we hold, published 30 July 2026 to 16 November 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.

Advertising

Ad load
7.59%
11 of 145 posts carry an ad marker
Regulatory tokens
11
posts carrying an erid · 11 distinct tokens
Median views · ads
792
over 11 measured posts
Median views · rest
835
over 134 measured posts

An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.

This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.

Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. They are printed side by side with the count behind each rather than as a ratio: an ad and an ordinary post are not otherwise matched — for topic, for length, for hour of day — so the gap between them is a description of two groups and not the effect of one being an ad.

Advertising tokens recorded on this entry
eridPostsFirst seenLast seen
2VSb5yBHX8N128 August 202628 August 2026
2VSb5ycmmWr131 August 202631 August 2026
2VtzquyZWbV119 August 202619 August 2026
2Vtzqv3oTWz13 August 20263 August 2026
2Vtzqv6aXmY128 October 202628 October 2026
2Vtzqv8QUNq130 October 202630 October 2026
2Vtzqvp5xRC113 November 202613 November 2026
2VtzqxMNyEn15 November 20265 November 2026
2VtzqxmQshQ130 October 202630 October 2026
2W5zFHKDrEm127 August 202627 August 2026
2W5zFJvZyAi113 November 202613 November 2026

A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.

Measured over the 145 most recent posts we hold, published 30 July 2026 to 16 November 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.

Recent posts

Telegram’s own ‘edited’ marker: 1 of 45 posts held from the last 30 days (2.22%) 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).

16 Nov 2026, 15:10 UTC315 viewsread 16 November 2026
Photo

Охота на директора-«гиппопотама»: как бороться с непредсказуемостью в разработке Аббревиатура HiPPO расшифровывается как highest paid person's opinion, а на русский переводится как «мнение самого высокооплачиваемого сотрудника». Для простоты давайте называть их носителей «гиппопотамами», а само мнение — «гиппо». Люди, у которых высокая зарплата, обычно считают, что уже это одно даёт им верный взгляд на вещи. Проблем…

16 Nov 2026, 13:00 UTC429 viewsread 16 November 2026
Photo

19 ноября представители Burger King, ВКонтакте, TANAiS и Вебфлай сравнят подходы к оценке эффективности команд на ГанТтели «Метрики без самообмана» Команда закрывает задачи, укладывается в сроки, выполняет KPI. Но означает ли это, что она работает лучше? В агентстве считают часы, загрузку и экономику проектов. В продукте — конверсию, выручку, удержание пользователей. А что делать, когда показатели растут, но пользы…

15 Nov 2026, 11:15 UTC582 viewsread 16 November 2026
Photo

Самые важные архитектурные шаблоны, которые нужно знать Архитектурный шаблон — это обобщенное часто используемое решение распространенной задачи в архитектуре ПО в заданном контексте. Часто разработчики не до конца понимают разницу между архитектурными шаблонами, а иногда вообще мало что о них знают. Разберемся в этой статье. Управление проектами и продуктами в ІТ

15 Nov 2026, 08:15 UTC572 viewsread 16 November 2026
Photo

Хочешь разбираться в Linux? Для тебя уже всё сделали. 🐧 Канал DevOps School делится полезными приёмами и лайфхаками Linux, DevOps и информационной безопасности. Подписывайтесь и прокачивайте свои навыки: @devops_sc

14 Nov 2026, 08:52 UTC580 viewsread 16 November 2026
Photo

Про самый попсовый термин в продуктовом глоссарии и почему MVP мёртв Этот термин уже давно звучит из каждого утюга имеющего отношение к продуктовой разработке. Ведь как гласит продуктовая мантра – экономь ресурсы, проверяй гипотезы быстро, с минимальными затратами. И тут на выручку приходит очевидное решение – запилить по-быстрому MVP, показать его пользователям и подтвердить или опровергнуть выдвинутую гипотезу о п…

13 Nov 2026, 13:10 UTC620 views2 reactionsread 16 November 2026
Photo

6 шаблонов досок в Miro для объединения кросс-функциональной команды Работа в кросс-функциональной команде – дело непростое. Когда людям из разных отделов приходится работать в одной команде, можно столкнуться с плохой коммуникацией, недоверием друг к другу и рассогласованностью действий. Если вы тимлид или менеджер проекта, то, по большей части, вы и несёте ответственность за то, чтобы все были на одной волне. Начн…

❤1👍1

13 Nov 2026, 11:04 UTC630 viewsread 16 November 2026
Advertisementerid 2Vtzqvp5xRCVideo

Как насчёт партии в Backend? 😴 Дело в чём: 17 ноября AvitoTech проводит Backend Roulette. Инженерные задачи там разложат как покерную партию: за каждым столом эксперт-крупье AvitoTech даст команде вводные, а по ходу игры добавит новые обстоятельства, чтобы перестроить решение. Можно не садиться за стол и провести время на сайд-активностях или в разговорах с коллегами. После игры всех гостей ждёт афтерпати и нетворк…

13 Nov 2026, 09:10 UTC624 viewsread 16 November 2026
Photo

Самоуправляемые команды и продуктовый менеджмент Материал будет полезен тем, кто хочет пойти в продукт или уже в нем развивается. А также, если вы хотите нанять себе подобного человека, эта статья поможет вам в понимании навыков, какими должен обладать PM. Управление проектами и продуктами в ІТ

13 Nov 2026, 07:00 UTC476 viewsread 13 November 2026
Advertisementerid 2W5zFJvZyAiPhoto

Дата запуска назначена, а требования еще уточняют Проектным и продуктовым руководителям часто приходится запускать проекты без полной информации и выбирать из многих задач. В программе TeamLead Conf 2026: — Мария Насырова (Яндекс), Требования появляются позже разработки, скоуп растет быстрее команды. Как стартовать без полной ясности, видеть зависимости рано и оставлять команде пространство для решений при общем к…

12 Nov 2026, 10:40 UTC730 viewsread 16 November 2026
Photo

Тимлид на испытательном сроке В этой статье автор подробно разбирает как тимлиду понять основные фокусы во время испытательного срока, какие есть советы и лайфхаки в этом процессе. Управление проектами и продуктами в ІТ

Showing the 12 most recent of 145 posts we hold for @product_and_project. 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.

Posts recorded as deleted after publishing

We recorded 45 posts on @product_and_project as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
7 August 2026
Most recent seen missing
13 November 2026
Median time before seen missing
2 days
Seen missing in the last 30 days
11

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 13 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.

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.

Управление персоналом | hr, карьера, кадры
@secrets_hr · 21,742
Telegram ranks this channel #7 of 93 here — alongside 92 others — read 22 September 2026
Системный и Бизнес-анализ
@ba_sa_analytics · 52,414
Telegram ranks this channel #7 of 90 here — alongside 89 others — read 24 August 2026
Excel Hacks | Бухгалтерия и Аналитика
@hacks_excel · 282,791
Telegram ranks this channel #8 of 85 here — alongside 84 others — read 10 August 2026
Базы данных | Access, SQL, Big Data
@databases_secrets · 29,986
Telegram ranks this channel #9 of 82 here — alongside 81 others — read 7 September 2026
Финансовый анализ
@fin_analytics · 41,480
Telegram ranks this channel #9 of 87 here — alongside 86 others — read 29 August 2026
1С Hacks | Бухгалтерия и Учёт
@secrets_1C · 46,365
Telegram ranks this channel #11 of 79 here — alongside 78 others — read 27 August 2026
Секреты аналитики | Data Science, BI, Tableau
@analytics_secrets · 46,746
Telegram ranks this channel #11 of 85 here — alongside 84 others — read 27 August 2026
Windows Community
@wind_community · 40,828
Telegram ranks this channel #21 of 74 here — alongside 73 others — read 29 August 2026
pmclub — учим управлять
@pmclub · 20,694
Telegram ranks this channel #28 of 97 here — alongside 96 others — read 26 September 2026
Python Hacks
@python_secrets · 40,300
Telegram ranks this channel #29 of 82 here — alongside 81 others — read 30 August 2026
ЭКСЕЛЬХАК
@excelhackru · 74,150
Telegram ranks this channel #29 of 87 here — alongside 86 others — read 19 August 2026
Магия Excel
@lemur_excel · 49,837
Telegram ranks this channel #30 of 95 here — alongside 94 others — read 25 August 2026
Про Проекты и карьеру в ИТ | Романова
@proProject1 · 40,730
Telegram ranks this channel #33 of 97 here — alongside 96 others — read 1 September 2026
🔥 Дмитрий Ирешев: AI • Продукты • Проекты
@dmitrii_ireshev_Agile_PMP · 37,536
Telegram ranks this channel #41 of 97 here — alongside 96 others — read 12 September 2026

This channel appears in 14 seed channels' Telegram-generated recommendation lists 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 14 November 2026 — this entry's latest reading, not the date you are reading this.

“Управление проектами и продуктами в IT | Project & Product Management” (@product_and_project), 16,578 subscribers as measured 14 November 2026. Telegram Register, tgregister.com/channel/product_and_project.

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.