ReadWriteStart

FEBRUARY 22, 2022

These are primarily China, the US, Japan, and Germany. They stand out with their product’s quality (both physical and digital). So, creating cutting-edge opportunities for the customers following the R&D path improves brand recognition, loyalty, and credibility. Reasons for new product development.

Offshore 140

Offshore Demand Germany Global 140

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

NOVEMBER 8, 2008

Lessons Learned by Eric Ries Saturday, November 8, 2008 What is customer development? When we build products, we use a methodology. But too often when its time to think about customers, marketing, positioning, or PR, we delegate it to "marketroids" or "suits." a roadmap for how to get to Product/Market Fit."

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

APRIL 14, 2009

Lessons Learned by Eric Ries Tuesday, April 14, 2009 Validated learning about customers Would you rather have $30,000 or $1 million in revenues for your startup? This may sound crazy, coming as it does from an advocate of c harging customers for your product from day one. They are gaining valuable customer data.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

OCTOBER 26, 2009

Lessons Learned by Eric Ries Monday, October 26, 2009 A real Customer Advisory Board A reader recently asked on a previous post about the technique of having customers periodically produce a “state of the company&# progress report. Many companies seek to involve customers directly in the creation of their products.

Advisory Board 151

Advisory Board Customer San Francisco Lean 151

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

JULY 5, 2010

I believe it is the best introduction to Customer Development you can buy. As all of you know, Steve Blank is the progenitor of Customer Development and author of The Four Steps to the Epiphany. You can imagine how well that worked. On the plus side, that means its a great deal. I think theyve succeeded.

Customer Development 166

Customer Development Developer San Francisco Customer 166

Hearpreneur

SEPTEMBER 22, 2021

It drives media attention and fosters customer retention rate, which is why most companies strive to have it in their mission statement. It seeks to solve customer problems in a better and modern way and helping such companies edge the competition. Innovative is a word often used to describe successful companies. 5- Shiseido.

Technical Review 120

Technical Review Entrepreneur Software Review SEO 120

Steve Blank

JANUARY 14, 2013

Government funding of research started in World War II driven by the needs of the military for weapon systems to defeat Germany and Japan. There they would be tasked to develop military weapons systems and solve military problems to defeat Germany and Japan. The weapons were then manufactured in volume by U.S. corporations.).

Silicon Valley 243

Silicon Valley Government Germany Japan 243

YoungUpstarts

FEBRUARY 10, 2013

Examples include Kawasaki’s rules on presentations such as the 10-20-30 rule (make a 10 slide presentation in 20 minutes with no font smaller than 30 points), qualities of a great product (deep, intelligent, complete, empowering and elegant), and providing a MAP (Mastery, Autonomy and Purpose) rather than money to motivate employees.

Technical Review 145

Technical Review Japan Employee Management 145

Up and Running

SEPTEMBER 28, 2015

Kanban: a method used to control production. To get things rolling, we’ll turn to the industrious nation of Japan. The word kanban means “signboard” or “billboard” in Japanese, and it’s a concept most commonly applied to “lean” or “just in time” production. Scrum: a flexible way to manage product development.

SCRUM 60

SCRUM Japan China Agile 60

Startup Lessons Learned

SEPTEMBER 14, 2008

Lessons Learned by Eric Ries Sunday, September 14, 2008 How to listen to customers, and not just the loud people Frequency is more important than talking to the "right" customers, especially early on. Youll know when the person youre talking to is not a potential customer - they just wont understand what youre saying.

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131

Startup Lessons Learned

DECEMBER 14, 2009

Lessons Learned by Eric Ries Monday, December 14, 2009 Business ecology and the four customer currencies Lately, I’ve been rethinking the concept of “business model&# for startups, in favor of something I call “business ecology.&# Let’s begin with the four customer currencies. And this is true outside of games.

Customer 156

Customer San Francisco Viral Lean 156

Gregg Fraley, Author of Jack's Notebook

MAY 22, 2019

Nearly all that training is for dedicated innovation teams , or employees who are focused on new product development. Engaged support for strategic and tactical innovation initiatives developed by others. Reduced expenses through greater efficiency and productivity in internal processes. And that’s a good thing.

Operations 54

Operations Employee Technical Review Agile 54

YoungUpstarts

JUNE 10, 2019

The industrialized countries such as Europe, America and Japan have completed the industrialization of CNC machine tools, and China started from the 1980s and is now in the development stage. Producing quality products. up product delivery. Production of custom prototypes.

China 188

China Product Japan Europe 188

Startup Lessons Learned

MARCH 25, 2010

This is the first post that moves into making specific process recommendations for product development. Defective prototype code was as often thrown out (because customers didnt want it) as it was fixed (when customers did). Labels: product development Speed up or slow down?

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

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

