01
Diagnostic Sprint
For
Leadership teams that need clarity on where to start.
Deliverables
- Maturity diagnosis across dimensions
- Value pool analysis and initiative list
- Three actions for the coming quarter, with owners and dates
Digital & AI Transformation · Programs
Three programs, one principle: transformation that isn't measured can't be managed.
The diagnostic can be taken on its own; delivery and handover continue optionally.
02
Program Setup
For
Organizations moving from one-off initiatives to portfolio management.
Deliverables
- Decision rights matrix and quarterly portfolio rhythm
- Outcome metrics and baseline measurement plan
- Scope and production acceptance thresholds for the first two pilots
03
Delivery and Handover
For
Teams taking a pilot into production and handing it to their own people.
Deliverables
- A use case running in production with an evaluation set and monitoring
- Human-in-the-loop design and governance records
- Handover package and 30 days of on-site support
Four steps, each with an output.
01
Diagnosis
We measure which step the organization is on and where the weakest link is.
02
Prioritization
We rank initiatives by value and readiness, and name their owners.
03
Pilot and production
We take the chosen use case into production against a threshold written in advance.
04
Handover
We hand the system, with its documentation, to the internal team that will run it.
- KVKK (Turkish data protection)
- ISO/IEC 27001
- ISO/IEC 42001
- EU AI Act
These frameworks describe how projects are designed and documented; they are not a claim of certification held.
Can we start with AI before finishing digital transformation?
Not across the whole organization, but yes in the relevant process. The prerequisite is not organization-wide maturity; it is that the target use case is ready in terms of process, data and decision rights. The Diagnostic Sprint establishes this per use case; where a use case isn't ready, we recommend completing the missing step first.
What is the pilot trap and how do we recognize it?
It is when a technically successful pilot never reaches production. Typical signs: acceptance criteria that weren't written before the pilot started, no separate budget for scaling, a pilot owned only by IT rather than the business unit, and repeated decisions to run “one more pilot”.
Does the program end with a presentation?
No. The Diagnostic Sprint ends with a written diagnosis and three actions with owners and dates. Delivery and Handover ends with a use case running in production, an evaluation set, governance records and a handover package for your internal team.
Isn't this structure too heavy for a mid-sized company?
The structure is the same; the scale is different. In smaller organizations the diagnosis is shorter, the portfolio is a handful of initiatives, and the decision rights matrix fits on one page. Because the programs can be taken separately, most companies start with the Diagnostic Sprint and continue as needed.
Can we join the program without buying den?
Yes; the program is independent of the product. den's organizational memory layer is integrated only if you want it.