Back to the AI Leadership Lab
PillarPhase 01 · DiscoverFocus: Firmenwissen / AI Readiness

Discover: what your company knows, and where sources disagree

Role of the Company Brain: Bring customer signals, meeting notes and company knowledge together. Show what is known and where sources contradict each other.

Who it's for

For CEOs and leadership teams who want to know, before the next AI initiative, what the company knows and where customer signals, conversations and systems contradict each other. The deep dive is for product and tech leaders.

Company Brain and the four phases
Kettenblatt am Rad justieren

Discover is the first phase of leading with AI: the leadership team establishes what the company knows before it decides. The Company Brain brings customer signals, meeting notes, Jira, code and documents together and shows where sources contradict each other. The result is a checked version you build on in Define.

Discover is the first phase of leading with AI. It establishes what the company knows before it decides.

Input is scattered signals: customer conversations, meetings, Jira, code and documents. The Company Brain brings them together and shows where sources contradict each other. Output is a checked version that moves on into Define.

The deep dive below shows what that means for AI product work: finding problems AI should actually solve.

Phase 01 · Discover
Today

Knowledge is scattered across meetings, tools and heads. Nobody sees where sources contradict each other.

What happens

Bring together customer signals, meeting notes, Jira, code and documents, and show contradictions with their source.

Result

A checked version the leadership team can decide on.

At the centre: the Company Brain

Every phase draws on the Company Brain and adds new knowledge. The guide explains what it is, who owns it and how quality holds.

Leadership questions in this phase

Answered in the Company Brain guide.

Read the guide

Deep dive for product and tech teams

What separates AI product discovery from classic discovery

Classic software is deterministic: same input, same output, and every defect traces back to a line of code. AI systems are probabilistic – they weigh probabilities, and their behaviour depends on training data, system settings and context. Discovery therefore has to answer one question more than it used to: can this problem tolerate a solution that is sometimes wrong?

The answer decides the product architecture. Fraud detection at a bank needs explainability and human control; a phrasing suggestion in an editor tolerates errors because the user corrects them in seconds. The deep dive “AI product discovery: finding problems AI should actually solve” provides the framework of four core questions for this – problem proven, AI justified, error tolerance defined, data legal.

The table below shows the shift at a glance. It also explains why discovery becomes more important in the AI era, not less: the less the system's behaviour is fixed in code, the more depends on a clean understanding of the problem.

DimensionClassic B2B softwareAI-powered B2B software
LogicRule-based and deterministicData-driven and probability-based
BehaviourStatic until the code is changedAdaptive, changing with new data
ControlComplete, via the source codeDependent on training data and system settings
DebuggingCauses traceable in the codeCauses often hard to reproduce
TrustBuilt through consistent resultsNeeds explainability and transparency
Value creationPrimarily through the written codeThrough the interplay of code and data
Classic versus AI-powered B2B software – the shifts discovery has to account for.

The hype trap: technology is not an end in itself

The most common mental traps at the start of an AI initiative are well documented: adopting trends blindly, ignoring negative signals from the test phase, and naively assuming that clean, structured data already exists. All three lead to the same result – a technically impressive feature that delivers no measurable business value.

The corrective is uncomfortable but simple: every initiative is measured against value, effort and risk before resources flow. A use case that is technologically fascinating but only optimises marginal processes gets rejected. That discipline starts in discovery – not in the roadmap debate, once political pressure has already distorted prioritisation.

The Company Brain: scattered signals become checked context

In most companies, market signals, customer feedback and technical knowledge sit spread across five or more systems – Jira, Confluence, code repositories, e-mail, people's heads. Good product decisions, however, need the whole context. A Company Brain connects these sources into a checked context that keeps learning and can be extended with the nuances that matter.

For discovery this changes the day-to-day concretely: when a customer reports confusing behaviour in the price calculation, you research directly in the source code instead of pulling developers out of focused work – and the investigation flows back into the system as a permanent artefact. Without this context every AI guesses; with it, it knows the historical and technical background of a decision.

The AI MVP: test the wizard before you build the machine

Building a custom model is the most expensive and riskiest way to disprove a wrong hypothesis. The discovery phase therefore validates with the smallest possible stake: Wizard-of-Oz tests, in which a human simulates the AI, and foundation models that make an idea testable in days instead of months.

