Skip to main content
Business LibreTexts

1.5.3.2: How Management Control Affects Resources

  • Page ID
    58637
    • Anonymous
    • LibreTexts

    \( \newcommand{\vecs}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)

    \( \newcommand{\vecd}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash {#1}}} \)

    \( \newcommand{\id}{\mathrm{id}}\) \( \newcommand{\Span}{\mathrm{span}}\)

    ( \newcommand{\kernel}{\mathrm{null}\,}\) \( \newcommand{\range}{\mathrm{range}\,}\)

    \( \newcommand{\RealPart}{\mathrm{Re}}\) \( \newcommand{\ImaginaryPart}{\mathrm{Im}}\)

    \( \newcommand{\Argument}{\mathrm{Arg}}\) \( \newcommand{\norm}[1]{\| #1 \|}\)

    \( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\)

    \( \newcommand{\Span}{\mathrm{span}}\)

    \( \newcommand{\id}{\mathrm{id}}\)

    \( \newcommand{\Span}{\mathrm{span}}\)

    \( \newcommand{\kernel}{\mathrm{null}\,}\)

    \( \newcommand{\range}{\mathrm{range}\,}\)

    \( \newcommand{\RealPart}{\mathrm{Re}}\)

    \( \newcommand{\ImaginaryPart}{\mathrm{Im}}\)

    \( \newcommand{\Argument}{\mathrm{Arg}}\)

    \( \newcommand{\norm}[1]{\| #1 \|}\)

    \( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\)

    \( \newcommand{\Span}{\mathrm{span}}\) \( \newcommand{\AA}{\unicode[.8,0]{x212B}}\)

    \( \newcommand{\vectorA}[1]{\vec{#1}}      % arrow\)

    \( \newcommand{\vectorAt}[1]{\vec{\text{#1}}}      % arrow\)

    \( \newcommand{\vectorB}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)

    \( \newcommand{\vectorC}[1]{\textbf{#1}} \)

    \( \newcommand{\vectorD}[1]{\overrightarrow{#1}} \)

    \( \newcommand{\vectorDt}[1]{\overrightarrow{\text{#1}}} \)

    \( \newcommand{\vectE}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash{\mathbf {#1}}}} \)

    \( \newcommand{\vecs}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)

    \( \newcommand{\vecd}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash {#1}}} \)

    Why are we so concerned about this “bathtub behavior” that all resources follow? Remember the problem we set out to solve, namely, what determines performance through time and how can management affect performance in the future. The logic is simple:

    • The resources in place drive performance at every moment.
    • Therefore we must know how the quantity of each resource changes through time.
    • These quantities are only explained by their inflows and outflows.
    • Thus to manage performance through time, the only way of exerting control is by managing the flows of resources into and out of the system.

    Consider your restaurant and see how these connections work (Figure 3.2.1). In Chapter 2 we looked at how the number of meals sold and the operating profits had changed during the previous 12 months and showed how these figures were driven by the number of customers and staff. Following the same logic, we next need to know what happened to customers and staff to bring about the performance history in Figure 2.2.1 and the inflows and outflows to these two resources.

    It is crucial to explain why the resource of customers developed over time as it did, and the only way to do this is to understand the flows (Figure 3.2.2).

    3.4.jpg

    Figure \(\PageIndex{1}\): How Changing Customer Numbers Drives Performance Over Time (for clarity, some items are not shown)

    Doing It Right: Units for Resources and Flows

    Figure 3.1.2 and Figure 3.1.3 label the flows entering and leaving the customer resource as “Customers won/lost during the month.” This is always the relationship between resources and the flows that fill or drain them: Whatever the resource in the tank, the flows are “[resource] per [time period].”

    There is never any exception to this rule!

    • It looks as if you had an early small inflow of customers, but this slowed.
    • So you did some serious marketing, which brought a flood of customers.
    • But this soon died away again, and your customer stock settled down at a steady but higher level, with seemingly no inflow or outflow at all.
    • Toward the end of the year, you experienced another flood of customers, but this time it was negative (the downward slope on the customer flow): You were losing customers fast.
    • Once again the flood soon slowed to a mere trickle and your stock of customers steadied at a lower level, again apparently with no inflow or outflow.

    3.5.jpg

    Figure \(\PageIndex{2}\): The Net Flow of Customers Into and Out of Your Regular Customer Group

    You can put flesh on these bones. By asking your customers if and when they have previously visited, you get a good idea of the inflow rate. Although you cannot easily ask how many people become ex-customers each month (because they are not there to be asked!), you can work out what the outflow must have been to reconcile with the net change each month (Figure 3.2.3).

    3.6.jpg

    Figure \(\PageIndex{3}\): The Separate Flows of Customers Into and Out of Your Regular Customer Group

    Doing it right: separating inflows from outflows

    If your restaurant experienced only the flows shown in Figure 3.2.2, you might be tempted to take the complacent view that nothing much is happening. Apart from the two puzzling spikes of customer gains around month 7 and losses around month 11, everything seems to be ticking along steadily enough.

    But appearances are misleading. During the middle period, turbulent activity is taking place, with lots of customers arriving and many others leaving. In fact, customer churn is so rapid that by months 9 and 10, you are almost certainly losing many of the customers that your marketing efforts brought in just a short time before.

    The factors driving resource gains are typically quite different from those driving losses, so you stand little chance of solving these challenges without distinguishing between the two flows.

    Always try to identify resource “gain” and “loss” rates separately.


    This page titled 1.5.3.2: How Management Control Affects Resources is shared under a CC BY-NC-SA license and was authored, remixed, and/or curated by Anonymous.

    • Was this article helpful?