Data maturity is sometimes presented as a score out of five. A single score is convenient, but it can hide the difference between a strong finance reporting process and a customer data process held together with spreadsheets. Assess maturity where actual decisions are made.
Walk through one real information journey
Pick a recurring question such as “Which products were profitable last month?” Follow it from the transaction system to the report used in the meeting. Record the handoffs, manual corrections, people involved and points where two teams disagree. This short journey often reveals more than a broad technology inventory.
Look at five dimensions. Availability: can authorized people obtain the required data? Quality: are key fields complete and plausible? Consistency: do teams use the same definitions? Timeliness: does information arrive before the decision? Accountability: who fixes an error and who approves a metric change? Each dimension needs evidence, not a confidence rating alone.
Separate symptoms from causes
A late dashboard may be blamed on the BI tool when the source system closes transactions two days after month end. Two different revenue numbers may reflect different refund rules, not a broken pipeline. Write the observed symptom, likely cause and owner beside each finding. When uncertain, mark it for investigation rather than turning a guess into a transformation project.
Turn the assessment into a short plan
Choose the two or three improvements that remove the most friction for the selected decision. One might be a customer ID reconciliation rule; another might be a documented definition for net sales. Establish a baseline, the person accountable and a review date. Repeat the journey after the change. Maturity means the organization can make a decision more reliably, not that it has purchased a more elaborate stack.
