DOC ROI · STRATEGY SPECIALISMOBJECTIVES & EFFECTS MODELLING
DESIGN · EXPLORE · ASSESS · IMPROVE

ISHIKAWA 2.0

An interactive fishbone-inspired framework to model objectives and KAI variables, trace the journey from A to Z, and prepare structured evidence for data monetization.

THE ACADEMY / 4 MODULES

Visual modelling workspace

Blank by default · Build A → Z → Y → X → V → F → SF · Allocate 100% of each parent objective

Autosave ready
A / Starting point
—
BASELINE
Z / Target
—
TARGET
Z / Modelled
—
PROJECTION
Target gap
—
POINTS
Z · OBJECTIVE COVERAGE
100% means the branches jointly deliver the entire A → Z gap. Overshoot stays visible.
Awaiting A and Z100% TARGET—
Not started
ECONOMÍA UNITARIA · EN DIRECTODel precio público al presupuestoUn solo panel conectado con Budget Studio. Los impuestos especiales se configuran por producto o servicio, sin alterar la cobertura de Z.
01 · PVPPrecio al público
PRECIO EN LA ETIQUETA—
—
02 · IVA / VATImpuesto general
IVA del PVP—
VENTA SIN IVA—
—
03 · ESPECIALESImpuestos selectivos
Especiales calculados0,00 €
Imputados al escenario0,00 €
Ya en coste de compra0,00 €
Puedes aplicar más de un impuesto; cada uno conserva su propia base.
04 · MARGENRetenido
Margen retenido—
—
05 · RESERVAObjetivos
Importe reservado—
Reserva financiera sobre la venta SIN IVA. No representa cobertura de Z.
06 · BUDGETDotación por unidad
DISPONIBLE PARA ASIGNAR—
Asignado en Y—
Saldo / exceso—
El saldo sigue las asignaciones Y.

Regla del presupuesto: PVP final − IVA = ingreso sin IVA. De esta base se descuentan los impuestos especiales pendientes de imputar, el margen y la reserva. No se descuentan dos veces los impuestos ya incorporados al precio de compra. Todos los importes se muestran redondeados; el cálculo conserva la precisión.

FINANCIAL SCENARIO · Volume, deadline, WACC and indicative ROI ⓘ

Unit revenue and allocated budget update live when you adjust PVP, margin or Y assignments. A forecast is not an observed result.

Net sales revenue—ex VAT · all units
Assumed resource outlay—allocation + excise not already in costs + reserve + fixed
Scenario ROI · horizon—(net result) / (planned costs)
Annualised ROI vs WACC—WACC required for hurdle comparison
The allocated envelope represents a planned spend assumption, not an invoice or audited cost.
Formal KAI·ROI / Customer Equity calculator · optional research inputs

Scientific distinction: C-Level, X, V, F and SF labels do not automatically identify or estimate the parameters of the sovereign KAI·ROI equation. Enter researched / validated coefficients explicitly. DIIIP, SIPOC and budgets provide sources of evidence, not substitute measurements.

FORMAL SPECIFICATION · SOVEREIGN KAI·ROI v1
KAI_i* = φ_i · u_i · f_i · ψ_i · SPO_i · P_i · Γ_g(i),t
ψ_i = promedio(DataActivation_i, I_net_i)
SPO_i = CC_i · ABCD_i · NPS_i
MD_i = Σ_s (I_i,s · R_i,s + E_i,s · Q_i,s)
CE_i = ((((KAI_i* · MD_i) − C_i) / C_i) − WACC_t) / WACC_t
CE_empresa = Σ_i CE_i
V%CE = (100 / N) · Σ_i 1(CE_i > 0)

Γ, authorized operational development only: Γ_g(i),t = √[(LTV_g,t/LTV_g,0) · (Retention_g,t/Retention_g,0)], with Retention = 1 − ChurnRate. Γ can exceed 1 and is not capped at a proxy score.

φ diagnostic is NOT a KAI multiplicative coefficient: φ_SWOT = POS − NEG, −100 to +100. Never insert φ_SWOT directly into φ_i. No unauthorized T(φ_SWOT) transformation is applied.

Unknown ≠ 0: blank means missing evidence. KAI* and CE_i are calculated only when every required formal numeric input is explicitly entered. The 0–1 operational assessment below does not feed the equation automatically. Costs must be included in C_i, not subtracted again inside MD_i.

Operational evidence readiness · 0–1 (NOT formal coefficients)

Independently rate the quality or readiness of evidence for each variable. Leave blank when unknown. The owners are a proposed governance assignment from the current organisation map; the user may review them. These scores are educational proxies, not KAI inputs, and never replace measured values.

