article thumbnail

Speed up or slow down? (for Harvard Business Review)

Startup Lessons Learned

This is the first post that moves into making specific process recommendations for product development. Hence, cutting corners often paid huge dividends. Pretty soon, a soul-searching meeting ensues. Labels: product development Speed up or slow down? Hence, cutting corners often paid huge dividends.

article thumbnail

How to Hack Growth When Growth Stalls

ConversionXL

Past Product: Lackluster Marketing Causes Growth Stalls, Too. These pitfalls are not limited to product development. Often, erosion of customer loyalty has been going on for years but the company has failed to perceive it—until it’s too late. Swimming with Sharks. Growth teams are like those sharks. Open Up the Ideation Process.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Lessons Learned: Work in small batches

Startup Lessons Learned

Its had tremendous impact in many areas: continuous deployment , just-in-time scalability , and even search engine marketing , to name a few. I owe it originally to lean manufacturing books like Lean Thinking and Toyota Production System. The batch size is the unit at which work-products move between stages in a development process.

article thumbnail

Lessons Learned: The one line split-test, or how to A/B all the time

Startup Lessons Learned

Thats when this approach can pay huge dividends. This gets me into trouble, because it conjures up for some the idea that product development 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.

article thumbnail

Lessons Learned: Inc Magazine on Minimum Viable Product (and a.

Startup Lessons Learned

But instead of spending the time and money to develop products on spec, TPGTEX creates mocked-up webpages that list the features of a potential new product -- such as a system for making radio-frequency identification, or RFID, labels -- along with its price. Read the rest. Why didn’t we learn more? Read the rest.

article thumbnail

How to conduct a Five Whys root cause analysis

Startup Lessons Learned

Labels: five whys root cause analysis , product development 15comments: Anonymoussaid. Luckily, in most prevention situations, even the first few steps in prevention can pay time-savings dividends quickly. Instead of telling people to look for *the* root cause, I have them search for *a* or *some* root causes.

article thumbnail

What to do when you get screwed

The Startup Toolkit

Unlike the much maligned case of a clueless business guy searching for indentured servants, he delivered real value and had secured a shocking number of customer commitments before the thing was built. After the team-poaching mentioned earlier, the goal ended up being to keep product development moving while a new tech team was found.