Last updated · By the Clerk2Officer editorial team · Report a correction
Begin with a management decision
Business analytics uses data and analytical methods to improve understanding and decisions. It is more than producing charts or collecting large datasets. A useful analysis begins with a question, a decision owner and an action that could change. Without that connection, even a technically impressive report can become a recurring exercise with no operational effect.
A branch manager might ask why applications wait longer, whether service errors are rising or which intervention could improve completion. These are different questions requiring different evidence. Define the outcome, population, period and constraints before selecting a method. A measure of speed should be considered alongside quality and required controls rather than becoming the sole objective.
Analytics supports judgement but does not remove responsibility. Data can be incomplete, definitions can change and a model can fail in new conditions. A sound recommendation states what the evidence supports, what remains uncertain and how an action will be monitored. A dashboard is a component of that process, not a substitute for it.
Descriptive analytics
Descriptive analytics summarises what happened. Examples include daily transaction counts, application completion rates, error frequencies and balances by product. Totals, averages, distributions and trends can help establish a baseline. The usefulness of a summary depends on the correctness of its definitions and the completeness of the underlying records.
An average turnaround of two days can conceal a large group completed immediately and a smaller group delayed for weeks. Examine the distribution and relevant segments rather than only the mean. A median or percentile can answer a different operational question, but should be labelled clearly. Do not compare unlike measures as if they were interchangeable.
Descriptive results do not explain causes by themselves. A rise in complaints after a process change can motivate investigation, but other factors may have changed too. State the observed association first and distinguish it from any causal interpretation. This discipline prevents a familiar chart from supporting an unjustified conclusion.
Diagnostic analytics
Diagnostic analytics investigates why an outcome occurred. It can involve segmentation, process mapping, exception review and comparison of related measures. The aim is to identify plausible mechanisms and test them against evidence. A correlation is a clue, not automatic proof of causation.
Suppose delays are concentrated in applications missing a particular document. Check whether the missing information actually causes rework, whether staff guidance differs and whether customer or product mix explains the pattern. Simply naming the segment does not identify the remedy. Review the process and consider alternative explanations.
Diagnosis should distinguish a data artefact from a real change. A new system may record waiting time differently, or a backlog cleanup may temporarily increase completed cases. Reconcile definitions and operational events before attributing the movement to employee performance. Poor diagnosis can produce actions that worsen the original problem.
Predictive analytics
Predictive analytics estimates future or unknown outcomes using observed relationships. Forecasting demand, estimating default probability and identifying likely service demand are examples. A prediction is conditional on its model, inputs and context. It does not establish that the predicted outcome will occur or that the model explains the underlying cause.
Separate development and evaluation data appropriately. Information that becomes available after the prediction date should not be used as though it were known at the decision. Such leakage can make testing look excellent while producing weak operational performance. Time, related records and repeated customers may require careful evaluation design.
Evaluate predictions using measures suited to the task. A fraud classifier needs more than overall accuracy, while a demand forecast should be assessed for errors that matter to capacity planning. Compare with a simple baseline and consider the cost of acting on errors. A more complex model should demonstrate useful improvement, not merely novelty.
Prescriptive analytics
Prescriptive analytics recommends actions under objectives and constraints. It can use optimisation, simulation or decision rules to compare alternatives. Staffing a service desk, allocating scarce processing capacity or selecting a feasible project combination can fit this category. The objective must represent the business responsibility rather than only an easily measured proxy.
For example, minimising waiting time without a quality constraint could encourage staff to close cases prematurely. A better model includes service, accuracy, capacity, authority and fairness requirements relevant to the task. Constraints are not inconveniences to ignore after optimisation; they define which actions are feasible.
Recommendations require implementation judgement. A mathematically optimal schedule may be fragile to absences or impossible under employment arrangements. Test sensitivity and operational practicality, and provide a fallback. The model should help a manager understand trade-offs rather than conceal them behind one recommended number.
Elements of an analytics workflow
Define the problem, identify relevant data, establish definitions, assess quality, analyse, validate, communicate and act. These stages interact: analysis can reveal that a required field was never collected, or validation can expose an unsuitable target definition. Record the decisions so the work can be reviewed and repeated.
Data preparation often requires joining records, standardising units, handling missing values and identifying duplicates. Each transformation can change results. Keep provenance and explain exclusions. Removing difficult records simply because they weaken the desired conclusion is not legitimate cleaning.
Communication should connect the finding with an action and its limits. Use a clear chart or table where it improves understanding, but include the denominator, period and relevant definitions. A reviewer should be able to distinguish observed values, forecasts and assumptions without guessing from colours or presentation style.
Data definitions and quality
An observation is a recorded unit such as a transaction, case or customer-period. Variables describe its attributes. The choice of unit affects aggregation and interpretation. Counting transactions is different from counting customers, and neither is automatically a measure of visits or meaningful engagement.
Quality includes accuracy, completeness, consistency, timeliness, uniqueness and fitness for purpose. A field can be technically complete but systematically wrong. Missing data can reflect process differences or selection, not random absence. Investigate the cause before filling values with a convenient average or excluding the records.
Use a data dictionary defining each field, unit, source and allowable values. Agree how reversals, cancellations, reopened cases and late updates are treated. Otherwise different departments can produce incompatible versions of the same metric. Clear definitions are often more valuable than adding another analytical tool.
Measures, denominators and rates
A rate requires a suitable denominator. If 40 applications contain errors out of 1,000 reviewed applications, the observed error rate is 4%. Dividing by all website visitors would answer a different and usually unsuitable question. State the eligible population and whether one application can contribute multiple errors.
Compare periods on a like-for-like basis. A rise from 100 to 150 transactions is 50%, but it may reflect more operating days or a changed product mix. A fall from 150 back to 100 is 33.33%, because the base differs. Percentage changes should always identify their starting value.
Distinguish percentage points from percentage changes. An error rate rising from 4% to 5% increases by one percentage point and by 25% relative to its original rate. Both statements can be correct, but they communicate different quantities. Reporting them accurately prevents exaggerated or understated interpretations.
Funnel analysis
A funnel tracks a defined sequence, such as landing on a page, starting an application and completing it. If 1,000 eligible users begin at the first stage, 200 reach the second and 80 complete, overall completion is 8% of the first stage. Completion from the second stage is 40%. The denominator determines the question answered.
A simple sequential funnel assumes stages refer to a consistent cohort and time window. Counts collected independently from different populations cannot automatically be divided into a meaningful conversion rate. Users may return, use multiple devices or complete outside the selected period. Define how those cases are handled.
Drop-off identifies where investigation may be useful, not necessarily why users left. A technical error, confusing content, ineligibility or a deliberate decision can all produce abandonment. Combine event data with appropriate operational evidence and user research before choosing the remedy. Do not assume every lost user should be pushed to complete an unsuitable action.
Cohorts and retention
A cohort groups observations by a shared starting event or characteristic, such as registration month. Retention measures later activity for that defined group under a stated rule. Comparing cohorts can reveal changes hidden in aggregate totals, especially when rapid acquisition makes total activity rise despite weak repeat use.
Suppose 100 customers join in January and 30 meet the defined activity condition in February. February retention for that cohort is 30%, assuming complete eligible observation. It is not the same as February active customers divided by all customers ever registered. Define the starting event and qualifying return action.
Allow enough observation time. A recently acquired cohort cannot yet have six-month retention. Product changes, acquisition channels and customer mix can also affect comparisons. Retention analysis is strongest when it separates these factors and avoids interpreting incomplete periods as a deterioration.
Big data analytics
Big data commonly refers to challenges involving scale, speed, variety and related issues of reliability and value. Large volumes can support richer analysis but also increase storage, processing and governance needs. More records do not automatically eliminate bias or compensate for an unsuitable measurement process.
Structured transaction tables, semi-structured logs and unstructured text require different preparation and methods. Combining them can create useful context but also inconsistent identifiers and definitions. Consider security, retention, access and the legitimate purpose of the analysis before centralising data merely because it is available.
Choose architecture proportionate to the decision and actual workload. A small, well-designed dataset can answer many management questions without expensive infrastructure. Streaming or distributed systems are justified when requirements demand them, not because the phrase big data sounds advanced. Operational reliability and maintainability remain important.
Web analytics
Web analytics examines activity on websites through defined observations such as page views, events and sessions. These are instrument-dependent measures, not direct equivalents of people. Server requests can include assets, bots, monitoring and retries, while browser events can be blocked or omitted. Understand what is measured before interpreting a traffic chart.
A user identifier can represent a browser, device or logged-in account depending on the system. Cookie deletion, consent choices and multiple devices affect counts. A session groups activity according to the tool's rules, which may change. Product-specific definitions should be checked in current official documentation rather than assumed universal.
Measure useful outcomes such as finding a lesson, completing practice or resolving a task, while respecting privacy and avoiding unnecessary collection. More page views can reflect genuine interest or difficulty finding information. Connect activity with the user's objective and examine quality, not only volume.
Mobile analytics
Mobile-app analytics can include installs, first opens, screen views, events, retention and crashes. An app download does not establish continued use. Platform restrictions, offline activity and version differences can affect data. Event definitions should identify the app version and the time basis relevant to the analysis.
Offline events may be sent later, creating a difference between event time and collection time. Repeated delivery can create duplicates unless handled appropriately. App upgrades can also change instrumentation. Review these issues before treating a sudden event-count movement as a change in customer behaviour.
Mobile web and native apps are different environments. A person may use both, and cross-device linkage requires an appropriate lawful and technically reliable basis. Do not assume an analytics tool has identified one unique human merely because it reports a user count. State the identifier and its limitations.
Comparing web and mobile
Compare equivalent outcomes and populations where possible. A web visit and an app session may use different definitions, while an install has no direct website equivalent. Acquisition channels and user intent can also differ. A simple side-by-side total can therefore mislead without context.
Define common business events, such as a completed application, while preserving platform-specific diagnostics such as app crashes or page-loading failures. Reconcile event names, parameters and counting rules. The goal is a coherent view of customer outcomes, not forced equality between fundamentally different technical measures.
For financial services, authentication, handoffs and interrupted workflows can matter. A user may begin on one platform and finish on another. Analyse the actual journey and avoid attributing the entire outcome to whichever platform happened to record the last event. Attribution models are assumptions, not complete causal proof.
Experiments and causal caution
An experiment can compare alternatives using a suitable assignment and measurement design. Randomisation can help reduce confounding, but implementation, sample size and interference still matter. Define the hypothesis, primary outcome and guardrails before inspecting results. Repeatedly searching for a favourable metric can create misleading conclusions.
If a revised application page increases completion, also check errors, complaints and suitability where relevant. A short-term improvement can come at a later cost. Distinguish practical importance from statistical evidence, and do not imply a small uncertain difference is a guaranteed business gain.
Where experiments are inappropriate or unavailable, observational evidence can still inform decisions with suitable caution. Compare plausible explanations and document limitations. Predictive accuracy does not establish that changing a correlated variable will cause the desired outcome. The action requires an additional causal and operational argument.
Governance and adoption
A worked service-improvement review
Suppose a service receives 1,000 applications in a month. Eight hundred are complete on first submission, and 720 of those are processed within the target time. A report stating that 90% met target uses the complete applications as its denominator: 720/800. Relative to all received applications, the corresponding count is 72%. Neither number should be presented without defining the population.
The manager should investigate what happened to the other 200 applications and whether the target clock excludes time spent obtaining missing information. A process can appear faster if difficult cases are removed from the measured population. That may be an appropriate operational definition, but customers and management may also need an end-to-end measure.
Next compare quality. If a proposed change raises timely completion but also causes more corrections, track both measures. The decision should seek improved service within required controls rather than maximise one favourable percentage. Segment by application type where complexity differs, and check whether the apparent improvement reflects a changed mix.
Finally, identify an action and evaluation plan. Clearer document guidance might reduce incomplete submissions, while a better handoff might reduce avoidable waiting. Implement a suitable test and compare consistent cohorts and periods. Record data-definition changes so a measurement improvement is not mistaken for an operational one.
This example shows the full analytics cycle: describe the baseline, diagnose plausible causes, estimate effects of alternatives and choose a feasible action. It also shows why a simple, well-defined table can be more useful than an elaborate dashboard built on an unsuitable denominator.
Assign ownership for definitions, data quality, access, models and decisions. Sensitive customer data should be used only with an appropriate purpose and controls. Restrict permissions, protect outputs and review retention. A useful dashboard should not expose personal details to people who do not need them.
Validate calculations and models independently where consequences justify it. Check totals against source systems, test boundary cases and inspect whether important groups are represented. Monitor after deployment because data and processes change. An analysis that was reliable last year may no longer describe the current operation.
The central lesson is to turn evidence into accountable action. Define the question, measure the right population, choose a suitable method and show uncertainty. Then test whether the decision improved outcomes under real conditions. Business analytics earns its value through that complete cycle, not through the quantity of data or the sophistication of the chart.
Chapter practice
This practice is separate from timed mock tests. Answers and explanations appear after you choose an option.
Your reading progress
Sign in to save your progress across devices.