A long proposal lands in your inbox an hour before the meeting. You skim it, you get the gist, and then the meeting starts and you have nothing sharp to ask. So you nod along while the other person drives. Most people fix this by asking AI for a summary. But you already skimmed it. You do not need it read back to you. You need to know what to question. So ask for questions, not a summary. Before: you walk in with "looks good, let's talk," and you leave having agreed to a timeline you never really read. After: you walk in with a page that asks whether eight weeks means from signing or from kickoff, whether the price covers changes later, and whether the plan is quietly assuming your data is ready on day one. Same document. Very different meeting. Here is the prompt. Use a document you are allowed to share, with no private details in it. Paste the document after the final line. You are helping me prepare for a meeting. Below is a document. Do not summarize it. Give me a one-page question sheet with five to seven questions I should ask in the meeting. Group them under Scope, Timing, Cost, Assumptions, and Missing details. For each question, add one short line on why it matters. Use only what is in the document, and if something important seems missing, say so. Paste your document after this line: In about ten minutes you have a page of real questions instead of a summary you will forget. One caution: read the questions before you trust them. AI can misread a page, or flag a gap that is actually sitting on page twelve. The sheet is a smart first pass, not the final word. Found a question that made you stop and think? Start a new post here with the best one AI dug up, and say which meeting it was for. Someone else is about to walk into the same kind of meeting, and your question might be the one they needed.

Most people pick their first AI task the wrong way. They pick the thing that looks most impressive. “Let AI answer customer emails.” “Let AI run follow-up.” “Let AI make decisions from my notes.” That can work later. But it is usually the wrong first move. Your first AI task should be boring, repeated, and easy to check. Use this simple rule: Pick by reversibility, not excitement. Ask: If AI gets this wrong, can I catch it before it reaches a customer, employee, vendor, or bank account? If yes, it may be a good first test. If no, shrink the task. Here is the best example. Bad first task: Let AI answer customer emails automatically. Why it is risky: - the customer sees it first - it can make promises - it can miss context - it can get the tone wrong - the mistake is hard to pull back Better first task: Let AI draft customer email replies for a human to review. Same workflow. Much lower risk. The AI helps with the blank page. The human still owns the promise. Use this test card: Workflow: Input I already have: Output I want: Who reviews it before use: What could go wrong if AI is wrong: How I will test it safely: Keep / adjust / discard decision: Example: Workflow: Draft replies to customer support emails. Input I already have: The customer email, our FAQ, our tone rules, our refund policy. Output I want: A suggested reply and a list of anything AI is unsure about. Who reviews it before use: Me. What could go wrong: It promises a refund we do not give, or sounds too cold. How I will test it: Run it on five old emails I already answered. Compare the drafts to what I actually sent. Send nothing. That is a safe first test. You do not need a new tool yet. You do not need a giant automation build. You need one small workflow that is safe to test. Your action: Pick one repeated task this week. Run it through the card. If you want help, make a new post with your Workflow Test Card.