Business → IT | IT → Business

Many organisations run vital work through ad-hoc automations: spreadsheets with macros, scheduled scripts, RPA bots, or low-code processes built by business teams. These 'shadow automations' solve immediate pain but quietly accumulate technical debt, create hidden dependencies, and shift responsibility away from IT. In this episode Mirko explains why business-built automations become long-term architecture problems, how IT perceives the maintenance cost, and where translation between urgent business needs and sustainable engineering decisions breaks down. Listeners get practical patterns for discovering shadow automations, deciding which to formalize, which to retire, and how to allocate ownership, budget and observability. The episode includes a generalized consulting example that shows common failure modes and a lightweight governance checklist that both business leaders and IT can use immediately to reduce surprise work and maintain agility.

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 organizations treat approvals, compliance checks, and procurement gates as administrative overhead — a checkbox before delivery. In reality these manual and semi-automated workflows are permanent product features: they shape technical architecture, define integration points, and set achievable timelines. In this episode I explain how business leaders frame controls as risk management while IT inherits brittle handoffs that become technical debt. I'll outline common failure modes — long feedback loops, optimistic deadlines, hidden handoffs, and escalation storms — and offer concrete alternatives: explicit ownership, decision SLAs, lightweight automation, and treating approval outcomes as part of the API contract. You’ll get practical rules for when to automate, when to keep human judgement, and how to reflect control gates in roadmaps and estimates. The aim is simple: preserve necessary governance, reduce surprise rework, and make approvals a deliberate design decision rather than a recurring emergency.

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 treat exceptions as an afterthought: temporary fixes, back-door workarounds, or promises to revisit later. Those decisions compound. Exceptions migrate into config, scripts, tickets, and tribal knowledge until they become the system. In this episode I unpack how routine choices about edge cases create technical debt, compliance exposure, and unpredictable operational costs — framed from both business and IT viewpoints. You'll get a practical, consultant-grounded walk-through for spotting exception drift, deciding which edge cases deserve investment, and creating small governance patterns that prevent one-off fixes from becoming permanent liabilities. Expect clear examples, a generalized project vignette, and precise actions business leaders and engineers can apply the next day to reduce surprise, cost, and friction without killing agility.

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 organizations use configuration to move faster: toggles, feature switches, YAML settings, environment variables, and admin screens promise change without code. That convenience carries a cost when business logic, policy exceptions and permanent rules quietly accumulate in config rather than in owned systems or documented processes. This episode explains how configuration sprawl forms, why business leaders assume high agility while IT inherits brittle, undocumented behavior, and how the translation gap multiplies risk across releases, audits and integrations. I walk through a generalized consulting case where a profitable pricing rule lived in six different configuration stores across regions, what went wrong, and practical, low-friction fixes that restore clarity: ownership contracts for config, meaningful naming and discovery, lifecycle rules for temporary settings, and guardrails that keep config fast and maintainable. Actionable, non-technical advice for leaders and engineers to make configuration an explicit business tool rather than an accidental product.

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.

Upgrades are treated as technical chores or inconvenient disruptions—until they silently shape strategy, risk and cost. This episode reframes upgrades as explicit business decisions with measurable trade-offs: choosing to postpone a platform update may avoid short-term change costs but increases security exposure, integration brittleness, support overhead and strategic inertia. Mirko walks through why business stakeholders say “not now”, why IT quietly accepts version drift, and how those choices compound into a persistent ‘upgrade tax’. The episode offers a practical decision framework, ownership patterns, and simple controls (risk windows, sunset plans, mitigations budgeting) that make upgrade consequences visible to executives and actionable for engineering. Listeners will leave with specific questions to ask before deferring change, a lightweight rubric to quantify the real cost of delay, and an executable approach to turn upgrade policy from a political quarrel into a governance discipline.

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.

Organizations routinely treat data shape and meaning as plumbing details. That tolerance creates silent breakages, costly firefighting, and stalled projects when a field changes or a dataset shifts meaning. This episode reframes data contracts — explicit, versioned producer-consumer agreements about schema, semantics, quality and SLIs — as a practical coordination mechanism at the business–IT boundary. I’ll explain how product managers, analysts and architects can use lightweight contracts to make change predictable, assign clear ownership, and convert mysterious production incidents into accountable decisions. You’ll get concrete patterns for versioning, consumer-driven checks, rollout tactics, and governance that doesn’t smother speed. The goal: fewer surprise outages, clearer trade-offs between speed and stability, and a repeatable way to evolve data without daily firefighting.

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 ask for 'fast' and 'secure' without the trade-offs; engineers hear vague goals and deliver defensive designs. In this episode I show why nonfunctional requirements (latency, reliability, scalability, security, observability) are fundamentally business decisions — not just technical knobs — and how to treat them as service contracts you can negotiate and measure. You'll get a practical way to turn abstract expectations into concrete Service Level Objectives, clear owners, and costed options that leaders understand. I cover common missteps that create brittle systems and surprised stakeholders, a generalized consulting example where an unspoken availability requirement doubled operations cost, and a compact set of actions both business and IT can adopt immediately. No hype, no vendor pitches — just the pragmatic framing and rituals that reduce rework and align incentives between product, engineering and operations.

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 rules aren’t just logic in code; they’re decisions embedded in policies, spreadsheet formulas, email threads and tribal knowledge. When those rules drift, organizations face inconsistent customer experiences, costly exceptions, and brittle integrations. In this episode Mirko Peters walks a consultant’s line between business and IT to show where rules typically live, why they decay, and how small governance and engineering practices stop drift without slowing the business. You’ll get a clear taxonomy of rule locations, realistic ownership models that respect operational realities, and actionable patterns—decision tables, rule registries, lightweight review rituals—that make rules discoverable, testable and changeable. No vendor pitches, no academic theory: practical steps leaders and technologists can start with tomorrow to reduce rework, speed decisions and keep systems aligned with evolving policy.

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 teams ship safely, run experiments, and decouple release from deployment—but without clear governance they become a source of operational risk, accidental complexity and misaligned incentives. In this episode Mirko Peters explains how feature-flag practices sit at the business–IT interface: product managers see a low-friction lever for experiments and fast launches, while engineers view a long-term maintenance burden that, unchecked, can fragment environments and obscure ownership. Through a consultant's lens Mirko walks through practical rules for when flags are acceptable, who owns lifecycle and metrics, how to keep experiments from becoming permanent shadow features, and governance patterns that keep experimentation productive instead of costly. Listeners will get concrete steps to introduce flag policies, decisions to automate or forbid, and lightweight rituals for handovers and cleanups. Useful for leaders, product managers, architects and platform teams who want the speed of experiments without the hidden tax of unmanaged flags.

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 organizations treat deployment as the finish line: code is released, dashboards show green, and everyone assumes the new capability is ‘in use’. In reality, adoption — the sustained change in behavior, process, and incentives — is the hard part. This episode unpacks why business leaders overestimate the impact of delivery and why IT teams underestimate the ongoing coordination needed to make change stick. You’ll get a concise, practical framework for diagnosing adoption risk, a generalized consulting example that highlights where rollout plans fail, and a checklist of concrete actions both sides can take before, during, and after deployment. The goal is simple: reduce wasted delivery effort, shorten the time to real outcomes, and set realistic accountabilities so systems actually change business behavior instead of quietly collecting dust.

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.