Am I building the right thing?

While the proof of concept helps us know if our ideas are even possible, the Concept Validation phase helps us find out if they’re any good.

CV builds typically work like the intended final product, but they’re made with non-production manufacturing methods so might not look the same. We might 3D print instead of injection mold, or CNC machine instead of casting. We’re looking for the cheapest, fastest way to build something that’s real enough to test.

This stage still requires creativity, but we’re adding a bit more process and structure too.

We’re focused on mimicking the eventual production design just enough to test. But where’s that line? We define “just enough” by translating our product goals into engineering requirements, and we let the requirements decide what functionality gets tested and how. Our CV build should be just mature enough to run these tests and help us gain confidence that our product goals are reasonable.

To perform well in the CV phase, a solid understanding of production and prototype manufacturing processes is extremely helpful, along with the ability to clearly define test procedures from product goals. We also have to be structured enough to track our test program and understand the results.

Who do you know who knows how things are made? How things are tested? Those people are extremely valuable during the CV phase.

-Brian Schoolcraft

The proof is in the prototype

Proof of Concept. The name says a lot, but what does it mean to you?

What are you trying to accomplish in this stage of the cycle? What skills does your team need to be successful here? Here’s my take.

At this point, we’re trying to prove to ourselves that this idea is technically feasible, and that with more (often much more) development, we can turn it into a product that the market will want. We spend a lot of time thinking about all the ways it could be made, the big risks and technical challenges, and what will be important to the customer. 

This is the stage where invention, creativity, and discovery all play a key role. Ideally, your team will have a breadth of relevant experience to draw from as they make fast paced judgment calls with minimal development time. A little “process” is good, just to make sure the many rapid iterations of the idea are documented, but too much process will drag you down.

The key to getting through the POC phase successfully is to focus on the big important questions, and ignore the smaller details. Pay close attention to the things that haven’t been done before, and convince yourself that they can be done.

Think about the kind of people you need to do this. Get them on your team. Then go prove it!

-Brian Schoolcraft

The life of a product

Everything has a life cycle, and your product is no different! There are many terms and systems for defining the cycle, let’s pick a set of terms and begin walking through them.

1. Proof of Concept (POC)

2. Concept Validation (CV)

3. Design Validation (DV)

4. Production Validation (PV)

5. Sustaining Engineering (SE)

When you reach the end, you either keep making it until it stops making money, or (more commonly) you begin again on a product variation or next generation product. Often your business is in multiple overlapping development cycles, one for each generation or product line.

Each step in the cycle requires a slightly different team composition. Different skills, tools, and procedures are necessary as your product matures. The move fast and break things attitude that can be very valuable in the POC phase can cost you big time in production.

Where are you in your product life cycle? Is your team the right fit for where you are? If not, let’s talk!

-Brian Schoolcraft