AUGUST 3, 2009

First, a definition: the minimum viable product is that version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort. MVP, despite the name, is not about creating minimal products. There is a distinction between product and offering.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Startup Lessons Learned

SEPTEMBER 22, 2008

The law of large numbers (of customers) says you cant help but make at least some money - your valuation is determined by how well you monetize the tidal wave of growth. Paid - if your product monetizes customers better than your competitors, you have the opportunity to use your lifetime value advantage to drive growth.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

Startup Lessons Learned

APRIL 4, 2010

The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? ► 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. Take a look and let me know what you think.

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

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. One of the most important of these hypotheses is always: what will the customer care about?

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Startup Lessons Learned

JUNE 9, 2009

Lessons Learned by Eric Ries Tuesday, June 9, 2009 The Lean Startup Tokyo edition I had a blast speaking at Startonomics Tokyo , which was organized to foster ties between the startup cultures in Japan and Silicon Valley. benjaminjoffe : early adopters of buggy product are visionary customers, sometimes smarter than founders!

Lean 60

Lean San Francisco Japan Continuous Deployment 60

Startup Lessons Learned

SEPTEMBER 2, 2008

After all, the worst kind of waste in software development is code to support a use case that never materializes. Scalable systems are no exception - if your assumptions about how many customers youll have, or how they will behave are just a little bit wrong, you can wind up with a massive amount of wasted code.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

JANUARY 30, 2009

Here are a few: We know what customers want. By hiring experts, conducting lots of focus groups, and executing to a detailed plan, the company became deluded that it knew what customers wanted. Everyone had fun; the product worked. But that was two full years before any customers were allowed to use it.

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

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. Labels: agile , listening to customers 3comments: hauteroute said.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

SEPTEMBER 13, 2008

Lessons Learned by Eric Ries Saturday, September 13, 2008 SEM on five dollars a day How do you build a new product with constant customer feedback while simultaneously staying under the radar? Slowly, over time, we optimized (or eliminated) each step in the process of becoming a customer by giving us money. SEM is a simple idea.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Startup Lessons Learned

OCTOBER 6, 2008

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 product development , low-cost (fast to market) platforms , and rapid-iteration customer development. However, that cant be the end of the story.

San Francisco 128

San Francisco Lean Continuous Deployment Agile 128

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. There are no customers for that feature, UI issues or no.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

APRIL 7, 2010

Instead, we try to accelerate with respect to validated learning about customers. There are often counter-intuitive changes in customer behavior that depend on little details. In fact, the curse of product development is that sometimes small things make a huge difference and sometimes huge things make no difference.

San Francisco 154

San Francisco Lean Metrics Design 154

Startup Lessons Learned

SEPTEMBER 30, 2008

When Ive asked mentors of mine who have worked in big companies about the role of the CTO, they usually talk about the importance of being the external face of the companys technology platform; an evangelist to developers, customers, and employees. Labels: product development 15comments: mukund said.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

SEPTEMBER 10, 2008

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? How to listen to customers, and not just the loud. No departments The Five Whys for Startups (for Harvard Business R.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Lessons Learned

FEBRUARY 28, 2009

Customers dont care if you have good metrics, only if you have a good product. And while its true that metrics sometimes can lead to a better product, in my experience just as often they had led to no insight whatsoever, like fancy reports that nobody reads or after-the-fact rationalizations (with graphs!)

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

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. He has a good team, and theyve shipped a working product to many customers.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

AUGUST 30, 2008

This basic pattern is useful in all aspects of product development. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Lessons Learned by Eric Ries Saturday, August 30, 2008 Refactoring for TDD and interaction design In TDD , we follow a rhythm of “test-code-refactor.&#

Software Review 74

Software Review San Francisco Design Continuous Deployment 74

Startup Lessons Learned

SEPTEMBER 15, 2008

In my experience, the majority of changes we made to products have no effect at all on customer behavior. The report is set up to show you what happened to customers who registered in that period (a so-called cohort analysis ). This report is set up to tell you about new customers specifically. One last note on reporting.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

www.lanceglasser.com

MAY 13, 2012

Product development. Queuing theory and product development. The Essential Product Investigation Phase Gate. So you want to ship the product early? Customer Equity. Thank you Japan. The Year of the Black Swan. Definitions of common financial terms. A Model for Return on Engineering Expenses.

CTO 40

CTO CTO Hire Technical Review Architecture 40

Startup Lessons Learned

FEBRUARY 10, 2009

As Ive argued elsewhere , my belief is that startups (and anyone else trying to find an unknown solution to an unknown problem ) have to measure progress with validated learning about customers. This was an effective approach to discovering a business by using a sequence of product prototypes to get early customer feedback.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123