Data, Analytics and Decision Products
Data becomes a product when someone can move from source, definition and interpretation to authority, workflow and action.
- Data products
- Analytics UX
- Decision workflows
Different decision products organise different evidence
A dashboard can display correct numbers and still leave the user unable to decide. The measure may have an unclear definition, the comparison may be inappropriate, the source may be stale, or the interface may stop at an alert without assigning an action.
Tcules designs data, analytics and decision products around the full path from source and definition to interpretation, authority and action. The work can include data-heavy SaaS, operational analytics, AI-assisted analysis, portfolio views and decision workflows.
The interface should not treat every product as a collection of charts. The central object may be an alert, investigation, comparison, forecast, recommendation or decision record.
- 01
Operational monitoring
Asks what changed, whether action is required and who owns it.
- 02
Portfolio and executive products
Ask how definitions remain comparable across assets, teams and periods.
- 03
Diagnostic products
Connect an observed signal to likely causes and the evidence for each.
- 04
Planning and forecasting products
Expose assumptions, scenarios and sensitivity rather than only one prediction.
- 05
Data platforms and observability tools
Help technical users inspect lineage, quality, incidents and system behaviour.
- 06
AI analysis products
Turn language into queries or explanations while preserving source, calculation and uncertainty.
A decision surface has seven layers
A useful decision surface shows the information required for a signal to support action rather than remain a dashboard observation. Definition, source, freshness, value, comparison, uncertainty, interpretation, ownership and follow-up need to stay connected.
- 01
Measure definition
The definition determines which source data belongs in the measure and what the measure can truthfully represent.
- 02
Source and lineage
The product identifies where the measure comes from and how the value was produced.
- 03
Freshness and quality
Freshness and quality qualify the current value before the reader treats it as decision evidence.
- 04
Current value and comparison
The value becomes meaningful when it is placed against a baseline, target, period, population or pattern.
- 05
Uncertainty and missing data
Uncertainty limits interpretation and keeps absent or incomplete evidence visible.
- 06
Interpretation and affected object
Interpretation connects the signal to the object, population or condition affected by it.
- 07
Accountable role and follow-up
The product identifies who can act and creates follow-up evidence that can change the next decision.
Data density is useful when the hierarchy follows the decision
The ConnectX case shows an adaptive approach. Eight situations linked user intent to required data, interface modules, digital-twin behaviour and action. The product did not display every energy metric to every role.
The Doodle case shows why a computed result needs product meaning. Availability alone could not represent meeting priority, so tentative schedule and organisational priority informed a bookability indication rather than an unsupported promise.
These cases establish product modelling and decision-surface work. They do not establish data-platform engineering, model performance or business outcomes.
AI-assisted analysis must remain inspectable
Natural-language querying and generated explanation can lower the cost of exploring data. The product still needs to answer practical questions before the result can support a consequential decision.
- Which metric or field did the system use?
- Which filters and time period were applied?
- Is the source current and authorised?
- What is observed, derived, forecast or inferred?
- Which alternative explanation remains plausible?
- Can the person inspect or modify the query?
- What action is being recommended, and against which objective?
For consequential decisions, evaluation should include query correctness, source coverage, explanation fidelity, action quality and recovery from missing or conflicting data.
How Tcules shapes the product
Tcules can combine research, data and object modelling, information architecture, data visualisation, AI Product UX, workflow design, design systems, frontend and backend development, APIs, integrations and implementation QA.
The wider portfolio includes DataBahn and AnalyticsVerse. The detailed examples on this page come from ConnectX, Doodle and Benchmark Gensuite because their relevant product decisions can be examined in public cases.
Bring one dashboard or analysis that produces discussion but not a clear action. Tcules can trace whether the missing layer is definition, provenance, comparison, interpretation, authority or workflow.
Discuss a data decision product
Bring one dashboard or analysis that produces discussion but not a clear action, and trace which decision layer is missing.