Why does an internal decision-maker block a proposal with broad support?

An organizational purchase usually involves a group, but its members rarely have equal responsibilities or equal authority. Some experience the problem every day; others assess systems integration, contractual terms or financial exposure. Johnston and Bonoma examined buying-center membership and communication patterns for industrial services and capital equipment in 31 firms [S1]. Their findings support studying the network around a purchase. Choffray and Lilien proposed a decision matrix to document involvement across stages [S3]. None of this establishes that every company has the same five buyer personas. It means the account team should identify who provides input, who defines approval conditions, who can stop a decision and who is legally authorized to sign. A familiar job title is a starting hypothesis, never a substitute for that mapping.

An end user, an IT lead, finance, procurement and the accountable owner may not evaluate the same platform against the same criteria. The comparison below turns potential gains and exposures into different questions and evidence formats. These are **working hypotheses**, not measured Neurofactor profiles. Ask every participant to confirm their actual mandate and concerns. The information sought can also shift with purchase stage and complexity, as organizational research among manufacturers suggests [S4]. A generic deck can be convincing to the user who wants less work and inadequate to the approver who needs a credible incident response. Selling to an organization therefore means making the proposal reviewable, not simply making one person more excited.

The highest-ranking person on an organization chart does not necessarily control every stage. For one purchase, a security specialist's expertise may outweigh a director's enthusiasm. Kohli analyzed 251 organizational purchase decisions and identified expert power as an important influence source; its effects varied with buying-center characteristics and decision conditions [S2]. Lilien and Wong likewise documented different patterns of participation across purchasing stages [S11]. Instead of asking only who attends a meeting, investigate whose judgment changes the views of others, whose expertise matters under these conditions and whose signature or formal review is required. The answer may differ between early exploration and contractual approval. That is why stakeholder mapping should be reviewed rather than frozen after a first sales call.

Suppose a supplier says: 'Our software simplifies planning.' A planner may think about fewer repetitive tasks. An operations leader may hear: a critical process is about to change. Finance may immediately wonder whether costs remain predictable over three years. The proposition is identical; its meaning depends on the decision context. Sitkin and Weingart examined how framing, perceived risk and risk propensity related to risky decision-making across two studies [S5]. Their evidence does not show that every executive values losses more than every employee. It does justify investigating perceived consequences alongside objective constraints. A worried expression in a meeting is not a psychometric result. A carefully documented interview, paired with a clear account of that person's responsibilities, is a better starting point.

Havenbrug Logistics is an entirely fictional business. The equally fictional supplier PlanKoers is proposing a scheduling platform for drivers and equipment. The internal project team expects less duplicate entry and better visibility. Operations director Farida, however, must ensure deliveries continue during an outage. IT specialist Els needs to understand data flows, and finance manager Amir needs clarity about cost exposure over time. Every organization, person, quote, proposed figure and reaction in this illustration is invented. No interviews were conducted, no brain measurements were made and no savings were calculated. The case is designed to show why a seemingly united buying team may still have several legitimate and distinct decision questions.

In the fictional scenario, Havenbrug's schedulers mainly recognize friction in their current work. During a demonstration they ask whether they can adjust routes without opening several spreadsheets. The tool suggests less frustration and more time for conversations with drivers. Their department lead focuses on managing peak demand. That positive assessment can be entirely reasonable, but it concerns local tasks and everyday value. A responsible account manager documents it as one part of the decision case, not as proof of organization-wide readiness. A successful user demo does not establish how the platform performs when the ERP connection fails, the supplier is unavailable or access rights are misconfigured.

Farida does not ask whether the fictional software is easier to use. She asks: 'Who calls our customers if deliveries stop, and how do we switch back?' The project team may hear unnecessary caution. For Farida this question is central to her role. She must explain consequences to customers, colleagues and the executive team, even if a failure emerges months after launch. What she needs may not be another feature demo but a credible incident plan, named responsibilities and evidence of a workable rollback. If those are missing, delay can be prudent. A sales approach that tries to bypass her concern may erode trust precisely where the account team needs it most.

