MethodKit AI Workshop
Hours leak from the same few workflows. You can't decide where AI goes first.
You've tried AI in pieces. You still can't tell which workflow is worth committing to first.
Free 20-minute online conversation. Bring one workflow that feels stuck.
Quotes scattered across spreadsheets, project state in one tool, invoicing in another, customer follow-ups carried in someone's head. A consultant tells you where to deploy AI and leaves. MethodKit runs a focused half-day with your team. You walk out knowing the one AI move worth funding next, scoped so you can build it with us, your own team, or anyone else.
Recognize this?
Look at a normal Tuesday in your company.
Not the process diagram. The real thing. Three small scenes you have probably stood inside.
The quote
A customer asks for a price. It starts in a spreadsheet someone built two years ago, gets a number from a person who "just knows" the margin, and goes out as a pasted email. Three days later nobody can say if it was sent.
The quote tool is a habit, not a system.
The handoff
The deal closes. Now the project has to move from the person who sold it to the person who delivers it. That handoff lives in a five-minute hallway conversation and a half-filled card in a tool only one of them opens.
The most important step has no home.
The follow-up
An invoice goes out. Whether it gets chased depends entirely on whether one person remembers. Some do, some quietly don't, and the difference is a number nobody is looking at.
Half your cash flow is memory with the memory removed.
You just recognized three places where hours leak and no tool owns the flow. You have tried AI on pieces of this. You still cannot say which leak to fix first.
The problem
The problem is not whether AI works. It is that the work is scattered.
Most teams pushing AI internally hit the same wall. The company runs across disconnected tools and undocumented habits, so no one can see the whole flow well enough to decide where AI should land. A model can suggest twenty automations; it cannot tell you which one your team should trust, fund, and reorganize around. It is a driver with a license and no map of your roads. Those roads are your dark context: the quotes, handoffs, and pricing rules your company actually runs on, carried in habits and memory, never written down. It is the part AI can't see.
And it is not a knowledge problem. A small handful of people in any company already get this; most are overwhelmed by everything coming at them. You have a dozen things on your plate and a strong feeling that one of them matters more than the rest. You just cannot say which. You can feel the hours leaking. You cannot agree on which leak to fix first.
Proof & authority
Built on 14 years of MethodKit facilitation craft.
Ola Möller created MethodKit, the card-based method used by IKEA, Spotify, governments, and schools in more than 120 countries. Ola also trained AI for German public television, so this is not a methodology brand guessing at AI; it is people who have done both. This AI workshop applies that facilitation craft to the question every leadership team is now facing: where should AI belong in how we operate?
We have run this conversation with founders, operators, and teams across very different businesses. The pattern is consistent: storage is not the hard part. Teams already have documents, spreadsheets, tools, and transcripts. The hard part is turning what the team knows into a decision everyone can act on.
How to solve it
Map the flow before you pick the tool.
The work starts with the team, not the tool. In one working session you map how the work actually moves, from first customer contact to paid invoice, and mark where the hours and money leak out. Only then do you choose what AI should touch first.
Ten people in an AI training leave with ten interpretations and the same Monday. One team that maps its own flow leaves with a single decision it can act on that week.
How MethodKit helps
A focused half-day that ends in a scope you can build against.
The point of the session is not to prove AI is real. It is to make the next decision concrete enough to act on.
What actually happens
- We map the operational flow end to end, across the tools and the steps only people remember.
- We mark where time, money, and rework actually leak.
- We name the single highest-leverage AI candidate (the one where freed hours turn into real money) and pressure-test it against what your team can realistically adopt.
What you walk out with
- A decision brief: the workflow you mapped, the candidates you considered, the one you chose, and why.
- A scope you can build against, whether with us, your own team, or another partner.
- A shared picture the whole team holds, not a plan that lives in one head.
The brief is a file your team owns. No tool to license, no platform to log into.
Book Office HoursWhat the brief looks like
You leave with a file, not a feeling.
Plain text. Your team reads it, any AI tool reads it, and you own it. Here is a slice of a real one, names changed.
# AI workshop - decision brief # Mapped: quote → project handoff → delivery → invoice → follow-up where_hours_leak: - "quote build: ~40 min each, rebuilt from scratch every time" - "handoff: sale→delivery, lives in one hallway chat" - "invoice chasing: depends on whether Anna remembers" first_ai_candidate: pick: "draft quotes from past jobs + our margin rules" why: "highest hours, lowest adoption risk, one owner" not_yet: "a customer-facing chatbot - no clear owner, high risk" what_has_to_stay_true: - "Anna still signs off on any margin under 15%" - "the draft is a starting point, a human sends it"
Fig. 01 / The brief is yours to edit next month and yours to shred. It is not a platform's.
The context AI can't see
The roads a model can't see are your dark context.
The quotes, handoffs, and rules your company actually runs on — carried in habits and heads, never written down. It is the part a general AI can't reach, and the part this workshop maps. We wrote up what it is, and why it's the real bottleneck.
Read what dark context means →Fit
This is for you if…
- You have already tried some automation or AI in the company.
- You believe AI can do serious work, but you are unsure where to go next.
- You can name a cost of not fixing the workflow in hours, money, missed sales, rework, or errors.
- Someone in the room has mandate to make the next decision.
This is probably not for you if…
- You need a general AI inspiration lecture.
- You have not tried AI at all yet.
- You want someone to define your strategy while the team stays passive.
- You already know exactly what to build and only need implementation capacity.
Comparison
Four ways teams try to solve this
| Approach | What you get | What is missing |
|---|---|---|
| AI consultancy | Recommendations and a deck | Weeks to a deck, then they leave |
| DIY with ChatGPT or Notion | Fast exploration, low cost | No shared decision record, no facilitation, drifts for months |
| Vibes workshop | A day of energy and inspiration | Weak link to operational value and implementation |
| MethodKit AI workshop | A facilitated team decision, mapped workflow, and buildable scope, all in a half-day | Requires the right people in the room and a real problem worth solving |
FAQ
What do we leave with?
A decision brief: the workflow we mapped, the AI candidates we considered, the candidate we prioritized, what the team agreed and rejected, and what the next build or test would require.
Is this a strategy workshop or an implementation workshop?
It sits between them. The session is strategic enough to choose the right place for AI, but concrete enough to produce a scope you can build from.
Do you build the automation afterward?
Sometimes. The workshop can lead to a scoped build engagement with MethodKit, but the brief is designed so you can also take it to your own team or another implementation partner.
Can this be run online?
Yes. The first workshops can run online. In-person is useful when the team needs stronger alignment, but not required for the first conversation.
How much does it cost?
To be clear about what we want: Office Hours is free, the workshop is a paid half-day. If it leads to a build, that gets scoped and priced separately. The number depends on scope and team size, and we settle it with you before anything is booked, never as a surprise after the room. Office Hours is where we work out whether the workshop is even the right fit.
Start here
If your team has tried AI and still cannot decide where it belongs, start here.
Book a free 20-minute Office Hours call. We will ask what you have tried, where it got stuck, and whether a MethodKit workshop is the right next step.