How to identify decision-useful information requirements and technology support for Core 2 management decisions.
Core 2 information-needs questions ask what management must know before making a decision. The answer is not “more data.” The answer is the specific information needed by a specific user to make a pricing, budgeting, capacity, governance, financing, operating, or performance decision.
Study this page as the first step in decision writing. If the information need is wrong, the calculation, report, system, KPI, or recommendation that follows will also be weak.
Management accounting is a major Core 2 emphasis. Information-needs questions test whether the candidate can move from a management decision to the specific information required for that decision.
| Coverage area | Core 2 question |
|---|---|
| Decision maker | Who needs the information, and what decision must be made? |
| Decision usefulness | Does the information change the recommendation, risk assessment, or follow-up action? |
| Technology support | Would technology improve capture, reliability, analysis, timeliness, monitoring, or communication? |
| Report detail | Does the report match user role, aggregation level, benchmark, variance explanation, and actionability? |
| Missing input | What missing fact would change the analysis or recommendation? |
Use a decision-usefulness test before asking for information.
| Question | Weak response | Strong response |
|---|---|---|
| Who uses it? | “Management needs the report.” | Names the user: board, owner, controller, operations manager, branch manager, project lead, or committee. |
| What decision depends on it? | “To evaluate performance.” | Identifies the decision: price, cut cost, add staff, fund project, change process, approve policy, or revise KPI. |
| What level is needed? | “Detailed data.” | Specifies product, service, customer, branch, program, region, channel, activity, or responsibility centre. |
| When is it needed? | “Monthly.” | Matches timing to the decision cycle, cash pressure, exception urgency, or reporting deadline. |
| What quality is required? | “Accurate data.” | Names relevance, reliability, timeliness, completeness, validity, and comparability. |
| What action follows? | “Review results.” | Names threshold, owner, corrective action, escalation, or monitoring. |
Core 2 often provides data that looks useful but does not answer the management objective. Available data becomes decision-useful only when it is tied to a user, decision, interpretation, and action.
| Available data | Why it may be insufficient | Better information need |
|---|---|---|
| Total sales | Does not explain price, volume, mix, channel, margin, or customer behaviour. | Sales by driver, product, customer segment, margin, and capacity effect. |
| Total labour cost | Does not show productivity, overtime, idle time, skill gap, or service quality. | Labour cost by activity, volume, error rate, utilization, and service outcome. |
| Average branch profit | May hide branch size, market, controllability, and allocation distortions. | Controllable profit, local drivers, customer mix, and benchmark-adjusted performance. |
| Website traffic | May not connect to conversion, revenue, service, or customer retention. | Conversion rate, acquisition cost, abandoned process, and revenue or service outcome. |
| Budget variance | Shows difference but not cause. | Price, volume, mix, timing, efficiency, benchmark, and accountability analysis. |
Technology should be recommended because it improves the decision process, not because it sounds modern. Useful technology support may include automated data capture, dashboards, exception reporting, integrated source systems, workflow approvals, scenario analysis, or better access to timely performance information.
| Technology role | When it helps | Limitation to mention |
|---|---|---|
| Dashboard | Management needs timely monitoring of a few important drivers. | Poor KPI design creates fast but misleading information. |
| Integrated system | Data comes from disconnected sources and reconciliation is slow or error-prone. | Implementation cost, data migration, user training, and control changes matter. |
| Exception report | Management needs to act only when thresholds are breached. | Thresholds must be meaningful and assigned to an owner. |
| Analytics tool | Management needs to detect trends, segments, or drivers. | Data quality and interpretation remain management responsibilities. |
| Workflow tool | Approvals or handoffs delay action. | Decision rights and escalation rules still need to be defined. |
| Step | Question | Output |
|---|---|---|
| 1. Decision | What decision, action, or performance question is management facing? | Decision statement. |
| 2. User | Who needs the information and what authority do they have? | User and responsibility. |
| 3. Needed input | What data, report, benchmark, or analysis would change the recommendation? | Information requirement. |
| 4. Quality test | Is the information relevant, reliable, timely, complete, valid, and actionable? | Information-quality assessment. |
| 5. Recommendation | What should management obtain, build, change, or monitor? | Practical next step. |
| Pitfall | Correction |
|---|---|
| Asking for all available data. | Ask for the information that affects the decision. |
| Ignoring the user. | Match detail and timing to the person who must act. |
| Treating activity measures as performance measures. | Explain whether the data shows outcome, driver, quality, cost, or behaviour. |
| Recommending technology before defining the need. | State the information requirement first, then choose technology support if needed. |
| Asking for missing facts without consequence. | Explain how the missing fact would change the recommendation. |