PEOPLE / KNOWLEDGE / MOMENTUM

Community

A lot of the public trail exists because I learned in communities and then tried to return the favour.

Microsoft MVP & SUGUK

THE USEFUL BIT

Community was never an audience. It was a feedback loop.

Talk about the problem. Show the thing. Have somebody tell you where it breaks. Improve it. Repeat.

Community engineering

2018 · Microsoft PnP

SharePoint development SIG

A Flow demo on Microsoft’s SharePoint Patterns & Practices development call, alongside engineering updates and community discussion.

2018 · Microsoft Flow Conference

PowerApps and Flow — Better Together

A session in Microsoft’s online Flow Conference programme on using Flow as middleware for PowerApps.

2019 onward · Collab365

Virtual summits and workshops

Recorded sessions across Teams, Power Apps, Power Automate and Microsoft 365, plus longer workshops built around real solutions rather than feature tours.

The Isolation Conversation

Teaching by building

Collab365 workshop · 4.5 hours

Employee Directory with Power Platform

A practical employee-directory build using Power Apps and Dataverse. The surviving course page includes feedback specifically about going beyond the obvious “simple” version and exploring more of what the platform could do.

Collab365 workshop · 5 hours

Change Management with Microsoft 365 & Power Platform

A longer-form solution build using SharePoint, Power Apps and Power Automate: data modelling, security choices, approvals, notifications and application UI. Less “here is a connector” and more “here is how the pieces become a system.”

The best technical communities are not audiences. They are distributed debugging sessions with better coffee.