Startup Lessons Learned

OCTOBER 4, 2008

He previously co-founded and served as Chief Technology Officer of IMVU. In 2007, BusinessWeek named Ries one of the Best Young Entrepreneurs of Tech and in 2009 he was honored with a TechFellow award in the category of Engineering Leadership. While an undergraduate at Yale Unviersity, he co-founded Catalyst Recruiting.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Austin Startup

SEPTEMBER 18, 2017

They adopt, measure, and manage key product performance metrics. They will manage the steps necessary to identify, select, and integrate your software and IT vendors, including third party product dependencies, email, network, wiki, intranet, project management, and telecommunications. Autonomy to self-manage.

Fractional CTO 54

Fractional CTO CTO Hire CTO Technical Review 54

Startup Lessons Learned

JANUARY 12, 2010

The Lean Startup Wiki (hosted by long-time lean startup pbWorks) contains a number of resources, including links to case studies , meetups, tools , and people who have volunteered to help. Its a wiki, feel free to consume and enhance it. Its a wiki, feel free to consume and enhance it. April 23, 2010 in San Francisco.

Lean 146

Lean San Francisco Wiki Startup 146

Startup Lessons Learned

SEPTEMBER 11, 2009

Lessons Learned by Eric Ries Friday, September 11, 2009 The cardinal sin of community management Once you have a product launched, you will the face the joys – and the despair – of a community that grows up around it. Nothing worked, until we finally had one of our community managers start talking to real customers on the phone.

Community 158

Community Management Lean Software Review 158

Startup Lessons Learned

SEPTEMBER 15, 2008

See Customer Development Engineering for my first stab at articulating the theory involved) Ferocious customer-centric rapid iteration, as exemplified by the Customer Development process. Very useful perspective - as a first-time CEO managing a small startup, these ideas are timely and thought-provoking. Less is more.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

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 initially gravitated to the CTO title, and not VP of Engineering.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

APRIL 4, 2010

► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. Amazing lean startup resources Is Entrepreneurship a Management Science? No departments The Five Whys for Startups (for Harvard Business R.

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

Startup Lessons Learned

JULY 28, 2010

To shed some light, I talked with kaChing , a destination that enables individual investors to find outstanding money managers to manage their money. kaChing launched a virtual portfolio management game on Facebook in January 2008 and a similar version shortly thereafter on kaChing.com.

San Francisco 158

San Francisco Lean Continuous Deployment SEC 158

Startup Lessons Learned

JUNE 17, 2010

They are leaders, visionaries, founders and managers having tremendous success. I was an engineer on the engineering team. For one, the engineers consider the artists stupid; the artists consider the engineers arrogant. Yet talent organized improperly can lead to failure. The meeting was tense.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

JUNE 2, 2010

As start-ups scale, this agility will be lost unless the founders maintain a consistent investment in that discipline. You can view previous essays in this series here: Is Entrepreneurship a Management Science? As start-ups scale, this agility will be lost unless the founders maintain a consistent investment in that discipline.

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

A Smart Bear: Startups and Marketing for Geeks

OCTOBER 24, 2011

My co-hosts were Bob Walsh and Patrick Foley , hosts of the well-known Startup Success Podcast. How cofounders can collaborate without going crazy. It helps you manage, at first a checking account, is where the name came from, through text messaging. It’s Episode 3 my little “ Loveline for startups. Ryan: C-H-E-X-T.

Cofounder 208

Cofounder Technical Review Software Review Differentiation 208

www.chubbybrain.com

SEPTEMBER 28, 2011

After a thorough analysis of those 32 start-up post-mortems, we have determined the common reasons founders gave to compile this list of the top 20 ways to have your startup fail. If getting VC or angel money is one of the ways that will help you avoid failure, why not check out the free Funding Recommendation Engine here ? #20

Cofounder 89

Cofounder Startup Technical Cofounder CTO Hire 89

steveblank.com

JULY 8, 2011

signup, upgrade, trial pricing Zuora – online subscription management FeeFighters – find the cheapest credit card processors HealPay – Collections made easy Customer Support Tender – support, knowledgebase tool for your site GetSatisfaction - conversations between companies / customers.

Software Review 110

Software Review Startup Silicon Valley Analytics 110

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 work hard to keep their house in order at all times, and there are strict rules and guidelines in place that prevent engineers and teams from doing things their own way.

Agile 76

Agile San Francisco Software Review Continuous Deployment 76

Startup Lessons Learned

JUNE 22, 2009

Some startups fail because the founders cant have this conversation - they either blow up when they try, or they fail to change because they are afraid of conflict. Although I wish I could take credit for these pivots, the reality is that they were not caused by my singular insight or that of my other co-founders.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

Startup Lessons Learned

AUGUST 2, 2008

Its to everyones advantage to let the world think the founders thought of everything. I say this as a founder: the contribution of founders is always overestimated. The danger here is that new founders, looking at existing founders, will think that theyre supermen that one couldnt possibly equal oneself.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

Startup Lessons Learned

AUGUST 3, 2009

We have to manage to learn something from our first product iteration. I do this as a core part of the Product Management process I use at all startups. Amazing lean startup resources Is Entrepreneurship a Management Science? In fact, MVP is quite annoying, because it imposes extra overhead. Great Post - could not agree more.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Startup Lessons Learned

NOVEMBER 29, 2008

Finding great engineers is hard; figuring out whos good is even harder. Balancing competing objectives is a recurring theme on this blog - its the central challenge of all management decisions. For software engineers, I think this absolutely has to be a programming problem solved on a whiteboard. Communication.

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

MARCH 16, 2009

In a startup, rather than think of ourselves as having a marketing department and an engineering department, I now believe its better to think of ourselves as focusing our energies on unknown problems and unknown solutions. Both Scrum and XP had a role which you could happily call by the modern title "Product Manager".

Agile 111

Agile Customer Development Developer San Francisco 111

Startup Lessons Learned

SEPTEMBER 22, 2008

I break the answer to that question down into three engines: Viral - this is the business model identified in the presentation as "Get Users." Thats why eBay advertises on search engines, and Facebook doesnt. Labels: search engine marketing 0comments: New comments are not allowed. Thats where Id like to pick up the discussion.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

Startup Lessons Learned

JULY 2, 2009

The person running the meeting does not have to be a manager or executive. You can almost hear a manager now: “sure, if you want me to spend the next six weeks setting this up, just let me know. Even in that case, we can ask the manager involved to simply spend the first hour of the six-week ideal solution.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

SEPTEMBER 13, 2008

Trying to answer that question at IMVU led me to discover Google AdWords and the world of search engine marketing. You declare how much someone clicking an advertisement is worth to you, and then the search engine does its best to get you as many clicks as it can at that price. Labels: search engine marketing 4comments: Tauya said.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Startup Lessons Learned

FEBRUARY 20, 2009

Its had tremendous impact in many areas: continuous deployment , just-in-time scalability , and even search engine marketing , to name a few. Every time an engineer checks in code, they are batching up a certain amount of work. Similar results apply in product management, design, testing, and even operations.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

SEPTEMBER 2, 2008

► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. Amazing lean startup resources Is Entrepreneurship a Management Science? No departments The Five Whys for Startups (for Harvard Business R.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

JULY 3, 2009

The same has been true of an unfortunate number of startups, they manage to generate a lot of hype, raise a lot of money, and sometimes make some of their investors, employees, or founders rich. Nothing is more demoralizing to an engineering team. Ive been there: is it me or my cofounder thats crazy?

Lean 60

Lean San Francisco Continuous Deployment Cofounder 60

Startup Lessons Learned

MARCH 25, 2010

You can view previous essays in this series here: Is Entrepreneurship a Management Science? You can view previous essays in this series here: Is Entrepreneurship a Management Science? Amazing lean startup resources Is Entrepreneurship a Management Science? This is the speed-up-or-slow-down moment. Bring your questions.

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Startup Lessons Learned

APRIL 9, 2009

No engineering team. But where it makes sense, that team may also include engineers building new experiments or prototypes to try with customers. And instead of design, engineering, QA, and operations we have a solution team implementing a startup-centric version of agile development. You need a problem team and a solution team."

San Francisco 132

San Francisco Continuous Deployment Lean Agile 132

Startup Lessons Learned

JANUARY 28, 2009

I was told they werent sure, because all of their engineers were currently busy refactoring. The engineering team has decided its reached a breaking point, and is taking several weeks to bring it up to modern standards, including unit tests, getting started with continuous integration , and a new MVC architecture. Practice five whys.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79

Startup Lessons Learned

JULY 13, 2009

For those who hunger for a rigorous approach to managing product development, Donald Reinertsens book is epic. If we showed the Toyota Production System to an Internet protocol engineer, it is likely that he would remark, "That is a tail-dropping FIFO queue. Managing timelines instead of queues. Reinertsen is the book for you.

Product Development 153

Product Development Developer San Francisco Product 153

Startup Lessons Learned

OCTOBER 28, 2008

whos on the engineering team? Most important slide: demo (if the product solves an obvious problem), engineering resumes (if the product is nearly impossible to build), " day in the life of a customer " (if neither of the above) Breakthrough technology Key questions: who owns the patents? how do you know anyone would want it?

San Francisco 128

San Francisco Lean Continuous Deployment DC 128

Startup Lessons Learned

SEPTEMBER 10, 2008

► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. Amazing lean startup resources Is Entrepreneurship a Management Science? No departments The Five Whys for Startups (for Harvard Business R.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Lessons Learned

NOVEMBER 8, 2008

When creating a new market, expect to spend as long as two years before you manage to get traction with early customers, but enjoy the utter lack of competition. Instead, we do everything possible to validate the founders belief. What kind of market are you in? We dont just abandon the vision of the company at every turn.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

SEPTEMBER 12, 2008

► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. Amazing lean startup resources Is Entrepreneurship a Management Science? No departments The Five Whys for Startups (for Harvard Business R.

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Startup Lessons Learned

NOVEMBER 13, 2008

Its why, at my previous job, we were able to get a new engineer completely productive on their first day. Most engineers would ship code to production on their first day. Let me show you what this looked like after a few years of practicing five whys in the operations and engineering teams at IMVU.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

SEPTEMBER 14, 2008

Later, when the company was much larger, we had everyone on our engineering team agree to sit in on one usability test every month. It wasnt a huge time commitment, but it meant that every engineer was getting regular contact with an actual customer, which was invaluable. Case Study: Continuous deployment makes releases n.

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131

Startup Lessons Learned

JANUARY 18, 2010

Ash Maurya is the founder of WiredReach , a bootstrapped startup that he has been running for seven years. If youre interested in contributing a case study for publication here, consider getting started by adding it to the Lean Startup Wiki case study section. This case presents a further complication: desktop software.

Continuous Deployment 151

Continuous Deployment San Francisco Lean Wiki 151

Startup Lessons Learned

MARCH 22, 2010

For example, over 25% of the technology companies founded between 1995-2005 had a key immigrant founder. Similarly, 24% of all the patents filed in the US in 2006 had a foreign resident as inventor or co-inventor. For example, over 25% of the technology companies founded between 1995-2005 had a key immigrant founder.

San Francisco 121

San Francisco Indiana Lean Startup 121