The Situation

When a new employee joined this mid-size organization, getting them fully operational was a multi-week ordeal. There was no centralized system for provisioning. Managers and coworkers had to manually walk new hires through finding every application they needed, requesting the right security access through the company's identity management platform, and tracking down the right equipment. Approvals trickled through email chains with no visibility. It wasn't unusual for a new employee to spend their first two weeks still waiting for the tools they needed to do their job.

The process wasn't just slow — it was inconsistent. What a new hire received depended entirely on who happened to help them, which meant gaps in access, duplicate requests, and frustrated teams.

The Approach

Before writing a single line of code, the entire onboarding workflow was mapped — every handoff, every approval chain, every dependency. The core insight emerged quickly: managers already knew what their new hire needed because they had existing employees in the same role. The system just didn't let them leverage that knowledge.

The Solution

A custom Power Platform application that fundamentally reimagined the onboarding workflow:

• Managers select an existing team member to "model after" — the system surfaces that employee's current equipment, software, and security access as a starting point
• The manager reviews and curates the list — selecting, removing, or adjusting items based on the new hire's actual role requirements. No access is granted by default; every item is an intentional choice
• Security access requests route through the organization's existing approval chains — nothing bypasses the governance process
• Key stakeholders receive rich adaptive cards in Microsoft Teams — with request details and direct links to take action in the appropriate systems. Teams notifications keep everyone in the loop without pulling them out of their workflow, while all security provisioning remains handled through the organization's identity management platform
• Once approved, the system integrates with Microsoft Intune to assign the correct software profile to the new hire's device. When they power on their machine for the first time, everything they need is already pushing to install
• IT receives a complete, structured provisioning package instead of scattered ad-hoc requests
• Real-time status tracking replaces "did you get that email?" follow-ups

The Impact

• Onboarding time reduced from weeks to days
• Standardized provisioning eliminated gaps in access and duplicate requests
• Managers gained a self-service tool that removed their dependency on institutional knowledge or tribal help
• IT shifted from reactive ticket-chasing to proactive, structured provisioning
• New employees reached full productivity dramatically faster
• Device readiness from day one — Intune pushed required software automatically before the employee ever logged in, eliminating the "first week of setup" entirely
• Security governance maintained throughout — every access grant was an intentional, manager-reviewed decision routed through the organization's existing approval process

The Situation

This organization's change order process was functional but fragmented. Requests came in through inconsistent channels — emails, phone calls, hallway conversations. The information captured varied wildly, and once a change order was submitted, there was no structured data to analyze. Leadership had no visibility into change order volume, patterns, root causes, or costs. They were making procurement decisions without the data to back them up.

The process worked, technically. But it generated zero insight.

The Approach

The goal was never to make change orders faster for the sake of speed. It was to bring structure to a process that had none — and to turn every change order into a data point that could inform smarter decisions. That meant designing an intake process that asked the right questions without creating unnecessary friction.

The Solution

A centralized change order application that replaced scattered intake channels with a single, structured workflow:

• All change orders flow through one system with standardized intake fields
• Strategic questions are embedded in the submission process — capturing the "why" behind every change, not just the "what"
• Once a buyer reviews and approves the change order, the official vendor form is auto-populated and generated — eliminating manual re-entry and ensuring accuracy
• Stakeholders receive actionable adaptive cards in Microsoft Teams — with change order summaries, direct links, and embedded approval buttons. Approving within Teams triggers downstream workflows automatically, from generating vendor documentation to updating procurement dashboards
• The structured data feeds into reporting dashboards that surface trends, patterns, and cost insights leadership never had access to before

The Impact

This is a case study about value, not speed. The change order submission process for the requester is slightly more involved than before — the structured questions take a moment longer than firing off an email. But the downstream efficiency gains (auto-populated vendor forms, elimination of manual re-entry, fewer errors) balance that out. Net time impact: roughly neutral.

The real win is what the organization gained that it never had before:

• Complete visibility into change order volume and trends
• Root cause data that surfaces why changes happen — not just that they happened
• Cost pattern analysis for smarter procurement decisions
• A single source of truth that eliminated conflicting records across channels
• Structured data that turns a reactive process into a strategic one

The Situation

When a driver's vehicle reached end-of-life, replacing it meant navigating a slow, manual process. Drivers had to contact the fleet team directly to find out what options were available, wait for responses, and go back and forth on configurations. The fleet team, meanwhile, was fielding the same questions repeatedly — what's available, what's eligible, what needs manager sign-off.

There was no centralized place for drivers to see their options, no structured workflow for approvals, and no easy way for the fleet team to control what was being offered at any given time. The process worked, but it didn't scale — and it pulled the fleet team into operational conversations that could have been self-service.

The Approach

The core challenge wasn't just building an ordering tool — it was designing two different experiences for two different audiences within the same system. Drivers needed simplicity: browse, select, submit. The fleet team needed control: manage available options, update configurations, and maintain full visibility into the replacement pipeline. That meant a dual-app architecture — purpose-built interfaces sharing a single source of truth.

The Solution

A dual-application ecosystem built on the Power Platform, each app tailored to its audience:

• Drivers log into a Canvas App to browse available replacement vehicles, select their configuration, and submit their order — self-service from start to finish
• The fleet management team operates a Model-Driven App to maintain and update all available vehicle options, configurations, and eligibility rules — giving them full administrative control without touching the driver-facing experience
• Both apps share a unified Dataverse backend, ensuring every change the fleet team makes is immediately reflected in what drivers see
• Teams notifications proactively alert drivers when it's time to initiate their vehicle replacement — no one has to chase them down
• Manager approvals are handled through Teams, keeping the process moving without requiring anyone to log into a separate system
• The full replacement pipeline is visible at every stage — from initial request through approval to fulfillment

The Impact

• Self-service ordering eliminated the back-and-forth between drivers and the fleet team entirely
• The fleet team shifted from answering repetitive questions to managing strategy — controlling what's offered, not fielding requests
• Proactive Teams notifications ensured drivers initiated replacements on schedule without manual follow-up
• Manager approvals stayed inside Teams, reducing friction and keeping cycle times short
• A single Dataverse backend guaranteed consistency — what the fleet team configured is exactly what drivers saw
• Full pipeline visibility gave leadership real-time insight into replacement volume, timing, and status