What happens during Discovery, and why spend money before CAD work begins? Discovery is the first stage of product development, where the team investigates the problem, constraints, standards, and opportunity before design starts. Paying for it first shows the client the full investment and what to change while changes are still cheap, according to Clay Martin, CEO of One3 Design.

Clay explained it to host Mike Downer in Episode 3 of The Design Orchestrator. One3 Design is a product development firm with facilities in Iowa and Georgia, and Discovery is the first of five stages behind its product design, engineering, and validation services, followed by define, design, build, and deliver.

What Happens During Discovery?

During Discovery, the team investigates the current state of the product or market, the constraints on the project, and the opportunity to create something better. “It’s very investigative,” Clay said. “We get into kind of CSI mode.”

The questions go beyond appearance. The team may investigate regulations, safety requirements, standards, validation needs, and manufacturing limitations. The American National Standards Institute explains that conformity assessment can include testing, inspection, validation and verification, while ASTM International lists more than 12,000 standards used worldwide to improve product quality and safety.

Discovery is the first of the five stages covered in Episode 2, which explained why One3 Design breaks product development into stages before anyone starts designing.

Why Spend Money on Discovery Before CAD Work Begins?

Spending money on Discovery before CAD work begins keeps a client from paying for a design built on the wrong assumptions. CAD drawings feel more tangible than research, but Clay warns against “running before we really understand the problem.”

Discovery gives clients an early chance to decide whether the project still makes sense. It can clarify the likely investment, expose expensive requirements and show where the scope could be adjusted to fit a budget.

As Clay puts it, the team must “make sure you understand the ask.” That understanding can prevent a company from paying for a design that later needs major changes.

He compares it to any large project: “You wouldn’t want to build a house, a swimming pool, or restore an old vehicle without a plan.”

The NIST Manufacturing Extension Partnership describes product development as work that can include market validation, prototyping, material selection and durability testing before manufacturing.

What Does Discovery Uncover That Clients Do Not Expect?

Discovery can uncover standards the product must meet, a manufacturing process that will not scale, and longer testing than the client expected. Clay explains that a higher estimated annual usage (EAU) can require moving from fabrication to die casting or injection molding, which raises the capital investment but can lower the price of each component. In his illustration, a product might need “maybe a thousand hours of durability testing,” and a failure sends the team back to repeat it.

Discovery can also reveal that an idea already exists. The U.S. Patent and Trademark Office provides Patent Public Search for reviewing U.S. patents and published applications.

How Long Does Discovery Take?

Discovery can take from about four or five days to a month in Clay’s examples, depending on the size and complexity of the project. His short example was a low-risk molded plastic part, and his long one was a mobile truck unit with hydrostats, electronics, control systems, and highway regulations.

Clients should not expect CAD during that period, and Clay says One3 Design makes it “very clear that you’re not going to see CAD taking shape” in the first two weeks. Instead, they receive research findings, meetings, customer feedback and, where a customer base exists, voice-of-customer interviews.

What Does the Client Receive at the End of Discovery?

Clay says clients leave Discovery with documentation covering the challenge, known risks, major technical hurdles and assumptions that carry into the next stage. It can arrive as a PDF, a written research report, a key summary, or a list of the assumptions carried into define.

Just as important, Discovery creates alignment. The client and development team should agree on what is being solved, what success looks like and what must be answered before moving forward.

The full guide to the discovery phase of product development walks through each deliverable and the questions it answers.

How Can Discovery Save a Client From a Costly Wrong Turn?

Discovery saves money by catching a wrong turn before it is built, such as an idea that already exists, a better manufacturing process, or a flawed approach that needs to change. In one case, reframing the problem and using simulation helped a client move toward a faster, more productive path.

That is the value of asking difficult questions early. What happens during Discovery, and why spend money before CAD work begins? Because a smaller investment in understanding the project can prevent a much larger investment in the wrong solution, which is why Clay said “it may be the most important step of the whole process.”

Watch the Full Episode on YouTube

