Business → IT | IT → Business

Teams plan delivery budgets but rarely budget the capacity to undo. That missing line turns rollbacks into emergency borrowing: all‑hands nights, hidden costs, and damaged trust. This episode introduces the Rollback Reserve: a compact planning artifact you write into change proposals and roadmaps that names the undo budget (minutes-to-undo target, on‑call allocation, cost cap, and acceptance criteria for rollback vs. remediate). Mirko contrasts the business trade-off (faster launches vs. the cost of potential reversals) with the operational reality (limited on‑call attention, stateful complexity, and reproducibility gaps). Listeners get an exact one‑line Rollback Reserve template to read aloud, a short ritual to include it in planning and sprint review, and a practical 7‑day experiment to pilot reserves on five changes. The result: fewer surprise all‑hands, clearer trade‑offs during prioritization, and a funded, measurable path to undo when things go wrong. CTA: attach a Rollback Reserve to your next ticket and leave a review if it reduced night pages.

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.

Hidden assumptions quietly trigger rollbacks, late nights, and weekend incidents. This episode reframes the practice as 'Assumption First‑Aid'—a fast triage to stabilize plans before they bleed. Mirko opens with a 20–30 second dramatized weekend outage vignette traced to a buried belief, then explains why a short ritual wins where checklists fail. Listeners get a copy‑paste Assumption Card example to read aloud: Assumption: 'Search API returns <100ms at 1k QPS'; Owner: Dana (PM); Signal: p95 latency >120ms; Quick test: 30‑min synthetic load to 1k QPS; Window: 7 days. The episode gives a 5‑minute drill script, a 7‑day pilot plan (validate five assumptions, run one quick test), and three concrete metrics to track in a single ticket column: assumptions validated %, mean time to validation, and surprises avoided per sprint. We point to a one‑page GitHub gist template and a 30‑second submission form in the episode notes so listeners can adopt, share results, and build momentum. CTA: run a drill this week, paste the card into a ticket, log the three metrics, submit one result via the form, and leave a review if it reduced surprises.

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 accelerate launches and experiments — until proliferation, orphaned ownership, and environment drift turn them into a fragile, incident-prone surface. This episode opens with a 60–90 second engineer/PM clip recounting a rollout regression caused by a stale flag to set stakes, then delivers an auditable Flag Lifecycle Contract (read aloud and provided as a downloadable GitHub gist) and a step-by-step 7‑day Tidy ritual teams can run live. We provide a verbatim owner-assignment script for cross-functional meetings, a short implementation walkthrough (screen-share audio) that models the tidy in action, and clear pilot metrics: percent flags cataloged, time-to-retire, and flag-related incident rate. Role-specific rules for PMs, engineers and SREs plus a conservative "graduate vs retire" decision rule with mandatory verification steps help prevent regressions. Listeners leave with copy-paste artifacts, a short script to reduce behavioral friction, and a concrete CTA to run the tidy on one release stream and track measurable impact.

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 asks and engineering answers through different lenses; what looks urgent to product can be low‑impact for operations, and what IT treats as risky can feel like a blocker to sales. This episode teaches a lightweight, reproducible practice: the Expectation Heatmap. Mirko explains how to run a 30‑minute cross-role mapping session that produces a single shared visual (business‑perceived impact vs. IT‑perceived effort) plus a paired readiness flag. Listeners get the exact readout script, a five‑cell heatmap template to copy, and a 7‑day experiment: map five upcoming tickets, run the heatmap readout, and prioritize the visible mismatches. The episode contrasts business and IT mental models, shares a generalized consulting vignette showing how a one-page heatmap stopped a misrouted sprint, and delivers clear, role‑specific takeaways: what business must name before asking and what IT must disclose before estimating. The CTA challenges listeners to run the 30‑minute readout this week and leave a review if it shrinks misalignment.

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 call work 'ready' while hidden conditions—configuration drift, undocumented dependencies, stale runbooks, observability gaps, or untested rollback paths—leave launches fragile. This episode introduces the False‑Ready Audit: a compact, tool‑agnostic diagnostic you can run in 30–90 minutes to surface where readiness is performative rather than operational. Mirko contrasts the business impulse to mark progress (ship dates, demos, stakeholder signals) with IT's deeper readiness signals (dependency ownership, monitoring baselines, restoration plan). Listeners get a copy‑paste Ready Truth Table (owner alignment, critical dependencies, test surface, observability baseline, rollback rule, compliance check) and a reproducible 7‑day sampling experiment: score five recent 'ready' items, compute the truth gap, and prioritize fixes. A generalized consulting vignette shows a declared‑ready rollout that degraded service for a day; Mirko models scoring on‑air and gives clear, cross‑role actions to reduce surprise and make 'ready' mean the same thing for everyone.

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 are good at dissecting failures—rarely at learning from what actually worked. This episode introduces a pragmatic Win Postmortem: a five‑minute, read‑aloud ritual plus a one‑page template that captures context, critical decisions, tradeoffs, verification signals, and the minimal conditions needed to repeat success. Mirko contrasts the business instinct to celebrate wins (market timing, PR, metrics) with IT’s view (configuration choices, deployment safety, monitoring baselines), showing how absent documentation turns lucky outcomes into fragile one-offs. Listeners get a reproducible habit: run a Win Postmortem within 72 hours of a meaningful success, append a one‑line 'repeat condition' to the runbook, and run a 7‑day reuse pilot to test whether the captured practice actually reduces rework. Practical examples, exact read‑aloud phrasing, and measurable pilot targets make this episode an immediate operational lever for leaders and practitioners who want to institutionalize repeatable wins.

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.

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.

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.

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.

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.