Buy-in

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

Buy-in is acceptance and support for a decision by the people whose cooperation is needed to carry it out.

Buy-in is active support and participation from everyone whose cooperation is needed to carry out a decision. Without it, resistance may appear as delay, repeated questioning, inaction, sarcasm, or gossip. section 9.2.2

Make the decision’s level of participation explicit. An idea invites broad influence; a suggestion states an intention while welcoming insight; a proposal presents a worked-out plan open to serious objections; a command informs people of a decision and their responsibilities. Misrepresenting the level—especially disguising a command—creates frustration and resistance. section 9.2.2

A software design decision

Bring the relevant stakeholders together around a shared model of the proposed solutions. Collaborative modeling makes their perspectives visible and enables evaluation and feedback, but it does not guarantee agreement. If the group chooses a solution that some people opposed, ask: “We’re going with this decision, so what do you need to go along with it?” Add practical support where possible, such as a communication storyline, regular check-ins, or a meeting with architects for clarification. section 9.2.3 section 9.2.3

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

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

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

How deep it goes

Distinguishes four decision-participation levels and gives a post-decision heuristic, while stopping short of a full facilitation procedure.

Examples

Uses software design modeling, stakeholder feedback, communication storylines, check-ins, and architect clarification meetings.

What it assumes

Assumes a decision involving multiple stakeholders and teaches from zero how to frame their expected participation.

What you can do after

Apply it via collaborative modeling and the question, “What do you need to go along with it?”

How it connects

Connects stakeholder involvement with decision-making, collaborative modeling, consensus, and resistance.

liveBookmanning.com

Read Collaborative Software Design: How to facilitate domain modeling decisions on liveBook Get the book at manning.com

Also explained in

• 

  liveBookmanning.com
  Interview SpeakBuy-in is acceptance and active support for a proposal, decision, or change by the people whose cooperation is needed.

Compare how 2 books explain buy-in →

Related concepts

• collaborative discovery and modelingproduced by · Collaborative discovery and modeling is a group technique in which stakeholders jointly create and refine representations to establish shared understanding of a domain or system.
• influenceproduced by · Influence is a factor or capacity that affects another person’s behavior, choices, decisions, or actions.
• metaheuristicproduced by · A metaheuristic is a high-level strategy that guides or coordinates heuristic search for good solutions to optimization problems without guaranteeing an optimal result.
• job interviewproduced by · A job interview is a structured or informal conversation in which an employer evaluates a candidate’s qualifications and suitability for an employment role.
• leadershipproduced by · Leadership is the practice or capability of guiding, influencing, coordinating, and making decisions for people or organizations pursuing shared objectives.
• stakeholderproduced by · A stakeholder is a person or group with an interest in, influence over, responsibility for, or potential impact from a system, project, decision, or outcome.

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.