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.
I was going to write about prevalence and incidence, and how so-called simple statistics can be much more important than people think and are vastly under-rated. It was going to be cool. Trust me. In the process, I ran across two things even more important or cooler (I know, hard to believe, right?) Here’s what…
I am old. I remember punched cards, COBOL, dumb terminals and having to walk over to the computer center and load tapes on to the drive if I wanted to use large data sets – large back then meaning 100,000 records or more with a few hundred variables. We thought that was pretty big data….
Some people may have said that hackathons are a stupid ass idea where a bunch of people who have can’t afford to buy their own pizza spend 48 hours with a bunch of strangers and no showers. Okay, well, maybe that was me. I take it all back. We kicked off our hackathon at noon…
The other night, I was annoyed. This is a common state for me, so not too surprising. I was annoyed because I could not log on to SAS On-demand. I would click the icon on my desktop and the log in screen would come up with my username filled in. About a minute after I…
Sometimes the simplest things can make life easier. When I start exploring a new data set, the first thing I do is the Characterize Data task. With even modest-sized datasets this produces a lot of output. For example, the data from Spirit Lake: The Game, with about 80 variables and 88 subjects produced 93 pages….
We had a cat named Beijing. “Had” is the key word in that sentence. This weekend I dropped Bejing off to live with my daughter, Jenn, who actually likes cats in general and this cat in particular. The main reason (besides that Jenn wanted her) is that the cat always wanted to sit on my…
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.”