Telegram RegisterThe public register of Telegram

Channel

Event Storming

@event_storming

On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry

1,699subscribers

+2 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001232936610
TypeChannel
Username@event_storming
CreatedBetween 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held3
Confirmed unchanged2 times, most recently 12 August 2026
On Telegramt.me/event_storming

Growth

1,6971,6991,6986 August 2026 — 1,697 subscribers6 August 2026 — 1,697 subscribers9 August 2026 — 1,699 subscribers6 August 20269 August 2026
3 measurements spanning 3 days, net +2. 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 1,697–1,699 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 16:221,699+2
6 Aug 2026, 07:161,697no change
6 Aug 2026, 06:171,697first reading

Engagement

19 posts held, back to 14 October 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
196.6%
avg views ÷ 1,699 subscribers
Avg views / post
3,340
1 post measured
Reaction rate
0.808%
reactions ÷ views · ER floor
Posts in window
2
of 19 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
WindowRolling 30 days · latest post in window 24 July 2026
Posts held19 (14 October 202524 July 2026)
Views total3,340
Reactions total27
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 17:43 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

Video runtime
6m 59s
Average length
6m 59s

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

124 reactions across 17 posts, in 4 distinct kinds. The most used accounts for 58.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥7258.1%
👍3427.4%
1713.7%
👎10.806%

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

Measured over the 19 most recent posts we hold, published 14 October 2025 to 24 July 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
1
across the posts below
Posts paid on
1
of 18 we hold a reading for · 6%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @event_storming. 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 19 most recent posts we hold for this entry, published 14 October 2025 to 24 July 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

22 Jul 2026, 19:06 UTC≈3,340 views26 reactions1 Starread 7 August 2026
Video

Вот так Notebooklm сжал теорию первого дня корп курса по Event Storming, очень хорошо сжал, я бы сказал. Никакой лишней информации нет, так что можно выложить :)

🔥214👍1

11 Feb 2026, 09:28 UTC≈1,420 views6 reactionsread 7 August 2026
Forwarded from @blog_sbPhoto

Темпоральность в Event Storming Вчера обсуждали с Геной Кругловым темпоральность в Event Storning, а сегодня выступал перед участниками IN HUB с темой «Картина производственной системы за часы» (домен промышленного производства и смежных отраслей) и был у меня в презентации такой слайд и вчерашнее обсуждение и сегодняшнее выступление привели к новым мыслям. Так вот, на этом слайде сразу четыре темпоральности (автор

👍51

11 Jan 2026, 07:14 UTC≈5,000 views12 reactionsread 7 August 2026

Формирование рабочей группы по разработке методологии «Стратегического Event Storming» На выходных меня не отпускала мысль, что что-то есть в предложении Юрия Куприянова интегрировать форсайт и Event Storming. Ведь фактически форсайт – это и есть варианты продолжения цепочек событий, но в будущее, а стратегическая сессия – это ограниченитель, фильтр для отбора вариантов. Когда кроссфункциональная команда создает со

🔥111

4 Jan 2026, 18:14 UTC≈1,330 views7 reactionsread 7 August 2026

Ответ к заданию 1. Не нужно выбирать единый свимлейн на всю модель 2. Вход в модель по каналам (свои события входа, своя модель подтверждения личности, свой UX) 3. После того, как определено намерение клиента (это может быть проблема, информация) - канал перестает иметь значение. 4. После того, как определено, что нужно сделать, в игру вступают продукты – они обозначаются как системы, так как по отношению к предметн

👍42🔥1

3 Jan 2026, 11:34 UTC≈1,240 views1 reactionsread 7 August 2026
Photo

Разомнемся на выходных? :) Ситуация с которой вы столкнетесь не раз и не два. Итак, представьте. Вы проводите Event Storming в службе поддержки клиентов. Служба поддержки использует 7 каналов взаимодействия с клиентами (телефон, чат, почта, …), клиенты бывают 3 разных типов (vip, обычный+, обычный), количество продуктов на поддержке - 50+. Структуру можно организовать разными способами (слева направо, см пример н

👍1

29 Dec 2025, 10:36 UTC≈1,230 viewsread 7 August 2026

👆максимально полезно для Event Storming

29 Dec 2025, 10:35 UTC≈1,070 views6 reactionsread 7 August 2026
Forwarded from @blog_sbFile

Наступает время личных и корпоративных стратегических выборов Стратегический выбор стоит начинать не с выбора решений, а с тщательного исследования Problem Space – что именно является проблемой, для кого и почему это вообще проблема. В связи с этим – полезный материал по изучению проблемы и выбора типов решений (полагаю, Тарасенко для большинства подписчиков моего канала – вовсе не новая фамилия, а для кого новая –

👍51

17 Dec 2025, 09:55 UTC≈1,220 views3 reactionsread 7 August 2026

Фокус проведения Event Storming В четвертом квартале у меня сильно сместился фокус проведения сессий Event Storming. Причем, не постепенно, а достаточно резко. Проведено много сессий в рамках стратегический сессий, на которых Event Storming выступал как метод формирования общего представления о текущей реальности для того, чтобы сонаправить участников стратегических сессий. Интересно и то, что я не вижу подобного и

1👍1🔥1

29 Nov 2025, 12:42 UTC≈1,180 views12 reactionsread 7 August 2026
Forwarded from @blog_sb

Продолжение про «похожие процессы» и про важность DDD. (кажется, получился очень глубокий и важный пост про важность DDD) Конкретным профессиям и их внутренней кухне (туризму, логистике, финансам, медицине) в профильных вузах учат годами. Для тех, кто прошел такой путь, типовые процессы внутри их отрасли выглядят очень похожими: одни и те же шаги, одни и те же риски, одни и те же точки принятия решений. Но есть оди

🔥82👍1👎1

20 Nov 2025, 18:45 UTC≈1,370 views6 reactionsread 7 August 2026

Публичный кейс :) https://scrumtrek.ru/cases/eventstorming-v-ecom-tech/

🔥6

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

Citation-graph rank

Citation-graph rank — 323,095 of 1,169,250entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

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

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 9 August 2026 — this entry's latest reading, not the date you are reading this.

“Event Storming” (@event_storming), 1,699 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/event_storming.

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.