A statement is an observation. An assumed underlying association is a hypothesis. These belong in separate fields in the sales record. The comparison shows how phrases such as 'not now' or 'who is accountable' can become **open diagnostic questions** rather than labels about a person's psychology. The five phrases are illustrative, not a measured ranking of common objections. Ask for prior incidents, explicit requirements and real approval gates. Only then decide whether the useful next step is a technical test, contractual clarification, a decision meeting or simply waiting. Treating every hesitation as a psychological weakness can damage a relationship faster than an incomplete quotation ever would.

A proposal can be financially attractive on paper and still be hard to defend personally. Someone accountable for service continuity, safety or public scrutiny faces a different downside from the employee expecting a smoother workflow. A failed implementation may cost money and also damage credibility with customers and colleagues. This does not mean reputational anxiety is always the true reason behind delay. Investigate whether the exposure is material, which rules apply and who bears the consequences. Invite the decision owner to define a plausible worst case, then examine likelihood, severity and recoverability separately wherever those can be estimated responsibly. Not every concern should be collapsed into a single currency value or dismissed as resistance.

The current process contains frustrations but also familiar workarounds. A new system promises improvement while introducing uncertainty. Samuelson and Zeckhauser documented preferences for existing options across several decision experiments, a pattern known as status-quo bias [S6]. Their findings do not make every postponed purchase irrational: transition costs can genuinely exceed expected gains. Sales should therefore compare the verifiable consequences of keeping the current process with transition costs, projected benefits and the feasibility of returning to the old one. Show assumptions rather than manufacturing fear. A decision may be well informed even when it ends with 'do not buy'. The point is to evaluate the options, not to diagnose bias whenever a prospect remains cautious.

Many salespeople ask: 'What is stopping you?' That can push the other person into defending a position. A better opening may be: 'Which question must you be able to answer internally before you can sign this?' Ask what scenario needs stronger evidence, which condition is already non-negotiable and who evaluates the outcome. Encourage the person to explain in their own words. Avoid leading guesses such as 'You must be afraid it will fail.' Record verbatim statements before inferring an underlying association. This produces testable hypotheses rather than a list of rebuttals. The aim is not to profile someone covertly but to understand what would constitute an adequately supported decision.

Map the real stages for the specific opportunity: need recognition, selection, technical review, security, finance, legal assessment, authorization and subsequent evaluation. Ask who enters at each point and what records they require. Compare responses because formal organization charts may not describe everyday decisions accurately. Do not paste a universal buying diagram onto every account. Choffray and Lilien's work examines functional participation across purchasing stages [S3]; Lau and colleagues found associations between purchase characteristics and buying-center structure [S4]. A concrete decision map helps sales plan a transparent process and prevents a late-arriving approval requirement from being misclassified as an inexplicable personal veto.

The question 'Is it safe?' is usually too broad to answer well. Break it down into possible failure events, the severity of their consequences, controls that reduce likelihood and recovery procedures when controls fail. Operations may want to know whether dispatch can continue manually during an outage. IT may ask about access revocation and audit logs. Finance may focus on liability, extra cost and long-term commitments. Sitkin and Weingart's research cautions against conflating a person's general willingness to take risks with their perception of a particular decision [S5]. Also assess the evidence-based risks of remaining with the current arrangement, without inventing dramatic scenarios. No option is completely free of risk, and a credible recommendation makes that explicit.

One more testimonial or attractive customer story may not address the actual gap. A data-security concern requires documented controls and processing arrangements. A continuity concern requires recovery tests, rollback conditions and incident response. A financial question needs an auditable total-cost model. The comparison pairs evidence with the uncertainty it can address and, importantly, what it **cannot** prove. A pilot is not a guarantee of flawless rollout across all locations. A security review does not eliminate every future threat. Credible sales materials state the scope and limits of each proof asset so an internal approver can explain exactly what is known and what still needs a decision.

Suppose sales gives fictional Havenbrug a savings model based on fewer planning hours. If Farida is concerned that the operation could stop after a system outage, that model does not answer her key question. The ROI calculation may still be useful, but it is not evidence of operational continuity. Instead, define one critical failure scenario, test what happens when a connection fails, document recovery steps and let the accountable owner set evaluation criteria in advance. State where evidence is missing. Only then compare the potential operational gains against residual risks and transition costs. No efficiency figure in this fictional example represents a real observation, measured outcome or promise of future performance.

