When building approval workflows in Power Automate, one of the most common challenges is preventing recursive execution. A flow updates a SharePoint item, the update retriggers the flow, the flow updates the item again, and before long a simple approval process becomes difficult to manage and troubleshoot. While building a multi-stage / multi-year approval process, I encountered this exact challenge. The solution was to separate business status from workflow state by implemen

You talk to the stakeholders, gather the requirements, and dive straight into the fun part: building. For me, the goal is always clear—make the process as human-free as possible, to reduce errors. I build systems that think, route, and automate so people can stop doing robot work and focus on human thinking. But once the main automation engine is working, you hit a different wall. You enter the "Admin Phase." Personally, I love this part of the project, where you get to make

Right now, communication across teams is kind of all over the place. People send announcements through email, Teams chats, random documents, or not at all. SharePoint News exists — and it’s a great tool — but most users either don’t know it’s there or don’t understand how it fits into their day‑to‑day communication. We’re also heading into the 11/5 SharePoint upgrade, and this is the perfect moment to tighten up how we communicate and give people a simple, repeatable way to s

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

Overview A user‑friendly toolkit designed to guide teams through the transition from legacy SharePoint and InfoPath experiences to modern SharePoint Online and Power Apps. This toolkit brings clarity to modernization by combining UX guidance, technical pathways, and practical resources. It reflects my approach to simplifying complexity, enabling users, and designing systems that support long‑term adoption. The Problem Many teams were still relying on legacy SharePoint feature

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

Power Apps are a fun and easy way to create forms quickly, but sometimes you need to add extra code for functionality that will improve the user experience. This demonstration shows how to add a pop-up screen based off of the user canceling edits to a form and if they have unsaved data. This same concept could be used for deleting items as well, by asking the user if they are sure they want to delete an item. Pre-requisites - Have an edit form on your app connected to a data

As a part of UX Design course I am tasked to redesign a fitness schedule application. The goal was to make the product more actionable based on what would be most important to the user. Below are the screenshots of the before and after. The original layout is on the left, with the re-design layout on the right. The original design was an endless scroll of classes forcing users who wanted to see Fridays classes to scroll to the bottom. Or if they were searching for a specific

Overview The goal of this design document is to outline the creation of a training program that will teach users a basic introduction SharePoint Online (SPO). Target Audience The target audience for this training program is SharePoint Online site owners, members, and contributors. Learning Objectives Upon completion of this training program, users will be able to: Understand the basic concepts and terminology of SharePoint Online Terms covered Lists, Libraries, and Web Parts