Steve Blank

JULY 7, 2015

My guests on Bay Area Ventures on Wharton Business Radio on Sirius XM Channel 111 were: Eric Ries , entrepreneur and author of the New York Times bestseller, The Lean Startup. Eric was the very first practitioner of my Customer Development methodology which became the core of the the Lean methodology.

Lean 120

Lean Technical Cofounder Silicon Valley Channel 120

Startup Lessons Learned

SEPTEMBER 15, 2008

Lessons Learned by Eric Ries Monday, September 8, 2008 The lean startup Ive been thinking for some time about a term that could encapsulate trends that are changing the startup landscape. After some trial and error, Ive settled on the Lean Startup. I like the term because of two connotations: Lean in the sense of low-burn.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

Steve Blank

DECEMBER 20, 2011

63 scientists and engineers in 21 teams made 2,000 customer calls in 8 weeks , turning laboratory ideas into formidable startups. 19 of the 21 teams are moving forward in commercializing their technology. We’ve been reading your blog about your Lean Launchpad class.” Over the last two months the U.S. Our country needs you.”

Incubator 301

Incubator Government Silicon Valley Lean 301

Startup Lessons Learned

AUGUST 31, 2015

The following is a guest post by Kirsten Cluthe and Ritika Puri from The Lean Startup Conference team Wondering what’s new in the Lean Startup community? Every year, our team conducts more than 500 customer development calls to understand what challenges the community is facing. Here are some of our favorites: 1.

Lean 60

Lean United States Fractional CTO Startup 60

Startup Professionals Musings

APRIL 28, 2014

VCs and Angel investors like to see a startup that is running lean and mean, with no more than three or four of the conventional C-level or VP titles. The most common ones I see and salute are CEO, CFO, and CTO. Chief Sales Officer (VP Sales). Chief Brand Officer. Chief Risk Officer.

CTO Hire 252

CTO Hire Fractional CTO Angel Investor Public Relations 252

Startup Professionals Musings

FEBRUARY 22, 2013

VCs and Angel investors like to see a startup that is running lean and mean, with no more than three or four of the conventional C-level or VP titles. The most common ones I see and salute are CEO, CFO, and CTO. Chief Sales Officer (VP Sales). Chief Brand Officer. Chief Risk Officer.

CTO Hire 244

CTO Hire Fractional CTO Startup Angel Investor 244

Gust

APRIL 20, 2014

VCs and Angel investors like to see a startup that is running lean and mean, with no more than three or four of the conventional C-level or VP titles. The most common ones I see and salute are CEO, CFO, and CTO. Chief Sales Officer (VP Sales). Chief Brand Officer. Chief Risk Officer.

CTO Hire 171

CTO Hire Fractional CTO Angel Investor Public Relations 171

Startup Professionals Musings

DECEMBER 1, 2010

VCs and angel investors like to see a startup that is running lean and mean, with no more than three or four of the conventional C-level or VP titles. The most common ones I see and salute are CEO, CFO, and CTO. Chief Sales Officer (VP Sales). Chief Brand Officer. Chief Risk Officer.

CTO Hire 227

CTO Hire Fractional CTO Startup Angel Investor 227

Startup Lessons Learned

OCTOBER 4, 2008

Maybe youd like to start with The lean startup , How to listen to customers , or What does a startup CTO actually do? ) He previously co-founded and served as Chief Technology Officer of IMVU. Eventually, I came to summarize these themes with the phrase " the lean startup." So thats me, your author.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Steve Blank

JUNE 6, 2016

— Ashok has taken a Lean approach to innovation at Verizon: Within a couple of weeks of joining Verizon, they said, “Before you learn a lot about the company, write down what you think we should do.” I presented them to our chief product officer and our CTO. Filed under: Customer Development.

Silicon Valley 120

Silicon Valley Entrepreneur Fractional CTO Analytics 120

Startup Lessons Learned

SEPTEMBER 14, 2008