Readiness remains Unknown until you enter evidence assessments.
Enter all formal coefficients and a positive WACC to calculate formal CE for the evaluated element.

ψ = mean(DataActivation, I_net); SPO = CC · ABCD · NPS; KAI* = φ · u · f · ψ · SPO · P · Γ; CE = ((((KAI* · MD) − C) / C) − WACC) / WACC. WACC must use a decimal fraction internally (e.g. 10% → 0.10). These are formal calculations on user-entered inputs, not predictions inferred from the diagram.

Simple allocation: A and Z are absolute values (−100% to +100%). Every Y is a % of the A → Z change; each X, V, F or SF is a % of its immediate parent's allocation. Children should total 100% at every parent. Over 100% is allowed and flagged—not silently capped.Allocation percentages measure responsibility for A → Z; euro amounts distribute the available unit-price envelope. Changing the margin or PVP never changes objective coverage.

Connect a manual data flow

FISHBONE / INTERACTIVE CANVAS
TARGET: —
100%
Y · StrategicX · AreaV · VectorF · FactorSF · SubfactorAutomatic I/OManual data linkPending / plannedDrag line midpoint · × deletes only this relationship
Drag nodes freely · Blue dashed = automatic I/O · Green dashed = manual I/O · Amber dotted = planned output · Click a file code to edit destination · Drag blue control handles to reshape arrows · × on arrows to disconnect · Connect to reattach · Scroll to zoomReady · New project
V13 · Objective hierarchy, colour-coded manual/automatic data flows and financial scenarios: Δ = Z target − A. Every connected Y receives an editable share of Δ; each connected X/V/F/SF receives an editable percentage share of its immediate parent. Each parent has a reference budget of 100%; an internal node's delivered share is the sum of the shares delivered by its direct children. A terminal node delivers its assigned share. Z modelled = A + Δ × total delivered Y shares / 100. Contributions beyond 100% are shown without capping. A negative Δ means planned improvement moves downwards. This is an illustrative planning convention, not an established causal model or a change to the KAI·ROI equations.
01 · PRECIO Y COSTES

Del PVP al coste por unidad y al EBITDA

Edite directamente € por unidad o % de la venta sin IVA. Cada importe se distribuye entre los C-Level responsables y se concilia con el Budget Studio del Ishikawa. Las asignaciones de objetivos no equivalen a gastos contables.

Modo de partida: el Budget conserva el margen objetivo configurado arriba. Active «Vincular costes» para que el resultado operativo sustituya a ese margen retenido en la planificación. «Cargar ejemplo» rellena un escenario genérico de aprendizaje; nunca se aplica automáticamente.
Origen del impuesto especial:El valor declarado es una hipótesis, no la cuota legal verificada.
Partida · editableImporte €/ud.% venta netaBase / coste fijoResponsable(s) · C-LevelImpacto
PVP FINAL CON IVA—IVA —
MARGEN CONTRIBUCIÓN BRUTO——
COSTE FIJO UNITARIO——
EBITDA OPERATIVO ESTIMADO——
i · Cómo se calculan los porcentajes, el reparto C-Level y el EBITDA
El 100 % siempre es el precio sin IVA. El margen de contribución bruto resulta de restar los costes variables, incluido el impuesto especial imputado. El EBITDA estimado descuenta además los costes fijos de estructura. El IVA repercutido no es un coste operativo. Cuando una partida tiene varios responsables, el reparto por C-Level es equitativo por defecto y no duplica el gasto. El modo de impuestos configurados toma el total imputable del configurador de especiales; los gravámenes marcados «ya incluidos en compra» se excluyen del segundo descuento. La reserva se resta del excedente en el presupuesto, pero no es por sí misma un gasto contable de EBITDA. No se calculan aquí amortización, intereses, Impuesto sobre Sociedades ni resultados observados.
04 · DOC ROI / BUDGET & KPIs

Unit Budget Studio · Cost Reconciliation

Translate the objective hierarchy into a transparent, per-unit resource allocation. This is a planning scenario, independent of KAI·ROI's formal equations.

RESULTADO DEL MODELO ECONÓMICOLos precios, IVA, margen y reserva se editan una sola vez en el panel financiero superior ↗. Esta sección contiene su reparto y los KPI por unidad organizativa.
P&L / PRESUPUESTO · CONCILIACIÓN EN DIRECTO

Asignaciones objetivo frente a costes previstos por C-Level

El coste imputado por responsable se distribuye sin duplicados. Las cuotas del Ishikawa son asignaciones de objetivos, no comprobantes de gasto. Las diferencias sirven para revisar los presupuestos.

