Startup Lessons Learned

MARCH 25, 2010

for Harvard Business Review) Over at Harvard Business Review, Ive been building up a series designed to introduce the Lean Startup methodology to a business-focused audience. This is the first post that moves into making specific process recommendations for product development. Labels: product development Speed up or slow down?

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

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.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Lessons Learned

APRIL 4, 2010

Kent is a significant figure in the field of software development. To his credit are Extreme Programming , jUnit, patterns, TDD , the list goes on. Kent is a significant figure in the field of software development. To his credit are Extreme Programming , jUnit, patterns, TDD , the list goes on.

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

Startup Lessons Learned

SEPTEMBER 30, 2008

So what does CTO mean, besides just "technical founder who really cant manage anyone?" I always assumed I wouldnt manage anybody. Being a manager didnt sound fun - deep down, who really wants to be held accountable for other peoples actions? So I wound up learning the discipline of managing other people. I dont think so.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

David Teten

SEPTEMBER 23, 2017

A major angel group used Influitive , an advocate management tool, to track, activate and motivate their members. Meyler Capital is taking the analytical rigor of modern internet marketing and applying it to fund marketing. 4) Manage deal flow. 2) Raise capital. Pitchbot.vc 3) Originate investments.

Private Equity 60

Private Equity Venture Capital Equity Technical Review 60

Up and Running

MARCH 21, 2018

Everybody and their mom uses the internet to discover new brands, influencers and ultimately to buy new products and services. If you want to compete with them, you’re going to have to develop a reputation and a strong web presence yourself. Even more so than pricing, reviews and location proximity. Custom development.

Entrepreneur 107

Entrepreneur Technical Review Hosting SEO 107

YoungUpstarts

OCTOBER 24, 2012

Instead, buyers are checking out product and service information in their own way, often through the Internet, their social network, or just plain word-of-mouth or customer reviews. He was building a better enterprise software product, and to get the word out, he organized ‘City Tour’ events and neighborhood ‘street teams.’

Marketing 234

Marketing Software Review Technical Review Social Network 234

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. The batch size is the unit at which work-products move between stages in a development process. For software, the easiest batch to see is code.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

JUNE 15, 2009

Of all the tactics I have advocated as part of the lean startup , none has provoked as many extreme reactions as continuous deployment , a process that allows companies to release software in minutes instead of days, weeks, or months. 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

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 same might be said of good software. Here we have the beginnings of a theory of design for software.

Software Review 87

Software Review Design Software San Francisco 87

YoungUpstarts

OCTOBER 12, 2012

The message is clear: Despite their propensity for splashing the details of their lives all over the Internet, people balk at having that information used to sell them what they may not want. A new firm, Zuberance, makes it easy and enjoyable for a company’s loyal customers to advocate for it on their social media platform of choice.

Social Media 164

Social Media Media Marketing Software Review 164

Startup Lessons Learned

NOVEMBER 6, 2008

Steveys Blog Rants: Good Agile, Bad Agile : "Google is an exceptionally disciplined company, from a software-engineering perspective. They take things like unit testing, design documents and code reviews more seriously than any other company Ive even heard about. Three concepts I found particularly helpful: Process = discipline.

Agile 76

Agile San Francisco Software Review Continuous Deployment 76

Startup Lessons Learned

JULY 29, 2009

But there is more to technical debt than just the interest payments that come due. Startups especially can benefit by using technical debt to experiment, invest in process, and increase their product development leverage. In particular, try these three things: Invest in technical debts that may never come due.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

SVPG

OCTOBER 14, 2014

” We were big practitioners of what we now call Customer Development, and our customer was typically the IT organization of large companies. I remember being immediately struck by how different we designed and built technology, versus how our customers did. In any case, the Internet happened. 4) Staffing.

Product 91

Product Technical Review Engineer CTO Hire 91

Startup Lessons Learned

AUGUST 2, 2008

Your natural tendency when an investor says yes will be to relax and go back to writing code. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Amazing lean startup resources Is Entrepreneurship a Management Science? Case Study: Continuous deployment makes releases n.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

Steve Blank

APRIL 2, 2009

Since no benchmarks existed, we enlisted our engineering department in a serious software development effort and wrote our own. And we made sure that instead of some artificial numbers, the benchmarks truly measured performance on these four key applications our customers told us were important.

Silicon Valley 127

Silicon Valley Technical Review RSS Software Review 127

Steve Blank

SEPTEMBER 14, 2009

Venture Capitalists on your board developed the expertise to get your firm public as soon as possible using whatever it took including hype, spin, expand, and grab market share because the sooner you got your billion dollar market cap, the sooner the VC firm could sell their shares and distribute their profits.

Silicon Valley 235

Silicon Valley IPO Technical Review Venture Capital 235

Startup Lessons Learned

MAY 31, 2010

And a special thanks is due to all of our presenters, panelists, and mentors. When I first encountered customer development , it was considered pure lunacy by mainstream entrepreneurs and VCs. Kent Beck is deservedly famous for his many contributions in the software industry. We all owe him our thanks for persevering.

San Francisco 133

San Francisco Lean Technical Review Software Review 133

Startup Lessons Learned

JUNE 17, 2010

They are leaders, visionaries, founders and managers having tremendous success. 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. I was an engineer on the engineering team.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

SEPTEMBER 15, 2008

I had the opportunity to pioneer this approach to funnel analysis at IMVU, where it became a core part of our customer development process. To promote this metrics discipline, we would present the full funnel to our board (and advisers) at the end of every development cycle. Check your assumptions, what went wrong?

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

