In most small businesses that have started using an AI assistant, one person becomes quietly good at it. She has learned, through trial and error, how to ask for a quotation letter that sounds like the firm, or a summary of a supplier contract that picks out the clauses the owner cares about. Her colleagues, working two desks away, type one-line requests into the same tool, get weak answers, and conclude that the tool is not much use. The knowledge exists inside the business. It simply never travels.
This article describes a plain remedy that needs no new software and no budget: a shared prompt notebook. It is a single document where the team records the requests that work, with enough context that anyone can reuse them. I will set out what goes into it, how to start one in an afternoon, and how to keep it alive after the first enthusiasm fades.
Why good prompts stay locked in one head
Skill with an AI assistant is built from small discoveries. You learn that the assistant writes a better reply when you paste in the customer's original message. You learn that asking for three versions gives you one you can use. You learn that a certain instruction stops it from inventing figures. None of these discoveries feels important enough to announce, so nobody announces them.
The second reason is that a prompt is tied to a situation. The person who wrote it knows which customer it was for, what tone was wanted, and what the assistant got wrong the first time. Without that background, the same words copied by a colleague may produce something quite different. Sharing the words alone is not enough. The situation has to travel with them.
The third reason is ordinary shyness. People are often unsure whether they are using the tool properly, and they do not want to show their working. A shared notebook, treated as a set of recipes that everyone improves, takes away that worry. Nobody is being examined. The team is simply writing down what works.
What one entry looks like
An entry in the notebook should be short enough to read in a minute and complete enough to use without asking anybody. Five parts are sufficient.
The first is the task, written the way the team would say it aloud: reply to a customer asking for a discount, turn rough meeting notes into action points, check a quotation for missing terms. The second is when to use it and when not to. A prompt that suits routine enquiries may be wrong for an upset customer, and the entry should say so.
The third part is the prompt itself, with square brackets marking what must be filled in each time, such as the customer's message or the product name. The fourth is an example of a good result, pasted in, so that a newcomer knows what to expect and can tell when the assistant has drifted. The fifth is the check: the one or two things a person must verify before the output leaves the building. For a quotation it may be the price and the validity date. For a letter it may be the name and the amount.
That fifth part matters most. An assistant can write fluently and still be wrong, and the notebook should make it normal to verify the facts that carry risk. A recipe that ends with a check teaches the habit along with the shortcut.

Starting the notebook in one afternoon
You do not need a workshop. Call the team together for an hour and ask one question: what have you asked the assistant in the past month that actually saved you time? Write each answer on a board. You will usually find between five and ten tasks, several of them shared by more than one person.
Pick the three that come up most often. For each one, ask the person who does it best to show the prompt they use, and write the entry together in the five-part form. Do it on a shared screen so everyone sees how little effort an entry takes. By the end of the hour you will have three working recipes and a team that understands the format.
Store the notebook where the team already works. A shared document or a pinned note in the office messaging group is enough. If people have to open a new tool to find it, they will stop looking. Give it a plain title, put the three entries at the top, and add a short line saying who to ask about each.
Keeping it alive
Most shared documents die within a month because nobody owns them. Give the notebook a keeper. This need not be the most senior person or the most technical. It should be someone who is orderly and who is trusted by colleagues. The keeper's job is small: add new entries in the agreed form, remove ones that no longer work, and remind the team that the notebook exists.
Attach the notebook to a rhythm the business already has. If you hold a Monday meeting, give it three minutes: has anyone found a prompt worth adding, and has any entry let someone down? A failed entry is as valuable as a new one, because it shows where the assistant cannot be relied on. Record the failure in the entry itself so the next person is warned.
Resist the urge to collect everything. A notebook with a hundred entries is as useless as no notebook, because nobody can find anything. Keep only the prompts for tasks that recur. A good test is whether the task will come up again within the month. If it will not, it does not belong.
What should never go into a prompt
A notebook is also the natural place to state the limits. Write them on the first page, in plain words. Customer bank details, identity numbers, passwords and anything a client has shared in confidence should not be pasted into a public AI tool. Where an entry needs customer information, show how to replace the sensitive parts with placeholders before sending.
Add one more rule: the person who sends the output is responsible for it. The assistant drafts, and a named human being approves. This single sentence prevents most of the embarrassments that come from sending out text nobody has read carefully.
What the owner gains
The first gain is consistency. When four people use the same recipe for a customer reply, the business begins to sound like one firm, not four individuals. The second is resilience. If the person who was good with the assistant goes on leave, the work does not stall, because the method is written down.
The third gain is quieter. The notebook becomes a record of how the business actually works: which tasks repeat, where judgement is needed, what must always be checked. Owners who read their own notebook after three months often find that it describes their operations more honestly than any manual they have written. It is, in effect, a process document that the team wrote without being asked.
There is an old principle in teaching that a skill is only truly learned when it can be passed on. The same holds for a business learning to use a new tool. Individual cleverness is a beginning. Shared practice is what makes it an asset.
One question to take away
If your best AI user were away for a fortnight, which three tasks would slow down, and are the prompts for those tasks written anywhere? Tell me in the comments what your team would put on the first page of its notebook; I read every reply.
If you would like practical notes like this in your inbox, you can join the free newsletter.
📬 Join 49,000+ Indian Professionals
The Inner Circle newsletter delivers curated MSME intelligence, leadership wisdom, and strategic insights every week — completely free. Plus receive the 20 Gita Lessons PDF as a welcome gift.
Subscribe Free →Ready to Go Further?
Is your MSME AI-ready? I help Indian businesses understand and deploy practical AI workflows — from automation to decision intelligence. Book a focused strategy session.
Book a Digital Strategy CallPublished 18 November 2026 · dibyenduchoudhury.com