エピソード

  • The 'Buy vs Build' Question Is the Wrong Question: Why Ownership Is What You're Really Deciding

    The 'Buy vs Build' Question Is the Wrong Question: Why Ownership Is What You're Really Deciding
    2026/09/18
    Every IT project starts with the same familiar debate: should we buy a package or build it ourselves? The problem is that this question is a trap. Buying still means you own integration, customization, upgrades, and the business process changes that come with it. Building means you own the code, the talent, the technical debt, and the long-term roadmap. This episode shows why the real decision is about ownership—of functionality, data, risk, and organizational capability. Mirko Peters explains why 'buy' rarely means 'done,' why 'build' rarely means 'unique,' and how to reframe the conversation around total cost of ownership and strategic control. He shares a generalized consulting example of a company that bought an off-the-shelf CRM, then spent eighteen months customizing it until it was neither standard nor simple. The result: the worst of both worlds. Practical takeaways help business leaders and IT teams ask better questions before committing millions. If you are facing a buy/build decision, this episode will change how you think about it.

    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.
    続きを読む 一部表示
    10 分
  • The Estimate Is Not a Commitment: Why Deadlines Become Fictions Before the Work Even Starts

    The Estimate Is Not a Commitment: Why Deadlines Become Fictions Before the Work Even Starts
    2026/09/17
    Estimates are the quiet battleground of business-IT alignment. Business hears a number and turns it into a budget, a roadmap, a promise to the board. IT knows the number is a guess wrapped in assumptions about scope, dependencies, and unknowns. Then the guess hardens into a deadline, and everyone starts protecting themselves: buffers get hidden, scope gets squeezed, status reports soften reality. This episode explores why an estimate is not a commitment and why treating it as one is one of the most expensive mistakes organizations make. Mirko Peters breaks down how business and IT use the same word to mean different things, why single-point estimates are so dangerous, and how to separate the conversation about uncertainty from the conversation about commitment. He shares a generalized consulting example where one number derailed a program, and gives practical takeaways that help business leaders ask better questions and IT teams give more honest answers. The goal is not better estimates—it is better decisions under uncertainty.

    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.
    続きを読む 一部表示
    19 分
  • The Budget Is the Architecture: Why Funding Decisions Shape Your IT Systems More Than Any Design

    The Budget Is the Architecture: Why Funding Decisions Shape Your IT Systems More Than Any Design
    2026/09/16
    Every IT project starts with a budget decision, but most business leaders treat the budget as a purely financial constraint—while IT teams treat it as a mystery that prevents them from building the right thing. The result is an architecture that nobody designed: siloed systems, duplicated capabilities, and technical debt that quietly grows with every funding cycle. This episode argues that the budget is not just money; it is the most powerful architecture decision an organization makes. When a business unit funds its own tool, it creates a silo. When finance insists on short-term cost savings, it defers the platform investment. When capital and expense rules change, they rewrite the system landscape. Mirko Peters explains how to see the technical consequences of every funding model, why finance and IT speak different languages, and how to align budget allocation with the target architecture. You will learn how to spot the budget decisions that shape your systems and how to turn funding from a constraint into a strategic lever.

    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.
    続きを読む 一部表示
    8 分
  • The Pilot Is Not a Strategy: Why a Successful Pilot Can Stall a Transformation

    The Pilot Is Not a Strategy: Why a Successful Pilot Can Stall a Transformation
    2026/09/15
    Every pilot project starts with cautious optimism and ends with a decision: do we scale this or not? Too often, business and IT answer that question differently. Business sees a successful pilot as proof that the idea works. IT sees a pilot as a controlled experiment that was hand-built, closely watched, and excused from the usual constraints. This episode looks at the pilot paradox: why a small win can become the most dangerous deliverable in a transformation program. We explore what business really means by 'it works,' what IT means by 'it's ready,' and why the gap between those two statements is where projects stall. You'll hear a generalized consulting example of a regional pilot that looked great and failed at national scale, plus practical questions to ask before you start any pilot. If you want to stop confusing proof of concept with proof of value, this episode gives you a clearer way to think about pilots, rollouts, and readiness.

    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.
    続きを読む 一部表示
    13 分
  • The Data Quality Myth: Why Cleaning Data Never Fixes the Process That Dirtied It

    The Data Quality Myth: Why Cleaning Data Never Fixes the Process That Dirtied It
    2026/09/15
    Every organization has a data quality problem. Business leaders see incorrect records, duplicate customers, and missing fields—and assume IT can fix it. IT teams know the data isn't the root cause; it's the output of broken workflows, missing ownership, and incentives that reward speed over accuracy. This episode flips the conversation. Mirko Peters explains why data quality is a business process problem wearing an IT costume, why cleaning data without changing the process is like mopping the floor while the tap keeps running, and how to stop the cycle. You'll learn how to define data ownership, how to turn data quality into a process requirement instead of a fire drill, and why the real fix often has nothing to do with technology. Practical, direct, and grounded in real consulting experience.

    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.
    続きを読む 一部表示
    7 分
  • The 'No' Is a Hidden Yes: When IT Refusals Are Actually Prioritization Decisions

    The 'No' Is a Hidden Yes: When IT Refusals Are Actually Prioritization Decisions
    2026/09/14
    IT's 'no' is rarely a refusal. It's a hidden yes—to keeping systems stable, to protecting security, to maintaining commitments already made. But when that logic stays invisible, business hears only rejection. This episode unpacks the unspoken trade-offs behind IT constraints and shows why every 'no' is actually a prioritization signal. Mirko Peters explains how to make these implicit choices explicit, using a simple framework to surface what IT is saying yes to instead. You'll learn how to reframe 'no' as an offer to negotiate trade-offs, why vague requests often create the very refusals they complain about, and how to turn conflict into a clear decision process. If you've ever been frustrated by an IT shutdown or had to defend an infrastructure decision, this episode gives you a new language for moving from opposition to alignment.

    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.
    続きを読む 一部表示
    9 分
  • The Integration Is an Organizational Chart: Why System Connections Fail Before a Single API Is Built

    The Integration Is an Organizational Chart: Why System Connections Fail Before a Single API Is Built
    2026/09/13
    When business leaders say 'we need to integrate these systems,' they usually mean 'make the data flow so we can see one truth.' IT teams hear a technical project: APIs, mappings, error queues. But the hardest part of integration is rarely technical. It is organizational. Every system boundary reflects a boundary between teams, budgets, and decisions. If two departments can't agree on who owns a customer record or what 'active' means, no interface can save the project. In this episode, Mirko Peters shows why integration projects fail before a single API is built, how to spot the real owners and hidden assumptions, and how to turn an integration request into a conversation about governance and trust. You'll learn practical ways to expose the organizational questions hiding inside technical requests—and how to prevent the expensive, frustrating cycle of connected systems that still don't produce aligned decisions. This is a clear-eyed, practical look at why system integration is business integration.

    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.
    続きを読む 一部表示
    7 分
  • The Test Is the Spec: Why Your Requirements Are Only as Good as Your Tests

    The Test Is the Spec: Why Your Requirements Are Only as Good as Your Tests
    2026/09/12
    Every requirement is a promise until it's a test. In this episode, we explore why automated tests are the only precise, unambiguous specification of what a system should do, and why they're often the last thing business stakeholders see. We'll look at the business perspective: why documents feel solid but are actually fuzzy. We'll look at the IT perspective: why developers trust tests over conversations. And we'll expose the gap that leads to costly rework. With a real-world example of a claims system where a single test revealed a missing definition, you'll learn practical ways to turn tests into a shared language. If you're tired of misunderstandings between business and IT, this episode gives you a clear, actionable path to alignment. No jargon, just honest advice from both sides.

    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.
    続きを読む 一部表示
    10 分