Startup Lessons Learned

SEPTEMBER 7, 2008

Lessons Learned by Eric Ries Sunday, September 7, 2008 Customer Development Engineering Yesterday, I had the opportunity to guest lecture again in Steve Blank s entrepreneurship class at the Berkeley-Columbia executive MBA program. Ive attempted to embed the relevant slides below. Talk about waste.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Gust

SEPTEMBER 16, 2012

For the business leaders I know, these priorities almost always include the following: Business agility. Implicit in agility is increased productivity on change initiatives. In today’s world of distributed data, global reach, and powerful incursion technologies, how do I protect my data and my customers’ data? Data security.

Technology 162

Technology Agile Architecture Distribution 162

YoungUpstarts

OCTOBER 15, 2017

Recent developments in applications have rendered the firewall outdated and incapable of deciphering the good and trusted from the bad traffic. Agile businesses have moved to the cloud because of its scalability, efficiency and reliability, amongst other benefits. Without a doubt, the firewall era has come to an end.

Security 140

Security Software Review Technical Review API 140

Startup Lessons Learned

APRIL 26, 2009

Lessons Learned by Eric Ries Sunday, April 26, 2009 Product development leverage Leverage has once again become a dirty word in the world of finance, and rightly so. But I want to talk about a different kind of leverage, the kind that you can get in product development. Leveraged distribution channels.

Product Development 88

Product Development Developer San Francisco Product 88

Startup Lessons Learned

SEPTEMBER 30, 2008

When Ive asked mentors of mine who have worked in big companies about the role of the CTO, they usually talk about the importance of being the external face of the companys technology platform; an evangelist to developers, customers, and employees. Thats more than just drawing architecture diagrams, though. What made them exceptional?

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

SEPTEMBER 2, 2008

We wanted an agile approach that would allow us to build our software architecture as we needed it, without downtime, but also without large amounts of up-front cost. After all, the worst kind of waste in software development is code to support a use case that never materializes. Expo SF (May.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Lightspeed Venture Partners

DECEMBER 10, 2014

We had seen Lightspeed portfolio company Nicira disrupt networking layers 2-3 with an architecture that consisted of highly distributed scale out software elements coupled with centralized control, culminating in an acquisition by VMWare for $1.25B in the summer of 2012.

Architecture 121

Architecture Stealth Agile Distribution 121

ReadWriteStart

JANUARY 18, 2011

There is not enough flexibility in them to really embrace change and use creative, innovative and hungry developers to the best of their abilities. Let's face realities here: it's no doubt tempting and cool for many developers to work for Google, Yahoo, Microsoft, Facebook or Twitter to name but a few. Don't believe the hype.

Europe 139

Europe India Hiring Engineer 139

Startup Professionals Musings

MAY 27, 2010

For the business leaders I know, these priorities almost always include the following: Business agility. Implicit in agility is increased productivity on change initiatives. In today’s world of distributed data, global reach, and powerful incursion technologies, how do I protect my data and my customers’ data? Data security.

Entrepreneur 220

Entrepreneur Agile Architecture Distribution 220

Steve Blank

FEBRUARY 23, 2016

As a formal method, the Lean Startup consists of three parts: The Business Model Canvas – to frame hypotheses, Customer Development – to test those hypotheses in front of customers, and Agile Engineering – to build Minimum Viable Products to maximize learning. Distribution Channel changes to Deployment.

Business Model 120

Business Model Revenue Channel Community 120

Startup Lessons Learned

SEPTEMBER 8, 2008

You dont need to invent a new architecture, and you dont need to even build your architecture up-front. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Thoughts on scientific product development Lo, my 5 subscribers, who are you? Were in a new wave of platform evolution.

San Francisco 68

San Francisco Technology Continuous Deployment Lean 68

andrewchenblog.com

MARCH 10, 2010

Coupled with A/B testing, customer development, and thinking through business problems in a scientific, hypothesis-driven way, you end up with a powerful cocktail of techniques to build a modern startup in the most iterative way possible. They’ve also done a lot to actually remove options from the menu and navigation. See [link].

Technical Review 47

Technical Review Design Las Vegas Product 47

Austin Startup

FEBRUARY 25, 2019

You now run Pilosa, what you describe as “an open source, distributed index designed to help analyze huge datasets at UI latency.” We are also in the process of building a world class management team and a distributed engineering team of the best developers no matter what time zone they reside in. How will it work with Molecula?

Open Source 48

Open Source Startup Caching Database 48

A Smart Bear: Startups and Marketing for Geeks

OCTOBER 4, 2017

“The future is inherently unpredictable,” insists the small company, spurred on by Lean and Agile mindsets. They could have taken the tens of millions of dollars that the product cost to develop, and made their existing operation just 0.01% more effective, and made the same amount of money. Risk-mitigation.

Government 223

Government Startup Cofounder Technical Support 223

Startup Lessons Learned

SEPTEMBER 22, 2008

Lessons Learned by Eric Ries Monday, September 22, 2008 Thoughts on scientific product development I enjoyed reading a post today from Laserlike (Mike Speiser), on Scientific product development. The goal of iterative development is to give us guard rails so we dont veer off to either extreme. you can be incredibly scientific.

Product Development 68

Product Development Developer San Francisco Product 68

Startup Lessons Learned

JANUARY 4, 2009

Lessons Learned by Eric Ries Sunday, January 4, 2009 Sharding for startups The most important aspect of a scalable web architecture is data partitioning. So far, this is just a summary of what all of us who have attempted to build web-scale architectures considers obvious. Support multiple sharding schemes. Easy to understand.

San Francisco 151

San Francisco Architecture Startup Database 151

sivers.org

JUNE 25, 2010

Say, “We are hiring a developer to create only the beginning of an application. Heres the source code,” make sure you finish with something like, “For completion of this project, please have this up and running on a development webserver I can access to test its functionality as described.” The requirements are as follows.”

CTO Hire 84

CTO Hire Hiring Software Review Technical Review 84