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. We first invested in co-founders Ben Forgan & Pat Wilbur in early 2015, when NextView led a $1.3M

Chicago 177

Chicago Cofounder Miami B2B 177

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. We first invested in co-founders Ben Forgan & Pat Wilbur in early 2015, when NextView led a $1.3M

Chicago 156

Chicago Cofounder Miami B2B 156

Startup Lessons Learned

OCTOBER 4, 2008

He previously co-founded and served as Chief Technology Officer of IMVU. He is the co-author of several books including The Black Art of Java Game Programming (Waite Group Press, 1996). While an undergraduate at Yale Unviersity, he co-founded Catalyst Recruiting. So much for timing. October 13, 2008 6:47 PM Luke G said.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

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. We first invested in co-founders Ben Forgan & Pat Wilbur in early 2015, when NextView led a $1.3M

Chicago 136

Chicago Cofounder Miami B2B 136

Startup Lessons Learned

APRIL 4, 2010

Kent is a significant figure in the field of software development. To his credit are Extreme Programming , jUnit, patterns, TDD , the list goes on. Kent is a significant figure in the field of software development. To his credit are Extreme Programming , jUnit, patterns, TDD , the list goes on. for Harvard Business Revie.

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

Startup Lessons Learned

SEPTEMBER 15, 2008

I am heavily indebted to earlier theorists, and highly recommend the books Lean Thinking and Lean Software Development. I also owe a great debt to Kent Beck, whose Extreme Programming Explained: Embrace Change was my first introduction to this kind of thinking. (So Otherwise it's a great idea. for Harvard Business Revie.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

Startup Lessons Learned

SEPTEMBER 7, 2008

Lessons Learned by Eric Ries Sunday, September 7, 2008 Customer Development Engineering Yesterday, I had the opportunity to guest lecture again in Steve Blank s entrepreneurship class at the Berkeley-Columbia executive MBA program. Unfortunately, positioning our product as an "IM add-on" was a complete mistake.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

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. for Harvard Business Revie.

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Startup Lessons Learned

AUGUST 3, 2009

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 Product Development/Management - a common misinterpretation of the Toyota Production System.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

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

JUNE 2, 2010

And yet the key to startup speed is to maintain a disciplined approach to testing and evaluating new products, features, and ideas. As start-ups scale, this agility will be lost unless the founders maintain a consistent investment in that discipline. Techniques from lean manufacturing can be part of a startups innovation culture.

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

Startup Lessons Learned

JANUARY 2, 2010

Lessons Learned by Eric Ries Saturday, January 2, 2010 Towards a new entrepreneurship When I started writing about the lean startup , my aspiration was to do more than just share a handful of tips and tricks that work for consumer internet startups. The result is a profound democratization of the digital means of production.

San Francisco 122

San Francisco Lean Continuous Deployment DC 122

Startup Lessons Learned

FEBRUARY 28, 2009

None of it would have happened if we had plenty of cash, or were content to count our progress by traffic or product development milestones. Luckily for me, my co-founders eventually prevailed and we went on to build a product that customers actually wanted. Labels: product development 4comments: Doug said.

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

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. Instead, we do everything possible to validate the founders belief.

Customer Development 168

Customer Development Developer San Francisco Customer 168

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. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? for Harvard Business Revie.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

MARCH 22, 2010

The cost of creating new companies is falling rapidly, and access to markets, distribution, and information is within the reach of anyone with an Internet connection. The result is a profound democratization of the digital means of production. [.] The result is a profound democratization of the digital means of production. [.]

San Francisco 121

San Francisco Indiana Lean Startup 121

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). for Harvard Business Revie.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

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. Ive been there: is it me or my cofounder thats crazy? Use some customer development to find out. Iterating at whiteboard !=

Lean 60

Lean San Francisco Continuous Deployment Cofounder 60

Startup Lessons Learned

MARCH 16, 2009

