This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
Continuous DeploymentConversionProduct Development
In the last few years Agile and “ContinuousDeployment” has replaced Waterfall and transformed how companies big and small build products. Agile is a tremendous advance in reducing time, money and wasted productdevelopment effort – and in having products better match customer needs.
And this year, we’re going to talk not just about business and productdevelopment, but we’ll be exploring one of the Lean Starutp movements next big frontiers: the role of design. Bring your tough questions – Brad and I will be having a conversation on stage and you’re invited to join us.
Jonathan Irwin will lead a workshop on advanced interview skills , including the different kinds of customer interviews, how to develop questions, and how to apply the answers to an actual decision around a product. Thus we reduce the risk of deployments. If there’s a problem in production, developers need to own it.
That is, once you’re no longer a small company and you have some success, how do you execute and continue to grow through innovation? As Shutterstock has grown, there are a few key elements to our continueddevelopment speed: Small, autonomous teams: The more a team can do on their own, the faster they can go.
Startups especially can benefit by using technical debt to experiment, invest in process, and increase their productdevelopment leverage. The biggest source of waste in new productdevelopment is building something that nobody wants. Leverage productdevelopment with open source and third parties.
I spent some time with his company before the conference and discussed ways to get started with continuousdeployment , including my experience introducing it at IMVU. They were deploying to production with every commit before they had an automated build server or extensive automated test coverage in place.
Our goal is to find out whether customers are interested in your product by offering to give (or even sell) it to them, and then failing to deliver on that promise. Most of the time, the experiments you run will have a zero percent conversion rate - meaning no customers were harmed during the making of this experiment.
This gets me into trouble, because it conjures up for some the idea that productdevelopment is simply a rote mechanical exercise of linear optimization. You just constantly test little micro-changes and follow a hill-climbing algorithm to build your product. Case Study: Continuousdeployment makes releases n.
At least, not in the traditional sense of trying to squeeze every tenth of a point out of a conversion metric or landing page. In fact, the curse of productdevelopment is that sometimes small things make a huge difference and sometimes huge things make no difference. For example, I’m a big believer in split-testing.
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. Case Study: Continuousdeployment makes releases n. Pivot, don't jump to a new vision Why ContinuousDeployment? Both are lethal outcomes.
Their product definition fluctuates wildly – one month, it’s a dessert topping, the next it’s a floor wax. Their productdevelopment team is hard at work on a next-generation product platform, which is designed to offer a new suite of products – but this effort is months behind schedule.
Those who are interested in work-in-process might want to take a look at Work in small batches and Continuousdeployment - Eric) Some specific TPS practices appear in Lean Startups. Conversion optimization is a form of kaizen. Conversion optimization is a form of kaizen. Case Study: Continuousdeployment makes releases n.
Ever since that time, I have struggled to explain how the feedback loop in customer development should interface with the feedback loop in productdevelopment. Labels: customer development , productdevelopment 8comments: Sarah Milstein said. Case Study: Continuousdeployment makes releases n.
Lessons Learned by Eric Ries Monday, October 6, 2008 When NOT to listen to your users; when NOT to rely on split-tests There are three legs to the lean startup concept: agile productdevelopment , low-cost (fast to market) platforms , and rapid-iteration customer development. Case Study: Continuousdeployment makes releases n.
The way forward requires getting everyone together in a room, and having a conversation about where were headed. My aspiration with the Lean Startup methodology has always been to provide such a framework, so that we have more intelligent conversations about what works and what doesnt for startups. Thats what this conference is for.
Unfortunately, the video of our sllconf conversation is not online (due to technical problems), but we have a physical tape backup which we are endeavoring to get online soon. Case Study: Continuousdeployment makes releases n. In the meantime his two books, The Monk and the Riddle and Getting to Plan B are both a must-read.
Brant and Patrick undertook a difficult challenge: to provide a generally accessible introduction to Customer Development, without diluting its impact or dumbing-down its principles. It is written in a conversational tone, doesnt take itself too seriously, and avoids extraneous fluff. Case Study: Continuousdeployment makes releases n.
This is the first post that moves into making specific process recommendations for productdevelopment. Heres an excerpt: The Startups Rules of Speed - The Conversation - Harvard Business Review Every startup that achieves success eventually faces a critical moment — whether to speed up or slow down.
We would pretty much bid on any phrase that was "[name of competitive product] chat" and variations like that. And then we would use that simple analytics system I mentioned to monitor the conversion rates of customers from each campaign. Case Study: Continuousdeployment makes releases n.
The economics of these process trade-offs are discussed in the Principles of ProductDevelopment Flow.) Heres an excerpt: In a previous article, we called Toyota’s productdevelopment system the “second Toyota paradox.&# Labels: productdevelopment 5comments: new york web development company said.
So I generally feel right at home in these conversations. When I reviewed a recent productdevelopment book, it immediately shot up to Amazon sales rank 300. Case Study: Continuousdeployment makes releases n. In other words, they are facing conditions of extreme uncertainty, just like startups. Is that a lot?
Given that most recruiting channels are pay-for-performance, its usually cheaper, too, because it has a lower conversion rate. Particularly the ContinuousDeployment and Split testing posts. Case Study: Continuousdeployment makes releases n. The blog is fantastic as well. January 23, 2009 4:13 PM TS said.
Id be honored to have you join the conversation. The Conversation - Harvard Business Review For most of us, the phrase management science conjures up a decidedly non-entrepreneurial image, and for good reason. Read the rest at The Conversation - Harvard Business Review. Id be honored to have you join the conversation.
The Five Whys for Start-Ups - The Conversation - Harvard Business Review Root cause analysis and preventive maintenance are concepts we expect to see in a factory setting. The Five Whys for Start-Ups - The Conversation - Harvard Business Review Root cause analysis and preventive maintenance are concepts we expect to see in a factory setting.
For example, say that your business model calls for a 4% conversion rate – as ours did initially at IMVU. After a few months of early beta at IMVU, we discovered that our actual conversion rate was about 0.4%. That’s not too surprising, because our product was pretty bad in those days.
If you find yourself getting asked non-key questions, try to use your answers to steer the conversation back to the key questions. Case Study: Continuousdeployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuousdeployment for mission-critical applica.
Two Ways to Hold Entrepreneurs Accountable - The Conversation - Harvard Business Review Way back when the money was doled out, the team made a compelling pitch about the large market that was going to adopt their new innovative product or service. Case Study: Continuousdeployment makes releases n.
davemcclure : amazing concepts on ContinuousDevelopment => "Cluster Immune System" @EricRies #LeanStartup @fbFund [link] dalelarson : Because most features take longer to argue and prioritize than to build. ericries #leanstartup Another new idea in the section on continuousdeployment and the cluster immune system.
Beyond just those who will be hearing about the lean startup for the first time, Im expecting to shake a lot of hands and have a lot of interesting side conversations. Case Study: Continuousdeployment makes releases n. Im especially curious to gauge the reaction of the civilian and military representatives of our government.
Conversely I have seen many teams loose productivity by having team members slip into a "low energy state" where they just do the minimum necessary, lost in their own little world with little interaction with others, low accountability and perhaps most importantly no clear line between what they are doing and the success of the company.
Each of those levers -- conversion rate, action/user, msgs/action, etc. -- are important when thinking about how and why users engage with your product. Its the roll-up into one all-encompassing number that guides your product decisions that Im skeptical about, but I see that thats not what youre interested in at all.
Most importantly, if you know a high-quality entrepreneur who you think would add to the conversation, would you be willing to try and convince them to attend? Case Study: Continuousdeployment makes releases n. Would you be willing to link to the Master Class info page from your blog?
Notice that cohort and conversion based metrics do not suffer from this problem. When we look at the same conversion percentage for cohort after cohort, we are effectively getting a new, independent, report card for our efforts each period. Notice that cohort and conversion based metrics do not suffer from this problem.
’&# They removed the core plan, and conversions went up. Because SlideShare has more than a million visitors a day, the team is used to developing features that at least 100,000 people will use. ’&# They removed the core plan, and conversions went up. Case Study: Continuousdeployment makes releases n.
Paul Graham is getting his startups the best advice he can in the best way he knows: by giving them exclusive access to off-the-record conversations that nobody else is privy to. Case Study: Continuousdeployment makes releases n. Similarly, journalists print vanity metrics because that’s all companies will release.
Lessons Learned by Eric Ries Tuesday, December 16, 2008 Engagement loops: beyond viral Theres a great and growing corpus of writing about viral loops, the step-by-step optimizations you can use to encourage maximum growth of online products by having customers invite each other to join. Thanks for being part of the conversation.
By all accounts, the conversation was a success. By all accounts, the conversation was a success. Case Study: Continuousdeployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuousdeployment for mission-critical applica.
Do it right, and your conversion rates might be as high as 20%. Case Study: Continuousdeployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuousdeployment for mission-critical applica. Do it wrong, and your LTV gets very close to zero.
Entrepreneurs: Beware of Vanity Metrics - The Conversation - Harvard Business Review : The idea is simple. Establish baseline metrics by building the minimum viable product — the minimum required to measure the response of early adopters. Case Study: Continuousdeployment makes releases n. For more, read on.
The Conversation - Harvard Business Review : Still, startups develop some kind of process — whether its disciplined, haphazard, bureaucratic or empowering — because building a great product depends on it. The Conversation - Harvard Business Review For Startups, How Much Process Is Too Much?
Lessons Learned by Eric Ries Saturday, March 6, 2010 Startup Visa update As I write this, I am traveling at 30,000 feet on Virgin Americas excellent IAD->SFO nonstop, following an intense few days of conversations in Washington, DC about the Startup Visa. Case Study: Continuousdeployment makes releases n.
This conference will be the first of its kind: an opportunity to have a conversation about the future of the lean startup movement. We want everyone who can contribute to that conversation to be there, regardless of their ability to pay. Case Study: Continuousdeployment makes releases n.
How do you drop a phrase like "voluntary salary reduction tool" and then not describe it :) Unless youre simply talking about the standard "hey, take less cash and Ill give you more options" type conversation. Case Study: Continuousdeployment makes releases n. When you said "tool" I thought you actually meant you had a tool.
This is the thinking that allowed us to overcome our fear of continuousdeployment at IMVU. Thanks so much to everyone who made the trip to SIPA and participated in the conversation, as well as to SIPA and HP for hosting me. Case Study: Continuousdeployment makes releases n. Your support means the world to me.
We organize all of the trending information in your field so you don't have to. Join 5,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content