In my sector, we manage a limited pool of software licenses, and historically the process for checking whether people still needed their license was messy, inconsistent, and very manual. My team gets pinged constantly for updates, use‑case info, and “who still needs what,” and there was no centralized place for any of it. So I built a system that solves all of that — and it ended up being a lot more instructional‑design‑aligned than I expected. I created a dedicated SharePoin

Driven by a massive cloud migration strategy, I designed and developed a data dashboard to track the adoption of a cutting-edge InfoPath-to-Power Apps conversion tool. By monitoring software license utilization and user engagement, this dashboard turned a complex SharePoint modernization effort into a measurable and visible success.

This project explores how a modern learning landing page can be designed using a combination of SharePoint’s flexible layout capabilities and custom visual systems created in Figma.

Standard navigation in Power Apps often requires repetitive work across screens, which is hard to maintain. I wanted to build a solution for my team that was functional but also visually aligned with our brand. My goal was to create a reusable left navigation component that simplifies development while providing a positive user experience. To keep the app "light," I used Named Formulas at the app level, under Formulas. This allows me to define the navigation table once—storin

Microsoft 365 provides various ways to build forms, ranging from simple tools to advanced development platforms.

Overview The team manages 50–100 specialized technical tools used across multiple teams. Each tool repair request requires a four step approval process, and requests often remain active for several years before approvals are complete. The legacy system was built on InfoPath from with 5 form views, SharePoint 2010 impersonation workflow and 2013 workflows. Item level permission breaking, creating a fragile environment that was difficult to maintain. The Form for the Process at

The Challenge: High-Risk Interaction Users frequently interacted with critical "fatal choice" buttons without a safety net. Meaning, they would reject or approve in one click. The best practice for these fatal choice buttons is to confirm with the user that the click wasn't an accident. Accidental clicks led to submissions with incorrect data or not ready for approval / rejection, causing data errors and broken business processes. The Solution: Dynamic Modal Component I devel

This project showcases the redesign SharePoint list form using JSON formatting. The work demonstrates UX design, process analysis, and Microsoft 365 solution building. The Problem The original SharePoint form had several issues that impacted daily operations: Important information was buried or unclear The form lacked visual hierarchy Users found the form confusing and time‑consuming This resulted in: inconsistent submissions frustration from both users and approvers To fix

Overview The company's legacy training request process relied on outdated InfoPath Forms, 2010 Impersonation Workflow steps, and 2013 custom workflows. With Microsoft retiring InfoPath, 2010 Workflows, and 2013 custom workflows with SharePoint Designer, the team needed a modern, automated solution to reduced administrative work. The Problem The existing process had several challenges: Requests submitted through outdated forms and emails No centralized tracking or visibility i