Watch the full episode of The Design Orchestrator on YouTube to hear Mike Downer and One3 Design CEO Clay Martin explain how One3 Design approaches Discovery, what teams investigate before design starts, and how early research can reduce risk. Their conversation shares practical examples of Discovery changing a product’s direction before costly commitments.

FAQs

What happens during Discovery, and why spend money before CAD work begins?

During Discovery, the team investigates the problem, constraints, standards, and manufacturing realities before design starts. Paying for it first shows the client the likely investment and what to change before CAD work commits money to the wrong solution.

What is the Discovery stage in product development?

Discovery is the first stage for understanding the problem, opportunity, constraints, risks, market and customer needs before detailed design begins.

Why shouldn’t a team start with CAD immediately?

Starting CAD too early can lock a team into assumptions before requirements, risks and manufacturing realities are understood.

What can Discovery uncover?

It can reveal regulatory requirements, testing needs, manufacturing limits, market competition, cost concerns and technical risks.

How long does Discovery usually take?

In Clay Martin’s examples, a simple molded plastic part may take four or five days, while a complex mobile system with electronics and highway regulations may take three weeks to a month.

Does Discovery include customer research?

It can. Voice-of-customer conversations can reveal how people use a product and what improvements matter.

What does a client receive after Discovery?

Deliverables may include research documentation, identified risks, key assumptions, major challenges and a roadmap for the next stage.

Can Discovery reduce product development costs?

Yes. Finding problems early can help teams avoid spending more on unsuitable designs, processes or testing paths.

Mike Downer: Hello, everybody. Welcome to The Design Orchestrator. I’m your host, Mike Downer, here once again with Clay Martin.

This is a podcast on how products actually get built, from the first idea on a napkin to a finished product rolling off the line. This show takes you inside the process that most people will never see.

How are we doing today, Clay?

Clay Martin: Doing great, Mike. Great to see you again, as always.

Mike Downer: Last time, we talked about your five-step process. So today, like I said on the last episode, we’re going to start breaking this down for people so that everybody can understand what goes into the process, let alone what you have to do on the back side of it, but just the process that they’re involved in.

Today, we’re going to be talking about what happens during the discovery phase, the very first stage of your product development process. The main topic I want to get into is this: why is paying to figure out what you need just as important as paying to build it?

Clay, if you could walk us through what actually happens during discovery, that would be great.

Clay Martin: Yeah. What happens during the discovery phase of our five-stage product development process, I think, is what you’re asking.

In the discovery stage, ultimately, we’re trying to understand the current state, the constraints, and the opportunity to create. We’re trying to understand what the opportunity is, both for us, of course, and for the client.

It’s very investigative. We get into kind of CSI mode. We work to understand what the product is trying to address. Oftentimes, you’ll say, “What is the issue?” Well, sometimes there’s not an issue. Sometimes it’s a new product introduction that is either meeting or competing with an existing product group, answering and meeting a demand for that type of product.

Or, you might say, with the iPhone, Steve Jobs invented something that people didn’t even know they needed. He said, “I’ll tell them what they need.”

So there are all aspects of that. But in that stage of discovery, you’re looking to understand what that is. If it’s solving a problem, what is the problem? What’s the failure mode? What is not being addressed?

If it’s an opportunity for innovation, how can we push the edges of the envelope here? What are some opportunities that haven’t been investigated yet? How can we make what’s out there even better?

If it’s to introduce something that hasn’t been done, a lot of your investigation is going to be looking at the marketplace and saying, “Where could we strike, and how would we strike?”

So you’re asking a lot of those questions. You’re uncovering regulations in an industry, compliance, validation requirements, elements of safety, ANSI, ASTM, FMV, and standards from America to Canada to Europe. There are different constraints, and you have to understand those constraints and requirements when you step into the development of a new product or the modification of an existing product.

So once again, you’re mining for information. You’re discovering. You’re understanding what our lift is going to be, but we’re also helping the client understand: do you understand what you’re asking us to do?

