Steve Blank

SEPTEMBER 16, 2014

For example, if you’re building a mobile app, then the key activities are: app software development, user interface design and demand creation skills. For medical devices it might be mechanical engineering, clinical trials, regulatory approval, freedom to operate (intellectual property) and figuring out a reimbursement strategy.

Cofounder 335

Cofounder Founder Intellectual Property Business Model 335

Steve Blank

JUNE 26, 2014

We’re changing the order in which we teach the business model canvas and customer development to better-fit therapeutics, diagnostics and medical devices. “Customer Development” to test the hypotheses outside the building and. Teams talk to 10-15 customers a week and make a minimum of 100 customer visits.

Intellectual Property 287

Intellectual Property Lean IP Open Source 287

Startup Lessons Learned

SEPTEMBER 15, 2008

But by taking advantage of open source, agile software, and iterative development, lean startups can operate with much less waste. I am heavily indebted to earlier theorists, and highly recommend the books Lean Thinking and Lean Software Development. The lean startup is an application of Lean Thinking.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

Startup Lessons Learned

NOVEMBER 4, 2008

Boyd emphasized the importance of agility in combat: "the key to victory is to be able to create situations wherein one can make appropriate decisions more quickly than ones opponent." Agile software development. Agile allows companies to build higher quality software faster. Customer development.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

JUNE 15, 2009

One large source of waste in development is “double-checking.&# For example, imagine a team operating in a traditional waterfall development system, without continuous deployment, test-driven development, or continuous integration. When a developer wants to check-in code, this is a very scary moment.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

DECEMBER 6, 2008

When youve mastered that, consider adding operations, customer service, marketing, product management, business development - the idea is that when the team needs to get approval or support from another department, they already have an "insider" who can make it happen. Keep the team size small, maybe just two or three people.

San Francisco 74

San Francisco SCRUM Lean Continuous Deployment 74

Startup Lessons Learned

FEBRUARY 22, 2010

I’ve seen many times what happens when a single department get’s holed-up in its own space, like the terrifying “ operations cave.&# Even if men have an innate advantage at software development, the gap would have to be massive in order to explain why startup after startup has an all-male team. Expo SF (May.

San Francisco 167

San Francisco Lean Sweden Continuous Deployment 167