Startup Lessons Learned

JUNE 2, 2010

Lessons Learned by Eric Ries Wednesday, June 2, 2010 The Five Whys for Startups (for Harvard Business Review) I continue my series for Harvard Business Review with the Lean Startup technique called Five Whys. Five Whys has its origins in the Toyota Production System. Applied to a start-up, heres how it works. Speed up or slow down?

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

Startup Lessons Learned

AUGUST 8, 2009

Lessons Learned by Eric Ries Saturday, August 8, 2009 Revisiting the Software Design Manifesto (and whats changed since then) My recent article on technical debt and its positive uses generated a fair bit of controversy. The argument itself got me thinking a lot about design and its role in building products.

Software Review 87

Software Review Design Software San Francisco 87

YoungUpstarts

OCTOBER 19, 2011

That was 1994, and now, almost 20 years later, QR code technology is experiencing a revival — but not in the automotive industry. The possibilities for their use are endless, and many translate into the college classroom , offering a fun and exciting way for students to use technology for learning. Link to book reviews.

Software Review 262

Software Review Technical Review Mobile Video 262

Feld Thoughts

JUNE 22, 2012

I’m a huge fan of William and his writing as you can see from my review of his book Avogadro Corp. There seem to be two schools of thought on how to predict the future of information technology: looking at software or looking at hardware. A big technical challenge we studied was piping streaming video over networks.

Artificial Inteligence 182

Artificial Inteligence Technical Review Bandwidth Software Review 182

dontbesoanalytical.blogspot.com

MAY 13, 2012

From time to time, Ill address information technology, and how it impacts business and daily life. Daddy, What Does a Chief Technology Officer Do? should rest with a COO; the CTO is a research and ad tech discipline in the strategic planning domain. Other firms may shy away from the uncontrolled side of these technologies.

CTO 40

CTO Technical Review Technology Software Review 40

Both Sides of the Table

AUGUST 23, 2010

I was an early user of Quora and like all new technologies they take a bit of playing with them for a while, discussing them with others and reflecting on them to let them sink in. The design, albeit not intuitive at first, was beautiful and in weird ways very graceful. It also feels very wiki like. really understand it.

Silicon Valley 301

Silicon Valley Pre-Money Valuation Technical Review Software Review 301

Startup Lessons Learned

SEPTEMBER 10, 2008

Notice that none of those five reasons deals with TDD or automated testing, which have changed the game. I love Joels approach to usability, and I still recommend his free online book on UI design. This is the approach of test-driven-development (TDD). I agree with the other Anonymous regarding TDD (Test Driven Development).

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

JANUARY 12, 2010

Recent economic events, technological change, and the rapid diffusion of information about the old models have combined to help us all realize just how important entrepreneurship is - and just how little we really know about it. Its a wiki, feel free to consume and enhance it. Its a wiki, feel free to consume and enhance it.

Lean 146

Lean San Francisco Wiki Startup 146

Startup Lessons Learned

JUNE 17, 2010

I was the junior guy on a project team; I was called in to do some technical due diligence for reasons that were obscure to me, because the team already had much more senior engineers assigned to it. As a technical fix, it was brilliant. I remember one such meeting vividly. So they react in two ways.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

ConversionXL

JANUARY 12, 2017

When sites are designed, developed and written with web accessibility in mind, everyone has equal access to online information, products, and opportunities. For example, a key principle of Web accessibility is designing Web sites and software that are flexible to meet different user needs, preferences, and situations. Guideline 1.4:

Web 48

Web Software Review Technical Review Canada 48

Startup Lessons Learned

OCTOBER 20, 2008

Heres my diagnosis of his problem: He has some automated tests, but his team doesnt have a continuous integration server or practice TDD. And has the tension goes down, it will be easier to get the whole team (including the MBAs) to embrace TDD and other good practices as further refinements. Good luck, engineering manager.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

AUGUST 2, 2008

Lessons Learned by Eric Ries Saturday, August 2, 2008 Paul Graham on fundraising I have found no better primer on the current realities of starting a new technology company in a startup hub like Silicon Valley than Paul Grahams essays. Lean Startup Wiki - including a complete list of local meetups and meetup organizers.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

