Click any area below to see the experience that shaped how I teach, guide, and structure this work.
Specialized AI Credentials
AI & Business Strategy
Focused on translating AI into results. I match tools with actual work processes so teams save hours and stay in control.
Harvard Business School OnlineAI for Leaders
UBC Extended LearningAI for Business Analysis
I learned this work in settings where quality, trust, and human judgment could not be skipped.
Why generic AI training gets ignored.
01
Generic Training
Broad advice gets ignored.
I watched teams adopt AI tools and host broad webinars. Once curiosity faded, employees returned to old habits. The tools sat unused because generic advice never reached the actual work people had to finish that week.
02
Real Tasks
Relevance starts with the task.
People do not need theoretical lectures or prompt directories. They need immediate relevance to see value. Learning sticks when the session uses the files, decisions, and bottleneck tasks already in front of them.
03
Co-created Workflows
The skill stays with the client.
We co-create prompt guides, review checkpoints, and reusable templates around real tasks. Practising the workflow and skill together builds independent habits, keeping you in control.
That is why every session starts with real tasks, review, and ownership—shaping how (re)think.ai teaches.
Four trust rules behind every session.
The session has to be safe, useful, reviewable, and reusable.
01
SECURE PRACTICE
Safe practice before real stakes.
You test workflows on guided examples before they touch client work, assignments, or public-facing outputs.
Standard:
Short practice rounds with clear limits on what to share.
02
CONTEXT FIRST
Real tasks, not theory.
03
HUMAN CONTROL
Human review stays visible.
04
REUSABLE HABITS
A workflow you can adapt.
Where should work feel easier?
Not ready to book yet? Choose the path that fits the work in front of you.
These are the questions people usually ask when they want work to get easier without losing control of quality, privacy, or trust.
Generic training explains tools. My coaching starts with one repeated task and turns it into a workflow you can use, check, and adjust.
You leave with the workflow, the prompts, and the review steps. The point is not to remember a lecture. The point is to have a process you can reopen.
Yes. We build around a real task, then name the logic behind it: context, constraints, review, and handoff. You can reuse that logic in future work.
We start with data caution. We review what should not be shared, which tools are approved, and where human review has to happen before anything moves forward.
The workflow has to fit the rules you already work under. If a policy limits what can be shared or automated, we design around that limit.