Module 5

The First Stone

How do you begin without getting it wrong?

Dark library interior, representing the first steps of a long journey
In 1325, a 21-year-old from Tangier set out on what he thought would be a short pilgrimage to Mecca. Ibn Battuta ended up travelling for 29 years, covering roughly 117,000 kilometres across three continents. He did not plan the whole journey before leaving home. He took the first step. The rest followed from there.

You have arrived at the module that most institutions skip. They study. They deliberate. They form a working group. They wait for the right moment, the right budget, the right hire. And while they wait, the gap between where they are and where they need to be quietly grows wider.

This module is about how to move — not recklessly, but thoughtfully, in a way your team can follow.


Why most digital transformation projects fail

The uncomfortable truth is that technology is rarely the reason projects fail. The tools, in most cases, work. What does not work is the context around them: unclear ownership, undertrained teams, unrealistic timelines, and change that was announced rather than built.[1]

In cultural institutions specifically, two failure patterns appear repeatedly:

Failure pattern 1: The top-down mandate +
The problem: Leadership decides on a digital initiative and announces it to staff. No co-design, no pilot, no feedback loop. Staff feel it was done to them, not with them.

What this looks like: High adoption in month one, rapid drop-off by month three. Staff find workarounds. The "new system" becomes the thing people do when they have to, not when they want to.

The fix: Small, visible early wins, chosen and shaped with input from the people who will actually use the tools.
Failure pattern 2: The perfect plan that never launches +
The problem: The institution builds a thorough digital strategy. It sits in a folder. Meanwhile, nothing changes.

What this looks like: A 40-page document with a 3-year roadmap that no one reads after month two. A steering committee that meets quarterly. A budget line that gets deprioritised every year because there is no momentum.

The fix: Start with one concrete action — even a small one — that produces a visible result. Momentum is a resource. Build it before you build the plan.

A framework for getting unstuck

At Artorythm, we use a five-step diagnostic framework called the 5C Methodology. It is designed to move an institution from "we know something is wrong" to "we know what to do about it" — forcing clarity at each step before moving forward.

The 5C Methodology · Artorythm

From situation to corrective action — in five steps

C1
Condition
What is the current situation?
C2
Criteria
What should it look like?
C3
Cause
Why is there a gap?
C4
Consequence
What does the gap cost?
C5
Corrective Action
What do we do about it?

What makes this useful is that most institutions already know their C1 — they can describe the current situation in vivid detail. What they struggle with is C3 and C4: the honest diagnosis of cause, and the concrete quantification of cost. Without those two, C5 tends to be vague and unfunded.

The 5C framework is the backbone of every Artorythm engagement. In Module 2, the Value Calculator addressed C4. In Module 4, the Digital Maturity Evaluation addressed C1 and C2. Now we bring it together into C5 — corrective action.


How to pick your first project

Not all problems are equally good starting points. A good first AI project is contained enough to complete in weeks, produces a result that is visible to the team, and is reversible if it doesn't work.

Ask these three questions about any candidate project:

?
Can someone explain what "done" looks like? If the success condition is vague, the project will drift. Pick something with a clear output you can point to.
?
Will it free up time in the first month? Early wins sustain momentum. The best first projects deliver a visible reduction in a specific, recurring task.
?
If it fails, can you go back? Reversibility lowers the emotional cost of trying. This is especially important for teams that are cautious about change.
Director lens

When building the business case internally, frame the first project as a learning investment, not a transformation initiative. This removes the pressure of proving a large thesis — and sets realistic expectations for the board.

Team lens

When proposing a pilot to your director, anchor it in a specific, named frustration — "the grant reports that take two days every quarter" — rather than an abstract argument for AI adoption. Concrete problems get concrete budgets.


Scenario exercise

Read the situation, then choose your approach. There is no single right answer — but some choices carry more risk than others. Select a card to see what typically happens.

The situation

Your institution has a cataloguing backlog of 3,000 items. You have one part-time archivist who spends roughly 60% of her time on manual data entry. The director has asked you to "do something about the backlog." You have a modest discretionary budget.

What approach do you take?

Select one of the three options below to reveal the outcome.
Option A

Buy a cataloguing software platform

Research top vendors, demo three products, get board approval for a 12-month subscription, and begin migration.

What typically happens

The selection process takes 3–4 months. Migration takes another 2 months. The archivist spends weeks on data import rather than cataloguing. The backlog grows during the transition. The new system is powerful — but 18 months later, the original backlog problem is still not solved, because the bottleneck was always the process, not the tool.

Risk: High · Duration: Long · Reversibility: Low

