Advice Process

1. What Is Advice Process?

The Advice Process is a participative decision-making framework in which a person makes a decision only after seeking input from people with relevant expertise and from those who will be meaningfully affected by the outcome. It is designed to combine the speed and accountability of individual decision-making with the quality and legitimacy that come from broad consultation.

In plain terms, it is neither top-down approval nor group consensus. The decision does not have to move up the hierarchy, and it does not require everyone to agree. Instead, the process gives a clear decision owner the responsibility to listen well, weigh the advice seriously, make the call, and own the consequences. In consulting practice, it is most often used in organization work involving self-management, decision rights, governance, and culture.

2. Origin and Background

Origin: No single inventor is universally credited. The practice was in use in self-managing organizations by at least the 1980s, and it was later synthesized and widely popularized by Frederic Laloux in his 2014 book Reinventing Organizations.

Laloux did not present the Advice Process as a purely academic model; he described it as an observed practice in organizations trying to operate with less hierarchy and more distributed authority. Companies often cited in this discussion include AES, Morning Star, and other self-managing or highly decentralized organizations. Because the framework emerged from practice rather than one seminal paper, its history is better understood as evolutionary than singular.

The underlying problem it addresses is an old one: how do you avoid slow, political, committee-heavy decision-making without reverting to rigid command-and-control? The Advice Process offers one answer. It pushes decisions closer to the people who see the issue most clearly, while still requiring consultation, transparency, and accountability. It became widely known through management literature, practitioner communities focused on self-management, and consulting work on decentralized organizations.

3. How Advice Process Works

The core logic is simple: the person closest to the issue should usually make the decision, but should not do so in isolation. Before deciding, that person must seek advice from two groups: people with relevant knowledge and people who will be affected. After that consultation, the decision owner decides.

This is why the Advice Process is often misunderstood. It is participative, but it is not democratic voting. It is inclusive, but it is not consensus. It is decentralized, but it is not a free-for-all. The quality of the process depends on judgment, candor, and clear norms about when advice is required and how seriously it must be taken.

In practice, most organizations that use the Advice Process add a few operating rules. They define who can decide within which domain, what kinds of decisions require broader consultation, which matters still need formal approval for legal or fiduciary reasons, and how decisions are documented so that others can understand the rationale.

Typical elements of the framework

Element	What it means in practice
Decision owner	A clearly identified person frames the issue, gathers advice, makes the decision, and owns follow-through.
Expert advice	The decision owner consults people with knowledge, experience, or data relevant to the issue.
Affected parties	The decision owner consults people who will feel the consequences, even if they are not technical experts.
Decision right	Advice informs the choice, but advisers do not usually have a vote or veto unless explicit guardrails say otherwise.
Transparency	The rationale, assumptions, and expected implications are communicated so others can understand the choice.
Accountability	The decision owner remains responsible for outcomes and should revisit the decision if assumptions prove wrong.

What makes it work

At its best, the Advice Process shifts the conversation from “Who has the authority?” to “Who has the best insight, and who needs to be heard?” That usually improves both speed and quality when knowledge is distributed across the organization. But it only works if people trust one another, share information openly, and understand that “seeking advice” means genuine engagement rather than a symbolic courtesy.

4. When to Use Advice Process

The Advice Process is most useful when decisions are frequent, information is widely dispersed, and the organization wants to move faster without sacrificing inclusion. It is especially powerful in knowledge-intensive businesses, professional-services firms, product organizations, mission-driven organizations, and operating environments where frontline judgment matters more than rigid central control.

It is also helpful when leadership is trying to reduce escalation and strengthen local ownership. In practice, it often sits inside broader organizational effectiveness efforts that clarify decision rights, simplify governance, and build a more accountable culture.

To use it well, teams need at least a basic fact base: the decision to be made, the alternatives, the people affected, the relevant constraints, and the likely risks and benefits. Small decisions may take a few conversations over a day or two. Larger decisions may require structured interviews, financial analysis, scenario testing, and several rounds of consultation.

