A little preparation turns a one-hour call into a plan you can act on. Here is a simple checklist.
A good consultation is a focused conversation, not a lecture. The more clearly you describe your situation, the more specific and useful the advice you receive.
1. Write down the one decision you need to make
Start with a single sentence: "We need to decide whether to rebuild or refactor our checkout." A clear question shapes the whole session and stops it drifting.
2. Gather the context people forget
Bring your current stack, team size, rough budget, deadlines and anything already tried. Links to the product, a short diagram or a screenshot are enough.
3. Name your constraints honestly
Legacy systems, compliance requirements and hiring limits all change which answers are realistic. Sharing them early saves time.
4. Decide how you will measure success
Faster pages, fewer incidents, higher conversion: pick one or two measures so recommendations can be judged against something concrete.
5. Plan what happens afterwards
Ask who will own the next steps and when you will review progress. A written summary is only valuable if someone acts on it.