I like this very much:<p>"In reality, process is not my problem. It’s what discussions around new processes often preview within a company. Lack of focus. Peacetime thinking. Complacency."<p>I recently wrote a small book for small startups called "One on one meetings are underrated; group meetings waste time" and I have gotten a lot of pushback regarding my emphasis on intuition, pragmatism, and favoring direct action over process. And over and over again, people reach out to me with some variation of "So you think the people who run Google are stupid? You think the people who run Apple are stupid? You think all of these brilliant people are actually idiots?" And my defense has been: "No, I just think those companies are large, and my advice is for small startups. Small startups are different."<p>It should be common sense to say that small startups are different, and need to operate by other rules. But I have noticed, there are some people in the tech industry who seem to think that the way a small startup becomes a huge tech giant is by imitating that huge tech giant exactly, including all of that tech giant's "best practices." But what is "best practice" at a huge company will not work at a small startup. In fact, many of those processes would be fatal, at a small company. They'd cause you to move too slowly, and they'd also cause you to give up the few advantages that you actually have as a small company, such as the ability to trust one another (when the whole team is just 5 people, it is easier to trust one another than when you've a company of 10,000 people).
Definition of desperation<p>1 : loss of hope and surrender to despair<p>2 : a state of hopelessness leading to rashness<p>Am I missing something or is it a term that is coopted to romanticize something particularly horrible? I'm not a native english speaker so perhaps I am missing something, but with severe depression and suicidal attempts I had understood states of a certain learned helplessness to be what desperation is about.<p>Adversity and hope are what I believe small struggling companies hold on to, which seems wholly different from "desperation" and much more conducive to growth and creation.. but perhaps I'm not understanding what natives would understand.
Maybe only somewhat relevant, but the title phrase resonated with me. Given my ADHD, desperation-induced focus was the only thing that got me through college with good grades. I wouldn't study until the night before the big exam because I was unable to focus under normal circumstances, or even pay any attention to what was being said in class, but the desperation-induced focus of the big exam in the morning finally enabled me to study, and in that circumstance, to study very well and do just fine on the test.
Perhaps this is a useful counterpoint:<p>Aviation Psychologist David Beaty on the phenomenon of ‘Set’ (1991):<p>“‘Set’ is a survival characteristic we have inherited. The human brain evolved to help individuals live and survive circumstances very different from our own. It predisposes us to select our focus on that part of the picture paramount at the time – a vision often so totally focused that it ignores the rest of the environment.<p>Once something is identified […] it takes on a reality of its own and sticks in the mind like a burr which is difficult to dislodge. […] The mind becomes tunnelled on a particular course of action. Add to that the ingredient of fatigue and it is not difficult to see that a ‘set’ as hard as concrete can result. Furthermore, ‘set’ is infectious. There is a follow-my-leader syndrome. So it is easy to see why most aircraft accidents are caused by ‘silly’ mistakes in the approach and landing phase.<p>[…] ‘Set’ has been a factor in many aircraft accidents. [In a case in 1972 over Florida], the crew of a Tristar were not sure that their undercarriage was down. The accident sequence was begun by a burned out light bulb in the system which is designed to show that the undercarriage is down and locked. […] the crew examined every possible of finding the trouble. The flight engineer crawled down into the nose, while the captain and the first officer tried every combination of switches and circuit-breakers. […] the three members of crew did not notice that the autopilot had become disengaged and the aircraft was sinking […] eventually crashing into the Everglades.<p>Because they had become preoccupied with an unsafe landing-gear indication, they failed to monitor the critical altimeter readings. Ironically, the air traffic controller noticed on his radar that the aircraft was losing height, but instead of pointing this out simply asked diplomatically “How are things coming along there?”.<p>The crew, still obsessed with their landing-gear problem, assuming he referred to that, for they could thing of nothing else, replied seconds before the crash, “Everything is all right!”<p>– Paraphrased from The Naked Pilot by David Beaty (Ch.6)<p><a href="https://books.google.com/books/about/The_Naked_Pilot.html?id=66R8AwAAQBAJ" rel="nofollow">https://books.google.com/books/about/The_Naked_Pilot.html?id...</a>
There is a kind of process that I think is worth it:
a group protocol on how we do things that allows you to walk into a situation and understand what’s being done and how to proceed without needlessly needing to talk to others that where involved before you.<p>* The documentation will be here and look like this.<p>* The deployment is done using code that lives here.<p>* The code would have been in a PR here.<p>Etc.
Tangentially related:<p>For a while, I had a girl friend who had a remarkable propensity to get herself into serious trouble, often while I was on a different continent. We noticed that when I got apprised of these acute situations, far away, unable to do anything about it, I would often score exceptional high scores on my favourite games. The stress and desperation I couldn’t put to good use to help instead manifested itself in laser focused game performance…
I always think the Spider-Man maxim needs to be turned around:<p>“With great responsibility comes great power”<p>If you need someone to have amazing output, rather than shackling them with a process, give them responsibility and the corresponding power to make decisions and to execute.
I think it depends on the process? Process isn’t a boogeyman. If a team is consistently deploying to production wrong and customers aren’t happy, you need a process.<p>A peacetime process though, then I’m. To agree
The post seems to have two separate topics - one I agree with, one I don't.<p>One is about keeping things simple and having focus. Could not agree with it more. On every proposal, ask, "What problem does this solve?", "Is the cure worse than the disease?", "If this is added, what else can be removed so that the overall weight stays the same?". All good points; I don't think that is controversial.<p>But then, the post goes into what I can only describe as a rant. Something about going to the whiteboard. About desperation. Some random tangent on bottle deposits. I don't agree with this.<p>A "small company" is not synonymous with a "poorly-run company". Sure, Mario Andretti's quote "If everything seems under control, you're not going fast enough" applies to almost every startup. There always will be some portion of the company that needs urgent attention. But valorizing constant struggles, throwing your hands up saying "Duh, startup" is poor leadership, IME.<p>The big tell for me is that Ravi does not explain what is a good process. There never is a "no process" world. The choice is between a stated, well-understood process OR a poorly-specified, poorly-understood, inefficient process.<p>A few years ago, startups used to say, "Oh, we have a flat organization - no hierarchies," and wear that as a bad of honor. Not really; there always is a hierarchy - except now it is based on who hangs out with who. I notice that most startup leaders understand this now, and the "no hierarchy" line is not trotted out these days. The "no process" bit is also like that, IMO.
> But now they are different. Most big companies aren’t focused on creating things out of nothing. Someone else made the magic money-making machine, and they assume that it will just keep working. With the one thing that actually matters taken care of, they care about luxuries like making sure as high a percentage of the company as possible feels included in the planning process. Or creating performance review frameworks with an ever-increasing number of boxes and categories. Or something else that matters even less than that. This lack of focus is a luxury and a disease.<p>Absolutely brilliant paragraph, couldn't have said it better. I wonder if this is some function of "idle hands do the devil's work": that is, people with not enough work to do find some moderately useless thing to do that feels like work and seems like work but is actually wasting time or even counterproductive. Perhaps a properly lean company always has a bit more work to do than it has the capacity to do it.
This echos "Desperate Ground"[1] or "Death Ground" in Sun Tzu's Art of War. I've put myself deliberately in this position many times in order to succeed. The day-to-day uses of this idea tend to be far less dramatic than the name implies. I've even applied it to process where I would phrase it as, "Create processes when you must, not when you can."<p>1. <a href="https://suntzusaid.com/book/11" rel="nofollow">https://suntzusaid.com/book/11</a>