Accept Waste
In new product development, in research, you WILL go down some dead ends. Accept it.
In new product development, in research, you WILL go down some dead ends. Accept it.
Any time you learn anything new it can be intimidating. That is true of programming as well as anything else. It may be even more true of using statistical software because you combine the uneasiness many people have about learning statistics with learning a new language. To a statistician, this error message makes perfect sense:…
Several times on this blog, I have mentioned that the most common errors I make, and most programmers*, are the simple things like typing or forgetting to close a bracket or tag. Many of those errors are now automatically fixed by the intellisense of various IDEs (Integrated Development Environment), like Webstorm, but they still pop…
You know that feeling after Thanksgiving dinner when you have had all of your favorite foods all at once and are so full that you think you will never eat again. Well, the past week has left my brain like that. Within twelve days, I attended the SPSS Higher Education Road Show at UCLA, then…
Well, this morning started out annoying, and not just because I had to be at LAX at 8 a.m. I am sitting here trying to analyze an SPSS file someone sent me last night and I get this … Command: CORRELATIONS Incomplete (truncated) SPSS Statistics data file: /Users/annmaria/blahblah.sav Execution of this command stops. I tried…
1. It’s free. Some people say this is just the evil corporate answer to R. Maybe. Probably. I don’t care. I don’t see Microsoft giving me anything for free. 2. It’s pretty easy for an instructor to get an account. I presume SAS verifies your instructor account. First you need a SAS Profile https://www.sas.com/profile/user/create.htm Then…
The first cool thing you should know about Dr. Patricia Berglund is that she and several others put their slides and more up at the SAS Global Forum take-out section. That is NOT, contrary to what you might believe, a place where you can pick up some really good Chinese food to eat while listening…
Transcript
—
Accept the fact that you’re going to waste some time.
That’s some advice I give to young people starting businesses; you’re going to waste time and you’re going to waste money. I mean that in the sense that some things you do, you’re going to have to do over. In our company, we often will start on something, get a certain way down the path and realise “you know, we really don’t want to do that in Ruby, we’re going to start over”. What you hope is that you don’t get too far down the path before you decide you have to start over, but it’s inevitable. I think sometimes larger companies – that’s why I said yesterday I was so impressed that IBM had actually written that article on Just In Time Design – larger companies often are so risk averse, in the sense of “we don’t want to ever have to throw anything away that we did”, that they’ll spend an inordinate amount of time planning something out so they don’t have to justify that we spent all this money on something we never used.
In our case, we’ll go ahead, we’ll try it; if it doesn’t work then we quit doing it. If it does work then we do some more of it. Whether it’s paying somebody to do a logo, if it’s doing 2D programming and then saying we need a combination of 2D and 3D, if it’s creating one model for a teepee and saying “it’s too cartoonish” and throwing it out. You often don’t know those things in advance and you just need to accept that as you progress you’re going to realise that some of what you do initially doesn’t fit any more. And that’s just the way it is.
I think the modern day buzzword for this notion is “pivoting”.
This is a key advantage of small business: the ability to rapidly change / adapt faster than the big boys. We aren’t as plagued with process or formalities (or “escalation of commitment” to use an OB term).
While big companies have more financial resources, SBs have more “pivoting” ability, which is a huge resource. I’ve also found it to be a huge advantage that employees wear many hats in a SB and seem to care much more about the big picture … seeing the forest for the trees if you will, vs. the typical “that’s not my job” mindset of a big corp worker.
37signals is a great company to study. They’ve purposely kept employee count as small as possible. I recommend the book “Rework” by Jason Fried and David Heinemeier Hansson (the later of which is the inventor of Ruby on Rails).
Thank you, Phil, for the transcript. I’m going to have someone type the next one for me (stealing your idea) because I need to put it up for a student.
Thanks, Clint for the book suggestion. I’ll read it when I take off next week.
To entice you a little more, here’s an excerpt from “Rework”:
“A lot of people get off on solving problems with complicated solutions. Flexing your intellectual muscles can be intoxicating. Then you start looking for another big challenge that gives you that same rush, regardless of whether it’s a good idea or not.
A better idea: Find a judo solution, one that delivers maximum efficiency with minimum effort. Judo solutions are all about getting the most out of doing the least.
Whenever you face an obstacle, look for a way to judo it.”