Oftentimes, some of those tough conversations involve us coming back and saying, “Do you realize that if you’re going to step into this arena, this is going to be an initial cost? This is going to be the validation you’re going to be required to perform.”

Sometimes that’s a real revelation, and it causes a rethink before you start going down the rabbit hole of trying to solve it.

Mike Downer: I know you said that in this stage, there is going to be an additional cost. Could you tell us why this stage is worth paying for before any real design work starts?

Clay Martin: Yeah. So why is it worth paying for the discovery stage before you jump in and start designing something?

This is a conversation I often have with our colleagues within ONE3, the team. Let’s ask ourselves: why are we running before we really understand the problem? We typically don’t do that because we follow the approach, but every now and then, you find yourself jumping the gun a bit and wanting to get to what your mind is already telling you the solution would be.

You’ve got to step back from that and make sure you understand the ask.

For the client paying in those early stages, sometimes it’s a lot of work just to put a proposal together. I mean, it’s a lot of work. Just setting the stage for the level of discovery that has to happen when we engage with the client is important. They need to understand that investing in this first stage may help them decide whether they want to move forward.

Investing in this first stage is going to help them understand: what will my investment be, and am I okay with that? Are there things I could do without versus the perfect idealization of this project?

Based on what you’ve unearthed, described, and shared with us, could we change what my mind had scoped a bit to make it more budget-friendly or safer, for instance?

It’s really establishing a canvas as you start to paint on it, with all the knowns and all the things to be aware of. That’s applicable to anything you do in your life. You wouldn’t want to build a house, a swimming pool, or restore an old vehicle without a plan. You have to understand what you’re getting into.

Mike Downer: I know that if I had an idea and I really wanted it done, and let’s just say that it ended up being a bad idea, I’d rather pay a little bit for the discovery phase than pay a whole lot by skipping it and making it wrong.

You can save a lot of headaches, heartaches, and wallet aches that way, too.

Clay Martin: Yeah.

Mike Downer: The wallet ache. That’s the one that everybody understands.

When you’re going through this process in this stage, what kinds of things get uncovered during discovery that clients didn’t expect?

Clay Martin: Sure. What kinds of things get uncovered during stage one discovery that maybe clients didn’t foresee or ultimately count on?

Sometimes it’s the realization, as I said earlier, that there are standards you will need to comply with and honor. Your product will have to satisfy the requirements of those standards in order to introduce it to commercialization or sell it to a client base.

Sometimes it’s awareness of things they didn’t know in terms of standards. I’m talking about industry organizations, as I said, ANSI and ASTM, for instance.

You’ll also get into the realization that if you want to reach a certain scale, we’re going to have to utilize certain manufacturing processes. If your EAU, or estimated annual usage, is at this level, then the processes you had planned on using may not work.

Let’s say you’re with a company that is an experienced product developer and they’ve gotten successful. They may ask, “How do we scale?” Well, you’re going to discover or communicate to them that their fabricated approach to doing this can’t keep up with the unit increase. So we’re going to have to go to a die-cast or injection-molded approach. That’s going to increase your capital investment, but your component price may come down.

Those things sometimes catch people off guard and catch them by surprise.

Maybe the other thing I would mention is when you illustrate during the discovery phase that if we’re going to go down this path in this industry, this type of machine, this type of component, and this level of testing—maybe a thousand hours of durability testing—will be required. And if we break something, we’re going to have to step back up here and redo that again.

A lot of times, that’s an eye-opener for them as well.

Mike Downer: No, that makes sense. How long does the discovery stage usually take?

Clay Martin: How long does the discovery stage usually take? I would say it depends. I know that’s probably an answer that everyone hates to hear, but it depends on the size and scale of the project and the size and scale of the problem or what it is you’re trying to solve or create.

The more complex the endeavor, the longer you have to spend understanding it.

I’ll give you an example. We designed a product recently that was a molded plastic component that could scale to accommodate various configurations. Understanding that industry and the risk factor was pretty low-risk. We had to keep some things from leaking. It had to be strong enough to support what you’re putting in it. You had to be able to lift it. There were some ergonomics involved.

