Accept Waste
In new product development, in research, you WILL go down some dead ends. Accept it.
Similar Posts
How to write a statistical analysis paper: Step Three
So far, we have looked at How to get the sample demographics and descriptive statistics for your dependent and independent variable. Computing descriptive statistics by category Now it’s time to dive into step 3, computing inferential statistics. The code is quite simple. We need a LIBNAME statement. It will look something like this. The exact…
SAS On-Demand making statistics professors’ lives better, since, oh, Tuesday
The downward mobility of Ph.D. students is like domestic violence in many ways. That is, the people in the “family” all know it is a fact of life, but they don’t talk about it among themselves, and to outsiders they pretend it doesn’t exist. The fact is, far more people will graduate from Harvard than…
Converting dates: from character to numeric, from Excel to SAS
I’m back with another SAS Tip of the Day. Like a lot of people, I work with dates very often. How many days is it from when a client applies to when he or she is determined eligible? How many days until the average client is employed? You get the idea. Inconveniently, in this particular…
Urban vs Rural Barriers to Ed Tech: An example of Fisher’s Exact Test
Who was it that said asking a statistician about sample size is like asking a jeweler about price. If you have to ask, you can’t afford it. We all know that the validity of a chi-square test is questionable if the expected sample size of the cells is less than five. Well, what do you…
Data quality – getting ready to teach data mining
Getting ready to teach a data mining course at the end of the year, I started looking through data sets I have on my desktop. Not sure what I will end up using. My first lesson, no matter what, is going to be on data quality. The very first thing I did was a series…
WUSS – It’s more than funny hats
What the hell is WUSS? Why would *I* ever go to anything with the name WUSS? It’s not just so you can get the cool hats which double as lunch bags, although that’s one possible incentive. It’s also not just so you can get your own original, signed illustration of the difference between ordinary least…
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.”