Someone calls, emails, or messages your business with a question you’ve answered hundreds of times. You know the answer. But you’re busy, so you type it from memory again. The next person on your team gives a slightly different version. Try this with one question you get every week: 1. Write down the answer you actually give. Include any conditions or details your team needs to check. 2. Paste the question and your rough answer into ChatGPT, Claude, or whichever AI tool you use. 3. Ask it to make a reply you can save: Read the result, fix anything inaccurate, and save it where your team already works. Update it when your policies change. The goal isn’t to have AI answer for your business. It’s to make an answer you’ve already figured out easy for everyone on your team to use. 🙏

Trying a new tool? Give the comparison a job. Pick one task you already do. Use the same non-sensitive input and the same definition of a good result. Compare the output, correction time, effort, and running cost. When you post a tool note, include: TASK: What did you use it for? SETUP: Which tool, version or plan, and date? RESULT: What did it get right and wrong? REVIEW: How much checking or cleanup did it need? FIT: Would you use it again for this task, and why? A polished demo is a starting point. The useful question is whether the tool improves your actual process after review and cleanup. One test is evidence about that test, not every business.

You do not need technical vocabulary to ask a useful question. GOAL: What are you trying to get done? STEP: Where are you stuck? EXPECTED: What should have happened? ACTUAL: What happened instead? TRIED: What have you already tested? Include the tool name and a small, anonymized example if they help. Include exact error wording with private details removed. Ask is for a specific question or stuck step. Teardowns is for mapping a whole process. Start with the work you need to do. When something fixes it, add the fix to your post so the next person can use it.

A win can be small: fewer corrections, a faster handoff, or someone else running the process without you. Post these five things: BEFORE: What happened, and what was the starting point? CHANGE: What did you actually change? CHECK: What did you test, over how many runs, and when? RESULT: What improved? Separate measured results from estimates. LIMIT: What still needs a person, breaks, or remains untested? Compare the same task before and after. Include review and cleanup time. Hours freed are not automatically cash saved. A failed test with a clear lesson is worth sharing too. Leave out private client details.

Pick one process you actually do. Copy these lines into a new Teardowns post: PROCESS: What are you trying to get done? TRIGGER: What starts it? STEPS: What happens now, and who does each step? FREQUENCY: How often does it repeat? TIME: How long does it take? Say whether you timed it or estimated. STUCK POINT: Where does it wait, get copied, or need rework? DONE: What would a correct result look like? TRIED: What have you already tested? A rough description is enough. Leave out client names, account details, and private documents. If you are replying, first check your understanding of the process. Ask for missing context, separate decisions from data movement, and suggest one small test. Sometimes the useful answer is to simplify the process or leave a step manual.