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
The University of California managed research and development of the bomb design lab at Los Alamos while the US Army managed the Los Alamos facilities and the overall administration of the project. Department of Research and Development. OSRD was essentially a wartime U.S. In 1947 the responsibility for all U.S.
These costs don’t take into account the many relevant systems within Shopify’s business such as maintaining its API, the infrastructure and server space needed to support its 50,000+ shops and designing and developing all of the beautiful templates that help make Shopify so successful.
In the article ” The Case for Old Entrepreneurs ”, Stanford professor and Washington Post columnist Vivek Wadhwa shared a 2008 study researching the backgrounds of nearly 700 U.S. – born CEOs and heads of productdevelopment at successful companies, and learned that the average age of successful founders was 39.
For instance, you might meet with one group to advise you on business expansion, another to discuss productdevelopment, another to help you identify new client prospects, and yet another to support you in handling employee issues. You’ll probably need to assemble different brain trusts for different tasks, too.
If you don’t, then how can you design and price your product and know whether it’s worth pursuing in the first place? Here are four steps you can build into the front end of your new productdevelopment process: Step 1: Identify benchmarking outcomes. Directly engage the customer in the innovation process.
Lessons Learned by Eric Ries Monday, July 13, 2009 The Principles of ProductDevelopment Flow If youve ever wondered why agile or lean development techniques work, The Principles of ProductDevelopment Flow: Second Generation Lean ProductDevelopment by Donald G. Reinertsen is the book for you.
Essentially, mobile productdevelopment and device-appropriate customer experience design are converging; people are spending more time on their mobile devices than ever before and expect more from their interaction with businesses. Professionalisms Comrade mobile mobile strategy mobile trends research study Young Pham'
by Lindsay Pedersen, author of “ Forging An Ironclad Brand: A Leader’s Guide “ In late 2008, Seattle’s adored Washington Mutual Bank (known locally and affectionately as WaMu) failed and was subsumed in a shotgun wedding with Chase Bank. And it’s not just productdevelopers who risk a lack of empathy.
Lessons Learned by Eric Ries Sunday, April 26, 2009 Productdevelopment leverage Leverage has once again become a dirty word in the world of finance, and rightly so. But I want to talk about a different kind of leverage, the kind that you can get in productdevelopment. Its a key lean startup concept. Great post!
He goes on to say: One reason I am participating in AlwaysOn Network’s blog is to hear from the tech community directly and to try to get beyond the traditional inside the Beltway Washington world where lobbyists filter the techies.
Lessons Learned by Eric Ries Tuesday, September 8, 2009 What would you want to tell Washington DC about startups? Im writing this post from an airplane headed to Washington DC, where Ill be presenting at the Government 2.0 So heres my simple question: What do folks in Washington need to know about the global community of entrepreneurs?
Lessons Learned by Eric Ries Monday, October 20, 2008 The engineering managers lament I was inspired to write The product managers lament while meeting with a startup struggling to figure out what had gone wrong with their productdevelopment process. Good luck, engineering manager. It was painful for a lot of people.
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.
One of the sayings I hear from talented managers in productdevelopment is, “good enough never is.&# And, most importantly, it helps team members develop the courage to stand up for these values in stressful situations. Lessons Learned by Eric Ries Monday, September 27, 2010 Good enough never is (or is it?)
He goes on to say: One reason I am participating in AlwaysOn Network’s blog is to hear from the tech community directly and to try to get beyond the traditional inside the Beltway Washington world where lobbyists filter the techies.
Own the development methodology - in a traditional productdevelopment setup, the VP Engineering or some other full-time manager would be responsible for making sure the engineers wrote adequate specs, interfaced well with QA, and also run the scheduling "trains" for releases. Labels: productdevelopment 15comments: mukund said.
I am convinced one of Joel Spolskys lasting contributions to the field of managing software teams will turn out to be the Joel Test , a checklist of 12 essential practices that you could use to rate the effectiveness of a software productdevelopment team. Thoughts on scientific productdevelopment Lo, my 5 subscribers, who are you?
Lessons Learned by Eric Ries Monday, September 22, 2008 Thoughts on scientific productdevelopment I enjoyed reading a post today from Laserlike (Mike Speiser), on Scientific productdevelopment. I agree with the less is more productdevelopment approach, but for a different reason. Now that is fun.
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. Take a look and let me know what you think.
The application of agile development methodologies which dramatically reduce waste and unlock creativity in productdevelopment. 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.
Also SJ's obsession with better taste (positively) contributes to the overall productdevelopment process. There are some good anecdotes about Chief Engineers in the Toyota ProductDevelopment Book. I really enjoyed this article, my first time reading any of your stuff. Will start to pay attention. Great post Eric.
Luckily, I now have the benefit of a forthcoming book, The Principles of ProductDevelopment Flow. Labels: five whys root cause analysis , productdevelopment 11comments: Peter Severin said. Its really helped me articulate my thinking on this topic, and includes an entire chapter on the topic of reducing batch size.)
Labels: five whys root cause analysis , productdevelopment 15comments: Anonymoussaid. Leave your thoughts in a comment. If you’ve tried Five Whys, please share your experiences so far. I’ll do my best to help.) Great article as always, Eric. Take a look and let me know what you think.
But first I think we need to save the product manager from that special form of torture only a waterfall productdevelopment team can create. Labels: productdevelopment 8comments: Vincent van Wylick said. This post has been removed by the author. Take a look and let me know what you think.
The technical interview is at the heart of these challenges when building a productdevelopment team, and so I thought it deserved an entire post on its own. Still, a startup productdevelopment team is a service organization. Labels: hiring , productdevelopment 5comments: TedHoward said.
In fact, the curse of productdevelopment is that sometimes small things make a huge difference and sometimes huge things make no difference. When we’re optimizing, productdevelopment teams encounter similar situations. I mean, here we are, paying them to be there, and they won’t use the product!
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.
Refreshing to finally see lean and agile thinking emerge in product/business-floors and not only in technology. Critical also, as the lean company/start-up can not be lean by just using lean principles in IT and not in ProductDevelopment/Management - a common misinterpretation of the Toyota Production System.
Customer development is a parallel process to productdevelopment, which means that you dont have to give up on your dream. Our goal in productdevelopment is to find the minimum feature set required to get early customers. This is a common mistake. Take a look and let me know what you think.
Sometimes we have the attitude that the ProductDevelopment team is the one responsible for Activation and Retention (hey, a great product would do that naturally) or that the Marketing team is responsible for Revenue and Referral (hey, go get me some money or free customers already). Take a look and let me know what you think.
In a startup, both the problem and solution are unknown, and the key to success is building an integrated team that includes productdevelopment in the feedback loop with customers. 2008 09 06 Eric Ries Haas Columbia Customer Development Engineering View SlideShare presentation or Upload your own.
Take a look and let me know what you think. Expo New York New York, NY Nov 19 The Lean Startup at MIT Boston, MA Nov 20 Lunch workshop at Dogpatch Labs Boston, MA Dec 17 Lean Startup Cohort program begins San Francisco, CA KISSmetrics KISSmetrics is loading.
Take a look and let me know what you think. Expo New York New York, NY Nov 19 The Lean Startup at MIT Boston, MA Nov 20 Lunch workshop at Dogpatch Labs Boston, MA Dec 17 Lean Startup Cohort program begins San Francisco, CA KISSmetrics KISSmetrics is loading.
Ever since that time, I have struggled to explain how the feedback loop in customer development should interface with the feedback loop in productdevelopment. Eric Ries Lean Startup Schematic View Of Agile Development And Customer Development View more presentations from Eric Ries.
This development philosophy created a culture around rapid prototyping of features, followed by testing them against large numbers of actual customers. It would be hard to argue against this productdevelopment strategy, in general. If a feature worked, wed keep it. If it didnt, wed trash it. But it worked. We made it.
Take a look and let me know what you think. Expo New York New York, NY Nov 19 The Lean Startup at MIT Boston, MA Nov 20 Lunch workshop at Dogpatch Labs Boston, MA Dec 17 Lean Startup Cohort program begins San Francisco, CA KISSmetrics KISSmetrics is loading.
Take a look and let me know what you think. Expo New York New York, NY Nov 19 The Lean Startup at MIT Boston, MA Nov 20 Lunch workshop at Dogpatch Labs Boston, MA Dec 17 Lean Startup Cohort program begins San Francisco, CA KISSmetrics KISSmetrics is loading.
Take a look and let me know what you think. Expo New York New York, NY Nov 19 The Lean Startup at MIT Boston, MA Nov 20 Lunch workshop at Dogpatch Labs Boston, MA Dec 17 Lean Startup Cohort program begins San Francisco, CA KISSmetrics KISSmetrics is loading.
Take a look and let me know what you think. Expo New York New York, NY Nov 19 The Lean Startup at MIT Boston, MA Nov 20 Lunch workshop at Dogpatch Labs Boston, MA Dec 17 Lean Startup Cohort program begins San Francisco, CA KISSmetrics KISSmetrics is loading.
Take a look and let me know what you think. Expo New York New York, NY Nov 19 The Lean Startup at MIT Boston, MA Nov 20 Lunch workshop at Dogpatch Labs Boston, MA Dec 17 Lean Startup Cohort program begins San Francisco, CA KISSmetrics KISSmetrics is loading.
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. I think Drucker said it best.
Take a look and let me know what you think. Expo New York New York, NY Nov 19 The Lean Startup at MIT Boston, MA Nov 20 Lunch workshop at Dogpatch Labs Boston, MA Dec 17 Lean Startup Cohort program begins San Francisco, CA KISSmetrics KISSmetrics is loading.
Anyone who has worked in a real-world productdevelopment team can tell you how utopian that sounds. Anyone who has worked in a real-world productdevelopment team can tell you how utopian that sounds. Take a look and let me know what you think.
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