C-LevelCuota Y / %Budget asignado / ud.Coste planificado / ud.Saldo / ud.

—

Click a row's ↗ to locate its source node on the canvas.
Top-down allocation follows connected Y → X → V → F → SF shares without normalising unbalanced groups. A node's planned amount is its share of its parent's planned amount. Bottom-up funding requests are direct, incremental cost claims per unit: a parent's total request includes its own direct claim plus all descendant claims, without double-counting the planned distribution. Missing or excess allocations remain visible; detached elements receive no objective budget. This is a scenario, not an accounting ledger or a KAI·ROI equation.
04 · DATA ARCHITECTURE / RELATIONSHIPS

C-Level Entity–Relationship & Data Lineage Studio

Each output appears at its originating C-Level and at the receiving C-Level's INPUTS, showing the exact X / V / F / SF producer and recipient. Blue solid arrows confirm a file-to-input match; amber dashed arrows indicate planned destinations. Drag entity headers and curve control points to create a clear, readable map.

Awaiting the first output.
100%
Confirmed output → input Recipient selected, input not confirmed⠿ Drag the C-Level header · Click file to find its node · Click a line to adjust its curve
LINEAGE INSPECTORSelect a connection to inspect its source, file and exact destination.

The cards grow vertically to show all declared outputs and receiving inputs. The arrows connect specific file attributes (not merely departments). For the full saved model, use Save JSON above; the ER JSON exports this relationship map independently. Lines describe planned or documented flow, not an automatically executed transfer.

Supplier / C-LevelOrigin X / V / F / SFOutput file / attributeFormatExact receiving nodeCustomer / C-LevelStatusLocate

Storage destinations · Editable data attributes

Choose the repository of each individual output and each incoming file. The same file can be written in ERP and consumed by CRM; these assignments feed Systems Entity–Relationship automatically.

FlowC-Level / exact nodeFile attributeSystem where this attribute resides

Modelling only: matched files are metadata and traces. Saving this model does not transmit or create the actual files. The relationship map is part of the full project's JSON and browser-local backup.

06 · SYSTEMS ARCHITECTURE / ATTRIBUTE-TO-ATTRIBUTE LINEAGE

Systems Entity–Relationship Map

CMS, CRM, ERP, KAIloop, communications and your custom platforms are containers. Every recorded file can reside in its source and destination system independently; arrows identify the precise producer and consumer. This is a design map, not a physical database or an ETL execution.

← C-Level ER
100%
Assign CMS / CRM / ERP / KAIloop / Communications to an output or input within a node to start the system map.
LINEAGE INSPECTOR Select a connector to identify its exact output and input systems, provider, file and recipient. Drag cylinders freely; move the control point on a selected connection.
● Blue · confirmed data flow○ Amber · intended recipient◌ Grey · system pending / unknownOnly documented links; no data are transmitted.
METHODOLOGY AT THE END OF THE JOURNEY

DIIIP · From qualitative objectives to actionable intelligence

In Ishikawa 2.0, value begins by turning an A → Z ambition into visible variables, traceable interpretations and measurable next steps. DIIIP guides the transition from an exploratory map towards evidence-based decision-making.

D
Data

Origin A, target Z, named Y/X/V/F/SF components, declared ratings and supporting observations.

I
Information

The variables are arranged hierarchically, defined consistently and exported as structured JSON/CSV evidence.

I
Intelligence

Transparent provisional aggregation displays contribution scenarios and the gap between declared aspiration and modelled outcome.

I
Insights

Teams identify priorities, conflicting assumptions, variables requiring measurement and questions for testing.

P
Personalization Actions

Prioritised measurement, ownership and follow-up actions prepare responsible data activation and monetization opportunities.

KAI·ROI EQUATION · CUSTOMER EQUITY

Ishikawa 2.0 prepares objective and variable maps for the KAI·ROI research layer

Ishikawa 2.0 supports the qualitative modelling of business objectives and KAI-related variables, identifying which data and evidence should be collected before any credible monetization, Customer Equity analysis or strategic decision.

The formal KAI·ROI formulation remains independent and unchanged. The financial scenario does not validate KAI·ROI. The optional research calculator accepts only explicitly supplied coefficients for one unit i; company-wide CE_empresa and V%CE require data for all N units.

EXECUTIVE RESOURCE

The KAI·ROI Equation Book

A concise guide to understand how data, ROI, Customer Equity and strategic decisions connect inside the DOC ROI ecosystem.

Inside the document:
  • What the KAI·ROI Equation is
  • Why Customer Equity matters
  • How ROI becomes a decision system
  • Why data must be monetized with purpose
Access the KAI·ROI Equation →