Case Study 04 • Business Acumen & Cost Avoidance

Enterprise SharePoint News Distribution System

Architecting an internal hub-and-spoke news ecosystem across SharePoint, Teams, and Outlook—securing executive buy-in to replace an external third-party vendor contract using existing enterprise tools.

Organization
Johns Hopkins Medicine
Leadership Scope
Platform Strategy, Architecture & Executive Pitch
Ecosystem Stack
SharePoint, Microsoft Teams, Outlook & OneDrive
Key Outcomes
Eliminated 3rd-Party Vendor Dependency • Executive Sign-Off

01 / Business Context & Identifying the Opportunity

Johns Hopkins Medicine was paying for a third-party software tool to distribute internal news across the enterprise. While internal communications teams needed reliable ways to publish updates across departments and reach employees where they already worked, maintaining a separate external vendor tool introduced unnecessary recurring licensing costs and workflow friction.

Recognizing that the organization already licensed the full Microsoft 365 suite, I initiated an architectural investigation to determine whether we could deliver a superior, native news distribution experience—and eliminate the third-party contract upon expiration.

02 / Technical Architecture & Stakeholder Alignment

To win executive approval, a slide deck wasn't enough—leadership needed proof that native tools could handle complex enterprise routing without creating administrative chaos:

PLATFORM MASTERY

Deep Microsoft 365 Feature Extension

I audited SharePoint News capabilities alongside OneDrive, Outlook, and Teams—designing tenant-wide metadata and content tagging types so articles could be categorized and routed dynamically across the organization.

WORKING PROOF OF CONCEPT

Live Hub-and-Spoke Test Environment

Instead of pitching abstract diagrams, I built live functional test sites—connecting central hub sites with departmental spoke sites to demonstrate bi-directional news syndication in real time.

EXECUTIVE BUY-IN & ROLLOUT

Migration & Launch Governance

I presented the working proof of concept to key stakeholders and executives, secured formal buy-in, and authored the migration and launch roadmap timed to the third-party vendor's contract expiration.

03 / System Architecture: Hub-and-Spoke Distribution Flow

Select each layer of the architecture below to see how news flows from creation to multi-channel employee delivery without third-party software.

Interactive Ecosystem Map • Native Microsoft 365 Architecture

Structured Tenant-Wide Metadata

Communicators author news directly inside familiar SharePoint templates backed by custom tenant-wide data types. Standardized tags classify each story by entity, department, audience, and priority at the moment of creation.

Benefit: Eliminates manual cross-posting and ensures consistent taxonomy across hundreds of internal contributors.

Bi-Directional Hub-and-Spoke Routing

Using SharePoint Hub architecture, enterprise-wide announcements flow outward from central Hub sites to connected departmental Spoke sites, while relevant local updates roll upward to enterprise feeds based on metadata rules.

Benefit: Employees see news tailored to their department and role without manual curation by site owners.

Meeting Employees Where They Work

Rather than forcing staff to remember to visit an intranet portal, news items integrate natively into Microsoft Teams channels and automated Outlook digests—reaching clinical and administrative staff inside their daily communication tools.

Benefit: Higher visibility and zero third-party licensing overhead.

04 / Business Impact & Leadership Takeaway

  • Direct Cost Avoidance: Designed a complete native replacement scheduled to retire an external third-party vendor tool at contract expiration.
  • Proof-First Executive Alignment: Built a live working hub-and-spoke prototype that resolved stakeholder skepticism and earned leadership sign-off.
  • Pragmatic UX Program Leadership: Demonstrated that strategic UX leaders evaluate total cost of ownership and existing enterprise capabilities before recommending new software.