Focus Is Not Genius. It Is a Kata.

Дата публикации: 09-08-2026 06:00:00

Image


In May 1997, at Apple's developer conference, an audience member stood up and insulted Steve Jobs to his face. Jobs paused, took a sip of water, and gave an answer that had nothing to do with the insult and everything to do with how he ran companies. "Focusing is about saying no," he said. "You've got to say no, no, no." And then the line that should be pinned above every roadmap: when you pursue too many directions at once, the total is less than the sum of the parts.We file moments like that under biography. Jobs was driven. Musk is driven. They separate signal from noise, work brutal hours on the single most important problem, and say no to good ideas because good is not the same as most important right now. The conclusion most people draw is that this kind of focus is a temperament, something you either have or hire. I think that reading gets the mechanism exactly backwards, and there is a lean routine that proves it.The Grid Said No So Jobs Did Not Have ToLook past the famous quote at what Jobs actually did in 1997. Apple was 90 days from insolvency and shipping dozens of overlapping products. Jobs cut over 70 percent of the product line and drew a two-by-two grid: consumer or pro, desktop or portable. Four boxes. iMac, iBook, Power Macintosh, PowerBook.The grid mattered more than the cut. Once it existed, nobody at Apple needed founder-grade willpower to reject the next plausible product idea. If it did not land in one of the four boxes, it was already dead. The structure made the decision before the meeting started. A year after the cut, Apple swung from a billion-dollar loss to a 309 million dollar profit.That is not a personality producing focus. That is a personality installing a mechanism that produces focus, and then letting the mechanism do the daily work of saying no.Musk Wrote His Down as an AlgorithmMusk made the mechanism even more explicit. Walter Isaacson's biography documents what SpaceX and Tesla call the algorithm, five steps in strict order. Question every requirement, and attach a named person to it (because requirements from "the legal department" cannot be argued with and requirements from a person can). Delete any part or process you can. Simplify what survives. Accelerate cycle time. Automate last.Two details give the game away. The order is non-negotiable, because optimizing or automating a thing that should have been deleted is the most expensive mistake available. And Musk expects deletion to overshoot: if you do not end up adding back at least 10 percent of what you removed, you did not delete enough. That is not a mood. That is a routine with an error budget, run the same way every time, by thousands of engineers who are not Elon Musk.So the two most famous examples of founder focus turn out, on inspection, to be two examples of practiced structure. Which raises the useful question: is there a version of that structure ordinary teams can practice without a founder attached?The Kata Is the Same Machine, DemocratizedThere is, and it has been running on factory floors for decades. Mike Rother spent years studying why Toyota's improvement kept compounding while its imitators stalled, and compressed the answer in Toyota Kata into a practiced routine with three moving parts.A challenge, six to twelve months out, that states the direction. One mountain, not a list.A target condition, a few weeks out, that states the next specific, measurable state on the way to that mountain. This is the focus device. Not everything that would help. The next condition to reach.And the step you run today: one experiment against the obstacle currently blocking the target condition, with a predicted result written down before you start.Map that onto the Jobs answer and the parallel is almost mechanical. The challenge is the grid. The target condition is the current box. The experiment is today's 18 hours, pointed at one problem. And the saying no, the part everyone attributes to temperament, is handled by the structure itself. When someone arrives with a genuinely good idea, the kata does not require anyone to be brave or difficult. It requires one question: does this remove an obstacle between our current condition and the target condition? If not, it is not rejected as bad. It is parked as not now. The no is impersonal, written on the wall, and nobody has to piss anyone off to deliver it. Jobs absorbed that cost personally and was famous for it. The kata spreads the cost across a routine until it stops being a cost.Tilo Schwarz, who ran this system as a plant manager before teaching it, built his work with Jeffrey Liker, Giving Wings to Her Team, around the same unfashionable idea: scientific focus is a coached skill, practiced in short daily cycles, not a mindset you announce. The coach's questions keep the learner pointed at one obstacle at a time, which is to say the coaching routine exists precisely to stop smart people from working on three interesting things at once.What This Buys a Product TeamI wrote a few weeks ago about what the kata gives agile that retrospectives never could. This is the strategic version of the same argument. Most product organizations do not suffer from too few ideas. They suffer from too many simultaneously alive ones, each defensible, each sponsored, none subordinated to a single next condition. The roadmap becomes a peace treaty among good ideas, and the total comes out less than the sum of the parts, exactly as Jobs warned.The fix does not require hiring a tyrant. Pick one challenge for the product that a 16-year-old could repeat. Set one target condition for the next few weeks, measurable, dated, visible. Run one experiment at a time against the obstacle in front of it, prediction first. And route every incoming good idea through the only question that matters: does it serve the current target condition, or does it wait? Write the parked ideas down where their sponsors can see them, because a visible not-now is easier to accept than a quiet never.Driven founders make focus look like a gift. The record says otherwise. Jobs drew a grid. Musk wrote an algorithm. Toyota practiced a kata. In every case the focus lives in the routine, not the person, and routines, unlike temperaments, can be learned by whoever shows up tomorrow morning.Ralph Jocham is Europe's first Professional Scrum Trainer, co-author of "Professional Product Owner," and contributor to the Scrum Guide Expansion Pack. As an ICF ACC certified coach, he works with organizations to build Product Operating Models where strategic clarity, operational excellence, and adaptive learning create measurable competitive advantage. Learn more at effective agile.References[1] Jobs, S. (1997) 'WWDC 1997 Closing Chat', 13 May, transcript. Available at: https://allaboutstevejobs.com/videos/misc/wwdc_1997_closing_chat[2] Macworld 'Steve Jobs's seven key decisions'. Available at: https://www.macworld.com/article/219225/steve-jobss-seven-key-decisions.html[3] Corporate Rebels 'Musk's 5 Step Algorithm to Cut Internal Bureaucracy at Tesla and SpaceX'. Available at: https://www.corporate-rebels.com/blog/musks-algorithm-to-cut-bureaucracy[4] Rother, M. (2009) 'Toyota Kata: Managing People for Improvement, Adaptiveness and Superior Results', McGraw-Hill. Available at: https://www.amazon.com/Toyota-Kata-Managing-Improvement-Adaptiveness/dp/0071635238[5] Schwarz, T. and Liker, J.K. (2023) 'Giving Wings to Her Team: A Novel About Learning to Coach the Toyota Kata Way', Routledge. Available at: https://www.goodreads.com/book/show/63077124-giving-wings-to-her-team

Схожие новости

#	Наименование новости	Тональность	Информативность	Дата публикации
1	Great Products Make Great Targets	0	11.1	19-07-2026
2	The AI Hype Reckoning Is Upon Us	-3	6	09-07-2026
3	“Scrum didn’t work for us.”	0	8.1	30-07-2026
4	Scrum Isn't for Stormtroopers	0	15.26	28-07-2026
5	Innovation vs. Novelty: The Distinction Every Scrum Master Must Master	0	7.24	12-08-2026
6	Der häufigste Fehler bei Produkt-Zielen Wie du mit KI bessere Produkt-Ziele formulierst, die nicht nur Features beschreiben, sondern die Unternehmensstrategie umsetzen	0	15.46	14-07-2026
7	Your Last Failed Transformation is not a Strategy	0	5.62	06-08-2026
8	Figma CEO says AI superintelligence is not a looming threat to the company	0	5	31-07-2025
9	Маск рвется в космос, а Китай уходит на дно: где ...	0	7	04-07-2026
10	Holding SpaceX Since The IPO? Why I'd Use The Strength To Sell	-3	4	18-06-2026

Классификация: Мнения. Схожих патентов: 0. Схожих новостей: 10. Тональность: 0. Информативность: 12.38. Источник: scrum.org.