Business → IT | IT → Business Podcast Por Mirko Peters arte de portada

Business → IT | IT → Business

Business → IT | IT → Business

De: Mirko Peters
Escúchala gratis

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 and how IT choices reshape business outcomes. Clear. Direct. Sometimes uncomfortable.
Always honest. If you work in business, IT, or anywhere in between—this podcast is for you.

Become a supporter of this podcast: https://www.spreaker.com/podcast/business-it-it-business--6867401/support.Mirko Peters Economía
Episodios
  • Bot Contracts: Make Your Automated Agents Accountable

    Bot Contracts: Make Your Automated Agents Accountable
    Mar 13 2026
    Automations act like invisible teammates: they make requests, change state, and fail at odd hours—but rarely carry explicit responsibility. This episode introduces the Bot Contract: a tiny, copy‑paste artifact you attach to any automation so business expectations and operational realities meet before trouble begins. Mirko opens with a short vignette (a pricing-bot that retried customers into double‑charges), contrasts what business expects from an 'always-on' agent with what engineering actually needs to operate one safely, and reads a live one‑line Bot Contract on air (Intent; Owner; Retry policy; Observable signal; Human fallback; Cost cap; Sunset). Listeners leave with a 7‑day pilot: attach contracts to five automations, run an observability watch window, and measure incident count and mean time to human handoff. Practical, tool‑agnostic, and immediate: make your bots accountable and keep human attention where it matters. CTA: attach a Bot Contract this week and leave a review if it reduced surprise 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.
    Más Menos
    10 m
  • Feature Toggle Lifecycle: Make Flags First‑Class, Time‑boxed, and Observable

    Feature Toggle Lifecycle: Make Flags First‑Class, Time‑boxed, and Observable
    Mar 12 2026
    Feature flags accelerate learning and staged rollouts but, when unmanaged, become hidden coupling, operational surprise, and long‑running debt. This episode prescribes a concise Feature Toggle Lifecycle you attach to each flag: Owner; Intent; Audience; Default; Rollout criteria; Observable metric; Kill‑switch; Sunset date; Minimal test path. We open with a short micro‑vignette of an orphaned flag that created costly investigation, then walk through three copy‑paste lifecycle templates (experiment, ops switch, gradual rollout), a one‑minute guest quote from a platform lead, and a practical 7‑day pilot plan. The pilot includes a measurable success plan (lifecycles attached, flags retired/scheduled, mean time to rollback) and low‑friction PR language you can paste into code reviews. Assets (one‑page lifecycle template, 7‑day checklist, and PR snippets) are available in the episode show notes. By the end you’ll have concrete steps, enforcement roles, and a measurement plan so adoption is visible and manageable.

    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.
    Más Menos
    11 m
  • Rollback Reserve: Budget the Capacity to Undo

    Rollback Reserve: Budget the Capacity to Undo
    Mar 11 2026
    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.
    Más Menos
    10 m
Todavía no hay opiniones