Business → IT | IT → Business

Business teams love low-friction requests: add one field, a new checkbox, a quick report column. IT knows these 'small' changes can ripple through authentication, data models, integrations, reporting, and support processes — and suddenly a one-hour request costs months and multiple teams. This episode walks through the life cycle of a single-field request from both sides of the table. You’ll get a clear, practical lens for spotting true small changes versus architectural changes masquerading as tiny asks, and concrete rules of engagement to reduce rework, preserve simplicity, and assign the right decision rights before code is written. Mirko Peters uses a generalized consulting example to show where incentives and language create the trap, why good intentions fail in handovers, and three pragmatic governance patterns teams can adopt immediately. No vendor hype, no theory — just direct, actionable advice that helps leaders and engineers make fewer expensive 'quick' decisions.

Become a supporter of this podcast: https://www.spreaker.com/podcast/business-it-it-business--6867401/support.

To continue the conversation, follow Mirko Peters on LinkedIn, where more insights and real-world examples are shared from both business and IT perspectives.

Feature flags let organisations move fast: decouple releases, run experiments, and reduce deployment risk. But speed without shared rules becomes a hidden source of operational fragility, confused ownership, and regulatory exposure. In this episode Mirko Peters explains why feature flags are a governance problem as much as a technical one. You’ll get a clear view of what business stakeholders expect (flexibility, targeted launches, measurable outcomes), how engineering experiences flags in practice (state explosion, coupling, runtime risk), and where translation routinely breaks down. The episode walks through a generalized consulting example where unchecked toggles created months of debugging and missed KPIs, then gives concrete, practical steps both sides can adopt: minimal flag taxonomies, lifecycles, ownership gates, and telemetry rules that preserve speed without turning flags into long-term debt. No vendor hype — just practical rules that keep experiments honest and production safe.

Become a supporter of this podcast: https://www.spreaker.com/podcast/business-it-it-business--6867401/support.

To continue the conversation, follow Mirko Peters on LinkedIn, where more insights and real-world examples are shared from both business and IT perspectives.

Data is not just a backlog item — it's an internal product teams exchange. In this episode Mirko Peters explains how data contracts — compact, enforceable agreements about schema, semantics, SLAs and ownership — convert fragile integrations into reliable business infrastructure. He contrasts the business expectation that data is 'available and obvious' with the IT reality of schema drift, lineage gaps and quality trade-offs, then outlines a practical path to close that gap. Listeners get a generalized consulting story where missing data guarantees derail a launch, followed by concrete, low-friction actions: assign owners, codify schemas, add lightweight validation and versioning, and choose whether the contract lives in policy, code, or both. This episode focuses on pragmatic governance you can pilot in weeks, not heavyweight committees — ideal for leaders, product and data owners, architects and engineers who need dependable data without slowing the organisation.

Become a supporter of this podcast: https://www.spreaker.com/podcast/business-it-it-business--6867401/support.

To continue the conversation, follow Mirko Peters on LinkedIn, where more insights and real-world examples are shared from both business and IT perspectives.

Business leaders treat automation and features as win/lose outcomes: either the process works or people handle exceptions. IT inherits a growing pile of one-off fixes, tactical scripts, and emergency procedures that never get productised. This episode explains why those rare exceptions accumulate into a predictable, expensive burden—the Exception Tax—and how both sides can prevent it. I’ll explain the business incentives that accept exceptions as acceptable risk, the technical realities that make exceptions expensive to handle at scale, and a repeatable consulting approach to convert recurring exceptions into governed decisions, measurable backlog items, or intentional manual processes. Listeners will get concrete patterns to recognise exception taxation early, a lightweight template for prioritising fixes versus formalising workarounds, and short actions business and IT can start tomorrow to stop the slow drain on capacity and reliability.

Become a supporter of this podcast: https://www.spreaker.com/podcast/business-it-it-business--6867401/support.

To continue the conversation, follow Mirko Peters on LinkedIn, where more insights and real-world examples are shared from both business and IT perspectives.

Spec Drift examines the everyday slippage that happens after a business request leaves a meeting room and before code ships. Mirko Peters pulls apart the precise moments context is lost — ambiguous wording in emails, assumptions baked into wireframes, unmet non-functional expectations — and shows how those small gaps accumulate into schedule overruns, surprise outages, and strained relationships. This episode stays practical: it explains both the business incentives that encourage shorthand requests and the technical realities that make assumptions expensive, then gives three concrete habits teams can adopt immediately to preserve the intent of a request without slowing delivery. Listeners will get a clear map of where spec drift starts, a consulting-style example of what goes wrong in the wild, and action items for business and IT to reduce rework and improve predictability.

Become a supporter of this podcast: https://www.spreaker.com/podcast/business-it-it-business--6867401/support.

To continue the conversation, follow Mirko Peters on LinkedIn, where more insights and real-world examples are shared from both business and IT perspectives.

