Purpose, context, and required information presented in one structured view.
Kaiser Permanente · Enterprise UX · SharePoint & Power Platform
Making internal business work clearer and more manageable.
A privacy-safe case study about designing SharePoint Online experiences, Power Apps, and Power Automate workflows around practical business needs—while respecting enterprise constraints and confidentiality.
- Submitted
- Review
- Action
- Follow-up
Representative portfolio visualization — not an actual Kaiser Permanente interface.
01 · Project overview
Enterprise UX shaped around internal business workflows.
My work supported internal experiences built with Microsoft 365 and the Power Platform. The goal was to translate business requirements into clearer tools for communication, collaboration, requests, data capture, and workflow support.
02 · My role
Connecting stakeholder needs with practical digital solutions.
The work focused on translating stakeholder needs into clearer internal experiences—reducing ambiguity around requests, improving visibility into status and next actions, and shaping practical solutions within enterprise platform constraints. SharePoint Online, Power Apps, and Power Automate provided implementation context rather than defining the experience.
03 · Business challenge
Internal work can become fragmented as processes grow.
At a high level, the design challenge was to make business activities easier to understand and complete when information, requests, decisions, and follow-up could otherwise require multiple disconnected steps.
04 · Design principles
Design principles.
Reduce unnecessary friction and make dense internal work easier to understand.
Help people understand status, ownership, and what needs to happen next.
Structure experiences around tasks and handoffs rather than organizational structure or platform limitations.
Balance usability with governance, permissions, compliance, and existing systems.
05 · How I approached the solution
Start with the work, then choose the right platform pattern.
Clarify requirements
Understand the business need, participants, information required, decisions, and expected handoffs.
Structure the experience
Organize content, forms, actions, and status information around the user’s task rather than the underlying technology.
Support the workflow
Use appropriate SharePoint, Power Apps, and Power Automate capabilities to reduce avoidable repetition and make next steps visible.
Prepare people to use it
Support adoption with clear documentation, stakeholder communication, and training.
06 · Enterprise UX and workflow thinking
Turn a sequence of tasks into a visible process.
Representative portfolio visualization — not an actual Kaiser Permanente interface.
07 · Power Platform and SharePoint contribution
A connected toolkit, applied selectively.
Representative portfolio visualization — not an actual Kaiser Permanente interface.
08 · Collaboration and adoption support
Enterprise design includes the conversations around the interface.
I worked with stakeholders to understand requirements, clarify constraints, review proposed solutions, and support delivery. Documentation and training helped make the resulting experiences understandable beyond the design and build process.
09 · Qualitative outcome
What the work improved.
- Clearer structure around internal requests and handoffs
- Better visibility into status, ownership, and next actions
- More consistent interaction patterns across related workflows
- Stronger alignment between business needs and platform capabilities
- Clearer documentation and adoption support
10 · Confidentiality note
Details are intentionally limited.
This work is confidential. Visuals shown are generalized portfolio representations and do not reproduce Kaiser Permanente internal systems, data, or proprietary interfaces.
11 · Key takeaway
Good enterprise UX respects both people and constraints.
The strongest enterprise experiences are not necessarily the most visually elaborate. They make complicated work easier to understand while respecting governance, permissions, platform limitations, and organizational reality.