The Advice Process

You have probably been told your organization is non-hierarchical, and then watched a decision sit for three weeks because nobody was sure they were allowed to make it.

That is the gap the advice process closes. It is the single most important mechanic in self-organization, and it is almost always the first one people get wrong.

What it actually says

Anyone can make any decision, after seeking advice from everyone meaningfully affected and everyone with expertise.

Read it twice, because both halves matter.

The first half is real. Not "anyone can propose". Not "anyone can make small decisions". Anyone can make any decision, including ones that spend money, change direction, or affect people who outrank them on whatever informal ladder your group pretends not to have.

The second half is binding. Seeking advice is not a courtesy. It is the condition that makes the first half safe. Skip it and you have not used the advice process; you have just acted unilaterally and used a nice phrase to describe it.

What it is not

It is not consensus. You do not need agreement. You will often make a decision that someone advised against. That is allowed and expected.

It is not a vote. Nobody counts. Advice is not weighted by how many people said the same thing.

It is not delegation. No one gave you this authority for this decision. You already had it.

It is not a suggestion box. You have to actually go and ask, specifically, the people it lands on. Posting in a general channel and waiting is not seeking advice. It is announcing.

How to run one

1. Write the decision down before you ask anyone.

One paragraph: what you intend to do, what it will cost, what changes if it works. If you cannot write it in a paragraph you are not ready to seek advice, you are still thinking. Seeking advice on a half-formed idea wastes everyone's attention and produces vague advice you cannot act on.

2. List who is meaningfully affected and who knows something.

These are two different lists and people confuse them constantly.

Affected means their work changes, their budget changes, or they carry the consequence if it goes wrong. Expertise means they have done this before or hold information you do not. Someone can be on both lists. Someone senior can be on neither.

Keep it honest in both directions. Padding the list with everyone is how the process becomes theatre. Trimming it to your friends is how it becomes a rubber stamp.

3. Ask them individually, and ask a real question.

"Any thoughts on this?" gets you nothing. Ask what you actually want to know:

"I'm planning to move our invoicing to the first of the month instead of on completion. You handle the client relationships. What breaks?"

Give them enough context to disagree with you. If you present it as already decided, you will get agreement, and agreement you engineered is worth nothing.

4. Listen for the thing you did not want to hear.

The value of the process is concentrated in the advice that contradicts you. Everything else is confirmation. If nobody pushed back at all, you either asked the wrong people or asked in a way that discouraged honesty. Go back.

5. Decide, and say what you did with the advice.

This is the step people skip, and skipping it is what kills trust in the process faster than anything else.

When you announce the decision, name the advice you took and the advice you did not take, and why:

"Ana pointed out this breaks the retainer clients' expectations, so I'm exempting retainers. Tom thinks we should wait a quarter. I'm going ahead now because the cash gap is the thing hurting us this month, and waiting has a cost too."

Someone who is overruled with a reason stays in the process. Someone who gives advice into silence stops giving it, and you lose the thing that made the mechanic work.

Where it goes wrong

"I asked and nobody replied, so I went ahead." Silence is not advice. Chase it, or narrow your list to people who will actually engage. If your organization is systematically silent, that is a different problem and this process will not fix it.

Seeking advice after deciding. People can tell. Once they have been through this twice they stop giving real advice, and you are left with a ritual.

Asking so many people that nothing moves. If your list is fifteen people for a decision about which project management tool to use, your list is wrong. Affected and expert, not interested.

The founder's advice weighs more. In practice, in almost every young organization, it does. Name this out loud rather than pretending. A founder who says "this is advice, not a decision, and I will back you if you go the other way" and then actually does it once, in public, is worth more than any amount of policy.

Using it for decisions that belong to a role. If someone holds the role of Bookkeeper and the decision is which day invoices go out, they decide. They may seek advice; they do not need to. Running the advice process on everything makes it heavy and people stop.

What good looks like

A decision that would have taken three weeks and a meeting takes four days and three conversations. The person closest to the work makes it. Two people disagreed and said so, in writing, and are still on good terms. The reasoning is written down where someone can find it in six months and understand why.

And nobody asked for permission.

Try this week

Take one decision currently stuck in your organization. Find the person closest to the actual work. Tell them: this is yours, seek advice from these three people, decide by Friday, and write down what you did with what they told you.

Then, when they decide something you would not have, back them in public.

That single act teaches the process better than this article does.