Current-state workshop
Understand what employees, managers and administrators actually do, where rules live, which approvals matter and what support teams need to maintain.
← Delivery roadmap · Healthcare & public sector
A staged Power Platform modernisation roadmap.
Ultron prepared four connected workstreams: discover and redesign an existing Power App, shape an executive Power BI report, define a Recognition App and provide ongoing Power Platform support capacity.
Proposal-stage evidenceDiscovery firstExecutive Power BIRecognition AppSupport plan
WORKSTREAMSDiscoveryApp refreshExecutive reportRecognition AppSupport
PROPOSED DELIVERY MODELDecision gates
Roadmap evidence01DiscoverCurrent usage, roles and rules
02DesignFuture state and implementation plan
03ApproveScope, access and workflow gate
04ImplementIf authorised by CAHS
Evidence→Decision→Delivery
Proposal stageScope and delivery thinking, not proof of adoption.
Four streamsApp, reporting, recognition and support are separated.
Discovery firstUsage, roles, rules and inputs are mapped before build.
Decision gatesEach stream has a clear approval boundary.
Why discovery comes first
Do not redesign an inherited app from screenshots alone.
The proposed first step maps actual usage, business rules, inputs and outputs, approvals, user roles, pain points and the current support model before a build commitment is made.
Decision-ready design
Produce a proposed interface, data model, rule set, process change list and implementation plan. A build phase proceeds only after CAHS reviews that design.
Four independently governed workstreams
Each stream has its own scope and decision gate.
The proposal keeps a potentially broad program legible: CAHS can approve, sequence and govern each workstream independently.
| Workstream | Proposed scope | Decision gate |
|---|---|---|
| Existing app refresh | Discovery, redesigned navigation and screens, data/rule review, then an optional implementation phase. | Approve the design and implementation plan before build. |
| Executive Power BI | KPI workshop, source review, data model, Power Query, executive layout, filters, drill-through, validation and handover. | Confirm KPI definitions, source ownership and access model. |
| Recognition App | Submission, review and approval, notifications, administration, basic reporting/export, deployment and handover. | Approve the recognition workflow, roles and notification rules. |
| Support capacity | Small Power Apps enhancements, Power Automate troubleshooting, minor Power BI updates, governance advice and monthly summaries. | Agree prioritisation, escalation and service boundaries. |
A transparent evidence boundary
This is a roadmap, not a completed-outcome claim.
The available source set consists of proposals. It establishes a credible scope and delivery approach, but does not prove implementation, production deployment, adoption or business results.
What is evidenced
Workshops, solution design, Power Apps refresh, reporting build, Recognition App scope, support activities and handover steps.
What remains open
Client approval, build execution, access decisions, deployment, acceptance testing and measurement of outcomes.
Why this is useful
A well-shaped discovery phase reduces the risk of building the wrong workflow or reporting model for a sensitive operating environment.
No completed-outcome claim: this page is intentionally presented as a delivery roadmap because the source set does not prove implementation, production deployment, adoption or business results.
Plan the right first phase
Have an inherited Power Platform workflow to modernise?
Share the current app, user groups, rules and support constraints. We can help turn a broad request into a sequenced, decision-ready delivery plan.
Plan a similar roadmap
Tell us what needs discovery before anyone starts building.