It was going to be outside a lot, so there was a material consideration for UV protection. Maybe you spend four or five days digging in, looking at the market, looking at what others are doing, asking how you can make this product unique, and figuring out how we might stylize it a little differently.

But on the other end of that spectrum, if a company comes to us and says, “Hey, we’ve got a mobile unit, a large truck that’s going to provide a service out in the world, and it has a number of machines, constituents, hydrostats, electronics, control systems, and all of these things,” and especially if we’re going to build it for them, we have to understand a lot.

What are the regulations? We’re taking this thing over the highway. Everything is going to have mass and weight associated with it. What environments is it going to be in? What regulatory constraints are going to be in place?

You may spend three weeks to a month evaluating, making phone calls, and understanding everything you need to know. But the more experience you get in any one of those spaces, the quicker those go. We certainly account for that when we put the proposal together.

We make it very clear that you’re not going to see CAD taking shape, and you’re not going to see certain elements you might otherwise expect to demonstrate the solution in those first two weeks. You’re going to have a lot of information fed back to you. We’re going to have meetings.

If you’ve got a customer base, we’re probably going to do some VOC, which is voice of customer. We want to talk to your customers. We want to talk to the representatives who understand this type of product and ask questions like, “What would make it better? Why would I need this particular function? Is there anything that we’re talking about now or proposing that could be improved? Help me understand the world this thing needs to live in.”

Those are all important aspects of that stage.

Mike Downer: Yeah, that makes complete sense. What does a client walk away with at the end of that stage?

Clay Martin: What does the client walk away with at the end of the discovery stage?

Mike Downer: Yes.

Clay Martin: What we provide for the client at that point is documentation and representation of what we understand the challenge to be.

It’s very important during that discovery phase that we’re communicative with the client. We’re staying in alignment. We can’t just go into our different camps and come back and say, “This is the way we see it.” Alignment is very, very critical.

If we don’t have a client and we’re designing something ourselves, we’re having that alignment with ourselves and making sure we fully understand. But most often, it’s with that client.

They’re going to walk away with documentation and a record of the work we performed to understand the problem. They’re going to walk away with a document and a record of risk factors that we see could be encountered in the project, or that the product would encounter in its use in industry.

We’re going to identify the largest challenges, the things that are going to take the most time, and what will be the biggest lift in solving the problem. We’re mapping that out and making sure we fully understand what they would like to see in terms of a finished product. We need to understand what that vision is so that we can finish that roadmap, map the plan into the subsequent stages, and make sure we stay in alignment all the way to the finish line.

Mike Downer: Perfect. We’ve kind of discussed this a little bit, but how do you handle a client who’s hesitant to pay for something that isn’t a product yet?

Clay Martin: Right. That’s a great question. How do we address the concern that you haven’t handed me something? It’s not a product, and it’s not a product yet. What am I paying for?

It’s conversations like this and having a very clear framework in the proposal that explain the specific activities that we’ll be taking part in and undergoing during these stages of the process.

Having an element of education for the client, if they’re unfamiliar with the stage-gated approach, is important. But it’s also really important to be illustrative of our plan. Put the bullet points in with exactitude.

At the end of each stage, we’re going to list the deliverables that would come from that stage. It’s not the same for every single product. It depends on the product. But we’ll clearly define what that end-of-stage deliverable is so they’ll understand that it’s going to come in the form of a PDF, a written research report, a key summary of the discovery elements, or an identification of assumptions that we’re taking into stage two, which is define.

They’re going to have a really clear summary description of all the activities that were performed and every deliverable that should result from those activities. We need to be in alignment because, at the end of that stage, they should understand: these are the deliverables, these are the decisions that were made, these are the things we need to know before progressing forward, and this is whether that has been fully answered.

If it hasn’t, you have to circle back around and work until you answer them all.

Mike Downer: Perfect. You’ve convinced me, and I completely understand and acknowledge why this stage is worth paying for. I get it.