It is not a good fit for every situation. It tends to perform poorly when legal or regulatory rules require formal approval, when a crisis demands immediate command, when roles are unclear, or when the culture lacks trust and candor. It can also produce misleading conclusions if the decision owner consults selectively, ignores dissenting views, or uses the process merely to legitimize a pre-made decision. Modern practitioners therefore usually add clear guardrails, spending thresholds, and escalation rules rather than treating the framework as pure ideology.

5. How to Apply Advice Process: Step-by-Step

1. Clarify the decision and scope. Start by defining the exact question to be decided, the time horizon, and the boundaries. Is this a policy choice, an operating change, a hiring decision, a capital investment, or a customer-facing decision? Be explicit about what is in scope and what is not.

2. Name the decision owner. The process breaks down when responsibility is fuzzy. Assign one person to own the process and the final call. That person may be the role holder closest to the issue, the budget owner, or the initiative lead, depending on the organization’s governance model.

3. Gather the required inputs and data. Assemble the facts before seeking advice. That may include financial data, operational metrics, customer feedback, legal constraints, risk assessments, benchmarks, and relevant prior decisions. For ambiguous issues, add interviews or a workshop to surface concerns and alternatives.

4. Define who must be consulted. Separate stakeholders into two lists: people with expertise and people materially affected. The same person may belong to both groups. Be disciplined here; under-consulting creates blind spots, while over-consulting creates drag and turns the process into a committee.

5. Run the advice conversations. Share the issue, the options, the fact base, and the constraints. Ask for recommendations, risks, assumptions, and second-order effects. Encourage people to challenge the framing, not just react to the preferred option. The standard is not courtesy; it is substantive input.

6. Construct the decision artifact. For simple choices, this may be a one-page decision memo. For larger matters, it may be a decision log, options matrix, business case, or risk register. Capture the recommendation, the advice received, the reasoning, the trade-offs, and any conditions under which the decision should be revisited.

7. Decide, communicate, and act. After taking advice, the decision owner makes the call and explains the rationale. Good practice is to state what was decided, why, what alternatives were rejected, what assumptions matter most, and who will implement what by when.

8. Test sensitivities, align stakeholders, and iterate. For consequential decisions, pressure-test the conclusion against alternative assumptions, new data, and edge cases. Then socialize the outcome, address unresolved concerns, and refine the operating rules if the process revealed role confusion or governance gaps.

6. Example: Advice Process in Action

The situation

A $700 million industrial manufacturer had given plant leaders more autonomy, but capital decisions still drifted upward to a central committee. A plant manager wanted to invest in packaging automation to reduce rework and improve on-time delivery, yet prior decisions had taken months and often ignored local operating realities.

Why this framework was chosen

The company wanted faster decisions without losing financial discipline. The Advice Process was selected because the issue was important but did not require a full executive committee debate if the right people were consulted and the economics were transparent.

How it was applied

The plant manager was named decision owner. She gathered data on downtime, labor hours, defect rates, payback period, safety implications, and customer service impact. She then sought advice from maintenance, frontline operators, finance, procurement, safety, and two leaders from other plants that had made similar investments. The consultation surfaced one key insight: the original vendor proposal understated training time and overstated throughput gains.

The outcome

The manager approved a revised investment with a different vendor, a phased rollout, and explicit success metrics for the first 90 days. The company later used the same logic in a broader organizational design effort to clarify which operating decisions belonged at plant level, which required shared-service input, and which still needed corporate approval.

7. Strengths and Limitations

Strengths

• Balances speed and inclusion. It avoids both slow consensus processes and unnecessary escalation.
• Clarifies accountability. One person decides and owns the outcome.
• Uses distributed knowledge. It taps expertise and frontline insight that hierarchies often miss.
• Builds engagement. People are more likely to support decisions when they were genuinely heard.
• Works with complexity. It is well suited to environments where no single manager has all the facts.

Limitations

• Depends heavily on culture. In low-trust settings, advice may be political, guarded, or ignored.
• Can become ambiguous. If domains and guardrails are unclear, people do not know who really decides.
• Invites inconsistency. Different decision owners may consult with very different levels of rigor.
• Does not remove power dynamics. Senior voices can still dominate informally even without formal approval rights.
• Can be misused as theater. Teams sometimes “seek advice” after the decision is already made.

