エピソード

  • Rollback Rehearsals for Stateful Changes: Practice the Hard Undo

    Rollback Rehearsals for Stateful Changes: Practice the Hard Undo
    2026/03/02
    Start with a thirty-second vignette: a payments startup ships a database migration, monitoring looks green, then latency and charge duplicates spike—on-call engineer Sana runs a manual rollback that stretches into hours. This episode reframes rollback as a short, repeatable rehearsal focused on stateful changes (schema tweaks, data migrations, third-party feature flips) that usually fail under stress. Mirko explains the business stakes, the technical pitfalls unique to state, and a compact 30–90 minute Rollback Rehearsal ritual tailored to preserve data integrity. Listeners get a one-page rehearsal template, concrete roles and verification checks, and a measurable pilot target (aim for <=20 minutes time-to-undo with zero customer-visible errors). Episode closes with three starter experiments and a clear pilot challenge: run one micro-rehearsal this week and use the template to report results.

    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 分
  • Automation Preflight: Decide to Automate — and Own the Outcome

    Automation Preflight: Decide to Automate — and Own the Outcome
    2026/02/26
    Too often automation is celebrated as a time-saver until the first silent failure, runaway cost, or orphaned script forces late-night firefights. This episode presents an Automation Preflight: a short, repeatable cross-functional ritual that tests whether automation is the right next step and makes post-deployment responsibility explicit. Mirko contrasts the business appetite for efficiency (expectations, SLAs, downstream promises) with IT’s operational reality (monitoring, drift, maintenance), then reads a compact, copy‑paste Preflight checklist on-air: rationale, success signal, scale assumptions, owner & support window, rollback/fallback, cost guardrail, and a 7‑day observation rule. Listeners get three low-friction rituals to try this week (preflight read, 7‑day watch, lightweight ownership tag), a measurable 7‑day pilot plan, and concrete signs automation should be paused or reverted. Closing asks listeners to run the preflight on one candidate automation, measure one outcome, and—if useful—leave a review.

    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.
    続きを読む 一部表示
    11 分
  • Minimum Operability Contract: Agree What 'Live' Actually Means (and Say It in One Line)

    Minimum Operability Contract: Agree What 'Live' Actually Means (and Say It in One Line)
    2026/02/26
    It starts with a 45‑second micro‑scene: 2 a.m., an alert flood, and three teams pointing at each other. This episode teaches a compact Minimum Operability Contract (MOC) you can write, read aloud, and attach to a ticket in under five minutes. We play a short live role‑play between a PM and SRE to show how two sentences remove assumptions. You’ll hear an explicit one‑line example (Owner=Product; Signal=error>1%; Rollback=manual on threshold; Support=9–5; Cost=approx $X/day; 7‑day watch=yes), three low‑friction rituals to try this week, and precise pilot metrics—overnight pages, median time‑to‑detect, and time‑to‑rollback—to measure improvement. The episode includes a downloadable one‑page template on the episode page and a prescriptive CTA: download the 1‑line MOC, use it on your next launch, run a 7‑day pilot, and share results with #MOCpilot.

    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 分
  • Derived Data Contracts: Make Ownership, Cost and Rollback Explicit

    Derived Data Contracts: Make Ownership, Cost and Rollback Explicit
    2026/02/23
    Organizations treat derived data—ad‑hoc dashboards, denormalized tables, ML features—as ‘free’ insight until a surprise bill, outage, or compliance question forces firefighting. This episode opens with a concrete vignette: a VP of Sales wakes to a $30,000 monthly cloud bill from the “Regional Sales Rollup” report and demands answers; Rina Patel, a Senior Data Engineer, explains how missing ownership and no rollback plan turned a 2‑hour analysis into months of toil. Mirko and guest analytics lead Carlos Mendoza present a one‑page Derived Data Contract (read verbatim on-air and available in show notes) and argue the counterintuitive claim: treat derived datasets as reversible products, not artifacts. Listeners get a live-filled example, three low‑friction week‑long rituals, a 7‑day freshness-and-cost audit, and a measurable pilot goal (catalog five derived datasets and cut surprise‑cost incidents by 50% in 30 days). CTA: copy the template from the notes, run the 7‑day audit, pilot one contract, and leave a review.

    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.
    続きを読む 一部表示
    11 分
  • Feature Sunsets: Design the Exit Before You Build

    Feature Sunsets: Design the Exit Before You Build
    2026/02/22
    Features don’t just ship — they stick. This episode argues that durable product thinking includes a clear, short sunset contract at conception: who can retire it, how to measure viability, what minimal migration or rollback looks like, and who owns the long tail. Mirko contrasts the business impulse to preserve options with IT’s experience of accumulating hidden maintenance, and he reads a compact, generalized vignette where a conveniently permanent feature cost months of work and morale. Listeners get a practical one-page Sunset Contract template, three low-friction rituals to try this week (sunset field in every PR, a 90-day viability checkpoint, and an automated sunset alarm), and a simple 7-day experiment to map the top five features most likely to become long-term drag. The episode is practical, tool-agnostic, and designed for leaders who prefer clear decisions over hopeful assumptions. CTA: run the 7-day map, pilot one Sunset Contract, and leave a review.

    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.
    続きを読む 一部表示
    12 分
  • Temporary Authority Contracts: Give Squads Permission — and a Sunset

    Temporary Authority Contracts: Give Squads Permission — and a Sunset
    2026/02/19
    Cross-functional squads and fast-response teams are how businesses move quickly — until their temporary privileges calcify into permanent exceptions that shift risk, cost, and responsibility. This episode argues for treating each short-lived team as a product with a one-page Temporary Authority Contract: explicit scope, delegated decision rights, limits, success signals, monitoring, sunset date, and a repatriation plan. Mirko walks both sides—why business wants autonomy to ship outcomes and why IT fears uncontrolled drift and hidden coupling—and shows how a simple, timeboxed contract preserves speed while protecting long‑term operability. Listeners get a compact contract template, three low-friction rituals to try this week (pre-launch contract read, mid-mission checkpoint, and automated sunset alarm), and a 7-day pilot to test whether temporary authority reduces blockers without creating governance debt. CTA: pilot one Temporary Authority Contract this sprint, collect one learning, and—if it helps—leave a review and follow Mirko on LinkedIn.

    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.
    続きを読む 一部表示
    12 分
  • Design the Escalation: Stop Turning Questions into Executive Emergencies

    Design the Escalation: Stop Turning Questions into Executive Emergencies
    2026/02/19
    Escalations are the organization’s safety valve — and when poorly designed they become the reason small uncertainties end up as executive crises, blame cycles, and recurring firefights. This episode reframes escalation as a product-like contract: clear trigger conditions, required context, decision window, and expected outcomes. Mirko walks both views—why business leaders expect escalations to protect outcomes and why engineering and ops fear them as permission costs that shrink autonomy—and shows how a few durable rules reduce churn, preserve learning, and make escalation an instrument of clarity, not crisis. Listeners get a one-page Escalation Contract template, three low-friction rituals to try in the next sprint (local guardrails, mandatory context snapshots, and a 24–72 hour decision SLA with rollback options), and a simple 7-day experiment to measure whether escalations drop in volume but improve in signal. CTA: run one Escalation Contract pilot this week, collect one learning, and—if it helps—leave a review and follow Mirko on LinkedIn.

    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 分
  • Prioritization Currency: Speaking the Same Value Language Between Business and IT

    Prioritization Currency: Speaking the Same Value Language Between Business and IT
    2026/02/16
    Priorities feel like opinions until you name the currency being spent. This episode argues that many alignment problems start because business and IT are paying for different things with the same budget: product asks for growth, finance watches forecast variance, IT budgets uptime and debt. Mirko defines a simple Prioritization Ledger (primary currency, owner, measurable signal, expected short-term cost, expected long-term cost, rollback rule) and walks listeners through how that artifact clarifies trade-offs in five minutes. The monologue contrasts common mismatches—features scored as ‘high priority’ for revenue but low-priority for operability—and offers three lightweight rituals: the one-minute currency declaration in planning, a weekly three-item currency audit, and a 7-day pilot mapping your top five backlog items. Clear examples, an anonymized vignette, and practical steps make this episode immediately usable. CTA: map five items this week, run the 7-day pilot, and—if it helped—leave a review and follow Mirko on LinkedIn.

    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 分