What gets established during Define that protects the client later? According to Clay Martin, CEO and president of One3 Design, the Define stage establishes a product requirements document, functional specs, target cost, target volume and the key constraints for the Design stage, along with an agreed picture of what “done” looks like. That written agreement protects the client because, in Clay’s words, “any change down the road is a visible change. It is not a hidden one.”
Clay explained it to host Mike Downer in Episode 4 of The Design Orchestrator, the podcast from One3 Design, a product development firm whose system definition and engineering services start from these requirements. Define is the second of the five stages in One3’s process, after Discover and before Design, Build and Deliver.
What Does the Define Stage Establish?
The Define stage establishes the written requirements that every later stage is measured against, refined from what the team learned in Discovery, the stage before any CAD work.
Clay explained that Define turns the information gathered during Discover into actionable project requirements: functional specifications, a target cost, a target volume and the key constraints that drive the Design stage.
Most importantly, the team establishes what a completed product should accomplish. “When we can build that vision for what done represents, then we can assign our resources,” Clay said.
Why Is the Product Requirements Document the Client’s Safeguard?
The product requirements document (PRD) is the client’s safeguard because it puts in writing exactly what will be built and what it will cost.
Clay called it “essentially the contract for what’s being built and what done looks like,” and the binding agreement that says, “When we deliver on the definition described here, this is the cost.”
Depending on the product, the PRD may identify:
- Materials, textures and physical characteristics
- Functional and performance requirements
- Environmental resistance, including UV exposure
- Testing and validation expectations
- Applicable industry standards
- Target costs and production quantities
These specifications establish measurable expectations for the Design and Build stages. “The level of validation at the Design stage and the Build stage will be defined by these parameters,” Clay said.
Writing requirements this way matches NASA’s guidance on how to write a good requirement, which asks for requirements that are clear, unambiguous and verifiable, and that state what is needed without prescribing how to provide it.
For clients, the PRD becomes a reliable reference whenever questions arise about deliverables, responsibilities or project expectations. Our step-by-step guide explains how to write a product requirements document for a physical product.
How Does Define Prevent Scope Creep?
Define prevents scope creep by giving both sides an agreed path, so any deviation from it can be seen, named and priced.
Scope creep occurs when additional features, requirements or responsibilities enter a project beyond its original agreement.
Clay explained that the requirements document makes these deviations easier to identify and to sort: was a change “a necessary deviation caused by the results of some element of evaluation during the Design process, or was it the customer changing their mind?”
For example, a client might request additional functionality after the design process has already started. Although the change may be reasonable, it could require additional engineering, testing or production resources.
The development team can then explain how that request affects the original scope and pricing. Clay said his team is “very gentle but assertive” about it and is happy to evaluate an alternative, as long as everyone acknowledges that “this is going to be a change in scope and potentially a change in price.”
Clay compared this situation to constructing a house. When homeowners request modifications beyond the approved plans, those changes typically require additional costs and revised agreements.
Instead of allowing changes to accumulate unnoticed, Define establishes boundaries that protect both parties.
How Does Define Make Cost Estimates More Accurate?
Define makes cost estimates more accurate because the requirements are locked, so the team is pricing “a scoped project rather than an open-ended concept,” as Clay put it.
Estimating development costs becomes difficult when a product exists only as an idea.
During Discover, teams explore possibilities, evaluate objectives and investigate potential solutions. However, many details remain uncertain.
Define narrows those possibilities into a clearer project scope.
Clay explained that preliminary sketches and computer-aided design models can help clients and developers establish a shared understanding of the intended product.
Although Define cannot eliminate uncertainty, it reduces the ambiguity that frequently contributes to inaccurate budgets and unexpected expenses.
Can Requirements Change After Define?
Yes, requirements can change after Define, but Clay said “it requires acknowledgement by all parties involved to go back and revisit the roadmap.”
Clay acknowledged that product development involves continuous learning. Testing might reveal performance limitations, unexpected material behavior or technical challenges requiring reconsideration.
When discoveries affect approved requirements, the team must discuss the implications with the client before proceeding.
One3 Design also uses stage gates to determine whether essential questions have been resolved before advancing.
This structured approach reflects recommendations in the NASA Systems Engineering Handbook, which calls for late requirement changes to be carefully evaluated for their impact on cost, schedule and technical design.
Clay also stressed the importance of resolving disagreements through collaboration. By returning to the original requirements document, clients and developers can clarify expectations and determine whether revisions are necessary.
Where Can You Watch Episode 4 of The Design Orchestrator?
Episode 4, “What Gets Locked In During the Define Stage of Product Development?”, is on YouTube and on podcast platforms under The Design Orchestrator. Watch Episode 4 on YouTube to hear Mike and Clay explain how One3 Design establishes requirements, manages client expectations and keeps every scope change visible.
Frequently Asked Questions
What gets established during Define that protects the client later?
Define establishes a product requirements document, functional specs, target cost, target volume, the key constraints and an agreed picture of what done looks like. Because that agreement is in writing, any later change is visible and can be discussed and priced instead of slipping in unnoticed.
What is the Define stage in product development?
Define converts discoveries and initial ideas into documented product requirements, technical specifications, cost targets and measurable project objectives.
How does Define prevent scope creep?
It establishes an agreed-upon project scope, making additional requests or deviations easier to identify, evaluate and price appropriately.
What is scope creep in product development?
Scope creep is the gradual addition of features, requirements or responsibilities beyond what a project originally agreed, often through a series of “what if” requests made after work has started.
What is the main deliverable of the Define stage?
The product requirements document outlines the agreed specifications, expectations and conditions for completing development work.
Can product requirements change after Define?
Yes. Requirements can change when testing, technical discoveries or client needs justify revisions. Both parties should acknowledge the implications.
Why does Define improve cost estimates?
Defined requirements reduce uncertainty, allowing development teams to estimate necessary engineering resources, testing activities and project costs more accurately.
What happens when clients skip Define?
Skipping Define increases the likelihood of misunderstandings, uncontrolled changes, inaccurate estimates and unnecessary development work. Clay Martin’s answer is to push back “assertively and professionally,” because without locked requirements “you’re flying blind.”
How does One3 Design resolve disagreements about project scope?
The team reviews the agreed requirements document, discusses differing interpretations and determines whether clarification or formal changes are necessary.
Mike Downer: Hello, everybody. Welcome to The Design Orchestrator. It is a podcast about how products actually get built, from the first idea on a whiteboard to the finished product rolling off the line.
This show takes you inside the process that most people never get to see. I am your host, Mike Downer. I’m joined once again by Clay Martin, CEO, president, and just all-around good guy. Clay Martin, what’s going on?
Clay Martin: Not much, Mike. Good to see you again, brother.
Mike Downer: It’s good to see you too, buddy. I always have fun with these. This is just such an interesting podcast. I don’t care who you are. If you’re not interested in this, then I don’t know what you’re going to be interested in because this is how everything starts, from an idea in somebody’s head to the finished product.
I mean, look at that cup you’re drinking from. Somebody had an idea to put a lid on a cup, and somebody had to think about it.
Clay Martin: There you go. There you go.
Mike Downer: I had to promote your new cup. I’m happy with the new cup. It looks great. You see how I got that in there?
Clay Martin: It works really well.
Mike Downer: So, we’re going to start at the beginning. Last time, we talked about all the different stages you go through and the process you’ve developed. Today, we’re going to get into what gets locked in during the Define stage of product development.
What actually goes into Define? What does Define actually lock down? Why does that protect the client from scope creep and any surprises later? So, what specifically gets defined during this stage, Clay?
Clay Martin: What gets defined during the Define stage? To remind everyone, the full gamut is Discover, Define, Design, Build, and Deliver.
Define is one of those early upfront stages that allows us to mitigate risk and gain greater certainty in terms of the work we’re going to be doing after this stage.
During the Define stage, we’re moving from Discover and taking the information we gathered during that evaluation, discovery, and investigative process. We’re refining that down into a product requirements document, functional specs, target cost, target volume, and the key constraints that are going to drive the subsequent Design stage.
Very specifically, in Define, we’re also defining what “done” looks like. When we can build that vision for what done represents, then we can assign our resources and very tactfully go about executing on that.
Mike Downer: Very cool. So, how does this stage prevent scope creep later in the project?
Clay Martin: I would say it prevents scope creep because you’re building a document. It protects the project by creating an agreed-upon contract with the client that says we both believe, based on the information we have and the goals we have in mind, that progression toward this solution likely makes the most sense.
Now, we know there are going to be things that are learned, and hypotheses that may or may not prove to be correct. But that allows us to both agree early on that this is where the effort is going to be placed.
If we start to deviate from that, we can identify the deviation. Was it a necessary deviation caused by the results of some element of evaluation during the Design process, or was it the customer changing their mind?
The kind of scope creep that can really get a project off target is when you stray away from that agreed-upon path. That happens when you start creeping and doing the “what ifs.” We’ll be very gentle but assertive in saying, “This isn’t what we talked about. This isn’t what we agreed upon.”
We’re happy to evaluate another alternative, but let’s all acknowledge that this is going to be a change in scope and potentially a change in price.
Mike Downer: Yeah, you have to keep people on track. That’s true with anything, any job or any business. I like the fact that this stage helps, in layman’s terms, keep everything going down the road you planned on.
So, what documents or deliverables actually come out of the Define stage?
Clay Martin: The key document that comes out of the Define stage is what we call a requirements document. That is essentially the contract for what’s being built and what done looks like. It puts everything in writing and says, “This is specifically what we’ve all agreed to.”
For everything that can be documented, you want to capture it there. Based on the discussions we had in Discovery, maybe we know this is going to be a polypropylene plastic. Maybe we know this type of texture will be used. Maybe we know it has to be resistant to sun or UV damage.
The level of validation at the Design stage and the Build stage will be defined by these parameters. Maybe it’s long-term endurance testing. Maybe it’s assurance of compliance with a given industry standard.
We capture everything we can possibly know in that requirements document in terms of what is going to go into the design. It is also the binding contract with the client that says, “When we deliver on the definition described here, this is the cost.”
I would say it’s kind of like building a house. Somebody creates a plan for constructing your house and gives you an estimate for what it costs to build. If you deviate from that plan, it generally results in a change order and probably a check being written if it changes the plan.
So, deviation from that requirements document is what leads to scope creep. But that requirements document is also what keeps us all aligned and on track during the overall product development process.
Mike Downer: Very cool. So, how does Define set the stage for a more accurate cost estimate?
Clay Martin: How does Define set the stage for a more accurate cost estimate?
I would say the best thing Define does is establish exactly what I described: the requirements are locked. Now you have a scoped project rather than an open-ended concept.
When you are in the early stages of Discover, that is a time when you’re doing a lot of “what if.” You’re asking, “What is driving the direction of this product? What are our objectives? What are our initiatives? What’s important? What’s critical? What are we trying to achieve?”
You’re throwing a lot of stuff on the wall and seeing what sticks. But as you ideate through that, a clearer image starts to emerge of what can be developed that satisfies all those things.
As you get those things dialed in and the picture becomes more crystal clear, that helps mitigate the chance for scope creep. It also eliminates a lot of ambiguity that might exist with the client, who might otherwise have a different imagination for what their product would be versus what we, as the service provider, may have pictured in our heads.
You eliminate that ambiguity by saying, “Let’s get an agreement.” It may require some sketches and early preliminary CAD models to define a common vision, but we can all lock in on that and agree.
There is still a lot more fidelity to be added, so this is conceptual and hypothetical, but we should all agree that this captures, with as much accuracy as possible at this point, the description of what we’re working toward.
Mike Downer: There’s always that impatient person out there. Everybody has dealt with them. If you’ve been in business of any sort, there are people who want it now.
Clay, what happens if a client wants to skip the Define stage and jump straight into Design?
Clay Martin: What do we do when a client wants to skip the Define stage or cut it short? We assertively and professionally push back.
When you don’t have those locked requirements, you’re flying blind. The assumptions can shift. Things that weren’t identified and labeled early on can become new introductions to the project. Or you can end up in this parallel-path battle where you’re going in every direction because you don’t have that clear line of sight.
We remind them that this isn’t what we agreed upon. If we need to step back into Define or Discover and evaluate further to gain more clarity and resolution, we’re happy to do that.
But you really have to be true to the system. You have to honor what the system will do for you by staying true to those stages and the rules of those stages, so that creep doesn’t happen and so that inadvertent jump, or desired jump, to a subsequent stage doesn’t happen.
Mike Downer: That leads me straight into my next question. You did a great job answering that.
Like you said, you want to stay on track and keep everything where it is supposed to be: time, money, and everything else. Can requirements change after Define, or is it meant to be locked in permanently?
Clay Martin: Can the requirements change after Define? They certainly can.
The world of design can be a gray area. It’s all about discovering things. There is an element of discovery in every stage of design. You’re going to find things that you didn’t foresee, even with the best intentions and the best framework. There are still going to be things you uncover.
That’s the beauty of design, especially when you’re innovating and doing something new. You’re unearthing possibilities.
Sometimes you have to stop. Many times, you get into our proven process and determine, “Wait a minute. This changes the landscape a bit. We have to reestablish the foundation of what we’re trying to do.”
When that happens, you acknowledge it. You and the client come to an agreement on what that ramification is to the project. Do we pause, go back, and reopen a decision point?
That is also the protection that these stages offer. At the end of these stages are stage gates, where we define what needs to be solved or what conclusion needs to be reached before we progress further.
If we don’t know whether this product can withstand certain temperatures, move at a certain rate, withstand the environment it is placed in, or function correctly from a kinematic standpoint, sometimes you have to stop, pull in the reins, and rethink things a bit.
But you try to avoid that. You try to do the work upfront and do the diligence upfront so you have a clear path to the finish line.
So yes, requirements can change, but it requires acknowledgement by all parties involved to go back and revisit the roadmap.
Mike Downer: We’ve talked about how things can change and how sometimes pivots need to happen. Again, that’s part of life.
When that does happen, Clay, let me ask you this, and this is how we’ll wind this episode down today. How do you handle disagreements with the client about what should be in scope during this stage?
Clay Martin: How do we handle disagreements if the client has a different perspective on what should be included? A lot of times, it is a matter of perspective.
Ideally, you’re in a partnership with your client. You’re able to come back to the table and say, “Was this the understanding we both had? Help me understand why you may see that differently than what we originally agreed upon.”
That usually requires going back to the requirements document. When we illustrated this, signed it, and agreed to it, how did you interpret it?
Now, if it’s a client trying to pull a fast one on you, you’re going to run into situations where they try to creep things in a little bit. But most of the time, you’re working with good people who understand that, with all of our best efforts, we put that requirements document together to protect both of us.
When you put Define in place, any change down the road is a visible change. It is not a hidden one. That is the protection this stage gives the client.
We have the ability to go back to that document and say, “Let’s see how that read and how it was interpreted.” Then we can determine whether we can realign on it or whether we need to add new verbiage.
Without that, when you have a lot of general conversations upfront and say, “Yeah, we’ll probably get there,” memories get short. Days, weeks, and months go by. People forget what was talked about.
Even with the best intentions, we may all recall things a little differently. So we establish that contract early on to have a touchpoint we can always refer back to and ensure that we maintain alignment.
Mike Downer: Perfect. I appreciate it. You explained that stage to us and did a great job breaking it all down.
Maybe on the next podcast, we can break down one little piece of it and have the hard conversation about budgeting. We love talking money, don’t we?
Clay Martin: That’s where all the complications happen, right? When the money happens.
Mike Downer: Exactly. Maybe we’ll dig into that a little bit and see where that leads us. I love the rabbit holes we go down. It’s kind of fun.
Clay Martin: One hundred percent. Thanks, Mike.
Mike Downer: Thank you. Have a great afternoon, Clay.
Clay Martin: You too. We’ll see you.
Mike Downer: Bye-bye.
Clay Martin: All right.