Stale KPIs stalled strategy — SharePoint hub with Snowflake & Power BI unifies plans

Overview

A distributed tech firm’s strategy communication was fragmented. Priorities, milestones, and KPIs lived in separate decks and chats, and teams heard conflicting messages about what mattered and when. Intelligex launched a leadership portal on SharePoint that centralized strategy narratives, decisions, and meeting notes, surfaced live KPI tiles sourced from Snowflake via embedded Power BI, and enabled permissions-aware search across strategy artifacts. A light publishing workflow captured reviews before updates went live. Leaders and teams gained consistent visibility, fewer mixed signals, and faster alignment around plans and timelines.

Client Profile

• Industry: Software and technology (product-led, distributed workforce)
• Company size (range): Multi-region enterprise with engineering, go-to-market, and shared services
• Stage: Scaling product portfolio and operating rhythm across business units
• Department owner: Strategy, Analytics & Executive Leadership (Corporate Strategy / Strategy Operations)
• Other stakeholders: Product & Engineering, Sales & Marketing, Finance/FP&A, People/Communications, IT/M365 Administration, Data & Analytics, Security & Compliance

The Challenge

Strategy artifacts were dispersed: roadmap decks in various SharePoint libraries, KPI snapshots exported from BI tools, and meeting notes stored in personal sites or Teams channels. Updates were distributed through email and chat, and different groups used local versions of key documents. When initiatives shifted, it was unclear which narrative was current, whose metrics were authoritative, and what changed since the last alignment session. Leaders spent time reconciling messages and timelines rather than guiding execution.

Tooling existed but lacked orchestration. SharePoint hosted sites and libraries, Power BI powered KPI views, and teams used Snowflake as the analytics hub. However, there was no common hub that combined narrative, live metrics, action items, and a search that respected permissions across spaces. Publishing relied on manual updates and screenshots, and there was no approval step before updates reached broad audiences. The ask: keep the existing stack and add a structured, easy-to-find leadership portal with live KPIs, governed publishing, and a search that found the right document the first time.

Why It Was Happening

Content and identities were fragmented. Strategy documents were stored in different sites with inconsistent metadata and naming, KPI tiles were exported into slides with stale timestamps, and meeting notes lived in personal or team-specific containers. Search surfaced multiple versions of similarly named artifacts without clarity on which was current. Permissions were set at the site or folder level, so users either saw too much or too little, and authors duplicated content to reach the right audiences.

Governance arrived late. Updates went straight from draft to distribution. There were no required tags for initiative, owner, or refresh window, and no approval step to check narrative consistency and data recency. As a result, leadership communications drifted, and teams followed different interpretations of priorities and timelines.

The Solution

We implemented a SharePoint-based leadership portal that centralized strategy narratives, meeting notes, and decision logs; embedded live KPI tiles from Snowflake via Power BI web parts; and enabled a permissions-aware search that respected existing entitlements. Managed metadata and content types standardized tags for initiative, owner, horizon, and refresh cadence. A lightweight publishing flow routed updates for review to Strategy Ops and Communications before going live. Nothing was replatformed: Snowflake remained the data platform, Power BI remained the visualization layer, Teams and SharePoint remained collaboration tools. The new layer orchestrated navigation, search, live KPIs, and governed publishing.

• SharePoint hub site with standardized libraries, content types, and managed metadata for initiatives, owners, and time horizons (SharePoint Managed Metadata)
• Live KPI tiles embedded with the Power BI web part, sourcing certified datasets connected to Snowflake (Power BI web part for SharePoint, Power BI connector for Snowflake)
• Permissions-aware search configured with verticals, bookmarks, and result types aligned to strategy content (Microsoft Search)
• Publishing workflow for page updates and KPI changes using approvals with comments and rationale (Power Automate Approvals)
• Role-based access via Microsoft Entra ID groups to scope leadership, manager, and all-hands views (Microsoft Entra groups)
• Decision and meeting notes templates with required fields for owner, date, next steps, and links to KPIs and artifacts
• Definitions catalog and data lineage links from KPI tiles to certified datasets and model documentation in Snowflake
• Microsoft 365 audit logging for page changes, approvals, and access to sensitive sections (Microsoft 365 audit)
• Homepage tiles for current priorities, upcoming milestones, and recent decisions, with drill-through to detail
• Human-in-the-loop review step for sensitive communications and initiative status changes before publication

Implementation

