Qualify a Portfolio Review Before Recommending Change

An overloaded initiative portfolio is a decision problem before a consulting engagement begins. Executives often agree work has piled up. Their reasons for keeping each item differ. One sponsor sees a customer promise. Another sees a required system change. A third remembers the political cost of stopping work already announced. A business development director earns trust by helping leaders name those differences before proposing a review.

Start with the decision, not with an inventory request. Ask the executive who requested the conversation, “What choice is the leadership team avoiding or delaying?” Listen for a date, a meeting, or a pressure point. “We need to set next year’s investment plan” is useful. “We need better visibility” needs more work. Follow with, “What would leaders need in front of them to make a decision they would stand behind?” Their answer shows whether the real need involves capacity, customer commitments, cash timing, delivery risk, or a conflict between sponsors.

Do not ask for every project file. A large document request creates work without proving the review has a purpose. Request a small, mixed sample instead. Include one initiative near launch, one initiative with a missed decision, one initiative linked to a customer promise, and one initiative without a clear sponsor. For each item, ask for the stated purpose, accountable leader, next decision date, known dependency, and evidence used to judge progress. The sample reveals how the organization speaks about work when no one has prepared a special presentation.

In a fictional discovery call, chief strategy officer Ellis says, “We have forty strategic programs and none of them will stop.” Director Nina replies, “Which decision is waiting for the portfolio review?” Ellis says the executive committee plans a cost review in six weeks and wants to protect customer commitments. Nina asks, “Who decides whether a program continues, pauses, or changes scope?” Ellis names the committee, then admits several members sponsor programs in the portfolio. Nina says, “A review will need to show the customer commitments, the decision dates, and the sponsors connected to each item. Would those facts help the committee discuss tradeoffs openly?” Ellis says yes.

Nina does not promise a recommendation during the first call. She tests the boundary of useful work. “Let us start with programs tied to the commitments your committee wants to protect. We will look at the next decision, the dependency, and the person accountable for moving each one. Then your leadership team decides what deserves deeper analysis.” This approach respects the executive team’s role. Nina offers a path toward a decision rather than a verdict prepared outside the room.

Definitions often create the first surprise. Finance often calls an initiative funded once a budget line exists. Operations often calls the same initiative active only after people have been assigned. Technology often treats a system dependency as a separate project. Ask each participant what “committed,” “started,” “at risk,” and “complete” mean in their working language. Write down the answer in plain words. If leaders use different meanings, the review needs a shared glossary before any score or ranking carries weight.

Suppose the sample includes a service portal, a pricing update, a data cleanup effort, and a warehouse redesign. The portal has an executive sponsor and a public launch date. The pricing update has a finance owner but no agreed decision date. The data effort supports both projects, although nobody listed the link in a portfolio report. The warehouse redesign has a strong operating case but depends on a site decision outside the current planning cycle. Such details change the conversation. A simple list sorted by budget would hide them.

Nina prepares a one page working document for the session. Each row has the initiative name, the decision awaiting action, the sponsor, the next date, the dependency, and the evidence available. A final field reads, “What would change our view?” This field prevents an argument from turning into a contest of personal certainty. An executive who wants to preserve a program has a place to name the missing fact. A leader who wants to pause work has a place to state what evidence supports the request.

At the working session, Ellis brings a finance partner and two operating sponsors. Nina opens with a limited purpose. “Today we are identifying where the current portfolio view supports a decision and where missing ownership or evidence blocks one.” She asks participants to correct facts before discussing priority. The finance partner notices the portal team has counted contractor time but not internal service staff. One operating sponsor says the data cleanup group has never been invited to the portal schedule meeting. These are facts the leadership team needs, not consulting conclusions.

Conflict deserves direct treatment. A sponsor might say a program protects revenue while another leader says the same program drains the people needed for a customer commitment. Ask each person to state the decision they want, the evidence behind their view, and the consequence they expect if leadership chooses another path. Record both positions without forcing agreement. The next step might be a smaller fact finding task, a decision meeting, or a request for an accountable leader to bring an updated estimate. The appropriate step depends on the decision date and the gap in evidence.

Watch for false ownership. A name on a report does not always mean a person has accepted responsibility for the next choice. Ask, “Has this sponsor agreed to bring a recommendation on the stated date?” If the answer is unclear, mark the item as an ownership issue. Also ask whether the sponsor controls the people and funds needed to act. A sponsor who lacks either still provides context, yet another leader needs to own the decision.

The director should explain what a short diagnostic would produce in concrete terms. Avoid promising a single master ranking. A useful output might show the few initiatives connected to protected commitments, the decisions due before a planning deadline, the dependencies no report currently shows, and the names missing from key choices. Leadership then chooses whether to pause, reshape, sequence, or investigate an item. The consulting team supplies structure and analysis within the agreed scope. Executives retain the decision.

Prepare for the next conversation with a fictional practice situation. Your colleague plays Ellis and insists every program must remain because each sponsor has already told staff to proceed. Place five initiative cards on a table. Give each card a purpose, sponsor, decision date, dependency, and evidence note. One card should lack a sponsor. One should depend on work no one has budgeted. Ask, “Which choice does your committee need to make first?” When your colleague answers, write the choice at the top of the sheet and circle the two cards closest to the decision date. Then ask your colleague to name the person who will bring evidence for each circled card to the next committee meeting.