Mirko Peters

Business → IT | IT → Business

Business EN ↓ 130 episodes

Business → IT | IT → Business A Consultant Podcast by Mirko Peters Business talks strategy. IT talks systems. Most failures happen in between. In Business → IT | IT → Business, Mirko Peters—consultant working on both sides of the table—translates what business means and what IT needs. No buzzwords, no vendor talk, no politics. Each episode untangles real-world problems where strategy, technology, people, and process collide. From digital transformation and architecture decisions to misaligned expectations and costly misunderstandings—this podcast shows how business decisions become IT reality...

Be sure to visit the podcast's website and support the creator: www.linkedin.com

Author

Mirko Peters

Category

Business

Podcast website

www.linkedin.com

Latest episode

Sep 18, 2026

Where to listen?

Podcasts in the app Replaio Radio Coming soon

Podcasts are coming to the app soon. Install now and be the first to see a whole new take on podcasts

Get it on Google Play Install for free Android 10M+ downloads · 4.7+ rating iOS soon

Episodes

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

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...

The Estimate Is Not a Commitment: Why Deadlines Become Fictions Before the Work Even Starts 17.09.2026

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....

The Budget Is the Architecture: Why Funding Decisions Shape Your IT Systems More Than Any Design 16.09.2026

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 bud...

The Data Quality Myth: Why Cleaning Data Never Fixes the Process That Dirtied It 15.09.2026

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...

The Pilot Is Not a Strategy: Why a Successful Pilot Can Stall a Transformation 15.09.2026

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 w...

The 'No' Is a Hidden Yes: When IT Refusals Are Actually Prioritization Decisions 14.09.2026

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 expli...

The Integration Is an Organizational Chart: Why System Connections Fail Before a Single API Is Built 13.09.2026

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 cu...

The Test Is the Spec: Why Your Requirements Are Only as Good as Your Tests 12.09.2026

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 convers...

The Legacy System Is a Business Decision: Why Old IT Isn't a Technical Problem 11.09.2026

