Podcast #20 Fireside Chat Too Much Governance Can Stiffen Innovation

Episode 20 – Transcription Timeline

00:03 — Opening Thesis

• Core statement: “Governance should come after innovation.”
• Sets the theme: guardrails slow creativity.

00:07 — Welcome & Context

• Host introduces the episode: “Hi all, welcome to another fireside chat.”
• Notes this is Episode 20 and the second consecutive release.

00:14 — Serendipitous Timing

• Mentions the previous episode about building an app and optimizing for time to business value.
• Here is the link to the previous episode – https://levelupm365.com/2026/04/06/podcast-19-fireside-chat-mitigate-risk-with-software-development/

00:33–00:43 — Connection to Previous Episode

• Encourages listeners to check the prior episode but clarifies it’s not required.

00:43–01:09 — Purpose of This Chat

• Focus: When to implement mechanisms and guardrails.
• Emphasizes high‑level thinking and trade-offs: “There’s not a perfect solution, only trade-offs.”

01:09–01:27 — Guardrails Can Hinder Early Creation

• Argues that early solution-building should avoid heavy governance.

01:27–02:23 — Rust vs. C Example

• Introduces Rust as a metaphor for guardrails.
• Rust prevents memory errors but can slow innovation.
• C and C-like languages powered systems for decades.
• Mentions iPhone hacks caused by memory leakage that Rust mitigates.
• Here is the write up on this story – https://medium.com/rustaceans/i-left-rust-and-went-back-to-c-763f241ba761

02:23–02:41 — Case Study: Team Abandoning Rust

• References an article about a team ditching Rust after 80,000 lines because it “was stifling innovation.”

02:41–03:17 — Innovation Requires Flow

• Innovation involves meandering and unknown paths.
• Guardrails create a “go, stop, go, stop” rhythm like football, which kills flow.

03:17–03:51 — M365 Example: Prototyping Without Restrictions

• Host prototypes in their own dev environment for freedom and speed.
• Quote: “I have global admin, God-like control.”
• Client-provided environments slow innovation.

03:51–04:10 — Tools & Hardware Constraints

• Requests VMs and local admin rights to avoid restrictive devices.
• Locked-down machines hinder creativity.

04:10–04:19 — Creative Process in IT

• Innovation requires experimentation: “You’ve got to throw a lot of things in the wall and see what sticks.”

04:19–04:54 — Closing Remarks

• Ends the fireside chat.
• Encourages feedback and engagement.
• Reaffirms M365/SharePoint as the host’s specialty: “My huckleberry is SharePoint and the M365 stack.”
• Directs listeners to levelupm365.com.

Follow

• Apple Podcasts – https://podcasts.apple.com/us/podcast/level-up-m365/id1718776415
• Spotify – https://podcasters.spotify.com/pod/show/levelupm365/
• Newsletter/Socials – https://levelupm365.com/subscribe-social-page/

If this post was helpful support the effort by ether of the following, share, like, subscribe, leave a tip!