8. Common Pitfalls and How to Avoid Them

• Treating advice as consensus. When teams assume everyone must agree, the process slows down and accountability disappears. Avoid this by stating clearly that consultation is required but unanimity is not.
• Choosing the wrong decision owner. If ownership sits too high, the process becomes hierarchy in disguise; too low, and the person may lack context. Assign the decision to the role closest to the issue that can reasonably bear the consequences.
• Consulting too narrowly. Important risks are missed when only supporters or technical experts are heard. Require the decision owner to consult both expertise holders and affected parties.
• Consulting too broadly. Pulling in everyone turns the framework into a committee. Define consultation thresholds based on impact, risk, and reversibility.
• Failing to document rationale. Without a record, people cannot learn from the decision or understand the trade-offs. Use a simple memo or log for consequential decisions.
• No guardrails. The process becomes risky if there are no rules for legal, safety, budget, or reputational boundaries. Set explicit exceptions and escalation paths.
• Stopping at the decision. Some teams make the call but never track outcomes. Build in follow-up reviews so the organization learns which assumptions were right.

9. How Advice Process Relates to Other Frameworks

Advice Process vs. consensus decision-making

Consensus aims for broad agreement before a decision is made. The Advice Process aims for broad input before an accountable individual decides. If commitment and collective ownership matter more than speed, consensus may be better. If speed and clarity matter more, Advice Process is usually stronger.

Advice Process vs. RACI, DACI, and RAPID

RACI, DACI, and RAPID are role-clarity frameworks: they specify who recommends, who decides, who must be consulted, and who executes. Advice Process is lighter and more principle-based. In many organizations, the two are complementary: role frameworks clarify the governance, while Advice Process shapes how a decision owner engages others.

Advice Process vs. Vroom-Yetton-Jago

Vroom-Yetton-Jago helps a leader choose how participative a decision process should be, based on factors such as quality requirements, time pressure, and the need for commitment. Advice Process is one concrete method a leader might choose when broad input is needed but formal group decision-making would be too slow.

Advice Process and formal operating models

As organizations scale, the Advice Process often needs supporting change management to build new habits, train managers to give and receive advice well, and reinforce the behavioral norms that make decentralization work. On its own, the framework is a decision rule; it is not a full operating model.

10. Key Takeaways

• Advice Process is a participative decision-making framework where one person decides after seeking advice from experts and affected stakeholders.
• Its central benefit is combining local ownership and speed with broader input and stronger decision quality.
• It works best in decentralized, trust-based organizations where information is distributed and roles are reasonably clear.
• It is not consensus, not voting, and not an excuse to bypass governance where legal, financial, or safety controls are required.
• To apply it well, define the decision owner, consult the right people, document the rationale, and review outcomes.
• Its biggest risk is superficial consultation that creates the appearance of participation without the substance.

11. FAQs About Advice Process

Is Advice Process still relevant today?

Yes. It remains highly relevant in organizations trying to move faster, empower frontline teams, and reduce unnecessary hierarchy. What has changed is that many companies now use it with clearer guardrails, decision logs, and role definitions than early self-management advocates sometimes described.

What is the difference between Advice Process and consensus decision-making?

Consensus seeks agreement from the group before action. Advice Process requires consultation, but the final decision stays with the decision owner. In practice, Advice Process is usually faster and clearer on accountability, while consensus may generate stronger shared ownership for a narrower set of decisions.

Can small or early-stage companies use Advice Process?

Absolutely. In fact, smaller companies can often use it more easily because communication lines are shorter and roles are less bureaucratic. The key is to keep it lightweight: define who owns the decision, ask the right few people for input, and avoid turning every choice into a workshop.

How long does it typically take to apply Advice Process in a real project?

For a modest operating decision, it may take a few hours to a few days. For a major policy, investment, or organizational choice, it may take several weeks if data gathering and consultation are substantial. The timeline mainly depends on decision size, stakeholder complexity, and how reversible the choice is.

What data is needed to use Advice Process?

The minimum useful inputs are a clear decision statement, the available options, relevant constraints, and a map of who has expertise and who is affected. Better decisions come from adding economics, risk analysis, customer or employee feedback, and evidence from similar past decisions.