liveBook · Manning

Buy-in level

As explained in Collaborative Software Design: How to facilitate domain modeling decisions

An idea buy-in level presents a possible direction as an open question that participants may freely influence or reject.

A buy-in level communicates how much influence stakeholders have over a decision and how firmly its direction has been set. Framing that level accurately helps people participate appropriately and reduces resistance during implementation. section 9.2 section 9.2.2

Use four levels to state the decision-maker’s intent and the remaining space for influence:

  • Idea: present a possible direction as an open question; invite everyone to generate, analyze, influence, or reject options. section 9.2.2
  • Suggestion: show clear intentions, investigated options, and a preferred option while remaining open to other insights. section 9.2.2
  • Proposal: bring a concrete, worked-out plan; allow only serious objections to influence the decision. section 9.2.2
  • Command: communicate a decided course of action together with the responsibilities that follow. section 9.2.2

Frame the conversation before inviting input

Before asking stakeholders to respond, state whether they are helping generate options, reviewing a preferred direction, challenging a worked-out plan, or receiving a decision. Avoid presenting a command as an idea: mismatched framing can produce questions, inaction, sarcasm, gossip, and broader resistance. section 9.2.2

Figure 9.4 Levels of buy-in plotted on the spectrum of democratic and autocratic decision-making styles

Use the spectrum view to compare the four buy-in levels with democratic and autocratic decision-making styles. section 9.2

How Collaborative Software Design: How to facilitate domain modeling decisions covers it

How deep it goes
Defines four levels and their participation boundaries, while stopping short of prescribing a specific decision.
Examples
Contrasts ideas, suggestions, proposals, and commands as progressively more fixed decision framings.
What it assumes
Assumes awareness of stakeholders and decision-making, while defining participation boundaries from the beginning.
What you can do after
Apply the four levels to frame stakeholder input and responsibilities accurately.
How it connects
Connects decision-making styles, stakeholder participation, sustainable design decisions, and resistance.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Collaborative Software Design: How to facilitate domain modeling decisions. The section links point to the parts of the book it draws on.