Lessons Learned by Eric Ries Sunday, September 14, 2008 How to listen to customers, and not just the loud people Frequency is more important than talking to the "right" customers, especially early on. Youll know when the person youre talking to is not a potential customer - they just wont understand what youre saying.

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131

Startup Lessons Learned

JUNE 22, 2009

Lessons Learned by Eric Ries Monday, June 22, 2009 Pivot, dont jump to a new vision In a lean startup , instead of being organized around traditional functional departments, we use a cross-functional problem team and solution team. Each has its own iterative process: customer development and agile development respectively.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

Startup Lessons Learned

JULY 28, 2010

kaChing has been very active in the Lean Startup movement. With case studies like this, we aim to illustrate specific Lean Startup techniques through the stories of current practitioners. in fact only five people converted into paying customers. The site has about 700 active paying customers. Which is a nice story.

San Francisco 158

San Francisco Lean Continuous Deployment SEC 158

Steve Blank

OCTOBER 8, 2009

Lessons to Learn By the time I joined Ardent I thought I was an experienced marketer, but I’ll never forget my first real lesson in what it meant to understand customers and product/market fit. Get Out of My Company At the top of his lungs he screamed, “You don’t know a damn thing about what these customers need!

Silicon Valley 271

Silicon Valley RSS Customer Development California 271

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 28, 2008

Lessons Learned by Eric Ries Sunday, September 28, 2008 The lean startup comes to Stanford Im going to be talking about lean startups (and the IMVU case in particular) three times in the next two weeks at Stanford. My suggestion: take a much-loved feature and split-test it with some new customers to see if it really makes a difference.

Lean 68

Lean San Francisco Continuous Deployment Startup 68

Startup Lessons Learned

SEPTEMBER 22, 2008

The law of large numbers (of customers) says you cant help but make at least some money - your valuation is determined by how well you monetize the tidal wave of growth. Paid - if your product monetizes customers better than your competitors, you have the opportunity to use your lifetime value advantage to drive growth.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

Startup Lessons Learned

SEPTEMBER 13, 2008

Lessons Learned by Eric Ries Saturday, September 13, 2008 SEM on five dollars a day How do you build a new product with constant customer feedback while simultaneously staying under the radar? Slowly, over time, we optimized (or eliminated) each step in the process of becoming a customer by giving us money. SEM is a simple idea.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Startup Lessons Learned

SEPTEMBER 2, 2008

