Pants. I put them on every weekday


In scenario-based competitive shooting, you’re put on squads. Each squad is assigned to a stage. Each shooter on a squad shoots the stage. Then squads rotate through the stages. 


A few years ago, a buddy of mine got squadded with Jerry Miculek. Figuring the man commonly considered to be the greatest all-around competitive shooter of all time might have some good pointers, my buddy asked, “Hey Jerry, have any tips?” In his trademark faint cajun accent, the winner of 50+ major championships replied, “Shoot fast, don’t miss.”


It was sly. It was funny. It was a flip acknowledgement that no single do-or-don’t will make that much of a difference; excellence is cumulative. I love it. I love it because it makes me think about how we often confuse high-level methods with process. 


I have a goal to lose weight. The simplest statement of the method by which I will achieve that goal is: eat less, exercise more. The process? Hell if I know. There’s a million fad diets, exercise regimes, and fatuous gurus. But the only way I’m going to achieve my goal is to eat less and exercise more.


In software, I hear tedious arguments about process. That’s not agile. This other thing is agile. Allow me to redirect your attention from our actual goals to the elaborate latticework supporting our day-to-day work. I respect process. When it achieves my goals. I hate orthodoxy. My goal at work is to make us more profitable. The methods are velocity and quality. When meetings get bogged down in a swirl or minutiae and tactics, I apply Jerry’s Razor: “How does this help us make better things faster?”