Startup Professionals Musings

MAY 4, 2016

Building your public image and presence should start even before product development, through your website, logo, and blogging. With the Internet and modern video communication tools, including Skype and Google Hangout, you can find the people you need, from anywhere in the world, and sign them up quickly.

Intellectual Property 120

Intellectual Property Startup Angel Groups Social Media 120

YoungUpstarts

APRIL 23, 2015

The leaders and even team members will communicate often in order to identify brand new opportunities for promotion, evaluate the competitive positioning of a brand and even address various product development issues that may appear.

Management 100

Management Reputation Campaign Developer 100

View from Seed

DECEMBER 6, 2018

It seems as though in many categories, especially in consumer internet space, a handful of startups pursuing quite similar or even apparently identical ideas launch within months of each other. independently come to launch very similar products/services. Another d2c gourmet pet food company ?

Seed Stage 120

Seed Stage Startup Cofounder Stealth 120

Hearpreneur

DECEMBER 30, 2020

I fell in love with the blogging community, traveling, and cooking (plus eating) new foods and flavors. My expertise in product development and project management came after working as a consultant in many industries. I started my business simply because I want to be of assistance to those who want to learn through the internet.

Technical Review 145

Technical Review Entrepreneur Software Review SEO 145

Startup Lessons Learned

SEPTEMBER 15, 2008

The application of agile development methodologies which dramatically reduce waste and unlock creativity in product development. 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.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

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 got my start programming on an old IBM XT; it was thanks to MUDs that I first discovered the internet. Eric, love the blog. Thanks much.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

MARCH 25, 2010

This is the first post that moves into making specific process recommendations for product development. Labels: product development Speed up or slow down? This is the first post that moves into making specific process recommendations for product development. Take a look and let me know what you think.

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

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. What makes this particularly significant, of course, is that 3M’s product developers are among the most innovative in the world.

Marketing 234

Marketing Software Review Technical Review Social Network 234

Startup Lessons Learned

APRIL 4, 2010

blog comments powered by Disqus Newer Post Older Post Home 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?) Take a look and let me know what you think.

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

Startup Lessons Learned

MARCH 16, 2009

Lessons Learned by Eric Ries Monday, March 16, 2009 Combining agile development with customer development Today I read an excellent blog post that I just had to share. In most agile development systems, there is a notion of the "product backlog" a prioritized list of what software is most valuable to be developed next.

Agile 111

Agile Customer Development Developer San Francisco 111

Startup Lessons Learned

SEPTEMBER 7, 2008

In a startup, both the problem and solution are unknown, and the key to success is building an integrated team that includes product development in the feedback loop with customers. 2008 09 06 Eric Ries Haas Columbia Customer Development Engineering View SlideShare presentation or Upload your own.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

View from Seed

AUGUST 10, 2021

Hologram is a leader in enabling large-scale connectivity of internet of things (IoT) devices, across the globe with 400+ wireless carriers, all through a robust but easy-to-use API. Today Hologram announced their $65M Series B round of funding led by Tiger Global.

Chicago 177

Chicago Cofounder Miami B2B 177

Startup Lessons Learned

SEPTEMBER 22, 2008

Sometimes we have the attitude that the Product Development 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.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

Entrepreneurs-Journey.com by Yaro Starak

JUNE 9, 2011

It’s what so many of us love talking (and blogging) about. I had many ideas about different products I could release and eventually narrowed it down to what I thought was the best idea – I could take all of my free YouTube videos and create a DVD package. Well, it all depends. Allow me to explain. Seriously, I was.

Product Development 83

Product Development Product Developer Video 83

Startup Lessons Learned

OCTOBER 5, 2008

But first I think we need to save the product manager from that special form of torture only a waterfall product development team can create. Labels: product development 8comments: Vincent van Wylick said. Ive written about it on our development blog at [link] October 6, 2008 3:34 PM Chris Hondl said.

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

SEPTEMBER 12, 2008

0comments: 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?) Take a look and let me know what you think.

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Startup Lessons Learned

SEPTEMBER 2, 2008

Thoughts on scientific product development Lo, my 5 subscribers, who are you? Get in touch: Twitter Email Facebook Linkedin Additional resources Startup LessonsLearned, All Seasons : Every post from the blog, in one 600+ page PDF. Startup Lessons Learned season one : Every post from the blogs first year in print form.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

JANUARY 7, 2010

