Skip to main content
Workforce LibreTexts

2.2.4: Case study- Portfolio Allocation Conundrum

  • Page ID
    66113
  • \( \newcommand{\vecs}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)

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

    \( \newcommand{\dsum}{\displaystyle\sum\limits} \)

    \( \newcommand{\dint}{\displaystyle\int\limits} \)

    \( \newcommand{\dlim}{\displaystyle\lim\limits} \)

    \( \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{\longvect}{\overrightarrow}\)

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

    \(\newcommand{\ket}[1]{\left| #1 \right>}\)
    \(\newcommand{\bra}[1]{\left< #1 \right|}\)
    \(\newcommand{\braket}[2]{\left< #1 \vphantom{#2} \right| \left. #2 \vphantom{#1} \right>}\)
    \(\newcommand{\braopket}[3]{\left< #1 \vphantom{#2}\vphantom{#3} \right| #2 \vphantom{#1}\vphantom{#3} \left| #3 \vphantom{#1}\vphantom{#2} \right>}\)
    \(\newcommand{\qmvec}[1]{\mathbf{\vec{#1}}}\)
    \(\newcommand{\op}[1]{\hat{\mathbf{#1}}}\)
    \(\newcommand{\expect}[1]{\langle #1 \rangle}\)
    \(\newcommand{\dfn}[1]{\emph{\textbf{#1}}}\)

    \(\newcommand{\avec}{\mathbf a}\) \(\newcommand{\bvec}{\mathbf b}\) \(\newcommand{\cvec}{\mathbf c}\) \(\newcommand{\dvec}{\mathbf d}\) \(\newcommand{\dtil}{\widetilde{\mathbf d}}\) \(\newcommand{\evec}{\mathbf e}\) \(\newcommand{\fvec}{\mathbf f}\) \(\newcommand{\nvec}{\mathbf n}\) \(\newcommand{\pvec}{\mathbf p}\) \(\newcommand{\qvec}{\mathbf q}\) \(\newcommand{\svec}{\mathbf s}\) \(\newcommand{\tvec}{\mathbf t}\) \(\newcommand{\uvec}{\mathbf u}\) \(\newcommand{\vvec}{\mathbf v}\) \(\newcommand{\wvec}{\mathbf w}\) \(\newcommand{\xvec}{\mathbf x}\) \(\newcommand{\yvec}{\mathbf y}\) \(\newcommand{\zvec}{\mathbf z}\) \(\newcommand{\rvec}{\mathbf r}\) \(\newcommand{\mvec}{\mathbf m}\) \(\newcommand{\zerovec}{\mathbf 0}\) \(\newcommand{\onevec}{\mathbf 1}\) \(\newcommand{\real}{\mathbb R}\) \(\newcommand{\twovec}[2]{\left[\begin{array}{r}#1 \\ #2 \end{array}\right]}\) \(\newcommand{\ctwovec}[2]{\left[\begin{array}{c}#1 \\ #2 \end{array}\right]}\) \(\newcommand{\threevec}[3]{\left[\begin{array}{r}#1 \\ #2 \\ #3 \end{array}\right]}\) \(\newcommand{\cthreevec}[3]{\left[\begin{array}{c}#1 \\ #2 \\ #3 \end{array}\right]}\) \(\newcommand{\fourvec}[4]{\left[\begin{array}{r}#1 \\ #2 \\ #3 \\ #4 \end{array}\right]}\) \(\newcommand{\cfourvec}[4]{\left[\begin{array}{c}#1 \\ #2 \\ #3 \\ #4 \end{array}\right]}\) \(\newcommand{\fivevec}[5]{\left[\begin{array}{r}#1 \\ #2 \\ #3 \\ #4 \\ #5 \\ \end{array}\right]}\) \(\newcommand{\cfivevec}[5]{\left[\begin{array}{c}#1 \\ #2 \\ #3 \\ #4 \\ #5 \\ \end{array}\right]}\) \(\newcommand{\mattwo}[4]{\left[\begin{array}{rr}#1 \amp #2 \\ #3 \amp #4 \\ \end{array}\right]}\) \(\newcommand{\laspan}[1]{\text{Span}\{#1\}}\) \(\newcommand{\bcal}{\cal B}\) \(\newcommand{\ccal}{\cal C}\) \(\newcommand{\scal}{\cal S}\) \(\newcommand{\wcal}{\cal W}\) \(\newcommand{\ecal}{\cal E}\) \(\newcommand{\coords}[2]{\left\{#1\right\}_{#2}}\) \(\newcommand{\gray}[1]{\color{gray}{#1}}\) \(\newcommand{\lgray}[1]{\color{lightgray}{#1}}\) \(\newcommand{\rank}{\operatorname{rank}}\) \(\newcommand{\row}{\text{Row}}\) \(\newcommand{\col}{\text{Col}}\) \(\renewcommand{\row}{\text{Row}}\) \(\newcommand{\nul}{\text{Nul}}\) \(\newcommand{\var}{\text{Var}}\) \(\newcommand{\corr}{\text{corr}}\) \(\newcommand{\len}[1]{\left|#1\right|}\) \(\newcommand{\bbar}{\overline{\bvec}}\) \(\newcommand{\bhat}{\widehat{\bvec}}\) \(\newcommand{\bperp}{\bvec^\perp}\) \(\newcommand{\xhat}{\widehat{\xvec}}\) \(\newcommand{\vhat}{\widehat{\vvec}}\) \(\newcommand{\uhat}{\widehat{\uvec}}\) \(\newcommand{\what}{\widehat{\wvec}}\) \(\newcommand{\Sighat}{\widehat{\Sigma}}\) \(\newcommand{\lt}{<}\) \(\newcommand{\gt}{>}\) \(\newcommand{\amp}{&}\) \(\definecolor{fillinmathshade}{gray}{0.9}\)

    Konkan Telecom: One Pool of Money, Two Non-Negotiables

    Konkan Telecom, a major mobile operator serving Mumbai and the wider Maharashtra circle, was staring down a hard ceiling on its capital budget for the year: 1.4 billion dollars, a number that couldn't be exceeded without triggering a board-level intervention nobody wanted to be the reason for. Two priorities were both reaching into that same pool of money at once, and neither one was willing to wait. The Department of Telecommunications had set a firm deadline for renewing the spectrum licenses that let Konkan operate parts of its own network legally, a requirement with no negotiating room built into it. At the same time, the company's long-promised 5G rollout, the project analysts and investors had been asking about for two years, sat ready to accelerate, and every quarter it slipped, a competitor already live with 5G in three circles gained ground that would be expensive to win back.

    Ananya Rao, the portfolio manager responsible for reconciling the two, ran the numbers with her finance team and found exactly the collision everyone had been hoping to avoid. Fully funding the spectrum renewal and the 5G rollout at the pace leadership originally wanted would blow past the 1.4 billion dollar ceiling by roughly 340 million dollars. Something had to give, and neither option was free of real cost. Delaying 5G handed the competitor more time to lock in early adopters in the market's most profitable segment. Delaying the spectrum renewal risked the company's legal right to operate in some of its most valuable circles altogether.

    A comfortable story had already started circulating before Ananya's numbers landed on anyone's desk, the idea that a compliance project like the spectrum renewal must come from its own separate, effectively unlimited budget line, untouched by whatever the rest of the portfolio was fighting over. Meera Joshi, who headed regulatory affairs, said as much in an early planning meeting. "The DoT renewal isn't really competing with 5G for funding," she said. "That's compliance money. It's a different pot entirely." It wasn't. Every rupee that went toward the spectrum renewal was a rupee that could not also go toward 5G, and Ananya said so directly. "There's one capital budget, not two," she told the room. "Believing otherwise doesn't make the number bigger. It just delays the conversation we're going to have to have eventually, probably at a worse moment than this one."

    Once that myth was off the table, the argument became a genuine fight between two people who were both right about the thing they cared most about. Deepak Iyer, the CTO pushing 5G, had a slide deck full of subscriber growth projections and a chart showing exactly how much average revenue per user Konkan stood to lose for every quarter the rollout slipped further behind the competitor already live in the market. "Every month we wait is a month our competitor's brand becomes synonymous with 5G in this city," he said. "We might get the network back eventually. We don't get that positioning back." Meera's counter was just as sharp, and legally, harder to argue with. "If we miss the renewal deadline in even one circle, we lose the legal right to operate there," she said. "Deepak's numbers are about market share. Mine are about whether we're allowed to be in business in that circle at all."

    Ananya brought the full board three real paths instead of letting the disagreement resolve itself by default. The first fully funded the spectrum renewal on schedule and pushed the 5G rollout back a full two quarters everywhere at once. The second fully funded 5G at the original pace and asked the DoT for a compliance extension that regulatory affairs wasn't confident would actually be granted. The third split the difference: fund the spectrum renewal in full, since the legal exposure made it non-negotiable, and phase the 5G rollout so the highest-revenue circles launched close to the original timeline while the remaining circles waited for the following budget cycle.

    The board chose the third path. Konkan's spectrum licenses renewed on schedule, and 5G went live in its two largest circles within a month of the original plan, generating exactly the subscriber growth Deepak's projections had promised there. But the circles pushed to the next cycle were smaller markets where the competitor already had a foothold, and nobody could yet say whether a delayed 5G launch there would still land the way it had in the flagship circles, or whether a year's head start would be enough for the competitor to make those markets genuinely difficult to win back. Ananya raised that uncertainty herself at the quarter-end review, when a board member asked whether the phased approach had actually solved the problem. "It solved this year's version of it," she said. "The circles we deferred are going to show up in next year's capital request too, probably fighting for room against whatever else needs the same one pool of money. I don't think this is a decision we made once. I think it's a decision we're going to keep having to make, and I'm not sure we've built anything yet that makes the next round of it easier than this one was."

    Reflections and Pulse-Check \(\PageIndex{1}\)

    This section is designed for you to pause and consider how these leadership concepts land in your own professional world. There are no right or wrong answers here. Instead, these questions are meant to help you audit your current approach and identify where you might want to pivot.

    1. Ananya rejected the idea that the spectrum renewal drew from a separate, unlimited pot of money, insisting the board see it as competing directly against 5G for the same 1.4 billion dollars. If you were on Konkan's board, would you have accepted her framing right away, or would Meera's "compliance has its own budget" instinct have felt safer to believe, at least for a little longer?
    2. The board chose to phase 5G rather than delay it everywhere or risk the compliance deadline outright. Given that the deferred circles were markets where the competitor already had a foothold, was fully funding the flagship circles first the right call, or should the trade-off have been spread more evenly across all circles instead of concentrated on the ones already weakest?
    3. Ananya ended the review admitting the deferred circles would likely resurface as a funding fight again next year. If you were advising Konkan now, what would you actually change about the portfolio process itself, rather than the specific funding split, so that next year's version of this exact collision is easier to resolve than this one was?

     


    2.2.4: Case study- Portfolio Allocation Conundrum is shared under a CC BY 4.0 license and was authored, remixed, and/or curated by LibreTexts.