YouTube2Text

Когда суета нужна для прорыва? Над этим смеются профессиональные менеджеры — Transcript

by Михаил Дашкиев · 1,716 words · 276 segments · language en · Watch on YouTube

Full transcript

  1. 0:00Many top managers aren't capable of
  2. 0:01building a business. Even managing
  3. 0:03billions, they start trying to create
  4. 0:04something very great, something global.
  5. 0:06They don't succeed at all. I notice
  6. 0:08this often, because their paradigm is
  7. 0:10stuck in this idea of "proper" business
  8. 0:12management. After every mistake, they
  9. 0:14hold regular working group meetings.
  10. 0:16Let's analyze what we've learned and
  11. 0:18what we're doing differently. What have
  12. 0:19we learned, and what are we doing
  13. 0:20differently? What have we learned, and
  14. 0:21what are we doing differently? Is that
  15. 0:23even possible? It's real. Is it
  16. 0:25possible? It happens. That it's
  17. 0:27possible to do it that way? And we play
  18. 0:28ping-pong. We are constantly processing
  19. 0:30and changing, processing and changing,
  20. 0:33processing and changing. We need to be
  21. 0:38able to do several things. I told my
  22. 0:41team this too, because I noticed a
  23. 0:42deficit in strategic development—that
  24. 0:45is, building something new or
  25. 0:46implementing reforms. People just get
  26. 0:49stuck in repetitive processes. And we
  27. 0:51identified several skills, several
  28. 0:53stages. Globally, they can be divided
  29. 0:56into setup and performance. In English,
  30. 0:59that's building and launching something
  31. 1:02versus maintaining and optimizing its
  32. 1:04development. These are two
  33. 1:06fundamentally different stages. These
  34. 1:07are fundamentally different ways of
  35. 1:09thinking. I, for example, am someone
  36. 1:11who knows how to do a setup. I can
  37. 1:13launch something new and create a unit
  38. 1:15from scratch, setting it all up. That's
  39. 1:18what it's called. I come in, set it up,
  40. 1:20hand it off, and then others start
  41. 1:23doing the work. It’s not so easy,
  42. 1:26because I have to deal with uncertainty
  43. 1:28. Nothing is clear; how things will
  44. 1:29turn out is unknown. I have to create
  45. 1:31the first precedent. Then there are
  46. 1:33other people, regular managers,
  47. 1:35professional managers; they might not
  48. 1:37know how to set things up, but they are
  49. 1:39great at performance, hitting targets,
  50. 1:41tweaking metrics and conversions, and
  51. 1:43handling operational efficiency. And
  52. 1:46within this setup, there are a few
  53. 1:49stages. The first stage is that of
  54. 1:51pushing the boulder, going from zero to
  55. 1:54one. That is, pushing the boulder and
  56. 1:55getting the flywheel spinning. What is
  57. 1:57important here? First, the precedent
  58. 1:58itself is important. A precedent is
  59. 2:00when a fact has occurred. The precedent
  60. 2:03of the first sale, for instance, or
  61. 2:05that someone else made the sale instead
  62. 2:07of you. Or the precedent that something
  63. 2:09came in from a new connection. The
  64. 2:11precedent that you bought something for
  65. 2:12the first time. And here, your specific
  66. 2:14will is needed. You decide: we are
  67. 2:16doing this. You simply exert your will
  68. 2:18and create an inevitability. We create
  69. 2:20a precedent. And most importantly, you
  70. 2:22change your attitude toward it. You
  71. 2:24realize this precedent won't be the
  72. 2:25prettiest or most profitable. It might
  73. 2:27be clunky, it might be lopsided, but
  74. 2:29that's exactly why you’re needed: to
  75. 2:32break through this uncertainty by
  76. 2:34creating and deploying this precedent.
  77. 2:36The next important thing here is the
  78. 2:38deadline and timing. Why timing? It's
  79. 2:40vital that the energy doesn't fizzle
  80. 2:41out. An idea arrives, you have to act,
  81. 2:44launch it, and provide momentum.
  82. 2:47Professional managers often see this as
  83. 2:49fuss, as lack of preparation, as being
  84. 2:51hasty. Like we haven't thought anything
  85. 2:54through and are just doing things as
  86. 2:56usual. Often this is even mocked later,
  87. 2:59like we’re just causing a stir again,
  88. 3:01but it's necessary at this stage. It's
  89. 3:05simply a different way of thinking.
  90. 3:06That is, speed and the very fact of the
  91. 3:08precedent are more important than
  92. 3:10beauty. Than thoughtfulness, than
  93. 3:13efficiency, and than everything else.
  94. 3:15Because here, we are solving the task
  95. 3:17of breaking through uncertainty. I mean
  96. 3:19, the key question at this stage is: is
  97. 3:22it even possible? Is it real, is it
  98. 3:24possible, does it even happen? That you
  99. 3:26can do it this way? The next important
  100. 3:28thing here, at this stage for me, is
  101. 3:29the locomotive. When I launch something
  102. 3:31like this from zero to one, it's
  103. 3:33important for me to find a guy I can
  104. 3:35rely on. I mean, someone definitely
  105. 3:36needs to direct energy into it. And my
  106. 3:39task as a leader is to ensure someone
  107. 3:41is working on this full-time. My move
  108. 3:44then is to "airdrop" a manager in with
  109. 3:46the goal of creating a precedent,
  110. 3:48pushing the stone by a certain date,
  111. 3:50and not slowing down for too long. And
  112. 3:52that's why the fourth word is to "get
  113. 3:54it done somehow." Get it done somehow,
  114. 3:57but actually do it, and get the result.
  115. 3:59That is the first stage. The second
  116. 4:01stage, let's call it from one to three,
  117. 4:03is optimization and tweaking based on
  118. 4:05mistakes. Tweaking, correcting errors.
  119. 4:08We made a mistake, but that's okay, we
  120. 4:10corrected it the next time. Did it
  121. 4:12differently, did it differently, did it
  122. 4:13differently, did it differently.
  123. 4:15Because here the team incorporates the
  124. 4:17experience of all previous mistakes.
  125. 4:19Like how to sell better, how to price
  126. 4:21better, what to include in the package,
  127. 4:22what not to include, how to account for
  128. 4:24these errors. Effectively, we've joined
  129. 4:27a working group, the group meets, the
  130. 4:29stage where something is already
  131. 4:31created, the baton has been passed, and
  132. 4:33now we live in a different mode. We
  133. 4:35need to learn how to fix mistakes. And
  134. 4:38here, what is actually important?
  135. 4:40What’s important is to make
  136. 4:41iterations frequent and fast. Frequent,
  137. 4:43fast. I mean, frequent effectively
  138. 4:45means fast and cheap. So, mistakes are
  139. 4:46necessary. Mistakes need to be frequent
  140. 4:48and cheap. Secondly, you need to draw
  141. 4:50conclusions. Draw conclusions and
  142. 4:52change. So, after every mistake, you
  143. 4:54need to hold regular working group
  144. 4:55meetings. Let’s analyze what we’ve
  145. 4:57learned and what we’re doing
  146. 4:58differently. What have we learned and
  147. 4:59what are we doing differently? What
  148. 5:00we’ve learned and what we’re doing
  149. 5:02differently. Third. Move in regular
  150. 5:03iterations. You need regular iterations
  151. 5:06here. This means the working group
  152. 5:08meets weekly, or maybe even every three
  153. 5:10days if the timing is critical—
  154. 5:11constantly checking, adjusting,
  155. 5:13checking, adjusting. This is important.
  156. 5:15I’m calling it "ping-pong with
  157. 5:17reality." It really looks like you hit
  158. 5:19it, you receive, you hit it, you
  159. 5:21receive, you hit it, you receive. These
  160. 5:23iterations start rolling. And we’re
  161. 5:24playing ping-pong. We’re constantly
  162. 5:26processing and changing, processing and
  163. 5:28changing. You don’t need any
  164. 5:30organizational structure here. You
  165. 5:33don’t need to think anything through,
  166. 5:35write anything down, or deal with
  167. 5:37business models, market research, or
  168. 5:39other intellectual fluff that slows you
  169. 5:40down. Because if you go into the first
  170. 5:44or second stage with this
  171. 5:45intellectualization and rationalization
  172. 5:47, you’ll screw everything up. You
  173. 5:50need intuition here, you need energy,
  174. 5:52you need common sense, and you need
  175. 5:54action—pure action. Well, it’s
  176. 5:57clear that you need a vision and so on.
  177. 5:58But all those smart things appear later
  178. 6:00. They are necessary, but they are
  179. 6:03needed later. That’s why, for example
  180. 6:05, many top managers are unable to
  181. 6:06create a business. Even while managing
  182. 6:08billions, they try to create something
  183. 6:10very grand and global. And nothing
  184. 6:12works out for them. I notice this often
  185. 6:15, because their paradigm is stuck in "
  186. 6:17doing things the right way." They start
  187. 6:20thinking everything through right away,
  188. 6:22but they fail on the basic premise that
  189. 6:24they understand this world. They
  190. 6:26don’t understand how the world works,
  191. 6:28so they can’t think it through. So,
  192. 6:31this second stage—tweaking errors—
  193. 6:33is just about playing each step. Making
  194. 6:35the next iteration better, more
  195. 6:37profitable, faster, simpler, cheaper,
  196. 6:38more efficient, and so on. One last
  197. 6:40important thing here is to think in
  198. 6:42terms of unit economics. Meaning, when
  199. 6:45I’m doing these new iterations myself
  200. 6:47, I’m improving, and I’m keeping in
  201. 6:49mind: "Can this be scaled to billions?"
  202. 6:52Like, I’m doing this—okay, we’re
  203. 6:54making these deals, and will this turn
  204. 6:56into a big story? And then the unit
  205. 7:00economics, the cost structure,
  206. 7:01everything I’m doing...I’m not
  207. 7:03thinking as if I’m selling three
  208. 7:05items, but as if I’m selling one out
  209. 7:07of 30,000. I’m already thinking: "How
  210. 7:11will others do this? And will this
  211. 7:13process even be expensive once it’s
  212. 7:15scaled?" Will this kill the human
  213. 7:16factor for scaling? In essence, through
  214. 7:19these iterations, I am forming a model
  215. 7:21for scaling. If we first pushed the
  216. 7:24boulder and set a precedent, now with
  217. 7:26these tweaks, I’m shaping the model.
  218. 7:29And I want to be able to hand this
  219. 7:31model over to operational efficiency
  220. 7:34and management later. And the next
  221. 7:36stage. Building to a five-star standard
  222. 7:37. Let’s call this scaling and
  223. 7:40operational efficiency. What is
  224. 7:42operational efficiency? It’s exactly
  225. 7:44that—fine-tuning all the conversions,
  226. 7:45metrics, and so on and so forth. What
  227. 7:47is important here? Organizational
  228. 7:49structure is important here. Motivation
  229. 7:51is important here, too, so that it
  230. 7:53doesn’t create conflicts, so that
  231. 7:54everyone is motivated by KPIs and
  232. 7:56parameters, so that motivation actually
  233. 7:58drives operational efficiency. Regular
  234. 8:01management and all those procedures are
  235. 8:03important here. It’s important to
  236. 8:06have operational people, not the "
  237. 8:08change-makers," but people who can
  238. 8:10consistently and systematically do the
  239. 8:13same things and hit targets, because
  240. 8:16some people get rattled when
  241. 8:18uncertainty increases. There are people
  242. 8:21who gravitate toward certainty, toward
  243. 8:23a higher degree of stability; when
  244. 8:25everything is unclear, it becomes hard
  245. 8:27for them. These are the people who
  246. 8:30strive for order. That’s who we need
  247. 8:33here. We need to learn how to find them
  248. 8:35. Operational people. We need all these
  249. 8:38metric tweaks and bringing indicators
  250. 8:40up to benchmarks. Benchmarks are like
  251. 8:42those of your competitors, roughly
  252. 8:43speaking. If competitors can maintain a
  253. 8:4520%conversion rate, then we can too. If
  254. 8:48they can keep food costs within a
  255. 8:50certain percentage, then we can too. So
  256. 8:53, we bring everything up to the
  257. 8:55required levels. We’re basically
  258. 8:57filing down the rough edges. This is
  259. 8:58where budget limit controls come in.
  260. 9:00Meaning you have a set budget. You
  261. 9:02shouldn't exceed it; you have to fit
  262. 9:04within these bounds. You have to fit
  263. 9:06within these constraints. And this is
  264. 9:08about building process optimization. So
  265. 9:09, in fact, this is what I do. I perform
  266. 9:12the setup. I push the boulder, create a
  267. 9:15kind of breakthrough, and then form a
  268. 9:17team so that the team can fine-tune and
  269. 9:20operationally optimize it. That’s it,
  270. 9:22it’s already working. Good. Then I
  271. 9:24look again, step back, and think: "
  272. 9:26Right, where is the main thing again,
  273. 9:27where do I need to push the boulder?" I
  274. 9:29create an impulse again. I push the
  275. 9:32boulder again, put the locomotives in
  276. 9:34place, and so on.

About this transcript

This page contains the full transcript of Когда суета нужна для прорыва? Над этим смеются профессиональные менеджеры by Михаил Дашкиев, generated from the public captions YouTube serves with the video. The transcript has 1,716 words across 276 segments, with the original timestamps preserved so you can click any line to jump to that moment in the embedded player.

What you can do with it

Use the transcript to take notes, quote the speaker, build a study guide, generate a summary with ChatGPT or Claude via the YouTube Summary tool, or export it as a timed subtitle file with YouTube to SRT. You can also re-open it in the transcriber to choose a caption track available on the video.

Free YouTube transcript tool

YouTube2Text is a free YouTube transcript generator — no signup, no daily limit. Paste any YouTube link and get the full transcript instantly, with timestamps, click-to-jump, caption language selection, AI prompts for ChatGPT, Claude, and Gemini, and exports to TXT, SRT, VTT, or Markdown.