So for that one doubter out there—there’s always that one guy—give us an example of discovery saving a client from a costly wrong turn. Something that you guys have done where, during discovery, they could have made a wrong turn, and you saved them quite a bit of time and money.

Clay Martin: Sure. An example of discovery saving a client money or time, or saving them from making a poor decision.

Mike Downer: Yeah.

Clay Martin: At the simplest level, you would say you have the conversation, and something sparks in your mind: “Man, this sounds like a really good product idea. So good, in fact, that there’s probably something already out there.”

With a little bit of research, you unfortunately find it and say, “Oh, yeah, that’s exactly it.” That’s kind of a letdown at times. That usually happens with individual inventors or folks who may not have a depth and breadth of invention experience.

But on the other side of that are the folks who have gone down a path for a while and can’t quite get to the solution. They’re burning money, and they bring you in and say, “Where are we going wrong?”

This particular client I can think of—most of what we do is so proprietary that I have to be very careful with specifics—had a very challenging technological and biological problem they were trying to solve. They had been going at it a certain way for a long time.

You can definitely get into that situation where the blinders are on, and you’re just continuing to hack away at something you think is going to be the solution. So we came in, applied our process, and in that discovery phase, we just started uncovering things that maybe they hadn’t thought of. Or they had been removed from the data early on long enough that they weren’t asking those fundamental questions that we had to ask to understand the problem.

It paused the program. We stepped back and saved them additional development costs, but we also helped them realign to a quicker, more prime path and introduce new tools and new technology.

We asked, “What if we used a simulated approach as opposed to real-world testing, for instance? We can fail faster. We can go through more iterations.”

Their combined intelligence and experience, along with our combined intelligence and experience, helped us realign the entire project and undoubtedly put us on a more productive course.

Another example I would give would be evaluating, once again, in that vein of assumption, what they may have perceived as a viable manufacturing process. They might be ready to pull the trigger, and we catch it before they do and say, “What if we could make this product do the exact same thing, still be really high quality, still look great, and save you 70% on manufacturing costs?”

They might ask, “What are you talking about?” Then you introduce them to a manufacturing process they may not have been familiar with, or may not have known was an option, and bring that collective community of solution providers together.

That happens a lot. You’re bringing the right people into the conversation because, as a consultancy, we have exposure to a lot. That’s usually one big example of saving someone from making a costly turn: you simply give them more options.

Mike Downer: It’s worth its weight in gold there, buddy. Worth its weight in gold, 100%. That’s what I think.

Well, thanks for explaining what all goes into the discovery process and why the time and effort are worth the investment. I hate to say “money you’re paying.” In actuality, I would call it more of an investment than paying for it. It’s worth investing not only your time, but also in their future.

Clay Martin: Yeah. They’re kind of investing in their own future. I think you summed it up great.

I think it may be the most important step of the whole process, taking the time to understand what you’re doing. Map it out to the end. Understand, if you have a budget, how you can apply that budget most effectively to reach your goals.

If you don’t have a budget, let’s get crazy. But most people have a budget, so you’ve got to map that and understand it.

It’s really difficult to effectively arrive at your goals, both in financial investment, functional achievement, and product introduction, if you don’t have a real clear understanding of what it is you’re trying to achieve and how to get there.

Mike Downer: Next time, we’re going to go into step two: define. On our next podcast, we’re going to go through the define stage, and you’re going to walk us through that.

Again, thanks for walking us through this. Today was a lot of fun. Every time I talk to you, I feel like I’m just a little bit smarter.

Clay Martin: Well, same to you. You’ve taught me some good multi-syllabic words that I can add to my vernacular now.

Mike Downer: Okay, somebody got Word of the Day toilet paper for Christmas.

Clay Martin: That’s right. That’s right.

Mike Downer: It’s always fun to add a little joke here and there. I do look forward to talking about define next time. As always, it’s been a pleasure, Clay, and I look forward to the next one.

Clay Martin: All right. Appreciate you, brother.

Mike Downer: Hey, buddy. Take care. We’ll see you later.