Why break product development into stages instead of just starting to design? Because each stage makes a team understand the problem, the constraints, and the requirements before it commits time and money to a design, which lowers both risk and cost, according to Clay Martin, CEO of One3 Design, a product development firm with facilities in Iowa and Georgia. Jumping straight into designing can feel more exciting, but that shortcut can create expensive problems later. In this episode of The Design Orchestrator, host Mike Downer and Clay walk through the five stages behind One3 Design’s design, engineering, and build services, and explain why understanding the problem, defining the solution, testing the result and maintaining client alignment create a more efficient path from idea to finished product.
How Do the Five Stages Create a Roadmap?
The five stages create a roadmap by moving every project through the same sequence: discover, define, design, build and deliver. Rather than treating these as arbitrary checkpoints, Clay describes them as a structured way to arrive at a solution.
Discover is about understanding the current situation, constraints and opportunity. Define establishes what success should look like and creates a roadmap. Design turns those requirements into a solution. Build brings that solution into the virtual or physical world for testing and refinement. Finally, deliver puts the completed solution into the form the client actually needs.
The exact deliverable can vary. One project might end with a manufactured product, while another might involve engineering data, drawings or another technical package that allows someone else to move forward.
What Goes Wrong When a Team Starts in CAD?
Starting in CAD too soon commits a team to a solution before it fully understands the problem it is trying to solve, which Clay calls a mistake companies make fairly often.
Once designers begin creating shapes, mechanics and components, they are already committing time and resources to a potential solution. If important requirements have not been identified first, they may later discover that the design was built around incorrect assumptions.
That is why One3 Design spends considerable time in discovery. The team works to understand what needs to be created, why it is needed and what requirements will affect the final product. That preparation can make the path forward much more direct.
Clay borrows a well-known line to explain the balance: “If you have an hour to solve something, spend fifty-five minutes understanding the problem and five minutes solving it.”
How Do Stage Gates Control Cost and Risk?
Stage gates control cost and risk because the team answers the important questions within the current stage before it moves forward, an approach Clay describes as “stage-gated.”
During discovery, those questions could involve material selection, load requirements, operating speed or applicable industry standards and regulations. Once those details are understood, the team can define the product more clearly and align with the client before detailed design begins. For consumer products, the U.S. Consumer Product Safety Commission also urges manufacturers to make safety a priority at the design stage and to learn the mandatory and voluntary standards that apply.
That concept is especially visible in regulated industries. For example, the U.S. Food and Drug Administration requires applicable medical-device development processes to address defined design inputs, outputs, reviews, verification, validation and risk analysis. While not every product follows medical-device regulations, it demonstrates why requirements and testing can be critical parts of structured development.
Does Building Always Start With a Physical Prototype?
Building does not necessarily begin with a physical prototype. Clay explains that teams can first build virtually using engineering tools such as finite element analysis or computational fluid dynamics.
Eventually, however, products intended for commercialization need to perform outside the computer. Physical prototypes may be tested repeatedly, exposed to environmental conditions and intentionally pushed toward failure. The goal is to determine not simply whether something works once, but how and why it performs under real-world conditions.
Testing can reveal weaknesses while there is still an opportunity to improve the product.
Does Every Project Need All Five Stages?
Not every client needs One3 Design to complete all five stages. Some clients may only need design support. Others may arrive with finished drawings and need help building a product.
Even with that flexibility, Clay says there is almost always some level of discovery and definition. The team still needs to understand the request, existing information and desired outcome before taking responsibility for its part of the project.
That flexibility allows the process to provide structure without forcing every project into exactly the same scope.
Why Break Product Development Into Stages Instead of Just Starting to Design?
Breaking product development into stages creates an opportunity at each gate to understand requirements, confirm assumptions, identify risks and make informed decisions before committing more resources.
The process does not slow development for the sake of adding steps. Its purpose is to make sure the work being completed is moving toward the right solution.
Watch the Full Episode on YouTube
Want to hear Clay Martin explain how discover, define, design, build and deliver work together in actual product development? Watch the full episode of The Design Orchestrator on YouTube. Hear more about One3 Design’s approach to reducing risk, improving client alignment and developing products for real-world use.
FAQs
Why break product development into stages instead of just starting to design?
Breaking product development into stages makes a team understand the problem, constraints, and requirements before it commits to a design, so each gate lowers risk and cost before more money is spent.
What are the five stages of One3 Design’s process?
The stages are discover, define, design, build and deliver.
Why is discovery important before product design?
Discovery helps teams understand the problem, constraints, requirements and opportunities before committing resources to a specific solution.
What happens during the define stage?
The team establishes what the completed solution should accomplish, documents requirements and aligns expectations with the client.
What is a stage-gated product development process?
It is an approach where important requirements within one stage are addressed before the project advances to the next.
Does every product need a physical prototype?
Not necessarily. Projects vary, and some work may end at the design or engineering-data stage rather than physical production.
Why is product testing important?
Testing helps teams evaluate whether a design meets established requirements and identify weaknesses before wider production or commercialization.
Does every One3 Design project use all five stages?
The overall framework is considered for each project, but the exact scope can change depending on what the client already has and what support they need.
Mike: Hello, everybody, and welcome to The Design Orchestrator, a podcast about how products actually get built, from the first idea on a whiteboard to a finished product rolling off the line. This show takes you inside the process that most people never get to see.
I’m joined by Clay Martin, CEO of One Three Design. How are we doing today, Clay?
Clay Martin: I’m doing great, Mike. Good to see you again, brother.
Mike: Good to see you too, man. It’s always a lot of fun talking to you. This is probably one of the most interesting podcasts that I do, by far, because this is something that I think everybody would be interested in. We all use this stuff every day, and you help make it come to fruition.
Clay Martin: Somewhere, right? It does. It does.
Mike: You’re one of the men who makes it happen.
Clay Martin: Yep, one of many.
Mike: Today, we’re going to be talking about why companies should use a five-stage process instead of just starting a design. Basically, we’ll be breaking down what happens when a company skips straight to designing without structured stages first. You’re going to explain all this to us, so let’s get right into it.
Can you give us the design, build, and deliver process?
Clay Martin: Yeah, Mike. The thirty-second framing of discover, define, design, build, and deliver would be that it is a structured format or approach, a formulaic approach, to arriving at solutions.
When you’re in the process of designing something, especially something very specific to meet a very specific requirement, you have to take the time to understand what you’re trying to solve, define a solution set that you believe will solve it, design the result of that hypothesis, and then ultimately build, test, refine, and deliver that final product.
Mike: Okay. That’s very logical, and it makes a lot of sense. It was more than thirty seconds, but that’s a pretty good synopsis.
Clay Martin: Thirty seconds was just a suggested timeframe.
Mike: It’s just suggestions here, buddy.
So what goes wrong when a team skips straight into CAD without any of those earlier stages?
Clay Martin: That’s a mistake we see companies make fairly often. Not everyone makes it, of course. Everyone has a varying state of capability in that space.
But when you jump right into defining what the solution is, especially when you’re pushing electrons around in CAD, making form, making shape, building mechanics, and doing all the things, you’re getting ahead of yourself if you haven’t taken the time in the discover and define stages to understand what you’re actually designing.
I can’t remember which really famous smart person said this, but if you have an hour to solve something, spend fifty-five minutes understanding the problem and five minutes solving it. I would say we implement that ideology a lot.
We’ll spend a lot of time in the discover stage making sure we fully understand the problem or the ask. What is the request to be created or solved? Once we understand that, we can start applying the right manufacturing process, discipline, and problem-solving approach to ultimately arrive at a solution.
When you can define that and build that roadmap before you start pushing electrons around on the screen, you invariably save time and money, and you reach the ultimate product solution through a much straighter, more efficient path.
Mike: You were talking about saving clients, and yourself, time and money. Why does breaking the process into stages actually save clients money?
Clay Martin: That’s a great question, Mike. Ultimately, the industry would refer to it as more of a stage-gated approach.
You can meter your way up, inch your way up on the problem and the work required to solve the problem by making sure that before you proceed to the next step, you’ve satisfied all the information in the current phase that is necessary to pass through that gate to the next stage.
If you’re in the discovery phase, for instance, and you’ve identified five things you need to know before moving forward, you have to answer those questions. Maybe it’s material selection because the product is going to be consistently exposed to UV. Maybe there is a load case that you need to honor so you can select a material that is strong enough. Maybe the question is how fast the thing has to move.
Here’s a big one: what industry standards and regulations does this product have to comply with, accommodate, and be validated against before we move forward?
Being very investigative in those early stages starts to paint a picture of what that final product will be. Then you step forward from that stage into define, and you take all that information and ask, “What would this look like?”
You get very specific in describing what that product or solution will look like. You map it out, document it, and get alignment with your client so both sides of the table understand and agree on what you’re moving forward with.
Then you move into the design stage, where you’re designing to what the define stage described and defined.
Ultimately, working through that staged approach and stopping at each gate to ensure you’ve satisfied all the requirements of that stage before moving forward allows you to mitigate risk and cost. It gives you the ability to stop if needed or recalibrate if you discover a different approach during the project progression that might increase or decrease cost.
Ideally, it decreases cost because you’re making smarter, more informed decisions as you move forward.
Mike: That makes perfect sense. Beyond just saving money, how do these stages protect the client specifically, and not just One Three?
Clay Martin: Yes, Mike. From a cost perspective, it can certainly reduce the amount of investment if we are a certain distance into the process and need to make an adjustment. Maybe we have to stop and recalibrate, or even end the project, which doesn’t happen often. Or maybe we make a discovery that says, “Hey, we’ve seen a really awesome opportunity here. If we adjust the scope a bit, we can really save time and money and reduce risk.”
The reduction of risk for the client is not just in capital tooling investment, material costs, and things like that, although that is key. But if you can make the product safer, or if you can unearth or uncover information and facts they were unaware of during the process, taking that staged approach and being inquisitive along the way helps protect the client.
Maintaining alignment and staying true to what you mapped in the project ultimately protects the client who is engaging with you for your service.
Mike: Is this process something you’ve developed over time, or did you always work this way?
Clay Martin: Did we develop it over time, or did we always work this way? It’s based in, if you go all the way back in my history anyway, and most engineers and problem-solving folks would say this, a formulaic way of solving problems.
That goes all the way back to school: setting up equations, listing your knowns, and so on. There’s a basis in that, in the fundamental principles of engineering and even in building a house. There are stages to doing things.
Ours became somewhat exclusive to the language we use because we took the generality of a stage-gated approach and got a little more specific. We used a vernacular that we relate to, and we found that our clients relate to it as well: discover, define, design, build, and deliver.
Those words, even without an elaborate additional description, kind of tell the story, as opposed to stage one, stage two, stage three, stage four, and stage five. By naming them and using that language in common communication with the client, we find our clients respond to and use the same language we use.
Discover makes a lot of sense. We’re unearthing, discovering, learning, and understanding what the problem is. Then we’re defining how we’re going to approach solving it. Then we’re going to design the solution.
Build and deliver make sense because whether they’re building it or we’re building it, it’s getting built. It’s getting tested, prototyped, and evaluated against the requirements you established in the early part of the program.
Then there is deliver. What does delivery mean? Are we supplying the finished product? Sometimes. Are we supplying the manufacturing and engineering data for someone else to supply the product? Sometimes.
So there’s a definition at the end that can move a bit in terms of what delivery means. Sometimes our delivery is an electronic representation, along with verbal explanations, spreadsheets, and so on, of a solution to a problem without any CAD.
Delivery and design can take different forms, but the framework of the five-stage process fits virtually everything.
Mike: Great answer. Great answer.
Clay Martin: I hope so.
Mike: It really was. I mean it. When you said that instead of calling it stage one, two, three, four, and five, you name the stages, that really helps. Just going through everything we were going to talk about today, I kind of halfway understood it. I mean, not really, but at least it gives you a clear picture.
Clay Martin: Right.
Mike: It clears up all the expectations.
Let’s say here I am, and I’m super smart, which I’m not, and I came up with this great idea. I’m ready to go. Clay, how do you explain this process to a client who just wants to get started?
Clay Martin: That’s a great question. I usually start, and our team usually starts, fairly simple. We use a bullet-pointed description of the five-step process because it resonates with experienced and seasoned product developers and program managers, but also with the layperson, someone who may have never designed anything before.
Discover means we understand the current state, the constraints, and the opportunity. That seems to resonate and make sense.
Define means we define what done looks like and align the scope and outcomes. We build that roadmap.
Design means we develop the right solution using the right pieces. As I said earlier, what disciplines, materials, approaches, organizations, and partners do we need to have in place to design the solution?
Build means we execute, test, and improve to optimize. You have to build things. You may be building them in the virtual world for a while and using technologies like FEA, finite element analysis; CFD, computational fluid dynamics; and other multi-physics solvers.
So there’s a virtual world you can build in, and then there’s the physical world you build in, where the rubber always meets the road. You build the design, test it, and evaluate it. Especially for mass commercialization, you’re going to test the heck out of it. You’re going to put thousands of hours on it. You’re going to leave it in the sun, get it wet, break it, and figure out when and where it breaks, and why it breaks.
Then you deliver in the real world. We always say we design for the real world. We develop solutions for the real world because we know what done looks like. We understand what a manufactured, produced part should look like, and we take that into consideration. We know what an elegant solution looks like.
So if I’m describing the five-step process to someone, or explaining how we engage and get started, we get started by starting in that first step: discover. Even in our first meeting, before we’ve quoted the project, we want to learn a little more about why we’re talking.
What do you need help with? What are you trying to solve?
Almost always, because of our initial naivete to the situation, we’ll unearth something. We’ll ask questions that maybe they haven’t thought to ask yet because they’ve been so buried in the woods with the trees. We’ll ask questions, get more familiar, apply our experience and knowledge, and dig deeper into the issue they’re trying to solve.
Mike: Perfect. Does every project go through all five stages fully, or do you have flexibility with that?
Clay Martin: Fundamentally and theoretically, that’s a great question. Do all projects go through the five-step process? The framework or ideology of it is considered on every project. You look at it and ask, “Where does this fit?”
There is almost always, I would say ninety-nine percent of the time, a discover and define aspect. No matter what you’re doing, you need to understand what you’re doing and why.
Maybe a client comes to us and says, “We have a dash component that needs to be modified.” What needs to be modified about it? Well, it has a highly organic Class A aspect to it. It’s made out of injection-molded plastic, and so on.
You learn all those things, and you start thinking, “Okay, these are the disciplines we need to be proficient in. These are the resources we’ll use. This is how we’ll stage it out.” We’re going to define what all of that is.
But by the time you get to design, build, and deliver, that’s where the flexibility comes into place. Maybe you’re only taking it to the design aspect. You’re not going to build something. You’re not going to deliver the final product. You may not even be working with the production suppliers to help finalize production designs. You may just be getting the client to the stage of design, and we’ll stop at that point.
Sometimes, we’re just asked to build things. The client comes and says, “Here’s the design. Here’s the drawing pack. Can you construct this for us?”
Certainly, if it’s fully defined and you’ve performed those earlier stages in your business, and you’re asking us to manufacture something for you, we can definitely deliver at that stage.
For clients that use an element or form of a staged approach, or who are just going through product development in general, from an idea to something that will ideally be commercialized, we may just be fitting into one piece of that process and supporting them in the way they need support, while adhering to their process.
But for whatever piece we pull out and own on our side, we’re going to apply our mentality to it to make sure we understand the issue and the solution.
Mike: That’s perfect. That’s a great answer. So even on what you guys consider the simplest of projects, you still give them the full autonomy on that.
Clay Martin: Yep. Yep.
Mike: Look at me using big words.
Clay Martin: I think you went to maybe four or five syllables there. That was pretty good.
Mike: I know. I don’t know many of those.
Well, that was awesome. That kind of described your process. I think that over the next few podcasts, what we’ll be doing here on The Design Orchestrator is breaking that down a little bit and discussing what each one of those steps includes, if that’s all right with you.
Clay Martin: Yeah, one hundred percent.
Mike: All right, Clay. Thanks for joining me today. This was a very cool thing to learn. Even though it seems like common sense, a lot of people, like you said, probably let their over-anxiousness get them to skip steps. Hey, look at that big word.
Clay Martin: Yeah, yeah. One hundred percent. Anything I can do to help. We love sharing the information we’ve compiled and our method for applying the experience we’ve gained over a lot of years of doing this.
Mike: Perfect. Well, once again, thanks for joining Clay and me on The Design Orchestrator. I look forward to talking to you again, my friend.
Clay Martin: Same to you. Have a good night, buddy.
Mike: Take care.