00The need
Some processes hold up the operation and never got a system of their own: they live in shared spreadsheets, in emails and in the judgment of a few people. They work as long as those people are around and the volume is small.
Sounds familiar if…
- The process lives in spreadsheets and emails
- Each person keeps their own version
- To know where a case stands, you have to ask
01The problem
The real operation lives in spreadsheets, emails and the judgment of a few people.
With the Solution- Where it livesIn spreadsheets, emails and paper
- VersionsOne per person
- Where it standsYou have to ask
- Notifications and approvalsBy email, when someone remembers
- Where it livesIn an app, with its steps
- VersionsA single one, for everyone
- Where it standsYou see it in the system
- Notifications and approvalsSent automatically, at every step
Key idea
If the process depends on specific people, it stops when they're out.
02The architecture
First the process is mapped as it's actually done, and the app comes after. On Power Platform, within Microsoft 365, three pieces.
- Power Apps
The app
Where each case is worked on, with its steps and its permissions.
DataverseThe data, in a single place
In Dataverse or in SharePoint, depending on the case.
Power AutomateNotifications and approvals
Each step notifies whoever is next and requests whatever approval is needed.
Key idea
The app adapts to the process, not the process to the app.
03The result
And since it lives within Microsoft 365, governance, permissions and lifecycle are already handled in your own environment.
The process no longer depends on who remembers what: every step is logged.
What you get
- The process, mappedAs it's actually done, with what's unnecessary flagged.
- An app in Power AppsWhere each case is worked on, with its steps and its permissions.
- The data in a single placeIn Dataverse or in SharePoint, within your Microsoft 365.
- Notifications and approvalsEach step notifies whoever is next and requests whatever approval is needed.
04How to engage
The same app, in the model that suits you: with your team, in your environment or in ours.
We adapt it to your case and put it into productionWho runs itWhere it lives- By your teamYour teamYour environment
- In your environmentdleverYour environment
- In our environmentdleverOur environment
Key idea
The architecture is the same, and you decide who runs it.