In the fictional case, PlanKoers proposes a bounded trial rather than a company-wide rollout. One scheduling team uses the new system for a defined period while the previous process remains available. Success is not determined by user satisfaction alone. Incidents must be recorded, recovery procedures tested and critical failures evaluated against thresholds specified before the trial. Farida, Els and Amir each contribute to the assessment. The pilot could succeed, fail or identify further questions. This description is an illustration of a research design, not a trial that has taken place. The useful lesson is that decisions improve when the proposal can be evaluated against actual responsibilities rather than when everyone is encouraged to agree politely.

Complex deals may lack ownership of the remaining risk rather than motivation. Specify who detects an incident, who reports it, who contacts the supplier, who performs recovery and who informs customers. A RACI matrix can help, but build it with the organization rather than presenting fictional governance as a certified process. Include supplier responsibilities and escalation timelines. Once those commitments become explicit, an association such as 'I would be left alone with the consequences' might shift toward 'this can be managed'. Whether it does shift requires testing; do not infer personal fear without asking. The matrix has value only if people understand their obligations, accept them and can perform them under realistic conditions.

Having to explain a decision to others may change the type of information a person seeks. In a laboratory personality-prediction task, Tetlock and Kim found differences in judgment processes when participants knew in advance that they would have to justify their answers [S7]. This is not a B2B procurement experiment and cannot establish that every director wants longer reports. It does suggest a narrower question worth testing: what must the accountable approver be able to justify later? The next sales asset may be a concise decision memo covering explicit criteria, tested assumptions, unresolved risks, named owners and go/no-go conditions. That serves decision quality more directly than adding dozens of persuasive slides or putting the stakeholder under social pressure.

Even a sound substantive proposal can meet resistance if a critical stakeholder is included only after others treat the outcome as settled. Blader and Tyler tested distinct aspects of perceived procedural fairness in two studies, including decision procedures and interpersonal treatment [S9]. This is not evidence that a courtesy meeting guarantees approval. Establish who gets heard, how objections are documented, which criteria apply consistently and how reconsideration works. Invite the accountable owner to specify conditions before the proposal becomes a fait accompli. Fair participation is not the same as giving every participant indefinite veto power. Formal authority and agreed decision rules still matter; process legitimacy should make those rules more transparent rather than override them.

A sales deck typically aims to earn attention. A decision memo should make the grounds of a decision inspectable. Create a short document containing the problem, options, financial assumptions, accountable risk owners, open questions and explicit stop conditions. Link to verifiable appendices rather than hiding gaps behind more slides. A commercially attractive quote must not imply certification that does not exist or silently transfer risk to the customer. Invite the buyer to correct the memo and its assumptions. If the resulting evidence shows that the business case is too weak, 'do not proceed' must remain a legitimate outcome. This creates a different kind of confidence: the organization knows what it is agreeing to and why.

Deals often stall because 'we will revisit this' never becomes a concrete process. End the conversation with four agreements: what evidence is missing, who is responsible for obtaining it, how the evidence will be reviewed and who can authorize the next stage. Set a realistic review date, not an arbitrary sales deadline. Respect external constraints such as existing contracts, funding windows and regulated tenders. The purpose is not to manufacture urgency. It is to convert an uncertain discussion into a transparent sequence of decisions. Preserve the possibility of a negative outcome. A customer whose questions have been taken seriously should not have to restate the same objection every time a salesperson follows up.

If the only metric is the number of enthusiastic stakeholders, a sales dashboard can generate false confidence. Evaluate several stages instead: before the discussion, after risk evidence is reviewed, after any trial and when a formal decision is taken. Record more than sentiment. Check understanding of conditions, correct recall of evidence, unresolved exposure, actual authority and objectively verifiable pilot outcomes. The table presents a possible evaluation design, not a universal standard. Specify in advance which results permit the next step and which stop it. Keeping attitudes, intentions, behavior and authorized approval separate prevents a more positive group conversation from being mistaken for a legally meaningful purchase decision.

