Intrenion

Intrenion Ledger

Christian Ullrich
2026-03-25

Make commitments explicit.

Define commitments between organizations and approve them transparently.

Foundational Commitment

We do not treat silence as agreement.

Problem: Vendor Projects Drift Because Commitments Stay Implicit

• We see that vendor projects rarely fail because of technical problems.
• We see that projects drift when commitments remain implicit.
• We see discussions end without clear approval.
• We see responsibilities shift without explicit confirmation.
• We see silence in an email treated as agreement.

Observations: What Vendor Tension Actually Sounds Like

• We recognize recurring signals when commitments were never clearly agreed.
• We hear teams say: “That’s not what we agreed.”
• We hear teams say: “We understood it differently.”
• We hear teams say: “This was never approved.”
• We hear teams say: “We need to reopen this.”

Observations: Why Email, Excel, and PM Tools Fail Under Pressure

• We recognize that traditional tools record activity but not commitments.
• We see email document discussions but not explicit approval.
• We see spreadsheets track items but allow silent edits.
• We see project tools assume alignment between teams.
• We see shared documents record notes, but not binding commitments.

Consequences: The Real Risk When Commitments Stay Implicit

• We see scope expand without formal confirmation.
• We see change requests turn into negotiation conflicts.
• We see delivery delays trigger blame discussions.
• We see contracts become harder to defend as escalation progresses.
• We see sponsors lose credibility when commitments cannot be proven.

Principles: Governance Rules for Explicit Commitments

• We require that commitments affecting scope, responsibilities, timelines, or cost be recorded.
• We require that stakeholders explicitly approve or reject commitments.
• We require that silence cannot be treated as agreement.
• We require that open commitments remain visible until resolved.
• We require that every approval and rejection become part of the permanent record.

System: How We Record and Approve Commitments

• We record commitments that affect scope, deliverables, responsibilities, timelines, or cost.
• We name the stakeholders responsible for approving each commitment.
• We request explicit approval or rejection from those stakeholders.
• We keep open commitments visible until they are resolved.
• We preserve the full history of approvals and rejections for later reference.

Limits: What We Do Not Use This System For

• We do not use this system to manage tasks or track daily project work.
• We do not use this system to replace project management software.
• We do not use this system to document meetings or store discussion notes.
• We do not use this system as a document repository or knowledge base.
• We use this system only to record commitments that affect scope, responsibilities, timelines, or cost.

Effects: What We Expect After a Few Weeks

• We expect fewer repeated discussions about decisions that were already addressed.
• We expect approvals to happen faster because responsibilities are explicit.
• We expect clearer ownership of commitments between client and vendor teams.
• We expect steering meetings to focus on unresolved commitments rather than revisiting prior discussions.
• We expect fewer scope disputes during project execution.

Applicability: When We Use This System

• We use this system when vendor projects create real financial or delivery exposure.
• We use this system when the scope, responsibility, timelines, or cost require explicit agreement.
• We use this system when repeated discussions indicate that commitments are unclear.
• We use this system when project sponsors need a clear record of approvals and responsibilities.
• We use this system when vendor relationships require governance beyond email and meeting notes.

Pricing: Commercial Terms for Project Governance

• Here is the corrected version with monthly in advance:
• We accept a price of 200 EUR per month for the governance of vendor commitments.
• We accept that subscriptions are billed monthly in advance.
• We include up to 10 users within the base subscription.
• We accept an additional 20 EUR per user per month for additional participants.
• We evaluate this system against the cost of a single unresolved scope dispute.

How Commitments Become Decisions

The system records commitments, requires explicit approval, and preserves the decision record.

1. Record a commitment: Project participants record commitments that affect scope, responsibilities, timelines, or cost.
2. Stakeholders approve or reject: Named stakeholders explicitly approve or reject the commitment.
3. The decision becomes the record: Every approval, rejection, and change becomes part of the permanent commitment history.