An answer is useful while it can still change the outcome.
Having information and being able to make a decision are not the same thing.
An answer may depend on a supplier email, an inventory record and a product document. Each holds part of the picture. Bringing those parts together can still take too long.
A delivery question needs an answer before a commitment is made. A changed shipment needs attention while an alternative is still possible. An origin claim needs records that actually support it.
What we mean by answerability
For LIMEN, answerability is the ability to produce a decision-grade answer at the moment it matters.
In practical terms: an answer that is specific enough to act on, supported by evidence, and clear about what remains uncertain. Not every decision needs perfect information. It does need an honest account of what is known.
Three situations that make the idea concrete
These examples illustrate the questions that guide our work. Each would need a solution suited to its own setting.
Can we deliver before the deadline?
Imagine a customer asking for a particular item in a particular configuration by a fixed date. A catalogue entry is not enough to answer. The decision may depend on stock, allocation, preparation, transit time and a supplier’s confirmation.
The useful answer is not merely “available.” It explains what can be committed to, on what basis, and what still needs checking.
Which orders does this change affect?
Imagine a supplier moving a delivery date. The update is in an inbox, while the affected commitments are recorded elsewhere. Someone must connect the two before deciding whether to expedite, substitute, reschedule or contact a customer.
The useful answer connects the change to specific commitments and shows which links are established and which are missing.
Where did this material come from?
Imagine a customer asking for the origin of a material used in a product. A general supplier assurance may not establish the origin of this particular batch. The relevant records need to be connected to the item in question.
The useful answer shows the supporting chain of records and its limits. Missing evidence should remain visible, not become a confident claim.
How we approach it
We start with the actual decision: who needs an answer, when they need it, and what changes depending on that answer.
Next, we look at how the answer is produced today. Which information already exists? Who controls it? Is the delay caused by searching, joining records, waiting for another company, or something else?
Only then do we test a focused approach against the existing workflow. A better process, an integration or a small tool may be enough. A broad platform is not the starting assumption.
Where existing systems already give a reliable answer in time, there may be nothing to add. Our interest is in the gaps that remain consequential.
What a useful answer should make clear
What it covers. The actual order, item, batch, location or commitment—not just a similar record.
What supports it. The source information and when it was recorded or confirmed.
What remains uncertain. Missing links, contradictions and assumptions that could change the decision.
These are standards we want to build and test against, not a claim that a universal solution already exists.
Bring a real question
What do you need to know, what does it take to find out today, and when does the answer stop being useful?