Strategy15 June 2026
The Problem Behind the Problem
Most organisations solve the wrong problem with extraordinary efficiency. Here's how to find the one that actually matters.
Read article
What if the problem isn't the problem?
Scroll to explore
PositioningSerious about outcomes.
Serious about outcomes.
Playful about possibilities.
Ludens sits at the intersection of strategy, data, technology, and commercial thinking.
We work with leadership teams facing problems that don't fit neatly into frameworks — where the obvious answer is usually wrong.
We don't sell slide decks or transformation theatre. We diagnose precisely, design intelligently, and build things that change how organisations decide, operate, and grow.
The name means play. The work means results.
The tension
Most organisations are solving the wrong problem with extraordinary efficiency.
The strategy is sound. The technology is modern. The team is capable. Yet outcomes stall, margins compress, and decisions feel harder than they should.
The visible problem is usually a symptom of something structural underneath. Ludens starts where others skip: finding the problem behind the problem.
Diagnosis before prescription
Capabilities
What we do
Integrated capabilities — not siloed disciplines. Each connects to the others.
Approach
Play → Experiment → Discover → Solve → Transform
01Find the real tension
Diagnose
Structured inquiry. Question assumptions. Map systems. Test hypotheses before committing to solutions.
02Architect clarity
Design
Decision frameworks, commercial models, and system architecture that survive contact with reality.
03Make it real
Build
Prototypes, models, platforms, and processes — built with technical rigour and commercial discipline.
04Make it stick
Embed
Capability transfer, governance, and feedback loops designed around how people actually work.
Why Ludens
Builtdifferent.Bydesign.
01
We start with inquiry, not assumptions
Most consultancies arrive with a framework. We arrive with questions.
02
Strategy meets engineering
The same team diagnoses, designs, and builds — with commercial rigour throughout.
03
Experiments over opinions
Small tests that confirm or refute critical assumptions before large commitments.
04
Outcomes, not deliverables
Measured by what changes — margins, decision speed, capability, growth.
Start here
Let's see what's possible.
No predefined packages. Every engagement starts with understanding your problem — deeply, precisely, without assumptions.