In this phase the MVP is not a sellable product but a learning instrument. It answers two questions: does the solution solve the problem well enough that users want it – and at what error rate does acceptance tip? The deep dive “The MVP for AI: test the wizard before you build the machine” shows the test setup in detail.

Customer journey: trust is part of the product

In surveys, roughly half of users say they distrust AI systems. For B2B software that means trust is not a marketing task after launch but a design problem for discovery. The AI journey has four decisive moments – expectation, first win, first error, habit – and the first error decides adoption more often than the first win.

A B2B user must be able to understand why a system makes a recommendation. A percentage alone is not enough; the product has to deliver the context of the decision. What an onboarding looks like that communicates uncertainty transparently instead of hiding it is covered in “Customer journey mapping for AI: onboarding that builds trust” – including how acceptance criteria for the define phase are derived from it.

The EU AI Act: compliance as a design principle, not a brake

The EU AI Act classifies AI systems by risk potential – and the risk class decides whether a product idea is legally and economically viable. That is why classification belongs in discovery, not in a legal review shortly before release. If the legal risk is too high, the problem framing or the data basis gets iterated before budget is committed.

Compliance by design means concretely: planning bias detection and mitigation, keeping data provenance fully traceable, and making machine decisions reviewable and overridable by humans – for high-risk systems this is mandatory. “The EU AI Act for product managers: compliance as a design principle” walks through risk classes, deadlines and the five building blocks that belong in the product.

Designing requirements for data, not just for features

Open language models have broad general knowledge. The strategic advantage of a B2B product comes from what they lack: specific process knowledge and proprietary, non-public data. The quality, relevance and real-world representation of that data base determine the quality of the end product – not the model choice.

For discovery this means: every product hypothesis comes with a data hypothesis. Where is the data captured, who owns it, which metric makes its quality measurable? Answer these questions in the discover phase and you avoid the most common failure of the build phase – a model waiting for data that will never exist.

The output of the discover phase: a qualified hypothesis

At the end of discovery stands a reviewable artefact, not a gut feeling: a proven user problem, a justified decision for or against AI, a defined error tolerance, a clarified legal position and a data hypothesis with a quality metric. Only this package justifies the transition into the define phase.

The order is the point. Teams that start with the prompt catch up on this work later – under time pressure, with budget committed and a half-finished feature at their backs. Teams that do it up front specify against a stable target.

Deep dives for this phase

Each article answers a concrete question from the practice of product and tech teams.

Matching Activities from the Playbook

From the article straight into practice: these Activities put the concepts to work with Teklens.

Frequently asked questions

What is AI product discovery?

AI product discovery is the first phase of AI product development: the systematic identification and validation of user problems that probabilistic systems can solve economically. The output is a qualified hypothesis with a proven problem, a defined error tolerance and a clarified data and legal position – before budget flows into models.

When does a problem really need AI?

When deterministic rules are not enough: patterns in unstructured data, language, predictions under uncertainty. If the problem can be solved with classic logic, the classic solution is almost always cheaper, faster and more reliable. The four core questions of the discovery framework make this decision explicit.

How do I validate an AI product idea without my own model?

With Wizard-of-Oz tests, in which a human simulates the AI behind the interface, and with foundation models via an API. Both make a hypothesis testable in days and answer the decisive question of the error rate at which users walk away – before a team invests months in training and infrastructure.

What role does the EU AI Act play in discovery?

An early one: the risk class of a planned system determines obligations, costs and in some cases feasibility. Check the classification during discovery and you can still adjust the problem framing and data basis while that is cheap – compliance becomes a design principle instead of a retrofitted brake.

Next phase in the cycle

From Discover to Define: a checked version goes in, a decision with rationale comes out. The Company Brain records what holds and why.

Phase 02 · Define – Define
Simon ScheurerAmr AbulseoudMarc Gasser
The lab letter

No new piece without you.

New articles, new interactive tools, new evidence – in your inbox first. And when you reply, we reply: you write directly with the authors, not with a no-reply.

No spam, no sharing, unsubscribe any time.

Bring one important decision.

Discovery Call: 30 minutes with a founder. Bring an important decision or a concrete context problem.

With a founder. No obligation.