Discuss Project Value When the Baseline Is Missing

When a completed project lacks a baseline, pressure often arrives late. An executive wants a concise account of value before a board review, a budget discussion, or a decision about further work. A single return on investment figure sounds tidy. Without comparable starting measures, such a figure asks too much from incomplete records. Your job as client partner involves guiding a review toward evidence people recognize, rather than filling a gap with a confident sounding estimate.

Start with a simple distinction. Project outputs are things delivered during the work. Observed changes are events or measures people saw after delivery. A value claim connects those two areas, yet connection needs evidence. A new operating process, a reporting routine, or an agreed escalation path belongs in outputs. A shorter cycle time, fewer handoffs, or a drop in backlog belongs in observed changes. Keep each statement separate until operations and finance agree on what records support a connection.

Ask the sponsor what decision sits behind the request. A request for proof often hides a more specific need. The executive might need approval for a next phase. Finance might need an explanation for a variance. A board chair might want management to explain why a prior target was missed. Those situations call for different material. If you know which decision waits, you help people gather evidence suited to a real audience instead of assembling a large slide deck with no clear purpose.

In a fictional practice situation, client partner Elena meets COO Marcus four weeks before a board session. Marcus says, “I need one number proving our project improved performance.” Elena replies, “Which board decision depends on this review?” Marcus says directors will decide whether management should extend the new operating model to two more divisions. Elena writes down an output already completed: a new intake process. She then asks which measure directors use when judging intake performance. Marcus names cycle time and unresolved requests.

Elena does not label either measure as a project result. She asks when each definition changed and who owns each report. Marcus explains cycle time used to begin when a request entered a shared mailbox. Operations now starts timing after a manager confirms scope. Unresolved requests used to count every open item. The current report excludes requests waiting for customer information. Both changes make a direct before and after comparison uncertain. Marcus sees why a headline number would invite questions his team cannot answer.

The next step is a working session with people who understand the records. Invite the operations analyst responsible for definitions, the finance lead who understands financial reporting, the executive sponsor, and whoever owns adoption of the new process. Give everyone a modest task before meeting. Ask for current definitions, prior definitions, report dates, known gaps, and any records explaining a change. A request for material evidence works better than a vague request for validation. People respond faster when they know exactly what needs review.

At the session, build a short evidence table in conversation. For every proposed statement, ask four questions. What happened. Where does a record show this. Who confirms the record. What limitation should the audience understand. You do not need to force every row into a conclusion. A row might say all service teams adopted the intake process by a named date, supported by rollout records, confirmed by an operations leader, with no claim about financial effect. Such a statement carries more weight than an unsupported estimate.

Suppose the analyst brings monthly cycle time reports from April through August. The reports show a lower average after June. Finance notes the earlier measure started at a different event. Elena records an observed trend rather than a matched comparison. In the review, management might say cycle time moved downward under the current definition during those months. Management should also say earlier data used a different start point. Directors receive useful information and see where comparison stops. Clear limits make follow up easier because nobody must defend a claim beyond available records.

Some evidence comes from events rather than dashboards. A plant manager might confirm a new approval path ended duplicate reviews. A service leader might show meeting notes where teams agreed on a shared queue. Such material supports an account of operational change. Do not turn statements from interviews into universal results. Record who observed the change, where they work, and whether another owner confirms a similar experience. If different leaders describe different outcomes, preserve those differences. Disagreement often points toward a useful question for management.

Finance needs a distinct role. Finance should explain which costs, benefits, and timing assumptions appear in management reporting. A client partner should avoid assigning financial value independently. In Elena’s fictional session, finance lead Priya says, “We see fewer external support invoices after July, yet our ledger groups several services together.” Elena asks, “Would you describe this as a cost trend worth further analysis, rather than savings from this project?” Priya agrees. Marcus now has language which respects finance records without presenting an unsupported cause.

Prepare the executive sponsor for direct questions. A board member might ask why baseline measures were missing at kickoff. The answer should name the condition without defensiveness. Marcus practices: “The project began before our reporting definitions were aligned. Management has documented delivered changes, current trends, and limits in earlier data. Operations and finance will establish a stable baseline for the proposed expansion.” This answer gives directors a factual starting point and describes management’s next responsibility.

A second question might test whether management plans to continue work without proof. Marcus answers, “The expansion decision rests on completed process adoption, current operating evidence, and a measurement plan for the next divisions. Financial attribution needs further work with finance.” Elena asks him to pause after each sentence during rehearsal. A rushed answer sounds evasive even when content is sound. A short answer with named evidence owners invites productive questions.

Avoid treating a value review as a consultant presentation. Give data owners room to correct wording before material reaches senior leaders. Send a draft claim sheet after the working session. Each owner should see their measure, their source, and their stated limitation. Ask them to mark anything inaccurate or incomplete. This step protects relationships. An analyst who sees their report described correctly is more likely to help improve future measurement.

The review also creates a better kickoff for later work. If management extends the operating model, agree on a baseline before rollout. Define the measure in plain terms. Name where data comes from, who maintains the source, when snapshots occur, and which events should not enter the measure. Finance should state whether any financial measure belongs in scope. Do not promise outcomes. Establish a way to observe changes responsibly.

For a fictional practice exercise, use Marcus’s expansion proposal. Write one output from the initial project, one current operating trend, and one question still open. Assign an owner and source beside each item. Then write the opening of a board response: “We delivered the intake process across the first division. Under our current definition, cycle time declined from June through August. Finance is reviewing whether related invoice movement supports any financial conclusion.” End by scheduling a forty minute evidence review with Priya and the operations analyst, bringing the April through August reports and the original definition notes.