Ever since that time, I have struggled to explain how the feedback loop in customer development should interface with the feedback loop in product development. Consider the classic project that was essential to the creation of extreme programming , the Chrysler Comprehensive Compensation System.

Agile 111

Agile Customer Development Developer San Francisco 111

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. Giving rise to three verbs: Implement (programming!) for Harvard Business Revie.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

FEBRUARY 10, 2009

This was an effective approach to discovering a business by using a sequence of product prototypes to get early customer feedback. The first version of the 3D IMVU client took about six months to build, and as the founders iterated towards a compelling user experience, the user base grew monthly thereafter. If it didnt, wed trash it.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

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. 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.

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

JANUARY 30, 2009

Without conscious process design, product development teams turn lines of code written into momentum in a certain direction. This is why agility is such a prized quality in product development. As far as I know, there are no products that are immune from the technology life cycle adoption curve.

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

Startup Lessons Learned

JULY 5, 2010

As all of you know, Steve Blank is the progenitor of Customer Development and author of The Four Steps to the Epiphany. I have personally sold many copies of his book, and continue to recommend it as one of the most important books a startup founder can read. No departments The Five Whys for Startups (for Harvard Business R.

Customer Development 166

Customer Development Developer San Francisco Customer 166

Startup Lessons Learned

NOVEMBER 29, 2008

If done right, a programming interview serves two purposes simultaneously. The technical interview is at the heart of these challenges when building a product development team, and so I thought it deserved an entire post on its own. Still, a startup product development team is a service organization.

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

APRIL 14, 2009

It should be even more important to the founders themselves, because it demonstrates that their business hypothesis is grounded in reality. Their product definition fluctuates wildly – one month, it’s a dessert topping, the next it’s a floor wax. In fact, this company hasn’t shipped any new products in months.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

NOVEMBER 4, 2008

For those interested in getting started with agile or customer development, I thought Id include a few links. My path to lean startups began with Kent Beck and extreme programming. The best resources there are his book Extreme Programming Explained: Embrace Change and the gentle introduction at extremeprogramming.org.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

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. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? for Harvard Business Revie.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Lessons Learned

SEPTEMBER 27, 2010

One of the sayings I hear from talented managers in product development is, “good enough never is.&# And, most importantly, it helps team members develop the courage to stand up for these values in stressful situations. I believe this is one reason why the myth of the dictatorial startup founder has such enduring appeal.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

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. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? for Harvard Business Revie.

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Startup Lessons Learned

AUGUST 30, 2008

This basic pattern is useful in all aspects of product development. ► 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. Learning is better than optimization (the local ma.

Software Review 74

Software Review San Francisco Design Continuous Deployment 74

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

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. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Interesting post.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

JULY 6, 2009

Its also frustrating how some founders see ANY form of struture/approach as limiting and go to the total reverse of waterfall by just doing what they were told by "their wifes friend" This is great and practical stuff.will make sure I pass it on and use in my discussions (giving credit to you!) for Harvard Business Revie.

Lean 115

Lean Video San Francisco Continuous Deployment 115

Startup Lessons Learned

SEPTEMBER 14, 2008

Most of the people building our product werent themselves target customers. So there was simply no substitute for seeing actual customers with the product, live. Today, when I talk to startup founders, the most common answer I get to the question "do you talk to your customers?" for Harvard Business Revie.

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131

Startup Lessons Learned

FEBRUARY 22, 2010

I have personally taught many “non-technical&# people to program – graphic designers, QA folks, even artists and animators. Instead of focusing on programs designed to specifically benefit any one group, I think our focus should be on making our companies as meritocratic as possible.

San Francisco 167

San Francisco Lean Sweden Continuous Deployment 167

Startup Lessons Learned

SEPTEMBER 30, 2008

So what does CTO mean, besides just "technical founder who really cant manage anyone?" Labels: product development 15comments: mukund said. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Thoughts on scientific product development Lo, my 5 subscribers, who are you?

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168