Advisory / AMA sessions

Use advisory for decisions like

• Should we ship this workflow now, simplify it, or cut it?
• Are we solving this with RAG, agent workflows, prompt design, or not at all?
• Is our evaluation plan measuring the right thing, or just busy work?
• Does this roadmap, prototype, or rollout plan survive contact with reality?
• Do we need a bigger workshop, or can this be resolved in one focused session?

What this is

High-signal working time focused on the decision in front of you, not a general brainstorming call.

Advisory is best when the team already has context and momentum. The session can be a deep dive on one hard question or a structured review across a few related decisions. The goal is to leave with sharper tradeoff calls, not another round of vague discussion.

A typical session

1. Get the core question on the table fast
2. Review the constraints, options, and tradeoffs that matter
3. Push on weak assumptions, hidden risks, and fuzzy language
4. End with a decision, recommendation, or narrowed set of next moves

What you get

• A written decision memo or review note you can share internally
• Clear tradeoff rationale, not just a recommendation with no spine
• A next-actions list for the team, owners included when useful
• Optional async review of docs, roadmaps, prototypes, or eval plans

Before we meet

• Send the core question in advance, not just a pile of context
• Share the one doc, prototype, or decision memo that matters most
• Prioritize the decisions so we spend time where it counts
• Bring someone who can act on the answer