Strategic Investment Systems

• Founded in 1972 by former IBM engineers.
• Original existential problem: real-time transaction processing with accounting integrity.
• Born to replace batch accounting with a single source of operational truth.
• ERP is native; analytics and reporting were added later (BW, BPC, SAC) to observe an already-normed system.
• S/4HANA attempts to reunify transaction and analytics on one technical substrate.

• What never changed: process primacy, end-to-end consistency, auditability.
• What was added: analytics, UX layers, cloud delivery.
• What was never transformed: the belief that valid processes precede valid decisions.

• Gravitation: standardized process as the center of gravity.
• Conservation: integrity, coherence, compliance.
• Perception: the enterprise as a set of normed transactional flows.
• Emergence: change is acceptable only if it can be formalized.

• Energy: very high (installed base, ecosystem lock-in).
• Optionality: low to medium (powerful but rigid paths).
• Embeddedness: extreme (finance, supply chain, regulatory cores).

• Assumes linear time, sequential decisioning, human alignment to process.
• Favors centralization, conformity, ex-post justification.
• Decisions are validated, not explored.

• Breaks when used as a decision system rather than a validity system.
• Produces organizational blindness to non-standard signals.

Dominant cognition: procedural, quasi-juridical.
SAP does not think decisions — it thinks validity.

• Origin in the late 1970s as a relational database company.
• Original problem: persistent, queryable, scalable data.
• ERP entered via acquisitions (PeopleSoft, JD Edwards), not by design.
• Analytics naturally extend the database worldview.

• What never changed: data sovereignty and performance obsession.
• What was added: business applications, cloud wrappers.
• What was not transformed: the reduction of the enterprise to data structures.

• Gravitation: persistent data.
• Conservation: performance, control, scalability.
• Perception: the enterprise as tables, schemas, queries.
• Emergence: through technical optimization.

• Energy: high but concentrated.
• Optionality: medium (integrated stack).
• Embeddedness: strong, primarily IT-centric.

• Assumes decisions follow from better data access.
• Encourages centralized analytical authority.
• Reduces ambiguity by reducing meaning.

• Fails when data richness is mistaken for organizational understanding.
• Treats social dynamics as noise.

Dominant cognition: computational rationality.
Oracle sees the enterprise as a data problem, not a social system..

• Originated in 1911 as a machine company, evolved into services and consulting.
• Core problem: how to make organizations decide better at scale.
• Never ERP-centric; analytics and BI are core (Cognos, SPSS).
• Watson represents the attempt to industrialize cognition itself.

• What never changed: belief in scientific rationality and models.
• What was added: AI, quantum computing, automation layers.
• What was not transformed: the assumption that decisions are calculable.

• Gravitation: assisted rational decision-making.
• Conservation: scientific authority, robustness, seriousness.
• Perception: the enterprise as an optimization problem.
• Emergence: via models, probabilities, scenarios.

• Energy: declining — the promise no longer mobilizes.
• Optionality: high intellectually, narrow operationally.
• Embeddedness: strong in slow institutions (banks, states), weak in adaptive organizations.

• Assumes decisions are outputs, not social processes.
• Pushes tool-driven decisioning over collective sense-making.
• Underestimates distributed, non-linear, post-rational human cognition.

The core error
IBM assumes: decision = calculable → therefore automatable.
But strategic decisions are distributed, contextual, conflictual, and often understood after being made.

The quantum irony
IBM explores quantum computing (probabilistic, contextual) at the machine level, while remaining classically rationalist at the organizational level — modeling humans as variables and organizations as closed systems.

• Collapses when used to replace human sense-making rather than make it legible.
• Produces organizations that run after decisions they never had time to understand.

Dominant cognition: analytic-scientific rationality.
IBM thinks before acting — often too far ahead of lived organizational reality.

• Born in the mid-2000s from Amazon’s internal infrastructure.
• Original problem: scaling experimentation without friction.
• No native ERP; analytics as composable primitives.
• Provides a meta-platform, not business semantics.

• What never changed: abstraction and modularity.
• What was added: analytics, AI services, industry accelerators.
• What was never transformed: refusal to encode meaning.

• Gravitation: modularity.
• Conservation: scalability, automation.
• Perception: the enterprise as an assemblage of services.
• Emergence: rapid experimentation.

• Energy: massive.
• Optionality: extremely high.
• Embeddedness: infrastructural, not cognitive.

• Assumes thinking precedes tooling.
• Enables distributed exploration, not convergence.
• Forces organizations to supply their own meaning.

• Fails when used without strong internal cognition.
• Creates chaos if optionality substitutes for strategy.

Dominant cognition: adaptive engineering.
AWS enables transformation — it does not think it.

• Founded in 2019 from frustration with rigid EPM/ERP tools.
• Original problem: make decision modeling usable and collective.
• Cloud-native, collaborative, non-transactional.
• Focused exclusively on projection, scenarios, steering.

• What never changed: decision as conversation.
• What was added: scale, integrations.
• What was not transformed: rejection of transactional authority.

• Gravitation: decision dialogue.
• Conservation: clarity, business ownership.
• Perception: the enterprise as a system of future choices.
• Emergence: collective iteration.

• Energy: high but fragile.
• Optionality: strong within EPM.
• Embeddedness: low to medium (dependent on ERP backbone).

• Assumes non-linear time and human judgment.
• Encourages distributed sense-making.
• Prioritizes exploration over execution.

• Breaks when expected to enforce discipline or execution.
• Requires mature organizational cognition.

Dominant cognition: exploratory rationality.
Pigment thinks the future — not the past or execution.