Although much of it will sound familiar to readers of this blog, whats new is my first step towards the " new entrepreneurship " that is my goal for 2010. Unlike previous cross-posting Ive done for blogs, where a lot of the discussion happens here, Id like to ask you to take a minute and click through to read the full article.

San Francisco 119

San Francisco Management Continuous Deployment Lean 119

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

JULY 5, 2010

Instead of that naive approach, I wish Id had a book like this one, to help me figure out how to get started with customer development step-by-step. While the customer development framework of Four Steps is universally relevant, The Entrepreneur’s Guide updates its practices for modern startups. Well done, Brant and Patrick.

Customer Development 166

Customer Development Developer San Francisco Customer 166

Startup Lessons Learned

SEPTEMBER 2, 2008

Its inspired by the classic OODA Loop and is really just a simplified version of that concept, applied specifically to creating a software product development team. There are three stages: We start with ideas about what our product could be. Thoughts on scientific product development Lo, my 5 subscribers, who are you?

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

SEPTEMBER 30, 2008

Own the development methodology - in a traditional product development 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: product development 15comments: mukund said.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

JUNE 2, 2010

blog comments powered by Disqus Newer Post Older Post Home 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?) Speed up or slow down?

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

Hearpreneur

JANUARY 26, 2022

With more of us working from home and placing more demands on our bandwidths, faster internet with increased capacity for file sharing and uninterrupted Zoom conversations is the natural next step. Once reformatted for usage on other platforms, video content can also be used to create blog content. Keep an eye on this.

Software Review 123

Software Review Technical Review Artificial Inteligence Entrepreneur 123

Startup Lessons Learned

SEPTEMBER 10, 2008

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 product development team. Thoughts on scientific product development Lo, my 5 subscribers, who are you?

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

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

Startup Lessons Learned

AUGUST 30, 2008

This basic pattern is useful in all aspects of product development. Get in touch: Twitter Email Facebook Linkedin Additional resources Startup LessonsLearned, All Seasons : Every post from the blog, in one 600+ page PDF. Startup Lessons Learned season one : Every post from the blogs first year in print form.

Software Review 74

Software Review San Francisco Design Continuous Deployment 74

Startup Lessons Learned

APRIL 14, 2009

Their product definition fluctuates wildly – one month, it’s a dessert topping, the next it’s a floor wax. Their product development 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.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

SEPTEMBER 14, 2008

As Seth writes this week in Seths Blog: Listening to the loud people , the most aggressive customers arent necessarily the ones you want to hear from. If youre just getting negativity from someone, they are more likely a internet troll - not an earlyvangelist. Thanks Eric, your blog has many golden nuggets!!!

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131

Startup Lessons Learned

FEBRUARY 20, 2009

Luckily, I now have the benefit of a forthcoming book, The Principles of Product Development Flow. Labels: five whys root cause analysis , product development 11comments: Peter Severin said. Startup Lessons Learned season one : Every post from the blogs first year in print form. Interesting post.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

SEPTEMBER 10, 2008

Labels: Test-driven development 0comments: 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?)

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Lessons Learned

NOVEMBER 4, 2008

Eric, Any thoughts on how forum feedback fits into customer development and agile product development? Youve probably addressed this in the past, but I continue to be blown away by how fast Blizzard reacts to noise in their forums and rapidly makes fixes to the product. What is customer development?

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

NOVEMBER 8, 2008

Customer development is a parallel process to product development, which means that you dont have to give up on your dream. Our goal in product development is to find the minimum feature set required to get early customers. A book I am looking forward to read after reading you blog. This is a common mistake.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

JULY 6, 2009

I worry sometimes about making this blog too much into a travelogue or journal of my public events. wow this blog is god awful. Get in touch: Twitter Email Facebook Linkedin Additional resources Startup LessonsLearned, All Seasons : Every post from the blog, in one 600+ page PDF. Eemo, thanks for the compliment.

Lean 115

Lean Video San Francisco Continuous Deployment 115

Startup Lessons Learned

JULY 30, 2009

Brad Feld also had some thoughts on this event on his blog. Get in touch: Twitter Email Facebook Linkedin Additional resources Startup LessonsLearned, All Seasons : Every post from the blog, in one 600+ page PDF. Startup Lessons Learned season one : Every post from the blogs first year in print form.

Lean 68

Lean San Francisco Continuous Deployment DC 68

Startup Lessons Learned

OCTOBER 20, 2008

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 product development process. Good luck, engineering manager. It was painful for a lot of people.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

AUGUST 2, 2008

0comments: Post a Comment Newer 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?) Take a look and let me know what you think.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125