Applied Capstone: an AI-assisted business improvement plan
Eight modules become one improvement plan a colleague could run from the document without you explaining it.
Objectives
- Assemble the course's outputs into one actionable improvement plan.
- Select and justify a single first use case.
- State the governance position and data boundary that apply to it.
- Define the human+AI workflow, with the review step placed deliberately.
- Set a baseline, a value measure and an evaluation date.
- Name the risks and the stopping condition.
- Plan adoption with the people who will run it.
Introduction
Eight modules have each produced a piece. This module assembles them into a single plan a business could actually act on in the next quarter — not a strategy document, but a short written position on one improvement, why it is worth doing, and how you will know.
It is deliberately narrow. Plans that propose transforming a business produce nothing; plans that propose one measured change to one process produce evidence, and evidence is what makes the second change possible.
The plan is also built to be revisited, because the answer to "was this worth it?" only exists after the evaluation date you set today.
What This Plan Is For
One improvement, evidenced — and why narrow plans succeed where transformation plans do not.
Assembling the Eight Pieces
Walking back through the course, taking one output from each module.
Pressure-Testing It
Three questions that separate a plan from a proposal.
The nine fields
One from each preceding module, plus the review trigger. Short is fine; vague is not.
Field → From:
- The use case, and why this one first — Module 2 or 3
- What stays human, and what may be delegated — Module 4
- Governance category and named approver — Module 5
- The data boundary for this use case — Module 6
- Baseline, value measure, and honest costs — Module 7
- Adoption approach and who is involved — Module 8
- The human+AI workflow, with its review step — Modules 2 and 4
- Risks and the stopping condition — Modules 5 and 7
- Evaluation date and review trigger — This module
The three pressure questions
Apply these once the nine fields are written.
yet a plan.
thought through.
Most businesses rewrite the workflow field after question one, because the review step turns out to have been described rather than specified.
- Could someone else run this from the document? If it depends on you explaining it, it is not
- What is the honest worst case, and who bears it? A plan without a named worst case has not been
- What would make us stop? Written before the evidence exists, or it will not be honest later.
Practical exercise
≈8 minWrite the nine fields, pulling directly from Modules 2–8 rather than starting fresh. Make the workflow concrete: the steps, who does each, and exactly where the review sits.
Make the baseline real. If you do not have one, the first two weeks of the plan are counting. Apply the three pressure questions and rewrite whatever they broke.
Write the adoption paragraph: who runs it, how they were involved, and what they were told about the job question. Set the evaluation date and the stop condition, both before starting.
The learner produces: a nine-field improvement plan, revised after three pressure questions, with a concrete workflow, a real baseline, an adoption paragraph and a pre-committed stop condition. Expected outcome: the learner leaves with something a colleague could run — and knows which field they were tempted to leave vague, which is almost always the review step or the stop condition.
Nothing is submitted or stored — this is yours. If you would rather not use your own material, or cannot right now, use the supplied alternative in the module's no-tool fallback instead; both teach the same skill.
Your progress
0 of 2 required activities complete in this module · course progress 0%
- ○ GlobSynk Lab™ · optional
- ○ Reflection
- ○ Checkpoint
GlobSynk Lab™
optional, ≈5 minAbout GlobSynk Lab™. GlobSynk Lab™ is the hands-on practice experience used throughout GlobSynk Academy. This Lab is optional hands-on practice: complete it now, skip it and continue the module, or return to it later. Skipping this Lab does not prevent you from continuing the course. For these activities you'll use an AI assistant that you already have access to, then return to Academy to continue your reflection and checkpoint.
Give your plan to someone else in the business and ask them to run through it aloud, without you explaining anything.
Wherever they stop and ask a question, that is a field that only exists in your head. Fix those. A plan that survives being read by someone who was not in the room is the only kind that survives being handed over.
Reflection
≈2 minLook at your plan. If this works, what is the second change you would make? If it does not, what will you actually do — and is that written down anywhere?
This reflection is yours alone — it is never sent to GlobSynk or stored. Only the fact that you completed it is saved.
Checkpoint
5 questions · unscored gate · instant feedback · retry as often as you like.
Answer all 5 questions to continue.
Key takeaways
- One measured improvement produces evidence; a transformation programme produces nothing.
- A described review step is not a placed one — name who, when, and against what.
- An estimate presented as a measurement is not a baseline.
- If someone else cannot run it from the document, parts of it exist only in your head.
- The stop condition must be written before the evidence exists.
Practice in Prompt Lab — optional
OptionalPractice the field you were most tempted to leave vague.
In Prompt Lab, take the field you found hardest — usually the review step or the stop condition — and test it against three invented situations to see whether it actually decides anything. A stop condition that never triggers is not a stop condition. Use invented business scenarios rather than your real operational or customer data.
Optional, and never required. Prompt Lab is not GlobSynk Lab™. Opening it is not part of module completion, the checkpoint, course progress, the Final Assessment, the certificate or Reward Points, and a learner who never opens it completes this course exactly as normal. Academy never depends on Prompt Lab being reachable.
Practice Prompting in the Real WorldOpens in a new tab. Optional practice — never required for this module, the checkpoint, your progress, the Final Assessment, the certificate or Reward Points.
Continue with GlobSynk — optional
OptionalDifferent plans lead to genuinely different next steps, so these are alternatives rather than a set. Pick the one matching what your plan is actually about — or none.
Your plan centres on a repeatable operational process.
Explore FlowSynkYour use case requires something to be built rather than adopted.
Explore BuildSynkYour business wants a packaged environment rather than a single capability.
Explore GlobSynk for Small BusinessYour immediate task is making the case to a board, an owner or a team.
Explore GlobSynk Present
Opens in a new tab. Optional — never required for this module, the checkpoint, your progress, the Final Assessment, the certificate or Reward Points. Each product decides its own access, eligibility and subscription; Academy does not.
Before you move on
You have a plan a colleague could run, tested against three questions that usually break at least one field, with an evaluation date and a stop condition set in advance. One module remains, and it teaches nothing new. It puts the nine parts together as a single method and prepares you for the Final Assessment.