The HUB Intranet

A company was using a folder structure on an old SharePoint infrastructure to provide company wide documents for multiple departments. As part of the MARCOM team, I developed a new web-based experience that utilized the SharePoint infrastructure but included custom SPFx webparts and embedded Power App solutions. The project also included branding and internal communication and promotional design.
Intranet Design
Power App Development
The HUB Intranet
No items found.

The Problem

  • A company's legacy SharePoint intranet lacked governance, scalability, and a user-centered information architecture. Fragmented document organization made critical resources difficult to find, slowing onboarding and day-to-day operations.
  • Inconsistent content management created duplicate files, outdated information, and low employee adoption. Departments lacked standardized ownership of content, resulting in knowledge silos and inefficient collaboration. Outdated processes exposed sensitive employee information, creating security, privacy, and compliance risks. The organization needed a modern, secure, and scalable digital workplace to improve usability, governance, and long-term growth.
  • The company’s intranet environment required a comprehensive transformation to align with modern operational standards, support organizational growth, and mitigate increasing data and security risks. The existing SharePoint-based system, while widely adopted, had evolved without governance or strategic structure, resulting in significant usability, security, and scalability challenges.

    The Answer

    Designed and implemented a centralized, modern intranet—The Hub—to replace a fragmented SharePoint environment with a scalable, secure, and user-focused digital workplace.

    Built using Power Apps, SharePoint (Online), SPFx, and Power Automate, the solution delivers a single access point for company resources, workflows, and communication across all departments. Employees can submit and track documents, access policies and benefits, stay informed on company updates, and engage with internal initiatives—all within a streamlined, intuitive interface.

    The architecture consists of 4 Canvas Apps, 10 custom SPFx web parts, and 7 connected SharePoint sites, with lists and libraries serving as the core data layer to ensure maintainability by non-technical teams. Custom admin panels and embedded guidance enable decentralized content ownership while preserving consistency and governance.

    A security-first model using Microsoft Entra ID groups ensures sensitive data is restricted to appropriate audiences, eliminating prior exposure risks and improving compliance posture.

    Key design decisions prioritized adoption and flexibility, leveraging SharePoint familiarity over Dataverse complexity, and Canvas Apps over model-driven apps to enable advanced UI/UX and custom logic.

    The Hub was delivered as a Minimum Viable Product (MVP) under an accelerated timeline. Iterative improvement spirals were implemented post-launch to refine functionality based on real user behavior.

    Result: Transformed the intranet into a trusted, actively used platform that improves operational efficiency, reduces risk, and scales with organizational growth.

    Key Contributions

    • Wireframing
    • SharePoint UI design
    • PowerApps development and design
    • Power Automate flow creation
    • Testing and Development
    • Admin Subsite design
    • Stakeholder engagement
    • QA/QC Feedback revisions
    • Launch design and marketing

    The HUB Intranet also included creation of dedicated spaces for 7  corporate departments, allowing teams to manage their department-specific documents, trainings, and resources while  connecting to the HUB’s main interface for general employee visibility. To ensure department administrative teams had comprehensive documentation on how their new sites function, I also crafted comprehensive sub-sites for each department, including write-ups and step-by-step instructions to ensure processes are clearly and universally followed.

    Decisions & Tradeoffs

    • Why SharePoint vs Dataverse: Each major corporate department team would takeover maintenance for their connected SharePoint site content and backend. All teams were familiar with the SharePoint structure so it became the most natural data source for the core interface.
    • Why Canvas vs Model-driven Apps:  Canvas apps allowed the most flexibility in filters, search capabilities, and UI design. It also allowed me the freedom to include custom download and viewing logic that automatically used the type of file to determine what functions should be allowed.
    • Logic and Automation: The majority of the logic lives within each of the 4 apps, 10 SPFx webparts, with minimal Automate Flows used to send team notifications when SharePoint items or files are changed, updated, or deleted.
    • Development Scope: Development was focused on creating a Minimum Viable Product using basic SharePoint structure, however there are future spirals intended to improve useablity post launch.
    • Testing and Iterative Improvements: The functions of the full system were directly impacted by department team leads, and due to the aggressive timeline there was no beta test period. We did complete a brief QA/QC prior to launch, but function and UI revisions were slated for development during the live launch period. This is currently ongoing based on user feedback and corporate needs.