An associative diagnosis should not start with a pre-filled buyer persona. Ask open questions first: which words come to mind when you think of this supplier, this change and being personally accountable for the outcome? Invite concrete examples of moments that increase or reduce confidence. Only then ask for explanations, formal requirements and missing evidence. Preserve verbatim responses and code patterns after collection. Where feasible, have two researchers code independently and reconcile disagreements. Do not promote a single colorful remark into a dominant cluster after the fact. Frequency, context and counterexamples matter. The resulting association map describes the studied material; it does not grant direct access to private thoughts or establish the causes of purchasing behavior.

When the research question warrants it, a carefully designed response-time task may complement interviews by examining relative associative links. That requires suitable stimuli, counterbalanced order, technical reliability and a preregistered analysis plan. An IAT-style measure does not directly reveal which finance director will approve a contract, and individual decisions cannot be predicted without validation. It may be more useful to compare associations such as control, confidence, risk and dependence at an appropriately aggregated group level. Keep associative responses, explicit ratings and subsequent behavior as distinct outcomes. A method is useful only when it fits the question and its limitations are disclosed. Do not use concealed testing or personalized psychological pressure on identifiable employees.

A research project can compare whether approvers understand the same material better in a case narrative, concise decision memo or risk matrix. Keep factual terms, prices, limitations and responsibilities identical. Where feasible, allocate participants randomly and define a primary outcome beforehand, such as accurately identifying who handles a service outage. Measure trust and intention as separate variables, not substitutes for understanding or formal approval. Better comprehension does not automatically mean greater preference; a higher intention score is not a signature. With small samples, report uncertainty plainly and replicate in other decision settings. Evidence-format testing should improve communication quality, not become a covert technique to overpower a skeptical stakeholder.

The fictional pilot may show that PlanKoers cannot handle a critical integration reliably enough. In that case Farida's refusal is not an awkward association to remove with clever framing. It is a reasonable response to a real weakness. A modified version, an alternative supplier or staying with the current process may be the correct next step. Record the evidence and share an inspectable summary. The account manager may lose the immediate sale while preventing a poor decision for the customer. That is a possible ending of an invented scenario, not a reported trial result. A strong account relationship allows trust to be built by admitting where the current offer falls short.

Compare two possible opening lines. The first is: 'Your team wants this, so when can we start?' The second is: 'Your team sees the value, but you may have other risks to evaluate. Which decision question have we not answered well enough yet?' The second line gives the approver room to name a real criterion instead of being portrayed as resistant. It can lead to a more useful discussion of responsibility, technical requirements and evidence. Use this language sincerely: do not claim to understand someone else's exposure before investigating their context. Listen before offering rebuttals. The purpose of the conversation is to improve the quality of a decision, not to refine a pressure tactic that might win a signature without genuine understanding.

Interviews about confidence, accountability and career consequences may touch sensitive professional contexts. Explain the purpose, collect only data that are genuinely needed and never turn responses into a covert means of putting pressure on a recognizable individual later. Establish access controls, retention periods, appropriate aggregation and meaningful freedom not to participate. Do not collect sensitive personal information unless there is a separate lawful necessity. Only connect findings to roles or study conditions when the evidence warrants it. A research report should not become a private psychological dossier about a named colleague. Trust is more likely to be served by treating someone's question fairly than by recording their presumed vulnerability in a CRM system.

Before labeling a deal 'internally blocked', answer six questions in the review: 1. Who has formal decision authority? 2. What problem does the proposal solve for users? 3. Which downside does the accountable owner carry? 4. What specific requirement or evidence is missing? 5. Can that uncertainty be tested proportionately? 6. Who will decide again, when and against which criteria? If any answer is unknown, 'increase persuasion' is a poor substitute for research. Collect the missing information first. Keep observed behavior, verbatim statements and inferred meaning in separate fields. That turns a stalled commercial conversation into a decision process that can actually be evaluated.

Why does an internal decision-maker block a proposal with broad support? Sometimes the proposal carries a different association for that person: less opportunity and more accountability. Sometimes an approval condition is missing, the timing is wrong or the proposal is objectively not safe enough. Those explanations must be separated. Investigate the people involved, the meanings they attach to the offer and the evidence necessary for a defensible decision. Make uncertainty visible, test what can reasonably be tested and accept the outcome. Good sales does not pretend that five positive reactions amount to a sixth signature. It helps an organization make a choice that users, accountable managers and suppliers can still defend after the contract is signed.