{"title":"The Legacy System Is a Business Decision: Why Old IT Isn't a Technical Problem","one_liner":"Legacy systems aren't just technical debt—they're a series of business choices frozen in code, and pretending otherwise leads to expensive rewrites and missed opportunities.","description":"Every organization has them: systems that have outlived their welcome, yet somehow remain mission-critical....

The Shadow IT Paradox: When Business Buys Its Own Tools, IT Pays the Price 10.09.2026

In this episode, Mirko Peters takes on shadow IT—the unofficial spreadsheets, cloud apps, and small scripts that business teams adopt to get things done when IT seems too slow. He explores why shadow IT exists, the real costs it hides (integration headaches, data silos, security risks, duplicated effort), and why the typical IT response—banning it—makes things worse. He offers a practical framewor...

The Workflow Is Not the Work: Why Automating the Diagram Can Preserve the Problem 09.09.2026

Organizations often ask IT to automate a workflow because the process has already been documented, approved, or drawn in a familiar diagram. That apparent clarity can be misleading. A workflow describes the sequence people follow; it does not necessarily explain the customer outcome, decision logic, hidden manual effort, or constraint the sequence was meant to address. This episode examines how bu...

The Approval Is Not a Decision: How Sign-Offs Create False Certainty 08.09.2026

Organizations often treat approval as the end of a conversation. A business sponsor signs a requirement, a steering group endorses a design, or a process owner approves a change, and everyone moves forward assuming the important choices are settled. But approval can mean many different things: agreement with the goal, acceptance of the risk, acknowledgment of the wording, or simple permission to c...

The Handoff Is a Lossy Compression Algorithm: How Meaning Disappears Between Business and IT 07.09.2026

A business request rarely reaches implementation in its original form. It passes through meetings, documents, tickets, models, estimates, and approvals, with each handoff simplifying the message. By the time IT delivers what was written, the organization may have lost why the request mattered, which assumptions shaped it, and what outcome was actually expected. This episode examines handoffs as a...

The Business Rule That Outlived Its Reason: How Old Decisions Become New Constraints 06.09.2026

Business rules rarely arrive with an expiration date. A pricing threshold, approval step, customer classification, or reporting requirement may have been sensible when introduced, yet remain embedded in processes and systems long after its original purpose has disappeared. This episode examines how outdated decisions quietly become permanent operating constraints—and why removing them is harder th...

The Decision Without an Owner: How Shared Accountability Creates Unowned Systems 05.09.2026

Organizations often say that important decisions are shared. In practice, shared responsibility can mean that no one has the authority, context, or obligation to make the call and stand behind its consequences. This episode examines what happens when ownership is distributed across business sponsors, product teams, architects, operations, security, and vendors without a clear decision owner. From...

The Metric Becomes the Machine: How KPIs Quietly Redesign Business and IT 04.09.2026

Organizations often treat KPIs as neutral instruments for observing performance. In practice, a metric can become an instruction. Once targets influence bonuses, escalation rules, prioritization, service levels, or investment decisions, they begin shaping business behavior—and the systems that support it. This episode examines how a seemingly reasonable measure can produce narrow optimization, cus...

The Calendar Is Part of the Architecture: How Timing Rules Become Business Constraints 03.09.2026

Organizations often treat timing as an implementation detail: a nightly batch, a month-end cutoff, a two-day approval window, or a promise that a report will be ready by morning. But once those timing rules enter workflows, integrations, contracts, and customer expectations, the calendar becomes part of the operating model. This episode examines how business assumptions about speed, deadlines, and...

The Exception Becomes the Process: How Temporary Workarounds Turn into Permanent Architecture 02.09.2026

Organizations often introduce exceptions with good reason: a customer needs special treatment, a deadline cannot move, or an existing system cannot support an important case. The trouble begins when a temporary workaround is repeated, remembered, and eventually built into everyday operations without anyone making an explicit decision. Business may see flexibility and responsiveness; IT may see und...

The Queue Is a Strategy: How Work Intake Decides What the Business Gets 01.09.2026

Organizations often treat work intake as administration: collect requests, add them to a backlog, and ask teams to work through the list. But the intake queue is where strategy becomes operational reality. It determines whose problems receive attention, which risks remain invisible, and whether urgent work continually displaces important work. From the business side, a request may appear to be a s...

The Small Change Illusion: Why Minor Policy Decisions Create Major IT Work 31.08.2026

Business leaders often describe a policy change as simple: one new approval step, a slightly different eligibility rule, or a revised deadline. IT may then respond with questions that sound disproportionate to the request. This episode explains why. Mirko Peters follows a minor policy decision across workflows, roles, data structures, interfaces, reporting, testing, training, and customer communic...

The Cost of Keeping Options Open: When Business Ambiguity Becomes IT Complexity 30.08.2026

Organizations often delay difficult choices by asking IT to build something flexible enough to support every possible future. The intention is sensible: preserve options, avoid premature commitment, and respond to changing priorities. The hidden cost is that flexibility requires rules, configuration, testing, governance, and ongoing explanation. When business decisions remain deliberately vague, I...

The Requirement Nobody Wrote: How Unstated Boundaries Become System Behavior 29.08.2026

Business and IT teams often spend hours discussing what a system should do while barely discussing what it must not do, who may use it, which exceptions are unacceptable, or what happens when assumptions fail. Those unwritten boundaries do not disappear; they are filled in by developers, vendors, operations teams, or customers. This episode examines how silence becomes system behavior. From the bu...

The Org Chart in the System: When Team Boundaries Become Customer Friction 28.08.2026

Organizations often treat their structure as separate from their technology. In practice, reporting lines, departmental ownership, and budget boundaries frequently become workflows, permissions, queues, data silos, and separate customer interactions. What looks sensible inside the org chart can feel fragmented outside it: customers repeat information, cases stop at team boundaries, and employees c...

The Business Case After Approval: When the Assumptions That Won Funding Vanish from Delivery 27.08.2026

{"title":"The Business Case After Approval: When the Assumptions That Won Funding Vanish from Delivery","one_liner":"A business case may secure investment, but unless its assumptions survive into design and delivery, the organization can build exactly what was approved and still miss the outcome it funded.","description":"An approved business case is often treated as a finish line: funding is gran...

The Word "Done" Is a Contract: How Completion Definitions Shape Business Outcomes 26.08.2026

"Done" sounds like a simple status, but it is often an unspoken contract between business and IT. For a business stakeholder, done may mean a customer can complete a task, a deadline can be reported, or a process can move forward. For IT, it may mean the code works, tests pass, security checks are complete, documentation exists, and support can take responsibility. When those meanings diverge, pro...

Listen to the Business → IT | IT → Business podcast in Replaio

Radio and podcasts in one app - free, with no sign-up. Install today and do not miss the launch

Get it on Google Play

Replaio is not a podcast publisher; show names, artwork and audio belong to their authors and are distributed through public RSS feeds.