Startup Lessons Learned

SEPTEMBER 15, 2008

Lessons Learned by Eric Ries Monday, September 15, 2008 The one line split-test, or how to A/B all the time Split-testing is a core lean startup discipline, and its one of those rare topics that comes up just as often in a technical context as in a business-oriented one when Im talking to startups. First of all, why split-test?

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

SEPTEMBER 10, 2008

Of the techniques he mentioned, I think four are fundamental and critical for any lean startup: TDD (or the even more politely named TATFT ) Continuous integration Automate your deployments Collect statistics The tools to help you do these things are getting better and better every day, but dont confuse tools with process.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Lessons Learned

MAY 31, 2010

And a special thanks is due to all of our presenters, panelists, and mentors. Although many of the non-technical folks in the room didnt understand what was happening in the moment, plenty of hackers were on high alert. If thats true, its primarily due to your hard work, building companies and testing new ideas. We all owe you.

San Francisco 133

San Francisco Lean Technical Review Software Review 133

Startup Lessons Learned

JANUARY 15, 2010

Lessons Learned by Eric Ries Friday, January 15, 2010 Two Ways to Hold Entrepreneurs Accountable (for Harvard Business Review) The next part in the series I am writing for Harvard Business Review is online. They are long-term bets on the development of a new line of business, a new technology platform, or the creation of a new market.

Hockey Stick 105

Hockey Stick San Francisco Entrepreneur Lean 105

Startup Lessons Learned

JANUARY 7, 2010

for Harvard Business Review) Im excited to have just published the first of several articles on entrepreneurship for the Harvard Business Review online. The Conversation - Harvard Business Review For most of us, the phrase management science conjures up a decidedly non-entrepreneurial image, and for good reason.

San Francisco 119

San Francisco Management Continuous Deployment Lean 119

Startup Lessons Learned

NOVEMBER 6, 2008

They take things like unit testing, design documents and code reviews more seriously than any other company Ive even heard about. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Anyway, thanks Stevey for your thoughtful post. Lo, my 1032 subscribers, who are you? Bring your questions.

Agile 76

Agile San Francisco Software Review Continuous Deployment 76

Startup Lessons Learned

FEBRUARY 20, 2009

Lessons Learned by Eric Ries Friday, February 20, 2009 Work in small batches Software should be designed, written, and deployed in small batches. Similar results apply in product management, design, testing, and even operations. Take the example of a design team prepping mock-ups for their development team. I dont think so.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

AUGUST 24, 2009

The other revels in the world as we all know it will be someday: limitless distribution enabled by new technologies, the importance of collaborative filters, and on-demand availability of all content for end-users. But the same technologies that make life difficult for traditional marketers also offer them unprecedented new opportunities.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

NOVEMBER 17, 2008

Playing with new technologies. One approach to the issue you bring up that's worked for us is to set an initial due date that’s overly aggressive, and expect that we’ll probably blow through it (while suspending disbelief as much as possible). Seeing whats possible. Building and testing prototypes. Bring your questions.

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

Startup Lessons Learned

AUGUST 26, 2009

Im also excited to share two long-form reviews from actual attendees. And one last specific practice that came up at this session: feverishaaron : UI, design and programmers are all in the same department, all have the same title, and all are evaluated the same. Technically you argue it goes back 30 years when StorageTek was founded.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

ConversionXL

MARCH 29, 2017

As David Arnoux of Growth Tribe explains, the successful growth hacks you’ve read about from tech superstars are merely the result of a finely-tuned process… David Arnoux , Growth Tribe : “What people call a growth hack is usually running through as many experiments as possible until we find something beautiful that works perfectly.

Marketing 48

Marketing Distribution Retention eCommerce 48

Startup Lessons Learned

MAY 14, 2009

Lessons Learned by Eric Ries Thursday, May 14, 2009 The Lean Startup Workshop - now an OReilly Master Class My rate of posting has been much lower lately, and this is mostly due to preparations for the upcoming Lean Startup Workshop on May 29. I joined a financial services tech startup in 1999. May 14, 2009 5:23 AM David said.

Lean 60

Lean San Francisco Continuous Deployment Software Review 60