• Discovery: Mapped the existing constellation of strategy sites, Power BI reports, and Snowflake certified datasets. Collected representative strategy decks, roadmaps, and note formats. Identified identity groups for leadership, managers, and working teams. Reviewed recent misalignments to surface the causes: stale KPIs, duplicated pages, and missing owners.
• Design: Defined the hub information architecture and navigation, content types and required metadata, and the publishing workflow and approval roles. Scoped KPI tiles and data sources, aligned to certified datasets and refresh windows. Configured search verticals and bookmarks for initiatives, decisions, and KPIs. Documented roles and permissions by audience.
• Build: Stood up the SharePoint hub, libraries, and managed metadata; embedded Power BI tiles pointing to Snowflake-backed datasets; configured Microsoft Search verticals and result types; implemented the approval flow with comments and change logs; and connected KPI tiles to definition and lineage pages. Created templates for meeting notes and decision records.
• Testing and QA: Piloted with a subset of initiatives. Verified KPI refresh timing and filter behavior, validated metadata and required fields, and ran search tests to ensure the current version surfaced first. Dry-ran approval paths with Strategy Ops and Communications. Confirmed role-based access and audit logging across leadership and all-hands sections.
• Rollout: Launched in read-only mode while legacy links and decks remained available. After stakeholders validated navigation, KPIs, and search behavior, enabled the publishing workflow and set the portal as the authoritative entry point for strategy updates. Redirected legacy links and consolidated duplicate pages.
• Training and hand-off: Delivered quick guides for content owners on page templates, metadata, and approvals; for executives on reading KPI tiles and finding decisions; and for data teams on maintaining certified datasets and definitions. Established ownership for taxonomy, search configuration, and KPI certification with a review cadence.

Results

Leaders and teams navigated a single portal for priorities, milestones, and KPIs. Live tiles reflected certified datasets with clear refresh windows and definitions, and meeting notes used consistent templates with links to the relevant metrics and artifacts. Search returned the current narrative first, trimmed by permissions, and eliminated guessing which deck or page to trust. Updates moved through a light review, so messaging and numbers aligned before broad distribution.

The strategy cadence became more predictable. Stakeholders referenced the same KPI definitions and decision logs, and questions about what changed and why were answered by the approval notes and lineage links. Teams aligned faster around priorities and timelines, and conflicting messages declined because page ownership, metadata, and approvals were explicit and auditable.

What Changed for the Team

• Before: Strategy updates were scattered across sites, chats, and decks. After: A SharePoint hub centralized narratives, decisions, and KPIs.
• Before: KPI screenshots aged in slides. After: Embedded Power BI tiles pulled from certified Snowflake datasets with visible definitions.
• Before: Search returned duplicates and stale pages. After: Microsoft Search surfaced the current, permissioned version with helpful facets and bookmarks.
• Before: Messages went out without review. After: A publishing workflow captured Strategy Ops and Communications sign-off with comments.
• Before: Meeting notes varied by team. After: Templates standardized owner, next steps, and links to KPIs and artifacts.

Key Takeaways

• Centralize the strategy story, decisions, and KPIs in a single portal; navigation and consistency matter as much as tooling.
• Embed live metrics from certified sources; lineage and definitions should ride with every KPI tile.
• Use managed metadata and content types so search can find the current version and filter by initiative, owner, and horizon.
• Add a light publishing gate; small reviews prevent misalignment and keep messaging and numbers in sync.
• Keep your stack—SharePoint, Snowflake, Power BI, Teams—and add governance and search around it rather than starting over.

FAQ

What tools did this integrate with?
We built the leadership hub on SharePoint with managed metadata (Managed Metadata). KPI tiles used the Power BI web part and certified datasets connected to Snowflake (Power BI web part, Snowflake connector). Search leveraged Microsoft Search (Overview). Approvals ran in Power Automate, access used Microsoft Entra groups, and auditability relied on Microsoft 365 audit.

How did you handle quality control and governance?
Content types enforced required fields for initiative, owner, and refresh cadence. KPI tiles linked to definitions and lineage pages for certified datasets. A publishing workflow captured reviewer comments and rationale before updates went live. Microsoft Search was configured with verticals and bookmarks to prioritize the current, governed version. Audit logs tracked edits, approvals, and access to sensitive sections.

How did you roll this out without disruption?
We launched the portal in read-only mode and kept legacy links and decks available during validation. After confirming KPI refresh, navigation, and search behavior, we enabled approvals and redirected stale links. Teams kept using SharePoint, Power BI, Snowflake, and Teams; the new layer standardized where to find the truth and how updates were published.

How were KPIs kept consistent and current?
KPI tiles referenced certified Power BI datasets connected to Snowflake, with refresh windows and definitions documented. Changes to metrics or filters required a brief review through the publishing workflow. Tiles linked to definition pages so users could see calculation logic and dataset lineage.

How did you manage permissions and sensitive content?
Microsoft Entra groups scoped who saw leadership, manager, and all-hands sections. Microsoft Search trimmed results by permission, and sensitive pages required approval to publish. Audit logs recorded access and changes, and templates encouraged linking to public-safe summaries when the underlying artifacts were restricted.