KhamsayPhimmasanh-Baig

Sixteen forms, three platform generations

Every production form and workflow on the intranet is one I built: thirteen in Power Apps with Power Automate approval flows, three in Microsoft Forms. They cover operations, safety and HR — the paper-and-email processes a manufacturing site actually runs on.

The one I’d point at replaced a paper form. First working draft in three days, live in under a week, and the paper never came back.

Then I moved all of it, twice more. 2010 to 2016 on my own with ShareGate. 2016 to 2019 with corporate IT. 2019 to SharePoint Online with SPMT. InfoPath and SharePoint Designer were end-of-life, so none of it was a content move. I inventoried every form, worked out which would survive and which had to be rebuilt, and mapped what depended on what before anything shifted.

Enterprise AI adoption

Appointed to lead AI adoption for the North American site — the approved tools, the acceptable-use attestation, and the enablement that has to sit around both.

I built the mechanism that records policy acknowledgment and training completion, so the business holds evidence rather than an assumption.

I’m the internal point of contact for people who want to get further with these tools. When someone asks, I sit with them one-to-one on prompting. The weekly tips go to a Teams channel either way.

The same problem, two employers ago

At LIN Media I built the SharePoint intranet — InfoPath forms and Nintex approval workflows for Legal, Finance, HR and Tax. Regulated departments, real approval chains, and permissions that had to hold up.

That was 2008. The platform has changed completely since and the problem hasn’t: someone has to sit between the department that needs a process and the system that has to run it. That’s the job I’ve been doing ever since.