Companies spend months, and sometimes years, developing a new product. Engineering works through the technical challenges, samples are evaluated, safety and performance testing is completed, and manufacturing prepares for production. Once everyone is comfortable with the results, the company declares the product ready for launch.
Then orders don’t come as quickly as expected. Sales struggles to explain the value, customers raise questions nobody anticipated, and the channel continues selling products it already understands. When orders finally arrive, installation or support issues begin consuming more time than the financial plan allowed.
The natural reaction is to question the product. Was the price too high? Did it have the wrong features? Did a competitor get there first? Any of those things may contribute, but sometimes the real problem is more fundamental. The product was ready, but the company wasn’t.
I have seen versions of this problem throughout my career in lighting product development, sales, global manufacturing, and commercialization. A company can develop a technically strong product and still be unprepared to bring it to market. Product readiness and company readiness are two different milestones, and confusing them can turn a good investment into a disappointing launch.
Product Readiness Is More Than Completing the Design
When a company says a product is ready, it usually means the engineering work is complete. The design has been released, the bill of materials is approved, the product performs as expected, and the factory can manufacture it. Reaching that point matters, but it only confirms that the company can build the product.
It does not confirm that the market wants it or that customers have a compelling reason to change. It also does not prove that sales can explain it, the channel can specify it, contractors can install it, or the company can support it after the order.
Lighting makes this distinction particularly important because a lighting product rarely operates on its own. A luminaire, LED driver, control, sensor, or connected system becomes part of an electrical system, a lighting design, a building environment, and an ongoing maintenance plan. The person who approves the purchase may never install the product, commission it, operate it, maintain it, or experience the light every day.
That is why I practice human-centered product development. The process begins by understanding the problem from the perspective of the people affected by it, but it does not end with an initial customer interview. A development team has to understand the entire product journey and the different people who influence whether the product succeeds.
A lighting designer may focus on photometric performance, color quality, glare, controls, and how the product supports the intended space. An electrical contractor may care more about mounting, wiring, labeling, access, installation time, and clear instructions. The representative and distributor need to know how to position, quote, configure, and order it. The facility manager needs confidence in training, system access, replacement parts, maintenance, and long-term support.
Each participant has a different definition of value and a different view of risk. If one person in that chain cannot confidently do their part, the weakness eventually reaches the customer.
Customers Need a Reason to Change
A strong product is not automatically a strong market opportunity. Customers rarely change suppliers, specifications, systems, or installation practices simply because a new product is available. They change when their current situation creates enough cost, frustration, risk, or lost opportunity to justify doing something differently.
Product teams can lose sight of that when they become too focused on features. A new driver may be smaller, more efficient, programmable, or easier to integrate. A luminaire may deliver better optical control, color performance, serviceability, or energy savings. A connected system may provide more data and functionality, but none of those improvements automatically answers the customer’s most important question: Why should I change what I am doing today?
Geoffrey Moore explores this challenge in Crossing the Chasm. Early adopters may accept complexity because they recognize strategic value in being first, while mainstream customers generally want evidence, predictable performance, lower risk, and confidence that support will be available. The technology may be the same, but the decision process is different.
That lesson applies directly to lighting. The development team may be excited about what the technology can do, while the customer is thinking about specification risk, compatibility, labor, training, project schedules, callbacks, and warranty exposure. Both perspectives matter, but the customer’s concerns determine whether adoption moves beyond a few early projects.
Human-centered development requires more than asking customers whether they like an idea. It requires observing how they currently solve the problem, understanding what would make them change, and testing whether the new product makes their work easier or adds another layer of complexity.
I have learned more by visiting job sites, listening to contractors, working with sales teams, reviewing warranty issues, and seeing products used in the field than I could learn from an internal presentation. Real applications expose problems and opportunities that are difficult to see when everyone involved already understands how the product is supposed to work.
The Channel Must Be Ready to Carry the Product
A product may make complete sense to the team that developed it and still be difficult for someone else to sell. Engineering and product management have lived with the project for months, so they understand every decision, feature, and tradeoff. A representative, distributor, or salesperson may have only a few minutes to determine where the product fits and why a customer should consider it.
If that explanation requires an engineer on every call, the company is not ready to scale the launch. Technical support will always have an important role, but the channel should be able to recognize the right opportunity and explain the core value without translating an engineering presentation.
Channel readiness involves more than preparing a product brochure or conducting one training session. The sales organization needs to know which problem the product solves, which applications fit, how it compares with the customer’s current approach, and when it should not be recommended. It also needs samples, specifications, pricing, lead times, application guidance, and a clear process for getting technical questions answered.
This is especially important in lighting markets that depend on specifications, independent representatives, distributors, contractors, and other influencers. Each participant helps create demand and reduce the customer’s risk, but each additional step also creates another point where an opportunity can stop. A missing specification file, an unclear quotation, an unavailable sample, or a delayed technical answer can remove a product from consideration before purchasing becomes involved.
Effective training should therefore focus on actual applications rather than a list of features. The salesperson should be able to qualify the opportunity, the representative should understand how the product fits the project, and the distributor should be able to order the correct configuration. They should also recognize applications that require additional engineering or commissioning support before committing to the customer.
The Real Test Begins After the Order
Winning an order does not prove that the company was ready for the product. In many cases, it is the first time every part of the organization has to work together under an actual customer deadline.
The order must be entered correctly, manufactured consistently, packaged appropriately, and delivered when promised. The product then has to be installed under field conditions that may differ from the assumptions used during development. If something does not work as expected, the customer needs a clear answer and an accountable person who can resolve the issue.
Connected lighting and control products increase this responsibility. Beyond the physical product, the company may have to support configuration, programming, system integration, cybersecurity, commissioning, software updates, and long-term compatibility. These obligations continue long after the initial shipment.
Current guidance from the Illuminating Engineering Society reinforces the importance of looking at the complete system. ANSI/IES LP-6-25 addresses the characteristics, selection, specification, and use of lighting control systems. ANSI/IES LP-16-22 focuses on documenting control intent and sequences of operation so the design can be communicated to construction and commissioning teams, while ANSI/IES LP-8-20 addresses commissioning against the owner’s project requirements.
The practical lesson is that a lighting control product does not succeed simply because devices communicated during laboratory testing. The design intent must be understood, the sequence of operation documented, and the installed system must perform as the owner expected. Delivering that result requires coordination across product management, engineering, sales, project management, installation, commissioning, and service.
A human-centered process continues through each of those steps. The development team should consider what the contractor experiences when opening the box, whether the labeling and instructions make sense in the field, and whether the commissioning technician understands what the system is expected to do. It should also consider how the facility team will operate the system after the project team leaves and what happens when a component must be replaced several years later.
Those issues are sometimes treated as operational details outside the product-development process. From the customer’s perspective, however, they are part of the product and part of the value the company promised to deliver.
Connected Products Create Long-Term Obligations
Lighting products are becoming systems that include software, sensors, wireless communication, data, remote management, and building integration. These capabilities can create substantial value, but they also introduce responsibilities that a traditional product-launch plan may not fully address.
The DesignLights Consortium maintains a Qualified Products List for networked lighting control systems from dozens of manufacturers. Qualification provides an important structure for reporting and evaluating system capabilities, but it should not be confused with complete commercial readiness. A qualified system can still be difficult to specify, install, commission, or support if the organization behind it has not built the necessary capabilities.
Interoperability expectations are also increasing. Matter, developed through the Connectivity Standards Alliance, is improving setup and coordination across connected-device ecosystems, primarily in residential and related Internet of Things markets. Commercial lighting has different code, project, commissioning, cybersecurity, and lifecycle requirements, but customers increasingly expect connected products to work reliably without becoming more difficult to manage over time.
Signify reported that its installed base reached 167 million connected light points at the end of 2025. That scale demonstrates how far connected lighting has progressed, but it also highlights the growing responsibility to support software, security, compatibility, system access, updates, and replacement throughout the product lifecycle.
A company entering the connected-lighting market needs to assign ownership for those responsibilities before launch. If product management, engineering, sales, and service cannot agree on who owns the customer after installation, the customer will eventually discover that gap.
The Financial Model Must Include the Cost of Serving the Customer
A product can produce revenue and still fail to create an acceptable return. The initial financial model typically includes material, manufacturing labor, freight, channel discounts, and the expected selling price, but those numbers may not reflect the full cost of commercialization.
Training, samples, application engineering, certification, field support, commissioning, returns, warranty reserves, replacement inventory, software maintenance, and product obsolescence can materially change the economics. The cost is even greater when normal sales and service questions repeatedly require engineering or executive involvement.
These demands do not always appear clearly on a product-level income statement. They show up as slower response times, distracted employees, reduced support for existing customers, and margins that look better in a spreadsheet than in practice.
Verne Harnish’s Scaling Up focuses on people, strategy, execution, and cash as companies grow. The same discipline applies to product commercialization because growth can create pressure rather than value when the organization lacks the people, processes, and working capital to support it.
Leadership should evaluate the financial model based on how the company will actually serve the customer. If the projected margin only works when every order is correct, every installation goes smoothly, and nobody needs technical help, the model is incomplete.
Five Questions That Reveal Whether the Company Is Ready
Over time, I have found it useful to review commercialization across five connected areas. This is not a replacement for a formal development process or technical quality system. It is a practical leadership review designed to identify organizational gaps before customers find them.
Is the product ready for real use? Laboratory performance is only part of the answer. The company should confirm that performance claims are supportable and that manufacturing consistency, packaging, installation, field conditions, compliance, serviceability, and replacement have been addressed.
Is the market ready to change? The product must solve a problem that customers consider important enough to act on. Positive feedback is useful, but observed behavior, field testing, purchasing interest, and early project experience provide stronger evidence.
Is the channel ready to sell it correctly? Salespeople and channel partners should understand the right applications, customer value, configuration, pricing, and limitations. They also need the tools and internal support required to move an opportunity forward without creating expectations the company cannot meet.
Are operations ready to deliver the complete experience? Manufacturing and logistics are only part of this question. The company also needs clear ownership for installation support, commissioning, technical escalation, warranty, software, cybersecurity, replacement, and long-term service.
Do the economics support the complete business model? Margin must cover more than the physical cost of the product. Leadership should account for the actual expense of training, supporting, maintaining, replacing, and improving the product throughout its expected life.
The Company Is Part of the Product
Every part of the review should include one additional question: What happens to the customer and each channel participant when something does not work as planned? Looking at failure from their perspective often reveals more risk than another internal launch checklist.
The strongest product-development organizations do more than move an idea through engineering. They connect customer insight, technical development, manufacturing, sales, service, and financial discipline from the beginning, with each group understanding the experience the company has committed to deliver.
This does not mean every possible issue must be solved before a product reaches the market. Waiting for perfection can be as damaging as launching too early, especially when a controlled field launch can generate the information needed to improve the product and the supporting process.
The right early customers and channel partners can expose gaps while the company can still respond. Their feedback should reach engineering, operations, sales, and leadership quickly so that the organization learns as one team rather than treating every field issue as an isolated problem.
In my experience, the strongest launches happen when commercialization is treated as a shared responsibility. Engineering does not simply hand the product to sales, sales does not make promises that operations cannot fulfill, and product management does not disappear after launch.
A product is ready when it performs as designed. The company is ready when it can repeatedly deliver the value that product was designed to create, even when field conditions are not perfect and the customer needs help. The market ultimately evaluates both, which is why completing the product is only part of completing the job.