A big call deserves more than one opinion. That's why JT5 puts up to 3 brains at the table and gives you a Team consensus: what to do, and why.

But a recommendation isn't a plan. You still need the steps, the weekly targets and a page you can hand to your team. It's easy to stop at the advice, or to start over in a new chat and lose what the table just worked out.

This workflow gets you both in one chat. Decide at the table, then build with one brain.

Important: if a brain shows Upgrade next to its name, or you see Upgrade required when you pick it, that brain isn't open on your login. Pick another brain, or let JT5 choose: Auto in JT5 Boardroom, AutoPilot AI in AutoPilot AI.

Mode to Use: JT5 Boardroom

Brain to Use: Auto (JT5 picks the best 3 brains for your question)

Objective: Get several expert views and one recommendation on your decision.

Example Command: Command 61 from the 75 commands from JT's Masterclass, with your decision written into the brackets:

"Pressure test this decision: [____]. List blind spots, risks, and assumptions."

Expected Output: The brains at the table answer one after another. When the last one finishes, the Team consensus pulls their views into one recommendation. Give it a minute or two.

Why This Order: Decide first. A plan built before the decision is pressure tested is just the wrong plan, built faster.

Tip: want a specific view at the table? Type @ and the brain's full name in your question, with no space after the @ (for example @Accountant CFO Brain). No list pops up, so type it out, or tick up to 3 brains yourself instead of Auto. For a pressure test, Brutal Honest Brain and 2nd Opinion Analyst are built to challenge you.

Mode to Use: The same answer. Nothing new to ask.

Brain to Use: Every brain at the table.

Objective: Find the real decision inside the answer.

Example Command: None. Read the Team consensus first. Then switch to Tabbed (one tab per brain) or Chat stream (every brain in order) and read each view.

Expected Output: A clear picture of where the brains agree and where they split. Look closely where they split.

Why This Order: The Team consensus tells you what to do. The disagreements tell you what could go wrong. Read both before you build anything.

Mode to Use: The same answer, with Try a lens.

Brain to Use: None. The lens works on the Team consensus.

Objective: Stress the recommendation with a proven thinking method.

Example Command: As soon as the answer finishes, click Try a lens right under it ("sharpen the consensus"). Pick Critique and Refine to keep what works and fix the gaps. Or open All and search Red Team vs Blue Team to attack it, then harden it.

Expected Output: A sharpened Team consensus appears below the original. The lens doesn't ask the brains again.

Why This Order: The lens only shows under the newest answer, right after it finishes, so use it now, before you ask anything else. A lens counts toward your usage like a question. Save it for decisions that matter. More in How to Use Try a Lens in JT5.

Mode to Use: AutoPilot AI, in the same chat. Click the left of the two icons inside the message box, by the mic.

Brain to Use: COO (How To Brain)

Objective: Turn the recommendation into a plan for this week.

Example Command: "Turn the Team consensus into a 5 step plan for this week."

Expected Output: A step-by-step plan that builds on the Team consensus. There is nothing to paste. The brain works from what is already in the chat.

Why This Order: The boardroom is built to decide. One brain is built to go deep. COO (How To Brain) is your on-demand playbook for step-by-step plans.

Pick the right builder. For other build jobs, pick the brain that owns the work: Accountant CFO Brain for budgets, margins and cash flow, Sales & Closer Brain for scripts and objection handling, and Marketing & Branding Brain for campaigns and messaging.

Mode to Use: AutoPilot AI, in the same chat

Brain to Use: COO (How To Brain)

Objective: Turn the plan into targets you can put on a calendar.

Example Command: Command 70: "Break the plan into weekly targets with deliverables."

Expected Output: Weekly targets, each with a deliverable.

Why This Order: A plan without deadlines drifts. Weekly targets turn the plan into something you can check every Monday.

Mode to Use: AutoPilot AI, in the same chat

Brain to Use: COO (How To Brain), or any brain. The PDF is made from the newest answer in the chat, so ask right after the answer you want on paper

Objective: Take the plan away with you and keep the chat where you can find it.

Example Command: "Send me that as a PDF."

Expected Output: A PDF, as a file right under the answer. Click the download arrow on it to save it. Asked on a boardroom answer, the PDF is made from the Team consensus. Prefer your browser's print window? Click the print icon under the answer. Then click the chat's three dots and choose Move to project to file it. Want to explore a different direction without losing this one? Choose Duplicate from the same menu. The three dots sit next to the chat in the list on the left.

Why This Order: A decision you can't find next week is a decision you'll make again. File it with the work it belongs to. See How to Attach Files, Print and Make a PDF in JT5 and How to Organize JT5 Chats With Projects.

Here is one question we ran through JT5, start to finish.

The decision. The owner of a 10-person marketing agency is choosing between a price rise and a new premium tier. They ask the JT5 Boardroom, on Auto.

The table. Auto brings Marketing & Branding Brain, Accountant CFO Brain and CEO (NFB) to the table, and each answers in turn.

The Team consensus. It sets out three things. Where the brains agree: a straight price rise is the simplest move. Where they split: whether the real problem is margin today, or how clients are grouped and where unpaid extra work slips in. And what to do first: run a client-by-client margin and scope-leakage audit, set the new price floor, and only launch the premium tier once enough clients already use the extras, or one buyer is close to certain.

The build. In the same chat, the owner switches to AutoPilot AI, picks COO (How To Brain), and asks: "Turn the Team consensus into a 5 step plan for this week." The answer opens by building on the consensus, then lays out five steps: pull the client-by-client margin and leakage audit, set the new floor and list the clients to correct, write the premium tier definition, have one conversation with one buyer, and review the data and set the 30-day action list.

One question to the table and one follow-up to one brain. The owner walks away with a decision and a week of work. What it is worth depends on doing the work.

Decide at the table, build with one brain. The boardroom gives you every angle and one recommendation. One brain turns it into the plan. Do both in the same chat, and you walk away with a decision, a plan and a page to print.