Sgnalcraft

The applied-AI desk for people who run things.

Get the 7am brief Start the AI Foundations course
Day 14 · Make it run without you

Your own 30-day workflow

Have one page that decides what you keep using, and what you stop.

13 min readPlus one task, about 10 min

The one idea

You now know enough to decide what to keep. Deciding what to keep is the actual skill. The course has given you experiments, not commandments. One prompt may have earned a permanent place. One automation may have proved too fragile. One tool may have been convenient for a week and wrong for your real documents.

Today is assembly, not a summary. You are taking the artefacts you made — the reliability baseline, saved prompt, comparison score, verification rule, decision, image rule, automation and never-paste list — and putting the useful parts on one page. The page is deliberately small. If it contains twenty commitments, it will become another document you avoid.

A workflow earns its place by surviving ordinary use. Write down what you will use every week, what you will verify, what you will never paste, and when you will review the decision. Then remove one thing that did not earn its place. The cut is as important as the collection.

Think of the page as a control panel, not a manifesto. You should be able to read it on a Monday morning and know which prompt to open, which claims to check and which information to leave out. If a rule needs a paragraph of explanation, put the explanation elsewhere and keep the page to the decision. A small visible rule is more likely to be followed than a perfect rule buried in a folder.

Why it matters

Most people learn a dozen things and change nothing. They leave with a folder of prompts, a list of tools and a vague intention to become more efficient. A page with three entries beats a plan with twenty because you can remember it while doing actual work.

The page also puts limits beside benefits. A saved prompt without a verification rule invites over-trust. An automation without a failure check invites silent errors. A useful tool without a privacy boundary invites careless pasting. You have seen each of these edges during the course, which is why this is not a motivational summary. It is a small operating manual for your own behaviour.

The thirty-day review matters because your judgement will improve with evidence. After a month you can ask which entries were used, which saved time, which needed correction and which were never opened. A workflow is not a monument. If it does not earn its keep, delete it. If it works but creates a new risk, redesign it. The review date is how you keep the page honest.

Use simple measures. Count how many times you reached for a prompt. Estimate the minutes it saved. Record corrections, especially corrections to names, dates, amounts or claims. Note whether the automation was helpful on bad input, not only on the clean example you built. You do not need a dashboard. Four handwritten numbers and an honest decision are enough to improve the next month.

Turn fourteen days into a working system

  1. Gather the outputs, not the lessons. Find your Day 1 reliability baseline, Day 4 reusable template, Day 5 scorecard, Day 6 verification rule, Day 9 decision, Day 10 image line, Day 11 audit, Day 12 automation and Day 13 never-paste list. If an exercise produced nothing you can find, that is information too.
  2. Sort each item into one of three piles: use weekly, verify or avoid. Do not put an item in ‘use weekly’ because it is interesting. Put it there only if it solves a recurring problem you actually have.
  3. Test your candidates against the last seven days. Ask whether you would have reached for each one without being told. A system that needs a course author standing beside it is not yet a habit; add a location, shortcut or reminder, or remove it.
  4. Write the one-page system with concrete names and locations. ‘Use AI for admin’ is not a usable instruction. ‘Run Client Update prompt in saved-prompts note every Thursday; verify dates against the source’ is.
    MY AI SYSTEM

Three things I will use AI for, every week:
1. ______
2. ______
3. ______

My saved prompts: [where they live, and what each is for]

Two things I will always verify by hand:
1. ______
2. ______

I will never paste: ______

One automation that runs for me: ______

I will review this page on: [date, 30 days from today]
  5. Make the cut. Choose one thing to stop doing with AI: a task that never earned its place, a tool you did not use, or an output you corrected so often that doing it yourself was simpler. Write the reason beside the deletion.
  6. Teach one part of the page to another person, then schedule the review. Explaining the surprising part exposes what you understand, and the dated review stops this page becoming another forgotten promise.
A thirty-square calendar with five squares tinted, placed beside a notes page with several written sections. AI-generated illustration
five deliberate entries on a month, beside the page that explains what each one is for.

See it

Imagine the page for a small business owner. The three weekly uses are: turn rough notes into a client update, turn a long supplier document into questions, and draft replies that the owner edits before sending. The saved prompts live in one note with a one-line description beside each. The owner verifies names, dates and prices by hand. Customer identifiers never go into a consumer chat. One private review workflow turns new enquiries into a short list, but it never sends a reply without a person reading it.

