--- sourceDocument: Xanadu Platform Analytics sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/xanadu/now-intelligence Release : - xanadu ft:locale : - en-US ft:publication_title : - Xanadu Platform Analytics ft:clusterId : - par bundleId : - par workflow : - Platform --- # Planning your indicators # Planning your indicators {#ariaid-title1} * Release version: Xanadu * * Updated August 1, 2024 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read Before creating an indicator, clarify what goals you wish to attain with the indicator. Ask these questions before you create an indicator: * What * What do you want to measure? Are you basing what you want to measure on progress towards a business goal? Consider starting with a business goal and then deciding what to measure. You can use [KPI Composer](https://servicenow-prod.fluidtopics.net/kFzGBJTE7vDxg2iyx8mfeQ "KPI Composer ensures that your performance management strategy aligns with business goals and has support from executive sponsors. Use KPI Composer to bridge the gap between defining your performance measurement strategy and the realization of that strategy from within Performance Analytics. Start with your business goals and plan all your components through indicators up to the final dashboard.") to help you. Do you want a simple count, like the number of open incidents, or something more sophisticated, like the average age to close an incident? * Is more better or is less better? For example, you would want the number of open incidents to be as low as possible, but the number of sales to go up. * What factors contribute the most to this number? * What factors would skew this number? Seasonality? A shift in staffing numbers or composition? * What will you do if the number goes from good to bad? {#planning-indicators__ul_e1b_1lc_hhb} * Who * Who is responsible for this indicator? A request fulfiller? A manager? * Who should not see this information? {#planning-indicators__ul_pxn_dlc_hhb} * Why * What is the next question you will ask? For example, once you know the number of open incidents, you may want to know what percentage of them has been open for more than 30 days. * Does this number predict what will happen or show what did happen? {#planning-indicators__ul_jlq_glc_hhb} * How * Do you measure this today? * If Yes, what do you do with it? * If No, why not? {#planning-indicators__ul_kxf_jlc_hhb} * When * How fast does the data change? * What is a meaningful period to look at? Are daily changes meaningful or too noisy? How much time does it take to establish a real trend? {#planning-indicators__ul_znt_klc_hhb} * Is there already an indicator that matches my use case, or do I have to build my own? * Has the Platform Analytics Solution for the subject area been installed? These solutions contain indicators for many common use cases. * In the indicator list, is there an indicator that matches, or comes close to matching, your requirements? Can I duplicate an existing indicator and tweak it? * Can I create a formula indicator from existing indicators that will meet my requirements? {#planning-indicators__ul_c2d_33r_m3b} {#planning-indicators__ul_e4q_xkc_hhb} **Related concepts** * [Analytics solutions](https://servicenow-prod.fluidtopics.net/6iRS~pr703nGYj5VqRFeRA "Prepackaged solutions featuring Platform Analytics dashboards with data visualizations and Performance Analytics indicators (KPIs) are available for many ServiceNow products. Use these solutions to get started quickly.") * [Design your Performance Analytics solution with KPI Composer](https://servicenow-prod.fluidtopics.net/kFzGBJTE7vDxg2iyx8mfeQ "KPI Composer ensures that your performance management strategy aligns with business goals and has support from executive sponsors. Use KPI Composer to bridge the gap between defining your performance measurement strategy and the realization of that strategy from within Performance Analytics. Start with your business goals and plan all your components through indicators up to the final dashboard.")