Desperation-Induced Focus(rkg.blog)
rkg.blog
Desperation-Induced Focus
https://rkg.blog/desperation-induced-focus.php
3 comments
Agreeable. But, wouldn’t it be really difficult to evaluate processes? It’s like evaluating safety systems. You’ll always underestimate the system’s impact on safety because a safe system is usually uneventful and asymptomatic. You wouldn’t know if threat is not so grave anymore, or that the system’s working so fine that you just don’t feel it. Similarly, evaluations of processes would pose a similar problem. If people are naïve enough to blindly apply it from one organization to another, what prevents them from wrongly undermining the impact of the process and yank it off like a knowitall?
Very relevant, and could not agree more. Your company does not need another process. Identify your top line goal and do whatever you have to to meet it.
"So, the next time you feel desperate, lean in. Embrace it. Use it as the fuel to create the next founding moment for your company"
"So, the next time you feel desperate, lean in. Embrace it. Use it as the fuel to create the next founding moment for your company"
A couple bad examples of processes:
Often, people implement processes because they are aware that <bad thing> can happen and they wish to avoid it. The challenge is that sometimes <bad thing> has a much lower occurrence (occasionally ~0), or cost in a different environment. Meaning that the process they used at another company isn't actually helpful for another company, and may actually cost more than it saves.
Processes can also become obsolete, but are rarely evaluated for that. Again, that means costs without appropriate savings.
Conclusion: Implement processes carefully, and constantly evaluate them for appropriate savings. And don't assume that a process that worked <there> will work <here>, unless you have proof of some sort.