Épisodes

  • Data Contracts: Who Signs the Schema?

    Data Contracts: Who Signs the Schema?
    May 4 2026
    APIs, event schemas, and data extracts are the invisible contracts that connect teams. Left implicit, they create brittle integrations, surprise outages, and creeping cost — but handled well, they become deliberate levers for scaling change safely. This episode explains data contracts in plain business terms: what a contract is, who should sign it, how to version and evolve it, and which tests and governance steps actually reduce risk without slowing delivery. I walk through the differing expectations from product owners, architects, and engineers, illustrate a consulting example where unclear ownership caused a month-long outage, and offer concrete, low-overhead practices (consumer-driven checks, backward-compatibility rules, ownership levels) that translate into fewer late-night rollbacks and clearer accountability. The emphasis is practical: stop arguing over tools and start agreeing on commitments that map to business 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.
    Afficher plus Afficher moins
    9 min
  • The Internal‑Vendor Trap: When Treating IT Like a Supplier Breaks Value

    The Internal‑Vendor Trap: When Treating IT Like a Supplier Breaks Value
    May 3 2026
    Many organisations fall into a familiar pattern: business treats IT like an external supplier, and IT responds with contracts, SLAs and handoffs that minimise risk but also diffuse responsibility. The consequence is predictable—split incentives, brittle integrations, slower decision‑making and features that meet a contract but not the outcome. In this episode Mirko Peters walks through the mechanics of the internal‑vendor mindset, contrasting the business expectations it aims to satisfy with the engineering realities it creates. Through a generalized consulting example he shows where ownership evaporates, how governance can quietly incentivize the wrong trade‑offs, and which small governance, funding and language changes restore end‑to‑end accountability. Practical, no‑nonsense, and immediately actionable for both leaders who sign the checks and technologists who build the systems.

    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.
    Afficher plus Afficher moins
    10 min
  • Launch ≠ Value: The Last Mile That Decides If Projects Deliver

    Launch ≠ Value: The Last Mile That Decides If Projects Deliver
    Apr 30 2026
    Many organizations celebrate a successful release like it is the end of a project. The reality is different: value is realized after launch, through monitoring, adoption, process change, training, billing, and ongoing ops. In this episode Mirko Peters walks the listener through the hidden last mile where technical delivery meets commercial and operational reality. You’ll hear the business expectations that assume instant benefit, the IT constraints that assume deployment equals delivery, and the common translation failures that turn launches into shelfware or continuous rework. Using a generic consulting example, Mirko explains where decisions get dropped, what causes slow or failed adoption, and what a pragmatic, accountable post-launch plan looks like. The episode concludes with concrete actions both business and IT can take immediately to convert releases into measurable outcomes and protect ROI.

    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.
    Afficher plus Afficher moins
    9 min
  • Escalation Tax: When Every Problem Becomes an Emergency

    Escalation Tax: When Every Problem Becomes an Emergency
    Apr 29 2026
    Every organisation pays an invisible fee when issues are escalated by habit rather than design. In this episode Mirko Peters explains the dynamics that turn predictable work into perpetual emergencies: unclear ownership, ambiguous priorities, missing rollback plans, and incentives that reward shouting louder instead of resolving root causes. The episode dissects both sides: what business thinks escalation achieves and why IT experiences it as context-free, costly interruption. You get a compact, practical framework to reduce escalation frequency and severity—triage rules, explicit escalation paths, lightweight reversible decisions, and ways to preserve context across handoffs. The goal is realistic: reduce firefighting, protect delivery cadence, and make escalation a deliberate governance tool instead of a reflex. This is a single-person, consultant-style monologue with precise, actionable guidance suitable for leaders, architects, and delivery managers.

    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.
    Afficher plus Afficher moins
    8 min
  • Temporary Isn't a Feature: How 'We'll Fix It Later' Shapes Systems and Strategy

    Temporary Isn't a Feature: How 'We'll Fix It Later' Shapes Systems and Strategy
    Apr 27 2026
    Most organisations treat "temporary" fixes as a verbal IOU: stitch something together now and replace it later. In reality those promises rarely survive handovers, budget rounds and new priorities—temporary code, manual workarounds and one-off processes become durable constraints. In this episode Mirko Peters lays out why "temporary" decisions calcify into permanent architecture and behaviour, how incentives and accounting practices make "later" invisible, and how both business and IT unintentionally incubate technical debt. You’ll get a concise, practical framework to classify temporary work, make time-limited choices explicit, attach sunset and ownership rules, and align budget and risk so interim solutions remain reversible. Expect clear, consultant-tested actions you can use next week: capture known-badness as a decision, set measurable sunset criteria, negotiate rollback funding, and create a lightweight governance pattern that keeps temporary actually temporary.

    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.
    Afficher plus Afficher moins
    8 min
  • Who Owns the Non‑Functional Story? Turning NFRs into Decisions, Not Arguments

    Who Owns the Non‑Functional Story? Turning NFRs into Decisions, Not Arguments
    Apr 25 2026
    Non-functional requirements live in the shadow of feature requests: everybody assumes them, nobody signs them. In this episode Mirko Peters reframes NFRs—reliability, performance, security, operability, maintainability—as a portfolio of explicit decisions that require owners, trade-offs, and acceptance criteria. Through the lens of business goals and technical constraints, he explains how vague demands become overruns, rework, and blame, and shows a practical path to turn qualitative concerns into measurable policies: priority mapping, decision records, service-level translations, and lightweight acceptance tests. Listeners get concrete scripts to extract business intent, a checklist IT teams can use to propose viable options, and a compact governance pattern that prevents NFRs from becoming permanent debt. This episode is for execs, product managers, architects and engineering leaders who need fewer arguments and more actionable choices when non-functional aspects determine cost, risk, and competitive capability.

    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.
    Afficher plus Afficher moins
    10 min
  • Budget Rhythms: How Financial Calendars Shape Technical Choices

    Budget Rhythms: How Financial Calendars Shape Technical Choices
    Apr 22 2026
    Budget Rhythms examines the invisible force that steers product and technical decisions: the financial calendar. Across organizations, quarter- and year-end deadlines, capital versus operating classifications, procurement windows and forecast-driven prioritization consistently nudge teams toward short-term fixes, scope-slicing, and risky cutbacks. This episode lays out the business incentives that make those choices sensible on paper and the technical realities they create over time. I’ll unpack where the common misalignments live, illustrate a typical consulting case where budget timing forced an avoidable rework cycle, and give concrete rules of thumb both leaders and engineers can use to negotiate trade-offs without trading away future agility. Practical, no-nonsense, and focused on decisions you can change tomorrow—this episode helps you treat budgets as a design constraint rather than a recurring surprise.

    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.
    Afficher plus Afficher moins
    9 min
  • Feature Flags as Business Instruments: who owns risk, experiments and release control

    Feature Flags as Business Instruments: who owns risk, experiments and release control
    Apr 21 2026
    Feature flags are everywhere: used for experiments, staged rollouts, and quick kill switches. But too often they are treated purely as code knobs, creating operational risk, hidden complexity, and unclear decision rights. This episode reframes feature flags as a cross-functional instrument that encodes business intent, risk policy, and customer promises. I'll walk through how business leaders think about launches and customer impact, how engineering teams see technical debt and operational burden, and where the translation between intent and implementation breaks down. You’ll get a concrete, consultant-style checklist to decide who owns flag lifecycle, what minimal metadata flags must carry, and how to fold flags into governance, monitoring and decommissioning so they stop becoming permanent technical debt. Practical, non-technical examples and a short consulting case show common failure modes and straightforward fixes anyone can introduce next week.

    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.
    Afficher plus Afficher moins
    10 min