FEBRUARY 22, 2009

See Paul Grahams Why Nerds are Unpopular to learn more) Take a look at this article on a programming Q&A site: How old are you, and how old were you when you started coding? We also learned that law is code , and that leadership was needed to build thriving communities in a digital age. Can I send you a review copy?

Programming 143

Programming San Francisco Lean Continuous Deployment 143

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. This shift allowed us to crank out working software quickly as a service. It was a disaster.

Lean 60

Lean San Francisco Continuous Deployment Software Review 60

ConversionXL

JANUARY 31, 2014

note: If you’re a startup, you’ll want to use customer development questions for your page to resonate with future traffic). Message Match] Project Management Software. Do This: Use customer development techniques found in this post to build a profile of your ideal buyer personas. image source.

Analytics 134

Analytics Video Matching Conversion 134

Startup Lessons Learned

AUGUST 26, 2009

And do your customer development. Im also excited to share two long-form reviews from actual attendees. When they could hear the customers complaints in their own voice, it became clear when it was time to up the quality level. You can learn more about that by reading The engineering managers lament.)

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

Rob Go

SEPTEMBER 9, 2013

MITX : Non-profit trade association hosting many events focused on digital marketing and internet business. Lean Startup Circle Boston – Meetup dedicated to the lean startup and customer development methodology. Raizlabs – Mobile Development. Intrepid – Mobile development. Walter Frick - Harvard Business Review.

Boston 71

Boston Technical Review Community Cofounder 71

Startup Lessons Learned

FEBRUARY 11, 2009

Lessons Learned by Eric Ries Wednesday, February 11, 2009 The free software hiring advantage This is one of those startup tips Im a little reluctant to share, because its been such a powerful source of competitive advantage in the companies Ive worked with. Especially for a startup, not taking maximum advantage of free software is crazy.

Software Review 68

Software Review Software Hiring San Francisco 68

Startup Lessons Learned

AUGUST 24, 2009

In the old days, the brand manager of a consumer packaged goods product had to spend energy inferring the effectiveness of their television ads through a combination of trailing indicators (like market share) or time-consuming market research. When I reviewed a recent product development book, it immediately shot up to Amazon sales rank 300.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

NOVEMBER 13, 2008

A new bit of code contained an infinite loop! why did that code get written? 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. Most engineers would ship code to production on their first day.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Steve Blank

APRIL 5, 2017

I was having coffee with the CEO of a new startup, listening to her puzzle through how to communicate to potential customers. She was an academic on leave from Stanford now selling SAAS software to large companies, but was being inundated with marketing communications advice. “My influencers”) and how they manage them (e.g.

Marketing 316

Marketing Audience Technical Review PR 316

Startup Lessons Learned

DECEMBER 8, 2008

Integration risk is the term I use to describe the costs of having code sitting on some, but not all, developers machines. It happens whenever youre writing code on your own machine, or you have a team working on a branch. It also happens whenever you have code that is checked-in, but not yet deployed anywhere.

Software Review 136

Software Review San Francisco Lean Continuous Deployment 136

www.ashmaurya.com

AUGUST 29, 2012

Robert has been working in software since 2005. You can learn more about his approach to developing customer relationships in his new book Cold Calling Early Customers. The most common reason I send it is because I get in a rush due to something exciting about the opportunity. He is a Ph.D. It rarely pans out.

Email 52

Email Customer Tennessee Software Review 52

SoCal CTO

DECEMBER 1, 2010

The United States is now a debtor nation to China and that the bill is about to come due. Equity-Only CTO and Equity-Only Developers - SoCal CTO , November 1, 2010 I had a recent email dialog with the founder of a company looking for a CTO for their startup. These are probably the two sites where I've posted the most reviews.

Technical Review 175

Technical Review Technology Product CTO Hire 175

Startup Lessons Learned

DECEMBER 7, 2008

In a few cases, they are clearly smart people in a bad situation, and Ive written about their pain in The product managers lament and The engineering managers lament. When I want to know about some concurrency issues between services in his cluster, he doesnt blink an eye when I suggest we get the source code and take a look.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

FEBRUARY 10, 2009

Our code pushes take another six minutes. Since these two steps are pipelined that means at peak we’re pushing a new revision of the code to the website every nine minutes. On average we deploy new code fifty times a day. Code reviews and pairing Great practices. Throwing out a lot of code.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

news.ycombinator.com

SEPTEMBER 16, 2011

Anyway, the way to manage that is still to execute better. The reason feedback - specifically from actual customers - is usually chosen is because it is more on the science side than the art side, but I surely cant knock those people and teams that can deliver product excellence due to vision, luck or art. -- arrel 215 days ago | link.

Stealth 41

Stealth Technical Review Startup Software Review 41

Startup Lessons Learned

MARCH 4, 2009

It connects to the internet to automatically download the necessary codes. Heres a representative view from an actual Amazon customer review : We all know how to operate our own entertainment center, but what happens when you have to explain it to your babysitter, mother-in-law, or your wife? They want to do activities.

San Francisco 68

San Francisco Lean Continuous Deployment DC 68

Startup Lessons Learned

MAY 7, 2009

Getting features and fixes into hands of users was the greatest priority - a test environment would just get in the way and slow down the validation coming from having code running in production. 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.

San Francisco 131

San Francisco Continuous Deployment Software Review Lean 131