Photo credit: Gemini
Show Notes with Timestamps
00:03 — Welcome & Episode Setup
Joe opens Episode 19 of the Level Up M365 Podcast. This episode is a fireside chat focused on a broader philosophy rather than strictly Microsoft 365.
00:12 — Episode Theme: Mitigating Software Development Risk
Introduction of the central topic: how to reduce risk in software development through mindset and approach.
00:20 — A Break from the Usual M365 Focus
Joe explains that while the show typically covers Microsoft 365, this episode explores a general philosophy that still connects back to M365.
00:25–00:39 — What a Fireside Chat Means
A fireside chat is conceptual and philosophical. Tools may be mentioned, but the emphasis is on mindset.
00:39–00:50 — How This Relates to M365
Listeners who only want M365 content can skip, but the philosophy ties back to M365 development and governance.
Core Philosophy
00:53–01:26 — Joe’s Background & Context
Joe shares his journey from front‑end JavaScript developer to low‑code practitioner. Skills may be rusty, but the principles remain.
01:26–01:53 — The One‑Sentence Philosophy
Time to business value faster — the key to mitigating risk.
Deliver something quickly, gather feedback, and reduce wasted investment.
02:05–02:32 — Why Speed Matters
Fast delivery enables:
- Early feedback
- Early gratification
- Reduced cost of wrong assumptions
- Lower risk exposure
02:32–03:29 — Why SharePoint & Power Apps Fit This Model
Joe’s “SharePoint‑first mindset”:
- Everyone already has it
- Easy to spin up lists
- Easy to build Power Apps
- Rapid delivery of ticketing, scheduling, surveys, notifications, approvals, e‑signatures
- Not meant to be enterprise‑grade at first—just “good enough”
03:29–03:49 — Good Enough vs. Perfect
Most clients don’t need a Ferrari; they need a reliable Camry that solves the problem quickly.
03:49–04:29 — The Cost of Slow Development
Anecdote: a multimillion‑dollar BlackBerry app that launched after everyone moved to iPhone.
Lesson: long cycles increase risk because requirements and technology shift.
04:29–04:40 — The Origin of “Fail Fast”
Build → Learn → Adjust → Repeat.
Pitfalls & Cautions
04:53–05:42 — Pitfall 1: Governance Gaps
Rapid builds may lack:
- Proper permissions
- Retention policies
- Taxonomy
- Cross‑platform compatibility
05:42–06:10 — Pitfall 2: Prototype Stagnation
COVID example: rough teleconferencing apps that never got improved.
Lesson: early versions must evolve.
06:10–06:32 — Product Ownership Matters
A product owner should guide vision, prioritize enhancements, and ensure continuous iteration.
06:32–07:15 — Show Progress Early & Honestly
Even small progress should be shown to stakeholders.
Honesty beats polished but misleading wireframes.
Additional Insights
07:15–07:37 — Honest Ugly Demos vs. Fake Pretty Demos
A rough but real prototype earns more respect than a beautiful mockup that fails in production.
07:37–07:55 — Invitation for Feedback
Joe invites listeners to share their own approaches to mitigating development risk.
Technical Analogy
08:00–09:22 — WebAssembly as a Cautionary Tale
WebAssembly promised native performance in the browser, but:
- Too complex
- High barrier to entry
- Developers preferred simpler frameworks
Lesson: power is irrelevant if the path to value is too hard.
Closing
09:33–09:46 — Wrap‑Up & Call to Action
Joe closes the fireside chat, encourages likes/subscribes/shares, and reminds listeners about the tip jar.
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!
Level Up M365 