Option B

Run a 4-week AI-assisted cataloguing pilot

Use an AI description tool on a sample of 100 items. Measure time saved per item. Decide whether to scale.

What typically happens

The archivist tests the tool for one week and finds it cuts her data-entry time by roughly half on standard items. Complex items still need full manual work. In four weeks, you have a real number — "this approach could clear 40% of the backlog in the next six months" — which you can take to the director with confidence.

Risk: Low · Duration: Short · Reversibility: High ✓ Recommended starting point

Option C

Hire a temporary cataloguing assistant

Bring in short-term help to reduce the backlog manually while you plan the longer-term solution.

What typically happens

The backlog shrinks while the assistant is there. When the contract ends, the backlog begins to grow again. You have not changed the underlying process — you have borrowed time. This is a reasonable interim measure, but it is not a solution. The same backlog problem will return within 12–18 months.

Risk: Medium · Duration: Short-term relief only · Consider combining with Option B


Five questions to ask any technology vendor

The market for "AI tools for cultural institutions" is growing fast. Some products are excellent. Many are not. Before committing budget or time to any vendor, ask these five questions directly — the quality of their answers tells you a great deal.

1
Can you show me a case study from an institution similar to ours? Generic testimonials from large national museums are not useful if you are a regional gallery with three staff.
2
What does your onboarding process look like, and who owns it? Good vendors have a named person and a structured process. Vague answers here predict vague support later.
3
What happens to our data? Where is it stored? Who can access it? Is it used to train your model? The vendor should be able to answer this clearly.
4
What does the exit process look like if we want to stop? Vendors who make it easy to leave are confident in their product. Those who make it difficult are not.
5
What does failure look like with your product, and what do you do when it happens? Honest vendors name their limitations upfront. This question separates the salespeople from the partners.

How to talk to your team about change

Change in cultural institutions is rarely blocked by logic. Most staff understand that their institution needs to evolve. What creates resistance is something subtler: the fear of becoming less valuable, the discomfort of not knowing what "good" looks like in the new process, and the feeling that their expertise isn't being respected.[2]

Three things tend to reduce this resistance:

1. Name the thing you are not changing +
People are more willing to accept change if they know what is staying the same. Before introducing any new tool, explicitly say: "This does not change who makes the decisions. It does not change who owns the collection knowledge. It changes how we handle the administrative work that surrounds that knowledge."
2. Involve someone from the team in the selection +
This does not need to be a formal process. It can be as simple as: "I'd like you to test this for a week and tell me what you think before we decide anything." Involvement creates ownership. People advocate for tools they helped choose.
3. Keep the first pilot small enough to fail safely +
If the first experiment is large, failure feels catastrophic. If it is small, failure is information. Explicitly frame the pilot as: "We are going to try this for four weeks, measure honestly, and then decide. If it doesn't work, we stop." This lowers the emotional stakes enough for cautious team members to engage.
Director lens

Building a business case for change? Frame it around mission impact, not efficiency metrics alone. Boards respond to "this frees the team to do more of the work the institution was founded to do" more than "this saves 3.5 hours per week."

Team lens

Proposing change upward? Give your director a reversible, bounded ask. Not "we should adopt AI" but "can I test one tool on one task for four weeks and report back?" Small asks get faster yeses.


📋

See what a real pilot looks like

The Artorythm free pilot is a structured 4-week engagement — one workflow, one team, one clear output. We document what we find in a Workflow Insight Report you keep regardless of what you decide next.

Download a sample Workflow Insight Report →
🚀

Apply for the free pilot programme

We work with a small number of institutions each quarter. The pilot is free. The only requirement is that someone from your team is available to work with us for four weeks.

Apply now — limited places available →

Reflect · Module 5
Where does your institution stand right now on the journey to its first AI project?
We have no active digital projects right now
We have been discussing it but haven't started
We are in early exploration — testing a few tools
We have a pilot running or recently completed
We have multiple projects running across the institution

✓ Module 5 complete

The first stone is the hardest.

You now have the framework to diagnose clearly, choose wisely, and start without waiting for perfect conditions.

🔍
Why most digital projects fail — people and process, not technology
🔄
The 5C Methodology: from condition to corrective action in five steps
🎯
How to pick a first project that is contained, visible, and reversible
🛡️
Five questions that protect your institution from vendor traps

Up next

Continue to Module 6 — Your Next Chapter →
AI for Cultural Institutions
Module 5 of 6 · ~15 min

Ready to transform your institution?

Artorythm logo

Independent AI & IT advisory for cultural institutions. Based in Berlin. Working internationally.