Offer a Turnaround Perspective Without Pretending to Know the Cause

A turnaround discussion loses value when every executive arrives with a settled cause. Sales points toward price. Operations points toward late delivery. Finance points toward margin discipline. Each view deserves a fair hearing. None belongs in a recovery proposal until a shared factual record supports a hypothesis. A consulting partner earns trust by holding competing explanations open long enough for evidence to separate them.

Start with the decision facing the chief executive. A board review four weeks away needs a different response from a priority account facing a service issue before Friday. Ask which choice needs executive direction now, which choice belongs in a board review, and which questions need more work first. This protects urgent service work from a broad diagnostic. Learn what leaders need to decide before offering an answer.

Ask what changed, when leaders first saw change, and where accounts differ. Request reports management already uses. Ask who prepared each report, which period appears in each one, and whether a manual adjustment changed a figure. One leader might speak about booked orders. Another might speak about recognized revenue. Both measures matter, though each records a different event. Clear labels stop a room from comparing unlike figures.

Write every possible cause as a short hypothesis. One hypothesis might say customers reduced orders after a price schedule changed. Another might say priority orders arrived late and harmed renewal discussions. A third might say reported revenue fell because signed work crossed a reporting period. Give every hypothesis fields for evidence seen, evidence missing, owner for missing evidence, and next decision affected. This exercise changes a contest of opinions into assigned work.

Keep observation separate from interpretation. A delivery record might show six priority orders shipped after promised dates in April. A sales leader might say customers lost confidence. The first statement belongs in an operating record. The second needs account notes, customer feedback, or another reliable source. State this difference plainly. An interpretation often feels persuasive because a senior person gave voice to an opinion. Rank does not turn an interpretation into proof.

Consider a fictional first meeting. Chief executive Nia says, “Our flagship line missed plan for two quarters. Tell me where we should intervene.” Partner Arun replies, “I hear a price explanation and a delivery explanation. Which records support each view, and what decision does your board expect next month?” Nia says her board expects a recovery proposal, a named owner, and a funding view. Sales and operations have not compared order history with delivery records.

Arun does not select a winner. He asks who owns order history, price approvals, renewal notes, delivery data, and margin reports. He then asks Nia whether a service issue needs containment before a board date. Nia says immediate action should focus on priority accounts, while funding choices belong in a board discussion. Arun records two decision paths. One path addresses near term service. Another prepares a recovery proposal. Each path receives separate evidence and owners.

The invitation for a ninety minute working session names a narrow purpose. Agree on a factual timeline, test competing explanations, and assign work for decisions needing executive direction. Arun asks Nia, a sales leader, an operations leader, and a finance lead to bring original records. He requests monthly orders, delivery performance, approved price changes, margin reports, and a small sample of account notes. A slide carrying a conclusion does not replace source material. Leaders need enough detail to test how a conclusion arose.

Preparation deserves care. A delivery measure might count only completed orders, leaving waiting orders outside view. A sales report might count signed agreements, while finance records revenue later. Different figures do not automatically show error. Ask for definitions. Ask whether a report includes cancelled orders, credit notes, or work delayed beyond a report date. When a figure needs context, write context beside a figure instead of leaving someone else to guess.

Open a session with Nia’s decision. Review events from a first warning sign through a present week. Put price changes, order patterns, delivery events, account notes, and financial results on one dated sequence. Leave blank spaces where no record exists. A blank space tells leaders what needs checking. When someone offers a cause, Arun asks, “What observation supports this view? What other explanation still fits a similar observation?” Those questions slow premature agreement without making anyone defensive.

In this fictional session, late priority orders rise in February. A price schedule changes in March. Sales shares April notes from two accounts worried about delivery reliability. Finance shows expedited shipping expense rose in March. These records strengthen a delivery hypothesis, yet no record proves why every order changed. Arun says, “We have enough evidence for a focused service response. We need a wider order review before presenting a full cause statement.” Nia asks operations for a priority order check by Friday.

The conversation then moves from broad claims toward specific tests. Sales owns a comparison of order patterns for priority accounts and other accounts. Operations owns a review of ten priority orders against promised and delivered dates. Finance owns a check for revenue moving between reporting periods. Arun asks each owner to state what result would weaken an explanation. For example, priority accounts might receive late orders yet place repeat orders at a usual pace. In such a result, delivery delays would explain less than assumed. A hypothesis deserves testing against evidence challenging a hypothesis, not only evidence supporting one.

Arun keeps a visible decision record during discussion. Beside every hypothesis, he writes records reviewed, unanswered question, named owner, due date, and affected decision. “Operations lead verifies ten priority orders by Friday” gives Nia a clear commitment. “Review delivery performance” offers no owner or finish point. He marks every line as a finding, an assumption, or a proposed response. Future meetings then show how management moved from evidence into direction.

False urgency deserves equal discipline. A board date matters, though no executive needs every question answered by one date. Ask which choices would create expense, customer commitments, staffing changes, or public statements. Those choices need review through current leadership paths. Record assembly and definition checks usually belong with named team members. Nia’s attention should stay on choices requiring her authority.

Watch language during coaching. “Our pricing problem” and “the operations failure” quietly assume an answer. Replace each phrase with neutral wording. Arun says, “We have a pricing hypothesis and a delivery hypothesis. Here is evidence from each record.” This wording gives leaders room to update a view without losing face. A partner who speaks this way sets a better standard for later discussions.

A useful meeting also separates response design from cause finding. Nia needs a response for priority accounts even if a complete causal account will take longer. Arun asks operations to list every priority order due during a next ten day period. The operations lead names an owner for each order and a check point before a promised date. Sales reviews account notes for concerns needing a direct call. Neither action claims a final cause. Both actions respond to records already available.

Before sending a board paper, Arun tests language against a decision record. “Delivery disruption caused a sales decline” goes beyond current evidence. “Records show late priority orders and account notes describing delivery concerns” reports what a team reviewed. “Management proposes a priority account response while a wider order review continues” tells a board what leaders intend to decide. Nia asks finance to show funding choices separately from evidence. Separation keeps a preferred response from rewriting facts.

Disagreement still has a place after a session. A sales leader might believe price contributed more than delivery. An operations leader might say a February staffing change explains late orders. Arun asks both leaders for a record, an owner, and a date for follow up. He does not invite a second unstructured debate. A disagreement becomes useful when a team knows what observation would support or weaken each view.

At Friday’s fictional check, Nia receives ten order records. Seven arrived after promised dates. Three account notes mention missed delivery windows. Sales finds two accounts reduced orders before March, so price timing deserves further review. Arun places those findings beside an earlier timeline. He asks Nia to open her Monday agenda with one decision: approve a focused priority account response while sales completes a pre March order review by Thursday.

For a practice session, copy five dates onto a blank page: first warning sign, price change, first late priority order, account concern, and board review. Write one observation beside each date. Then write two competing hypotheses beneath a sequence. Give every hypothesis one missing record and one owner. Finish by asking a fictional chief executive to choose a response for priority accounts before Friday, then enter a named owner and check point beside every due order.