That page is not impressive. It is useful. It says where the prompts are, what the assistant is allowed to prepare, what must be checked and what information stays out. It also contains a review date. In thirty days the owner can count uses rather than rely on memory: three client updates drafted, eight supplier questions prepared, twenty replies started, two corrections, no use for the abandoned image workflow. The page can then be edited from evidence.

Compare that with a page that says ‘use AI to save time, automate marketing and improve research’. The second page sounds ambitious and cannot tell you what to do on Thursday morning. A working system is specific enough to run and modest enough to change.

The page should also make stopping easy. If a prompt no longer matches the way you work, cross it out and write the replacement rather than quietly keeping two competing versions. If the automation has not run in a month, say so. If a verification rule catches errors every week, keep it visible. You are not trying to prove that the technology belongs in your life. You are deciding which small pieces have earned the space.

Write the page, then teach it

The cut and the explanation are the two steps that turn fourteen days of exercises into something that survives contact with a normal month.

  1. Get out everything you built: your Day 1 baseline, Day 4 template, Day 5 scorecard, Day 6 verification rule, Day 9 decision, Day 10 image line, Day 11 audit, Day 12 automation and Day 13 never-paste list. Put the originals beside you rather than relying on memory.
  2. Write it onto one page, using this structure. One page: if it needs two, you are keeping too much. Replace every blank with a real task, a real location, or a real rule.
    MY AI SYSTEM

Three things I will use AI for, every week:
1. ______
2. ______
3. ______

My saved prompts: [where they live, and what each is for]

Two things I will always verify by hand:
1. ______
2. ______

I will never paste: ______

One automation that runs for me: ______

I will review this page on: [date, 30 days from today]
  3. The cut. Go back to your Day 11 list and pick one thing to stop doing with AI — something that never earned its place, or that you never actually did. Removing it is a real decision, and it is what protects the three you are keeping. Write ‘stopped because…’ beside it.
  4. The test. Write one sentence for each of the three weekly uses explaining why it survived. Include the evidence: minutes saved, a better first draft, fewer repeated questions, or a clearer decision. If you cannot say why, put that item on probation rather than in the list.
  5. Teach it. Explain one thing you learned to another person — a colleague, family member or friend. Five minutes is enough. Pick the thing that surprised you most, usually Day 6, Day 8, Day 12 or Day 13. Let them ask one question, and update the page if your explanation exposed a gap.
  6. Put the review date in your calendar now rather than tomorrow. On that date, count what you used, what failed, what you corrected and what you stopped. Keep the page only if the evidence earns it.

What you should notice

Notice how much of your system is about what not to do — what to verify, what not to paste and what to stop. Beginners assume the skill is knowing features. It is actually judgement about limits, and you have it now because you found the limits yourself rather than being warned about them.

Notice the difference between Day 2 and today. On Day 2 you asked an AI tool what you should use it for. Today you answered that yourself, from evidence you gathered. You know which tasks are repetitive, which claims need checking, which inputs should be anonymised, which prompt has earned reuse and which automation has to stop when the input is unclear. That is the whole fourteen days.

The page is allowed to be small. Three weekly uses are enough. One saved prompt is enough. One automation is enough, or none if you found that a reminder solves the problem more safely. The course is complete when your choices are deliberate, not when your system contains every feature you have seen.

Keep the page where the work happens. If your prompts live in one note, put its location on the page. If verification means opening the original document, name that document. If the privacy rule applies only to a certain account, write which account. Specificity is not bureaucracy here. It is the difference between a rule you can follow and a good intention you have to reconstruct from memory.

A tidy personal toolkit made of three tool cards, a checklist and a notebook arranged together. AI-generated illustration
a small working kit, not a catalogue: three useful tools, checks and one notebook.

If you have five more minutes

Teach the page to somebody who does not use AI. Ask them to point to the part they would misunderstand or ignore. Rewrite that part in plainer language. A system that survives a sceptical reader is usually easier for you to follow as well.

Tomorrow

That is the course complete. What comes next is the full Learn AI library — and, if you want it, the daily 7am Brief. Both are offered; neither is assumed.