Contracts and procurement processes are usually treated as legal paperwork—until their wording becomes the organisation's operating rules. In this episode Mirko Peters takes a consultant's scalpel to procurement language: SLAs, change control, termination clauses, data ownership, payment milestones and acceptance criteria. You’ll hear how the business reads those clauses as risk allocation and commercial leverage, how IT reads them as technical constraints and operational requirements, and where well-intended language hardens bad architectural choices. The episode delivers a practical framework to identify harmful incentives, three lightweight contract edits that reduce long-term cost and vendor lock-in, and governance patterns that keep procurement from solidifying short-term fixes. No legalese, no vendor hype—just clear patterns and actions leaders, consultants, and IT professionals can use in RFPs, SOWs, and vendor conversations to align contracts with desired outcomes.

Become a supporter of this podcast: https://www.spreaker.com/podcast/business-it-it-business--6867401/support.

To continue the conversation, follow Mirko Peters on LinkedIn, where more insights and real-world examples are shared from both business and IT perspectives.

Many organisations build shared platforms, APIs, and internal services and then assume those components behave like external products: predictable roadmaps, clear value metrics, and dependable SLAs. Without explicit product thinking, business leaders hear vague promises and platform teams inherit shifting priorities, unpaid maintenance, and invisible costs. In this episode Mirko Peters walks through how treating internal platforms as real products changes funding conversations, decision rights, and the behaviour of both sides. You’ll get a pragmatic set of patterns: a one-page product charter for platform teams, how to translate business outcomes into platform SLAs, funding and prioritisation options that avoid stealth technical debt, and simple communication practices that reduce rework. This is a practical, non-hype look at operating models that produce predictable capability delivery while keeping maintenance visible and accountable.

Become a supporter of this podcast: https://www.spreaker.com/podcast/business-it-it-business--6867401/support.

To continue the conversation, follow Mirko Peters on LinkedIn, where more insights and real-world examples are shared from both business and IT perspectives.

Many organisations mistake governance for bureaucracy: unclear decision rights stall delivery, spawn rework, and turn simple requests into months-long sagas. This episode presents Decision Ownership Maps — a one-page, outcome-focused artefact you can create in a 90-minute workshop that stops approval loops and makes decisions actionable. I explain the map’s fields, how it ties specific decisions to artefacts (requirements, data contracts, release gates), and three crisp differences from RACI and decision-flag approaches so this isn’t just “more process.” You’ll hear a de-identified consulting example where the map halved review cycles and learn three measurable metrics to track (reopened tickets, review rounds, time-to-decision). I’ll read the template aloud, give a lean workshop recipe, and set simple maintenance and escalation rules. Practical, non-theoretical, and immediately usable—designed for leaders, product managers, consultants, and IT professionals who need faster alignment between strategy and delivery.

Become a supporter of this podcast: https://www.spreaker.com/podcast/business-it-it-business--6867401/support.

To continue the conversation, follow Mirko Peters on LinkedIn, where more insights and real-world examples are shared from both business and IT perspectives.

Too many organisations treat decisions like one-off events: specified during a project then left unmanaged after go-live. The result is 'ownership debt' — decisions with no clear owner, dissolving accountability into fragile systems, recurring rework, and hidden costs. In this episode Mirko Peters explains how unclear decision ownership amplifies technical debt and business risk, why it happens (project handovers, incentives, and governance gaps), and how to design for responsibility across the lifecycle. Through a generalized consulting example Mirko shows the typical missteps that leave features orphaned and roadmaps inconsistent, then gives concrete patterns to reassign ownership, create lightweight decision records, and align incentives between product, operations and architecture. Listeners will get practical guidance they can apply in the next week: how to name owners, set review cadences, and make small governance changes that stop ownership debt from compounding. This is for leaders, architects and delivery managers who want decisions to survive beyond the slide deck.

Become a supporter of this podcast: https://www.spreaker.com/podcast/business-it-it-business--6867401/support.

To continue the conversation, follow Mirko Peters on LinkedIn, where more insights and real-world examples are shared from both business and IT perspectives.

Most organizations measure success with KPIs, yet business and IT often mean different things by the same metric. This episode unpacks why dashboards that look aligned can hide fatal misunderstandings: revenue vs recognized revenue, "uptime" vs user-perceived availability, velocity vs predictable delivery. I’ll show how language, unit mismatch, and aggregation choices bend decisions toward the wrong trade-offs, and why measurement gaps amplify at scale. Using a generalized consulting case, we examine a product team that chased "faster delivery" metrics and ended up increasing rework and customer churn. The goal is practical: give leaders and technologists a repeatable checklist to translate business intent into technical measures, expose false signals, and design metrics that reduce ambiguity. Expect clear rules for naming, ownership, sampling, and escalation—no vendor hype, just concrete steps to make your KPIs actually drive the outcomes you want.

Become a supporter of this podcast: https://www.spreaker.com/podcast/business-it-it-business--6867401/support.

To continue the conversation, follow Mirko Peters on LinkedIn, where more insights and real-world examples are shared from both business and IT perspectives.