How Shared Data Supports Organizational Decision-Making

Hello! In the previous lesson, you distinguished operations, marketing, finance, and HR by the questions each function answers. You also saw that a decision such as extending a café’s hours needs more than one function’s perspective.

This lesson asks what happens when those perspectives are supported by shared data. You’ll follow one proposed decision from customer interest to a workable, but still uncertain, plan. Then you’ll examine a documented case in which sharing assumptions helped several functions plan together. Allow about 35–40 minutes, including the readings.

Shared data gives a decision more than one view

An organization records facts as it works: orders placed, prices charged, ingredients used, hours staffed, and bills paid. A fact becomes useful information for a decision when it is organized and interpreted in relation to a question. “Twenty-four orders” means little on its own. “Twenty-four additional evening orders per night, at a particular price and cost” can help assess whether later opening hours are viable.

Read how OpenStax distinguishes data from useful information, then follow its example of an order database serving several functions.

The important idea is not that everyone needs every field in a database. Marketing might need order totals by time of day to gauge demand; operations might need item counts to plan supplies; finance might need sales and cost figures. Sharing relevant data means making the appropriate facts and their definitions available to the people making a joint decision—not distributing every customer or employee detail indiscriminately.

Build a decision from four contributions

Return to the café considering evening hours. Suppose its decision is specific: Should it try staying open two hours later on two evenings each week? A decision-maker needs to know whether customers are likely to come, whether orders can be served, whether staff can cover the hours, and whether the additional revenue is likely to cover additional costs.

These are not four votes on an identical question. They are four parts of the evidence needed to answer one organizational question. The exchange also goes both ways: if operations cannot prepare the proposed menu quickly enough, marketing may need to change the offer; if finance identifies a cost gap, the group may need to reconsider the hours or staffing plan.

Consider some illustrative estimates, not facts about an actual café. Marketing estimates 24 additional orders per evening at an average sale of $12 each. Operations estimates $5 in additional ingredient and packaging costs per order and says it can serve up to 30 evening orders with the planned supplies. HR confirms that the proposed shifts can be covered; the additional wages would be $130 per evening. Finance adds $20 in additional utilities.

At 24 orders, estimated sales would be $24\times \$12=\$288$. Estimated order-related costs would be $24\times \$5=\$120$. After the additional $\$130$ in wages and $\$20$ in utilities, the estimated amount remaining is $18 per evening. Finance could not make that estimate from sales alone. It needed marketing’s demand and price assumptions, operations’ cost and capacity information, and HR’s staffing estimate.

But $18 is an estimate, not an outcome. If only 15 additional orders arrive, the same assumptions yield $\$180$ in sales, $\$75$ in order-related costs, and a $45 shortfall after wages and utilities. A small change in demand changes the conclusion. That makes a limited trial more defensible than immediately committing to permanent evening hours.

Make the shared evidence comparable

Combining figures only helps if they describe the same proposed plan. Before relying on the café estimate, the functions would need to clarify several points:

• Does “24 orders” mean additional orders per evening, or 24 orders across the entire two-evening trial?
• Is the $12 average sale based on the evening offer being proposed, or on a different daytime menu?
• Does the $5 cost per order include the items customers are expected to buy?
• Can the staff and supplies that support a 30-order capacity actually be available on both evenings?

These checks are part of decision-making, not clerical details. A forecast of 24 orders per week paired with costs per evening would give a misleading result even if every individual figure had been copied correctly.

The functions should also distinguish observed records from assumptions. Past order counts show what happened under past hours. Customer feedback may indicate interest, but interest does not guarantee purchases. The proposed price, expected order count, and staffing cost should therefore be visible as assumptions that can be checked during the trial.

That shared understanding supports a practical decision: try the two evenings, record actual additional orders and costs, and review whether the results justify continuing. The decision is informed by data without pretending that the data remove uncertainty. It also requires coordination: marketing must communicate the trial hours, operations must prepare for the expected orders, HR must arrange coverage, and finance must compare actual results with the estimates.

The following image offers a broad view of how organizations turn data into action. Use it to locate the café example conceptually, not as a requirement that a small decision use every technology named in the diagram.

What happens when functions plan from different assumptions?

The café example is hypothetical. A documented supply-chain case shows why the same issue matters in a larger organization. In the case below, sales forecasts were passed informally to operations and finance. Other functions questioned those forecasts and made their own. As you read, concentrate on the decision problem caused by incompatible or mistrusted inputs, rather than the technical details of forecasting.

The lesson is not “one department was wrong.” Sales had knowledge of customers; operations was responsible for avoiding shortages; finance needed a financial plan. Yet if each function plans around a different demand figure—or does not trust the figure it receives—the organization can make inconsistent commitments. Sharing a number is not enough when the people using it disagree about what it measures or why it should be believed.

The case then describes a planning process that made product and promotion assumptions available to the group, brought different forecasts into discussion, and checked the resulting plan against financial and operational constraints. Read the overview rather than trying to master every forecasting term.

The common ground in that process was not just a shared file. It included explicit assumptions about offerings and promotions, discussion of differing demand estimates, and checks on whether a plan made financial and operational sense. If a proposed plan failed one of those checks, participants could revise it. The café would do the same on a smaller scale if, for example, its staffing cost rose or its expected evening menu exceeded preparation capacity.

Key takeaways

Data shared between functions supports an organizational decision by giving each function relevant evidence and a common set of assumptions to examine. Marketing can inform expected demand, operations can test delivery and costs, HR can test staffing, and finance can test financial viability. The evidence is strongest when figures use compatible definitions and time periods, uncertainty is stated openly, and the functions can revise a plan when one of its constraints is not met.

Next, you’ll look more closely at the data analyst’s role in this work: turning a broad business question into evidence decision-makers can use.