I just came across a great set of slides put together by Garrett Dimon the creator of Sifter, a bug and issue tracking software package. He talks about the leaps needed to go from creating something to developing it into a fully fledged company. It’s a fascinating insight into the trials and tribulations of starting front scratch and carries some massively important lessons we all should learn. Enjoy!
Image via Wikipedia Interesting post on the New York Times by Dick Brass who used to be a Vice President at Microsoft. He talks about what he believes is one of the downfalls of the company; that it stifles innovation when instead it should be nurturing it. He describes a number of cases where great ideas were sacrificed for personal ambitions; a symptom of an organisation that is politically motivated. This sort of organisational behaviour can be detrimental in the…
I came across some good pointers in a magazine which I thought I’d echo here for posterity. They’re good points to remember and provide a good framework for things you need to keep in mind. Change must be actively and proactively managed, as unforeseen effects can be costly and risky Detailed impact analysis must be carried out, to see what the ramifications will be throughout the company and among all stakeholders Behavioural and cultural changes will have the most impact…
“Enterprises must learn how to be less dependent on the shrinking number of folks who are well versed in the applications running the business like COBOL, PowerBuilder, and Oracle Forms,” … “Most CIOs won’t admit it, but not only do many of them not know how these applications work, they don’t know if these applications work. All they know is they’ve got 30 million lines of COBOL code and no COBOL programmers, institutional knowledge, or documentation. They need to go…