After all, the worst kind of waste in software development is code to support a use case that never materializes. Scalable systems are no exception - if your assumptions about how many customers youll have, or how they will behave are just a little bit wrong, you can wind up with a massive amount of wasted code. Expo SF (May. .

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Steve Blank

OCTOBER 5, 2009

Oh, and since it was not code compatible with anything, we were going to have to port all the key scientific applications our customers needed (as soon as we figured out who they were.) Personal supercomputer s meant yet again learning something completely new; new computer architectures, new applications and customers, new markets.

North Carolina 125

North Carolina Silicon Valley Fractional VPE Part-Time VPE 125

Startup Lessons Learned

MAY 7, 2009

As the product matured, they were able to ratchet up the quality to prevent regression on features that had been truly embraced by their customers. On the negative side, we got a visceral feel for the kinds of changes that could really harm customers, like commits that take the whole site down. And that was not a lot of fun.

Continuous Deployment 131

Continuous Deployment San Francisco Software Review Lean 131

Steve Blank

MARCH 5, 2015

On our first show, Monday March 9 th 4-6pm Pacific Time join me, as I chat with Alexander Osterwalder – inventor of the Business Model Canvas , and Oren Jacob, ex-CTO of Pixar and now CEO of ToyTalk on Sirius XM Radio Channel 111. On April 27 th , on my next program, my guest will be Eric Ries the author of the Lean Startup.

Channel 120

Channel Venture Capital Lean Business Model 120

Startup Lessons Learned

SEPTEMBER 2, 2008

Labels: agile , listening to customers 3comments: hauteroute said. Wouldn't it make more sense to Learn (customer discovery) then proceed to ideas,code, data, implement and measure? The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Great points Eric. Expo SF (May. .

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

DECEMBER 7, 2008

This is one of the bedrock practices of any lean startup , and so its a common piece of advice I give out. Hire a CTO or VP Engineering. A really good technology executive can notice problems like the ones Im talking about today and address them proactively. However, its particularly helpful in this situation. Guess what?

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

The Next Web

JANUARY 27, 2013

Four books helped me out a lot over the last few years: Four Steps to the Epiphany by Steve Blank, Running Lean by Ash Maurya, The Four Hour Workweek by Timothy Ferris and Rework by Jason Fried & David Heinemeier Hansson. So far, they’ve passed the legal department of our customers without any problems. Sean Connery, The Rock.

Netherlands 159

Netherlands Technical Review Software Review Cofounder 159

Startup Lessons Learned

SEPTEMBER 12, 2008

0comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) Expo SF (May. . Expo SF (May.

Audience 119

Audience San Francisco Continuous Deployment Lean 119

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. . Expo SF (May.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Lessons Learned

SEPTEMBER 10, 2008

Plus, as product development teams in lean startups become adept at learning-and-discovery (as opposed to just executing to spec), its clear that some bugs shouldnt be fixed. You can keep the team focused on customer-centric results, rather than conformance to spec. There are no customers for that feature, UI issues or no.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Steve Blank

JULY 30, 2009

Your Customers are Not Who You Think For years I thought this “million unit chip sale by accident&# was a “one-off&# funny story. That is until I saw that in startup after startup customers come from places you don’t plan on. Your board nods sagely at your target customer list.

Silicon Valley 131

Silicon Valley RSS California Customer Development 131

Startup Lessons Learned

SEPTEMBER 5, 2008

October 13, 2008 9:44 PM Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) Expo SF (May. . Expo SF (May.

Open Source 107

Open Source San Francisco Continuous Deployment Lean 107

Rob Go

SEPTEMBER 9, 2013

link] – Not a meetup, but a great mentorship program started by serial CTO Sean Lindsay. Lean Startup Circle Boston – Meetup dedicated to the lean startup and customer development methodology. Custommade – Marketplace for Customer Products (NextView Portfolio Company). Coworking Spaces and Accelerators.

Boston 71

Boston Technical Review Community Cofounder 71

Startup Lessons Learned

SEPTEMBER 18, 2008

When you have an infinitesimal number of customers, it can be embarrassing. But as long as your ego can take it, there are huge advantages to having a small number of customers. Most importantly, you can get to know those few customers in a way that people with zillions of customers cant. You can even meet the friend.

San Francisco 133

San Francisco Lean Continuous Deployment DC 133

Startup Lessons Learned

SEPTEMBER 2, 2008

Labels: continuous deployment 0comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) Expo SF (May.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

SEPTEMBER 18, 2008

But from a customer experience point of view, Im not yet sold. Even with only a few months of development, third parties have crammed every single category in the store full of apps. Not many customers ever browse the app directory or search for specific apps - they dont have to, they find out about apps by being invited by a friend.

Distribution 74

Distribution San Francisco Lean Continuous Deployment 74

Startup Lessons Learned

JANUARY 12, 2009

In my role as a CTO, Ive always tried to choose the right tool for the right job. I am CTO of a SaaS vendor, and we use PHP. PHP does it "OK" but theres really no excuse not to be using J2EE (either full on, or customized) if youre going that way. The Lean Startup Intensive is tomorrow at Web 2.0. I certainly dont.

PHP 166

PHP Software Review Ruby San Francisco 166

Up and Running

MAY 23, 2016

Step 1: Start with a lean plan. It’s the fastest way to get your idea onto paper, and it’s the very first step in the lean planning process, which is much easier and more iterative than traditional business planning methods. Also, make a bullet list of the marketing activities that will drive customers to your door.

Software Review 74

Software Review Software Delaware Forecast 74

Startup Lessons Learned

SEPTEMBER 1, 2008

Labels: Test-driven development 0comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?)

San Francisco 68

San Francisco Developer Continuous Deployment DC 68