Startup Lessons Learned

NOVEMBER 7, 2008

So, if youre interested in helping avoid mistakes like that, here are the steps: Get a domain name. It doesnt have to be the worlds catchiest name, just pick something reasonably descriptive. If youre concerned about sullying your eventual brand name, dont use your "really good" name, pick a code name.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

OCTOBER 4, 2008

Lessons Learned by Eric Ries Saturday, October 4, 2008 About the author ( Update January, 2010: This post originally dates from October, 2008 back when I first started writing this blog. Ken Yagen (@kenyagen) KenAtYagenDotCom January 3, 2010 1:38 PM Paramendra Bhagat said. November 25, 2009 9:54 AM Danny Wong said. Blew my mind.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

SEPTEMBER 7, 2008

In addition to presenting the IMVU case, we tried for the first time to do an overview of a software engineering methodology that integrates practices from agile software development with Steves method of Customer Development. Ive attempted to embed the relevant slides below. What about a hardware business with some long-lead-time components?

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Startup Lessons Learned

JULY 29, 2009

Like a financial debt, the technical debt incurs interest payments, which come in the form of the extra effort that we have to do in future development because of the quick and dirty design choice. We can choose to continue paying the interest, or we can pay down the principal by refactoring the quick and dirty design into the better design.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

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. Its had tremendous impact in many areas: continuous deployment , just-in-time scalability , and even search engine marketing , to name a few. I dont think so. This is a fantastic article.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

SEPTEMBER 10, 2008

Lessons Learned by Eric Ries Wednesday, September 10, 2008 Smarticus — 10 things you could be doing to your code right now Smarticus — 10 things you could be doing to your code right now A great checklist of techniques and tools for making your development more agile, written from a Rail perspective. Expo SF (May.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Lessons Learned

NOVEMBER 8, 2008

This theory has become so influential that I have called it one of the three pillars of the lean startup - every bit as important as the changes in technology or the advent of agile development. This is a self-published book, originally designed as a companion to Steves class at Berkeleys Haas school of business. Heres the catch.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Steve Blank

APRIL 6, 2009

Not surprising with a CEO with a PhD in Math, at ESL the engineers ran the company, pursuing bleeding-edge designs in antennas, receivers and microwaves – at times hand in hand with Stanford’s engineering department. could design and produce, and a good part of it was coming from Silicon Valley. Never in Gulag, only in exile.

Silicon Valley 176

Silicon Valley Stealth RSS California 176

Steve Blank

APRIL 27, 2009

So they systematically designed electronic devices called “jammers&# to shut down each part of the German air defense system. And 30 years later I was teaching in a building named after him and never knew a thing about him. Reply Augusta Prince , on April 16, 2010 at 3:08 pm Said: My late friend Gordon P.

Silicon Valley 185

Silicon Valley Technical Review Europe Germany 185

Startup Lessons Learned

SEPTEMBER 15, 2008

The new design improved on the old one in several ways, but these improvements didnt translate all the way through the funnel. Usually, I think that means youve lost some good aspect of the old design. The designers might be telling you that the new design looks much better than the old one, and thats probably true.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

AUGUST 26, 2009

Accept that many successful companies are going to want to be backed by big-name firms in other cities. Thank you @ericries for drastically altering my perception of agile startup Thank you all so much for your kind words. That meant getting designers, programmers, and QA folks to cross-train and work together as peers.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

Steve Blank

APRIL 30, 2009

Customers went into the store either looking for the SuperMac product by name (if our demand creation activities had been effective) or went in unsure of which brand of board to buy. The design was actually a negative drag on selling anything off a retail shelf. From grumbling skeptics, they all became packaging design converts.

Sales 120

Sales Silicon Valley RSS Las Vegas 120

Startup Lessons Learned

OCTOBER 20, 2008

When I first encountered agile software techniques, in the form of extreme programming , I thought I had found the answer. I explained it to people this way: agile lets you make the trade-offs visible to whole company, so that they can make informed choices. Even worse, agile wasnt really helping me ship higher quality software.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

JULY 30, 2009

I want to thank Techstars for putting this event together and giving me a chance to experience the scene, even if it lacks a name. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, Traveling to new startup hubs is one of my favorite things about being able to do this full-time. Expo SF (May.

Lean 68

Lean San Francisco Continuous Deployment DC 68

Steve Blank

APRIL 9, 2009

But what I wanted was an agile marketing team capable of operating independently without day-to-day direction. This year, marketing need to provide sales with 40,000 active and accepted leads, company and product name recognition over 65% in our target market, and five positive product reviews per quarter. Blog at WordPress.com.

Silicon Valley 263

Silicon Valley Technical Review RSS PR 263

Startup Lessons Learned

APRIL 14, 2009

Their product development team is hard at work on a next-generation product platform, which is designed to offer a new suite of products – but this effort is months behind schedule. Go on an agile diet quickly. With a product development team that is not shipping, any agile methodology will surface major problems quickly.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

SEPTEMBER 12, 2008

It’s easy to overestimate the impact of this kind of traffic because it just feels good to have your name and company featured. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, April 23, 2010 in San Francisco. It strokes your ego. Expo SF (May. Conference streaming, sponsors, discounted tickets.

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Steve Blank

MARCH 18, 2011

Lean Startups/Back to Basics (2000-2010): No IPO’s, limited VC cash, lack of confidence and funding fuels “lean startup” era with limited M&A and even less IPO activity. 2001 – 2010: Back to Basics: The Lean Startup. The New Bubble : (2011 – 2014): Here we go again…. The IPO offering document became the playbook for startups.

Internet 334

Internet IPO Silicon Valley Agile 334

Altgate

SEPTEMBER 16, 2010

When outsourcing, remember that lawyers are like VCs…it matters less who’s name is on the front door than who you work with. Unless you’re a designer you’re going to outsource the graphical design work you have, but remember, you get what you pay for. Again…another nobrainer unless you’re LegalZoom.

Software Review 65

Software Review Offshore Startup Boston 65

Startup Lessons Learned

JANUARY 18, 2010

Lessons Learned by Eric Ries Monday, January 18, 2010 Case Study: Continuous deployment makes releases non-events The following is a case study of one entrepreneurs transition from a traditional development cycle to continuous deployment. Ive previously named his post Achieving Flow in a Lean Startup as one of my favorite blog posts of 2009.

Continuous Deployment 151

Continuous Deployment San Francisco Lean Wiki 151

Startup Lessons Learned

OCTOBER 26, 2009

In previous posts, I’ve mentioned quite a few of these, including these most important ones: having engineers post on the forums in their own name when they make a change routinely split-testing new changes routinely conducting in-person usability tests and interviews Net Promoter Score Each of these techniques is fundamentally bottoms-up.

Advisory Board 151

Advisory Board Customer San Francisco Lean 151

Steve Blank

SEPTEMBER 17, 2009

In future posts I’ll describe how Eric Ries and the Lean Startup concept provide the equivalent model for product development activities inside the building and neatly integrates customer and agile development. A few successful ones do all these things. A few successful ones do all these things. This post describes such a model.

Customer Development 246

Customer Development Developer Customer Silicon Valley 246

Startup Lessons Learned

JANUARY 19, 2009

Much of what I have found effective is counter-intuitive, because it requires investing more effort in each hire - all in the name of efficiency. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, April 23, 2010 in San Francisco. This is another sub-optimization caused by incentivizing the wrong metric.

Lean 140

Lean Hiring San Francisco Continuous Deployment 140

Startup Lessons Learned

JUNE 5, 2009

We're starting our new business, fanminder.com, to help small merchants instantly communicate with their customers, and I'm increasingly hearing your name and reading your keen insights. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, April 23, 2010 in San Francisco. Expo SF (May.

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

www.ere.net

JULY 15, 2012

by Dr. John Sullivan May 10, 2010, 12:16 am ET. It might surprise you to know that the average recruiter cannot name the distinct steps in the recruiting process, nor the goals or common failure points for each step. May 10, 2010 at 6:26 am. May 10, 2010 at 9:39 am. May 10, 2010 at 10:09 am. Advice and How-Tos.

Hiring 57

Hiring Metrics Search Widget 57

www.smashingmagazine.com

MAY 5, 2011

Most designers are familiar with the conventional ways. In this article, we’d like to present a couple of new ideas that might be useful for your next designs. Ask for a User Name After The User Has Signed Up Sign-up forms typically ask users to create a name that is unique to the website.

AJAX 104

AJAX Security Design Naming 104

Steve Blank

JUNE 22, 2009

The original Hewlett Packard which made test and measurement products was spun-out and renamed Agilent. The remaining company kept the Hewlett Packard name and focussed on computers. Agilent is a $5.8 Technology changes, culture changes, customer needs change, more agile competitors emerge, etc.

Silicon Valley 169

Silicon Valley RSS California Agile 169

Steve Blank

SEPTEMBER 10, 2009

In future posts I’ll describe how Eric Ries and the Lean Startup concept provided the equivalent model for product development activities inside the building and neatly integrates customer and agile development. Perhaps you can determine whether a product is new by asking customers to name the competition. It was a new product.

Customer Development 203

Customer Development Developer Customer Silicon Valley 203

Steve Blank

DECEMBER 7, 2010

Or more accurately, startups are a temporary organization designed to search for a scalable and repeatable business model.) There are few courses which teach aspiring entrepreneurs the skills (business models, customer and agile development, design thinking, etc.) Deliverable for Jan 18 th : Find a name for your team.

Wiki 312

Wiki Lean Management Business Model 312

Steve Blank

JUNE 8, 2009

Waterfall, Agile, Lean? Building a Chart We realized that if we wrote the names of the vertical markets across the top of the board, and then the startup functions on the left of the board, we could make a chart that could visually compare what differs across the vertical markets. Theme: Digg 3 Column by WP Designer.

Vertical 123

Vertical Silicon Valley RSS Marketing 123

Startup Lessons Learned

AUGUST 3, 2009

MVP, despite the name, is not about creating minimal products. Alan mentions above what I believe is the critical learning element your team needs to gain insight into via the Minimum Viable Product, Compelling Product Offering or other named approach. January 10, 2010 12:57 PM talltodd said. Some caveats right off the bat.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Steve Blank

APRIL 20, 2009

When I read the funny names of these microwaves devices… Backward wave oscillators, TWT’s, Magnetrons…long silent memories came back. An interesting phenomena of the 1920s that illustrates the fragility and cost of vacuum tubes is the “Reflex Receiver&# design methodology.

Silicon Valley 279

Silicon Valley RSS San Francisco Technical Review 279

Startup Lessons Learned

FEBRUARY 7, 2010

Lessons Learned by Eric Ries Sunday, February 7, 2010 Tell your Startup Visa story Ive been promising big Startup Visa -related news on Twitter for a few weeks. If youre a startup investor, and you support the goals of the Startup Visa proposal, wed like you lend your name to our efforts. Soon, I promise. For now, take my word for it.

San Francisco 118

San Francisco DC Startup Lean 118

Startup Lessons Learned

JULY 13, 2009

Lessons Learned by Eric Ries Monday, July 13, 2009 The Principles of Product Development Flow If youve ever wondered why agile or lean development techniques work, The Principles of Product Development Flow: Second Generation Lean Product Development by Donald G. Product development deals in designs, which are fundamentally intangible.

Product Development 153

Product Development Developer San Francisco Product 153

YoungUpstarts

JULY 30, 2015

Back in early 2003, a Dane named Janus Friis and a Swede named Niklas Zennström had an idea for a software application, and founded a business with the help of three Estonian software developers. They set about registering an internet domain name and preparing for the release of a Beta version of their app later that year.

Dominican Republic 100

Dominican Republic Global San Francisco Arizona 100

Startup Lessons Learned

DECEMBER 16, 2009

For those whove heard it, it contains a length discourse on the subject of agile software development and extreme programming, including its weaknesses when applied to startups. As Im pontificating about agile, I see the name Kent Beck in my peripheral vision. Eric Names matter. There is a dark side to naming.

Lean 140

Lean San Francisco Continuous Deployment Startup 140

Startup Lessons Learned

SEPTEMBER 27, 2010

Lessons Learned by Eric Ries Monday, September 27, 2010 Good enough never is (or is it?) This is precisely the dilemma that the doctrine of minimum viable product is designed to solve. Lean manufacturing , agile software development , and Theory of Constraints are all examples of this idea in action. And it’s really hard.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167