Startup Lessons Learned

AUGUST 3, 2009

In a lot of cases, this requires a lot of energy invested in talking to customers or metrics and analytics. Refreshing to finally see lean and agile thinking emerge in product/business-floors and not only in technology. Thanks Eric, great blog! In fact, MVP is quite annoying, because it imposes extra overhead. Thank you.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

SoCal CTO

APRIL 28, 2014

This is something I’ve explored several times already in my blog: Startup Founder Developer Gap Startup CTO or Developer Technical Advisors – Why Every Startup Needs Them Bottom line - for most startups, what they really need is a technical advisor or part-time CTO along with some development resources.

Technical Cofounder 280

Technical Cofounder Developer Fractional CTO CTO Hire 280

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. I hope you take something of value from this blog. Eric, love the blog. Thanks for your professional blog. So thats me, your author.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

NOVEMBER 7, 2008

This is one of the blog we posted about how some company is doing SEO to promote the website. To help find the right keywords, Ive written an article on my blog Web Startup Help that details How to Do Keyword Research for startups. This post has been removed by a blog administrator. link] November 8, 2008 7:13 PM Jason said.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

ConversionXL

NOVEMBER 10, 2020

Have you checked out this blog post, this video, and this infographic? Awareness would then grow as they perused our landing pages, read our blog posts, and filled out a form to download an in-depth white paper. Metrics for this depth are rare and only long-term. The metrics for this level are more concrete and objective.

Agile 139

Agile Social Media Audience Software Review 139

Startup Lessons Learned

NOVEMBER 13, 2008

Because five whys kept turning up a few key metrics that were hard to set static thresholds for, we even had a dynamic prediction algorithm that would make forecasts based on past data, and fire alerts if the metric ever went out of its normal bounds. Wed never heard of five whys, and we had plenty of "agile skeptics" on the team.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

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

OCTOBER 5, 2008

Eventually, I hope to get them on a full agile diet, with TDD, scrums, sprints, pair programming, and more. I went through some of this in bringing agile methodologies to my current firm - except that I am the product manager in question at this case. October 6, 2008 12:17 AM r& said. Expo SF (May.

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

APRIL 25, 2011

It may be hard to remember that there was a time when people in the agile software development community thought Lean Startup was incompatible with agile practices. For readers of this blog, Steve needs no introduction. No BS, no vanity metrics, no launches, no PR. And those are just our keynotes!

San Francisco 146

San Francisco Silicon Valley Lean Agile 146

Startup Lessons Learned

MARCH 25, 2009

Lessons Learned by Eric Ries Wednesday, March 25, 2009 The Lean Startup at Agile Vancouver April 21st A surprising number of respondents in the latest Lessons Learned survey hail from one of the flourishing startup hubs in Canada. In order to reduce my incredible ignorance about other such hubs, Im heading to Vancouver. Thank you so much!)

Agile 60

Agile Lean San Francisco Continuous Deployment 60

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. Thanks for this post, I was going to buy the book anyway after reading Stevens blog but this post definitely made me get it faster (just ordered).

Customer Development 168

Customer Development Developer San Francisco Customer 168

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. Now, this webcast was packed, hundreds of people were logged in.

Lean 140

Lean San Francisco Continuous Deployment Startup 140

Startup Lessons Learned

SEPTEMBER 15, 2008

Focus on the output metrics of that part of the product, and you make the problem a lot more clear. To promote this metrics discipline, we would present the full funnel to our board (and advisers) at the end of every development cycle. Max Levchin of Slide and Paypal has noted that 10% of Slides headcount is devoted to metrics only.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

MARCH 24, 2009

Lessons Learned by Eric Ries Tuesday, March 24, 2009 The metrics and levers of engagement, presentation on Engagement Loops for Facebook Developer Garage SF Ill be presenting a talk at the Facebook Developer Garage SF Wednesday evening. Unfortunately, its easy to lose track of positioning effects when optimizing for a single metric.

Metrics 88

Metrics San Francisco Lean Viral 88

Startup Lessons Learned

SEPTEMBER 2, 2008

