Your goals and metrics will vary, depending on your organization's use case. Start by using the business challenges previously documented and the desired outcome that CSL was selected to solve. These considerations should have been made while aligning on a use case.
Next, specify your goal for addressing the business challenges: how will CSL alleviate the problem? Your goals should be measurable.
Common goals include:
Don't forget to also document "soft" metrics, such as customer satisfaction and employee confidence.
After identifying your goals, determine which metrics or key performance indicators (KPIs) measure success.
Before you deploy CSL, you must document your organization's "as-is" state. If you fail to establish baseline metrics, it will not be easy to measure whether CSL had a meaningful effect on your organization.
For example, if you're trying to reduce design time on a specific product, quantify how long it takes to design using your current method. In this example, consider the time it takes to design and optimize the product and the time required by the analysts. Then, once CSL has been deployed, track specific parts/assemblies that have been designated as "must use CSL" through their lifecycle to create the "to be" measurement. Once you have both numbers, you can compare them to calculate change.
Establishing your baseline metrics allows for clear articulation of how CSL met the business goals defined at the project start.
After you identify your goals and metrics, it's essential to document a detailed measurement plan.
The measurement plan should outline:
Example: Your company may be focused on increasing analysis throughput by decreasing the number of times engineering sends parts/assemblies to the Analysis team for full analysis. First, review past designs and the frequency/quantity of times analysis was requested. Also, look at the number of times the same Part or Assembly was re-sent for analysis. This will establish your baseline. Next, define what your future state should look like. One example could be to decrease the number of requests for analysis from Engineering by 25% within 3 months of making CSL available to design teams. Now, once you have deployed CSL, you can observe new designs and review the frequency of analysis requests.
Share the measurement plan with stakeholders early, and refer back to it throughout the project to ensure you're on track.
Have a question? Submit your contact information and we’ll reach out within 1 business day. You’re never obligated to purchase or commit.