Where AI creates real business value
Identify work that benefits from speed, synthesis, structure, or scale.
✦ Course · Beginner
Use AI to plan, research, communicate, and operate faster - without losing judgment, security, or brand quality.
Start courseYOUR OUTCOME
Identify work that benefits from speed, synthesis, structure, or scale.
Gather evidence, compare options, and make uncertainty visible.
Turn goals and constraints into clear plans, checklists, and operating rhythms.
Create on-brand content without flattening your point of view.
Prepare, personalize, summarize, and follow up using the right context.
Bring tools into a workflow while controlling scope and access.
Encode recurring methods so good work becomes repeatable.
Match the depth of review to the consequence of the work.
Track cycle time, quality, adoption, and rework instead of novelty.
Choose owners, workflows, safeguards, and success signals.
What each lesson covers
Identify work that benefits from speed, synthesis, structure, or scale.
Here are the eight things my accounts team does every week: (paste the list). Sort them into four groups, needs speed, needs synthesis, needs structure, needs scale, and for each task say what a first Oppermind workflow would produce and what should stay manual.
Gather evidence, compare options, and make uncertainty visible.
Attach aurora.pdf, kestrel.pdf and marlin.pdf, then type: Compare these three telematics proposals in a table: three-year total cost, exit terms, data ownership, support hours. Where a proposal says nothing, write Not stated instead of guessing, and list what to ask each supplier.
Turn goals and constraints into clear plans, checklists, and operating rhythms.
We open a second store on 3 November. Constraints: six staff, fit-out finished 20 October, stock arrives 27 October, council sign-off still pending. Build a six-week launch plan as a project schedule with owners, and a weekly check-in checklist beside it.
Create on-brand content without flattening your point of view.
Click +, open the Brands tab and pick your kit, then type: Write three LinkedIn posts announcing our 24-hour turnaround on structural engineering reviews. Keep my actual view in them: most review delays come from unclear briefs, not slow engineers. No exclamation marks.
Prepare, personalize, summarize, and follow up using the right context.
Attach last-call-notes.docx and proposal-v2.pdf, then type: Prepare me for tomorrow's call with Harbourline Logistics: where we left off, the three objections they raised, my answer to each from the proposal, and a follow-up email I can personalise after the call.
Bring tools into a workflow while controlling scope and access.
In Settings, Connectors, connect your helpdesk and read what it will let Oppermind see and change. Back in chat, click +, open the Connectors tab, choose it, then type: Summarise open tickets tagged billing from the last 7 days: count, top three causes, and any customer who has written more than twice.
Encode recurring methods so good work becomes repeatable.
Open Settings, Skills, Create skill and name it Invoice exception check. Method: inputs are a supplier invoice PDF and po-register.xlsx; match the PO number, compare totals, flag any variance over 2%; output a short exception note; check that every flagged line cites the invoice line number.
Match the depth of review to the consequence of the work.
Attach request.docx and flex-policy.pdf, then type: Draft a reply to this flexible-work request under our policy. Treat it as high consequence: list the policy clauses you relied on and the points HR must confirm before anything is sent to the employee.
Track cycle time, quality, adoption, and rework instead of novelty.
Attach proposal-log.xlsx, then type: Build a sheet comparing the six August proposals done with Oppermind against the six done without: average hours, number of revisions, acceptance rate. Figures only, no commentary.
Choose owners, workflows, safeguards, and success signals.
Write our 30-day Oppermind adoption plan as a document. Three workflows: weekly sales summary, supplier invoice checks, customer FAQ drafts. For each, one table: owner, review or approval step, the connector or skill it needs, and the signal we check at day 30.
Keep going
Make the learning stick
Open Oppermind beside the lesson, apply each step, and leave with something you can use.