Startup Lessons Learned

FEBRUARY 22, 2009

That data is completely consonant with the people I know who are successful technologists today, and similar patterns are documented in each recent wave of technology innovation. There would be no Microsoft, Sun Microsystems, or countless other job-creating tech companies today if early computers required corporate authorization to use.

Programming 143

Programming San Francisco Lean Continuous Deployment 143

Startup Lessons Learned

NOVEMBER 13, 2008

Hes a new employee, and he was not properly trained in TDD So far, this isnt much different from the kind of analysis any competent operations team would conduct for a site outage. What started as a technical problem actually turned out to be a human and process problem. We didnt even practice TDD across our whole team.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

DECEMBER 7, 2008

Its common to find a hacker at the heart of almost any successful technology company. When a startup encounters difficult technical problems, this is the guy you want solving them. As the company grows, hes the go-to person for almost everything technical, and so hes very much in demand. Every day counts, every minute counts.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

JUNE 15, 2009

Thanks to a phenomenon called the Fundamental Attribution Error in psychology, humans tend to become convinced that other people’s behavior is due to their fundamental attributes, like their character, ethics, or morality – even while we excuse our own actions as being influenced by circumstances. April 23, 2010 in San Francisco.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

JULY 2, 2009

That’s because Five Whys will often pierce the illusion of separate departments and discover the human problems that lurk beneath the surface of supposedly technical problems. But if we stay stuck at the technical parts of the problem, and never uncover the human problems behind them, we’re not going far enough.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

AUGUST 3, 2009

Refreshing to finally see lean and agile thinking emerge in product/business-floors and not only in technology. While it is still possible - and recommended to experiment with customers in order to determine the minimum that they need, the exercise is bit more complicated due to the formality of the release process. Thanks Eric.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Startup Lessons Learned

FEBRUARY 11, 2009

Yes, you may be more familiar with the term open source, but lets give credit where credit is due , at least for today). Ignore the famous people who are busy giving lots of speeches about how technology X will change the world. Lean Startup Wiki - including a complete list of local meetups and meetup organizers.

Software Review 68

Software Review Software Hiring San Francisco 68

www.igda.org

JULY 24, 2012

Electronic Arts is no different than many high-tech companies in this regard. Where O is total output, X is the given output during a benchmark number of hours, designated by Y , and t is the actual number of hours worked. hours per week — but after that many hours, whos still counting?

Software Review 90

Software Review Technical Review Widget Los Angeles 90

Startup Lessons Learned

JULY 13, 2009

Product development deals in designs, which are fundamentally intangible. Team New Zealand designed the yacht that won the Americas Cup. When they tested improvements in keel designs, they used two virtually identical boats. The unimproved boat would sail against the improved boat to determine the effect of a design change.

Product Development 153

Product Development Developer San Francisco Product 153

Startup Lessons Learned

SEPTEMBER 27, 2010

This is precisely the dilemma that the doctrine of minimum viable product is designed to solve. Over time, such teams either explode due to irreconcilable differences or dramatically slow down. If there are investors involved, they should be fully briefed on the expectation that these early efforts are designed to fail.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Startup Lessons Learned

OCTOBER 5, 2009

Due to an interaction effect between your hardware, solar flares, and quantum flux, this virus will crash your computer and erase your hard drive sometime soon. In the past, we invested in brilliant architecture, code reuse, refactoring, modular design, etc. I have detected a secret virus in your CPU. The curse of prevention Beware!

San Francisco 133

San Francisco Architecture Lean Continuous Deployment 133

Startup Lessons Learned

FEBRUARY 10, 2009

Code reviews and pairing Great practices. So that you can learn from our mistakes, Chad has helpfully listed ten reasons why you want to manage this dirty-code (sometimes called "technical debt") problem proactively. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Bring your questions.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

Startup Lessons Learned

SEPTEMBER 18, 2008

From a technical point of view, its amazing. All I see is a name, an icon, a price, the developers name, and a review star-rating. The reviews are all over the map. But even clicking through to see a screenshot and some reviews is incredibly time consuming, given the hundreds of apps in most categories.

Distribution 74

Distribution San Francisco Lean Continuous Deployment 74