We wanted an agile approach that would allow us to build our software architecture as we needed it, without downtime, but also without large amounts of up-front cost. You can also download our presentation, " Just-In-Time Scalability: Agile Methods to Support Massive Growth." Expo SF (May.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

APRIL 9, 2009

Thats the essence of so many of the lean startup techniques Ive evangelized: customer development , the Ideas/Code/Data feedback loop , and the adaptation of agile development to the startup experience. Answering that question is what Im striving to do on this blog (and at future webcasts and workshops ).

San Francisco 132

San Francisco Continuous Deployment Lean Agile 132

Startup Lessons Learned

MARCH 3, 2009

In order to give people the data they need to apply the strategy, we were very open with our company metrics, making all reports generally available and easy to run. When you think a certain feature will give a 50% boost to a given metric, and it only eeks out a 5% boost, you cant spin that as failure. March 5, 2009 8:56 AM Eric said.

Employee 146

Employee San Francisco Lean Software Review 146

Startup Lessons Learned

SEPTEMBER 30, 2008

If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? I would love to see some blog posts on any experiences you have had with set-based design. But along the way, something strange happened. And what about if deployment takes forever? Great piece!

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

TechEmpower

FEBRUARY 13, 2013

Focusing on the metrics that ultimately drive the business, often the bottom line, has provided a reality check, a counter-weight to the desire to consume all new technologies. Besides, more development time means the client can be more agile with functionality and has a greater potential for success.

Guinea 200

Guinea Application Development Ruby Web Development 200

Startup Lessons Learned

FEBRUARY 20, 2009

Sounds very similar to agile development which is the way. Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down? February 21, 2009 7:39 AM Rocky1138 said. Expo SF (May.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

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. Two Ways to Hold Entrepreneurs Accountable Beware of Vanity Metrics For Startups, How Much Process Is Too Much? Start-ups supposedly dont have time for detailed processes and procedures. Speed up or slow down?

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

Startup Lessons Learned

JULY 28, 2010

Lessons Learned by Eric Ries Wednesday, July 28, 2010 Case Study: kaChing, Anatomy of a Pivot (The following guest post is a new experiment for this blog. And if you’re a regular reader of this blog, you may know that IMVU started out as an instant messaging add-on. kaChing has been very active in the Lean Startup movement.

San Francisco 158

San Francisco Lean Continuous Deployment SEC 158

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. This speeds up the Ideas-Code-Data feedback loop.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

SEPTEMBER 10, 2008

I know plenty of people who prefer more advanced source control system, but my belief is that many agile practices diminish the importance of advanced features like branching. Its not that the idea behind them is wrong, but I think agile team-building practices make scheduling per se much less important. Youd better. Expo SF (May.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

FEBRUARY 28, 2009

This builds on a lot of great thinking that has come before, like the agile movements insistence that only the creation of working code counts as progress for a software development team. I used to think that investments in metrics were a form of waste. I used to think that investments in metrics were a form of waste.

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

Startup Lessons Learned

JULY 29, 2009

I hope to show why lean and agile techniques actually reduce the negative impacts of technical debt and increase our ability to take advantage of its positive effects. Yet other agile principles suggest the opposite, as in YAGNI and DoTheSimplestThingThatCouldPossiblyWork. But this blog put into better perspective.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

APRIL 14, 2009

Every board meeting, the metrics of success change. Go on an agile diet quickly. With a product development team that is not shipping, any agile methodology will surface major problems quickly. Time-to-complete-a-sale is not a bad metric for validated learning at this stage. And yet, their investors are frustrated.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

OCTOBER 16, 2013

One good example is the way in which we''ve adjusted the length of different phases of our agile sprints. We don''t follow a set agile methodology, but rather follow a more home-grown, minimal version of various approaches. We have a blog that''s internal-only to capture important stories for prosperity.

Lean 167

Lean Startup Software Engineering Agile 167

Startup Lessons Learned

MARCH 25, 2010

Two Ways to Hold Entrepreneurs Accountable Beware of Vanity Metrics For Startups, How Much Process Is Too Much? Two Ways to Hold Entrepreneurs Accountable Beware of Vanity Metrics For Startups, How Much Process Is Too Much? Read the rest of The Startups Rules of Speed - The Conversation - Harvard Business Review. Expo SF (May.

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Startup Lessons Learned

MAY 31, 2010

Sean Murphy has an excellent and comprehensive roundup of resources about the conference: all of the slides, videos, summaries, notes and write-ups are listed on his blog here. You can read the rest of his posts on his blog : Introduction , Part 1 , Part 2.) All video from the conference is available for free at Justin.tv

San Francisco 133

San Francisco Lean Technical Review Software Review 133

Startup Lessons Learned

SEPTEMBER 2, 2008

Labels: agile , listening to customers 3comments: hauteroute said. Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down? Split-test experiments that go on forever?

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Steve Blank

OCTOBER 24, 2017

It’s hard to imagine, but in the 20th century there were no startup blogs or books on startups to read, and business schools (the only places teaching entrepreneurship) believed the best thing they could teach startups was how to write a business plan. To be fair there wasn’t much of an alternative.

Founder 281

Founder Technical Review CTO Hire IPO 281

Steve Blank

APRIL 9, 2009

But what I wanted was an agile marketing team capable of operating independently without day-to-day direction. And the results weren’t the traditional PR metrics of number of articles or inches of ink. We were constantly creating metrics to see the effects of different PR messages, channels and audiences on end-user purchases.

Silicon Valley 272

Silicon Valley Technical Review RSS PR 272

Startup Lessons Learned

SEPTEMBER 13, 2008

July 20, 2009 1: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.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Startup Lessons Learned

AUGUST 26, 2009

Im always excited to see how these ideas are expressed by entrepreneurs in their own words: petewarden : Another blog post, this one on the @ericries Lean Startup Workshop I attended: [link] #leanstartup tmarkiewicz : Notes from the Lean Startup Dinner with @ericries [link] #leanstartup And I can never resist sharing some positive feedback.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

Startup Lessons Learned

AUGUST 24, 2009

Despite all the energy invested in talking to authors about the size of their platform, very few gatekeepers have a rigorous set of metrics for measuring it. My blog has over 14000 subscribers, for example. And how could they possibly review a blog? Is that a lot? What is the right revenue model?

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

JANUARY 12, 2010

Beyond my own efforts on this blog ( and more ), there is now an amazing variety of resources for lean startup practitioners. When I first started blogging, the startup blogging mafia immediately came to meet me and find out who I was: Dave McClure , Andrew Chen , Sean Ellis and Venture Hacks. Have a favorite who I overlooked?

Lean 146

Lean San Francisco Wiki Startup 146