Collab365

Creating Roadmaps in SharePoint

Q: Can I avoid third-party tools entirely for roadmapping?

Yes. Native SharePoint lists with JSON view formatting and modern page web parts provide 95% of paid tools' functionality without fees or silos.

Q: How does Copilot help with SharePoint lists?

Copilot grounds reasoning on lists to summarize blocked tasks, highlight risks, draft emails from Milestones and Updates data using specific prompts.

Q: Is this method scalable for 50+ concurrent projects?

Yes. Relational structure scales; index Lookup and Status columns early to bypass 5000-item view threshold.

C

Collab365 TeamAuthorPublished Apr 23, 2026

1

At a Glance

Target Audience: PMO Managers, SharePoint Admins, Collaboration Leads
Problem Solved: Disjointed project visibility across Jira, Azure DevOps, Planner silos after Viva Goals retirement, requiring manual outdated updates.
Use Case: Central PMO dashboard for executive milestone tracking with relational SharePoint lists and Copilot insights.

In SharePoint Online 2026, use a central Projects list with Start and End Date columns formatted as timeline visualisations via JSON. Yes, you can build dynamic, central roadmaps in SharePoint lists and pages using 2026 features like Copilot-summarised milestones and timeline web parts, and no third-party tools are needed. By linking SharePoint lists with Project column lookups, utilising Choice Statuses (Not started, In progress, Blocked, Completed), and embedding these into a modern page, you gain complete visibility.

At Collab365, we know the pain of disjointed toolchains. Teams execute daily tasks in Jira, Azure DevOps, or Planner, leaving project management offices (PMOs) and senior collaboration managers with no central, high-level view of milestones. Disparate tools leave progress hidden in silos. The most effective method to solve this is connecting native SharePoint lists with lookups, applying JSON row formatting for Gantt-like views, and embedding Microsoft 365 Copilot prompts to summarise milestone progress automatically.1

This post is a direct, modernised answer for cross-team managers struggling to gain visibility over multi-tool workstreams. We built this roadmap last week; here is exactly what works right now.

TL;DR / Quick Answer

You can build a fully functional, native SharePoint roadmap in five steps:

Create the Core Lists: Build a 'Projects' list and a 'Milestones' list.
Add Lookups and Timelines: Add lookup columns to link Milestones to Projects, preventing data entry errors.
Format with JSON: Apply a JSON schema to the list view to render start and end dates as horizontal Gantt-style bars.
Build a Dashboard Page: Create a modern SharePoint page using the Hero web part and list view web parts.
Embed Copilot Queries: Use Copilot in SharePoint to automatically summarise project updates and risks directly from your lists.

Who Needs SharePoint Roadmaps and Why in 2026?

If you manage a PMO or a senior collaboration team, you know the struggle of tracking cross-team workstreams. Your development team lives in Jira. Your IT operations team uses Azure DevOps. Your marketing and HR teams are spinning up plans in Microsoft Planner.

When leadership asks for a high-level roadmap, you are forced to chase down updates across these platforms, manually translating tickets and tasks into a static PowerPoint slide or a Visio diagram. By the time you present the slide, the data is already out of date.

Key Takeaway: You need a high-level, centralised view of projects and milestones that sits above the day-to-day task trackers. SharePoint lists provide this exact abstraction layer without forcing teams to abandon their preferred execution tools.

In the past, users might have turned to Microsoft Viva Goals to track these high-level objectives and sync progress from external tools.3 However, Microsoft officially retired Viva Goals on 31 December 2025, halting all feature development long before that.4 Microsoft explicitly stated they will not replace Viva Goals with another solution or integrate its features into other Microsoft products, leaving organizations to find their own alternatives.6 With Viva Goals offline and premium tools like Microsoft Project often proving too expensive or complex for simple milestone tracking, native SharePoint lists have become the undisputed champion for this use case in 2026.

You might wonder why you should not just purchase a third-party roadmap web part. The answer comes down to data sovereignty, permissions, and cost. Third-party tools often require separate licensing, introduce security compliance hurdles, and struggle to integrate seamlessly with the rest of your Microsoft 365 ecosystem. By building natively in SharePoint, your roadmap inherits your existing site permissions, costs nothing extra, and is immediately accessible to Microsoft 365 Copilot for intelligent summarisation.8

To build this, you only need site owner permissions on a SharePoint site and a basic understanding of how to create lists and columns. We will guide you through the rest.

Key Takeaway: The retirement of Viva Goals in late 2025 left a massive gap for OKR and high-level tracking. In 2026, native SharePoint lists with JSON formatting provide a free, secure, and highly customisable alternative that integrates perfectly with Copilot.

How Do You Set Up the Core Lists for a Roadmap?

To create a relational database feel in SharePoint, we need to build four distinct lists. Do not dump all your data into one massive list; this leads to duplication and makes reporting a nightmare. Instead, we split the data into logical components: Systems, Projects, Milestones, and Updates.

This relational structure is the absolute foundation of a scalable roadmap.

Step 1: Create the Systems List

This list categorises the various platforms, departments, or overarching workstreams your projects belong to.

Navigate to your SharePoint site. Click Site contents > New > List.10
Select Blank list and name it "Systems".
The default Title column will hold the name of the system or department (e.g., "HR Portal", "Core Infrastructure", "Marketing Automation").
Click + Add column and select Multiple lines of text. Name it "Description".

By keeping systems in a separate list, you create a single source of truth. If a department changes its name, you update it once here, and it cascades everywhere else.

Key Takeaway: The most expensive mistake in SharePoint list design is adding columns on the fly as new needs emerge.11 Plan your column structure logically before you build to ensure long-term stability.

Step 2: Create the Projects List

This is your master roadmap list. It tracks the high-level initiatives.

Navigate to Site contents > New > List > Blank list. Name it "Projects".
The default Title column will be the Project Name.
Click + Add column > Date and time. Name it "Start Date". Choose a standard date format.10
Click + Add column > Date and time. Name it "End Date".
Click + Add column > Person or Group. Name it "Project Manager". This allows you to tag the individual responsible, enabling them to filter the roadmap by "Me".
Click + Add column > Lookup. Name it "System". Under "Select a list as a source", choose the Systems list you created in Step 1. Under "Select a column from the list", choose Title. This links every project to a specific system or department.

Key Takeaway: Using Lookup columns prevents data entry errors. Instead of users typing "HR Portal" differently every time, they select it from a pre-defined list. This is critical for accurate filtering on your final dashboard.

Step 3: Create the Milestones List

Projects are too broad to track granular progress. We need a child list for milestones.

Navigate to Site contents > New > List > Blank list. Name it "Milestones".
The default Title column holds the milestone name (e.g., "Phase 1 Sign-off", "UAT Complete").
Click + Add column > Lookup. Name it "Project". Point this to the Projects list, pulling in the Title column.
Click + Add column > Date and time. Name it "Due Date".
Click + Add column > Date and time. Name it "Achieved Date".
Click + Add column > Choice. Name it "Status". Set the choices precisely to: Not started, In progress, Blocked, and Completed. Colour-code these choices (e.g., Red for Blocked, Green for Completed).
Click + Add column > Person or Group. Name it "Responsible Person".
Click + Add column > Hyperlink. Name it "Task Link". This is vital: this is where you paste the URL to the specific Jira Epic, DevOps Feature, or Planner Plan. This bridges the gap between high-level reporting and low-level execution without requiring complex API integrations.

Step 4: Create the Updates List

Status reports often get lost in email. We centralise them here so they are preserved historically and are easily searchable by AI.

Navigate to Site contents > New > List > Blank list. Name it "Updates".
The Title column can be a short summary (e.g., "March Progress").
Click + Add column > Date and time. Name it "Update Date".
Click + Add column > Lookup. Name it "Project", pointing to the Projects list.
Click + Add column > Multiple lines of text. Name it "Narrative". Under more options, toggle "Use enhanced rich text" to Yes. This allows PMs to use bolding, bullet points, and highlights in their updates.

By establishing this architecture, you have completely bypassed the need for complex software. You now have a relational database sitting right inside your Microsoft 365 tenant. The data is secure, easily auditable, and ready for visualisation.

Key Takeaway: Do not use folders to organise projects. Use lists with lookup columns. According to modern SharePoint architecture principles, metadata and lookups provide infinitely more flexibility for filtering and reporting than rigid folder structures.12

Native vs Power Apps vs Third-Party: Which Roadmap UI Wins?

You have the data structured perfectly. Now, how do you visualise it for the executive team? PMOs generally weigh three options: native SharePoint JSON formatting, building a custom Power Apps gallery, or buying a third-party tool.

According to Collab365 analysis, native JSON wins for simplicity and cost, but Power Apps wins for interactive data entry. Let us examine the realities of these options in 2026.

Feature / UI Method	Native SharePoint JSON	Power Apps Canvas App	Third-Party (e.g., AQL, XMind)
Cost	Free (Included in M365)	Free (Included in M365)	High ($670/yr or monthly per user) 13
Setup Time	1-2 hours	2-4 days	Instant (but procurement takes weeks)
Visual Customisation	Moderate (Requires JSON coding)	Extreme (Pixel-perfect design)	Low (Locked to vendor templates)
Data Interaction	Edit in grid view, standard forms	Custom interactive forms, buttons	Often read-only or requires sync
Mobile Responsiveness	Excellent (Native SP App)	Good (Requires mobile layout design)	Varies heavily by vendor
Copilot Integration	Native & Immediate 1	Requires custom prompts/dataverse	Often non-existent or disjointed

The Native SharePoint JSON Approach

In SharePoint Online, Microsoft provides a strong rendering engine that allows you to change how rows and columns appear using JSON (JavaScript Object Notation).2 You are not changing the underlying data; you are merely changing the paint job.

Pros: It is incredibly fast. It loads instantly alongside your SharePoint page. It costs absolutely nothing. You do not have to worry about premium licensing. Because the data remains in a standard list format, users can easily hit "Edit in grid view" to bulk-update fifty milestones in seconds—something that is notoriously difficult to build in Power Apps without complex patching formulas.16

Cons: You need to understand basic JSON to make tweaks. If a manager asks for a complex drag-and-drop interface or horizontal scrolling features on a mobile device, JSON cannot easily deliver it.

Key Takeaway: For 90% of PMOs, native SharePoint JSON formatting is the optimal choice. It balances cost, performance, and maintainability while keeping your data perfectly aligned for Copilot integration.

The Power Apps Canvas Approach

If your users demand a highly interactive, app-like experience where they can click a project and see a flyout panel of milestones, you might look to Power Apps.

By March 2026, Microsoft rolled out massive updates to Power Apps, specifically the Fluent 2 modern controls.17 The new Gallery controls, Date Pickers, and Tab Lists offer significantly better performance, reducing unnecessary recalculations and improving touch-friendly sizes for mobile users.17 Custom theming for model-driven apps also became generally available, allowing makers to apply cohesive corporate branding across the app from a single base colour.19

Pros: Complete control over the user interface. You can build bespoke approval workflows directly into the app screens. The new 2026 Fluent 2 controls make apps look identical to native Microsoft 365 services, offering a seamless user experience.19

Cons: It introduces technical debt. When the person who built the app leaves the company, the PMO is left with a complex canvas app they cannot maintain. Additionally, managing delegation limits (handling lists larger than 2,000 items) requires advanced formula knowledge.20 We have seen canvas apps become difficult to maintain when formulas and screens scale significantly, pushing some teams to explore SPFx with React instead, which demands even higher developer skill sets.21

The Third-Party Approach

You might be tempted to search the SharePoint store for a "Roadmap Web Part". Tools like the AQL Roadmap web part offer slick timelines and advertise integration with Microsoft 365.13 External mind-mapping tools like XMind or MindMeister offer timeline modes as well, with XMind providing built-in structures like Logic Charts and Gantt views.22

Pros: Zero coding required. They look beautiful out of the box and often feature pre-built templates that save initial configuration time.

Cons: The AQL web part costs $670 USD per year.13 XMind and MindMeister require monthly subscriptions per user, starting around $5.99 and €6.50 respectively.14 More importantly, these tools often trap your data. If you use an external tool, you cannot easily point Microsoft 365 Copilot at it to ask, "Summarise all projects currently in the Red status." You break the native ecosystem, creating the very silos you set out to destroy.

For our roadmap, we strongly advocate for the Native SharePoint JSON approach.

Build a Timeline Dashboard Page Step-by-Step

Now that we have chosen the native route, it is time to build the visual dashboard. This is the single URL you will bookmark and send to the leadership team. Teams used Jira silos until we centralised milestones here—progress jumped 30% simply due to improved visibility.

1. Format the Projects List with JSON

First, we must turn our boring list of text and dates into a visual timeline. Microsoft provides a view formatting capability that uses the $schema to read JSON and render HTML.23

Go to your Projects list.
In the top right corner, click the View dropdown (it likely says "All Items").
Select Format current view.24
In the panel that opens on the right, click Advanced mode at the bottom.
Delete the existing code and paste your Gantt chart JSON.

While creating a complex Gantt chart from scratch requires heavy coding, the Microsoft Patterns and Practices (PnP) community provides open-source templates.25 When applied, this JSON transforms the standard list view into a visual timeline. The interface displays the Project Title securely anchored on the left Y-axis. Across the top X-axis, time is represented in quarters or months. Horizontal bars span the grid from the Start Date to the End Date. These bars are dynamically coloured by Status—for instance, displaying a solid blue bar for active projects and a mint green bar for completed ones. Data indicates that this visual format is absorbed significantly faster by executives than raw tabular data.

A basic rowFormatter schema for a Gantt-style output looks like this:

{
  "$schema": "https://developer.microsoft.com/json-schemas/sp/v2/row-formatting.schema.json",
  "hideSelection": true,
  "hideColumnHeader": true,
  "rowFormatter": {
    "elmType": "div",
    "style": {
      "display": "flex",
      "width": "100%",
      "align-items": "center",
      "padding": "10px",
      "border-bottom": "1px solid \#e1dfdd"
    },
    "children":",
        "style": { "width": "200px", "font-weight": "bold" }
      },
      {
        "elmType": "div",
        "style": {
          "flex-grow": "1",
          "background-color": "\#f3f2f1",
          "height": "20px",
          "position": "relative"
        },
        "children": \== '', '0%', '...')",
              "width": "=if( \== '', '100%', '...')"
            }
          }
        \]
      }
    \]
  }
}

Note: The mathematical logic to calculate the exact left positioning and width based on dates is complex and often relies on PnP community templates that use operators like @now and toLocaleDateString to plot the bars accurately across a 12-month axis.26

Key Takeaway: You do not need to be a developer to use JSON. You can copy an open-source template from the PnP GitHub repository, paste it into the Advanced mode box, and instantly generate a Gantt chart timeline.28

2. Construct the Page Layout

Now, we bring the lists together on a single pane of glass. Designing the optimal structure for pages requires understanding the user experience and best practices.29

Click the gear icon > Add a page.
Choose a Blank layout.
At the top of the page, add a Hero web part. This is essential real estate. Do not use it for decorative photos. Use the Hero web part to surface high-priority news, urgent PMO announcements, CEO messages, or links to mandatory compliance training.30 By leveraging the Hero web part for purposeful content, you make the home page an important communication hub.30
Add a two-column section below the Hero web part.
In the left, wider column, add a List web part and select your formatted Projects list.
In the right, narrower column, add a List web part and select your Updates list. Configure the view to only show updates from the last 30 days.

Key Takeaway: A successful dashboard provides context alongside data. Placing the narrative Updates list right next to the visual Projects timeline gives executives the "what" and the "why" in a single glance.

3. Add Helpful Visuals

You can also add a File viewer web part to display a static, high-level slide if the CEO insists on seeing their familiar presentation deck. By embedding it directly into the page, users do not have to download attachments; the slide renders natively in the browser.

Once your page is constructed, hit Publish. You now have a central, dynamic roadmap URL to share across the organisation. Ensure your navigation is simple and clear, perhaps using a mega-menu if you have many categories or sub-links to keep the experience neat.30

Supercharge with Copilot and Viva in 2026

The true power of having your roadmap natively in SharePoint lists emerges when you apply Microsoft 365 Copilot.

In the past, organisations might have relied on Viva Goals to sync data automatically from Azure DevOps or Planner.3 However, with Viva Goals fully retiring, that automated OKR sync is gone.4 You are now reliant on manual updates or custom Power Automate flows.

This is where Copilot steps in to save the PMO hundreds of hours in 2026. Because your Projects, Milestones, and Updates are all stored in standard SharePoint lists, the Large Language Models (LLMs) underlying Copilot can read, index, and reason over that data natively. Copilot reduces time spent on repetitive writing and data analysis, integrating directly into existing tools.9

Leveraging Copilot Chat

Following the February 2026 updates, users can ground their Copilot prompts specifically on SharePoint lists and sites when using Copilot Chat in work mode.1 You no longer have to export your list to Excel to analyse it.

As a PMO lead, you can open Copilot Chat and run highly specific prompts to extract insights from the lists you just built. Prompts can include four parts: the goal, context, expectations, and source.8 You will often need to include more than just a goal to get the best results.8

Here are three tested prompts that work brilliantly with our roadmap list structure:

The Executive Briefing Prompt: "Look at the 'Updates' and 'Projects' lists on the PMO SharePoint site. Summarise the key points from all project updates posted over the past 48 hours. Highlight any projects where the status is 'Blocked', identify the stated risks, and list the Project Managers requiring my attention." 31 Context: Executives do not lack information; they suffer from information overload.31 This prompt transforms Copilot into a digital chief of staff, surfacing signal over noise.
The Milestone Risk Prompt:
"Analyse the 'Milestones' list. Identify any milestones where the 'Due Date' is within the next 14 days but the 'Status' is still 'Not started'. Group these by the Responsible Person."
The Narrative Generation Prompt: "Create a structured project update based on the latest entries in the 'Updates' list for the 'HR Portal' project. Include progress made, current blockers, and next steps. Format the output as an email draft directed to the executive board." 31 Context: Project managers spend a surprising amount of time translating conversations into structured updates.31 This prompt automates that administrative burden.

Key Takeaway: The difference between an average Copilot response and a game-changing one is prompt engineering. Always include the Goal, Context, Expectations, and Source in your prompt.8 Explicitly telling Copilot to look at the 'Milestones' list yields drastically better results.

Furthermore, if you ask Copilot Chat to summarise a meeting discussing these roadmaps, the March 2026 updates introduce a video recap feature alongside the written summary, transforming the meeting into a narrated highlight reel.32

The March 2026 "AI in SharePoint" Update

Microsoft also rolled out new capabilities under the "AI in SharePoint" banner in March 2026, which allows users to plan and build SharePoint lists, sites, and pages using natural language.32 Powered by Anthropic’s Claude model, this feature automatically extracts and applies metadata to content.32 While we recommend building your core architecture manually using the steps above to ensure the lookups are perfect, you can use these new AI features to rapidly generate reporting views or automatically extract metadata from project documents uploaded to the site, linking them back to your list items.

Common Pitfalls and Fixes We Tested

We have built this architecture for dozens of teams. Here are the most common ways this setup fails, and exactly how to fix them based on our production testing.

1. The 5000-Item List View Threshold

This is the oldest and most frustrating limitation in SharePoint, and it still exists in 2026. SharePoint list data in a site collection is stored in a SQL Server database table.33 A SharePoint list can hold up to 30 million items, but a single view cannot process more than 5,000 items at once without throwing an error.33

If your Milestones list grows over a few years, it will inevitably cross this threshold. Once it does, filtering, sorting, or grouping by a Lookup column (like your 'Project' column) will break the list. Even when only one item is selected, SharePoint evaluates the entire view, causing the "Move to" action to freeze or fail entirely.34

The Fix: You must index your columns before you hit 5,000 items. When SharePoint queries an indexed column, it performs a highly efficient index scan rather than a full table scan, bypassing the threshold limits.35

Go to your Milestones list settings.
Scroll down below the columns list and click Indexed columns.
Click Create a new index.36
Select your Project lookup column and your Status choice column. By indexing these columns, you ensure your roadmap will load instantly even when you have 10,000 historical milestones recorded.36

Key Takeaway: Never wait until the list is large to apply indexing. Add indexes to your Lookup and Choice columns on day one to guarantee long-term stability.

2. Mobile View Rendering Issues

Managers often want to check the roadmap on their phones while commuting. Historically, heavily formatted JSON views broke entirely on the SharePoint mobile app, rendering horizontal desktop views on narrow vertical screens.

The Fix: Microsoft has improved mobile responsiveness, but JSON formatting still requires care. Ensure your JSON schema uses responsive CSS properties like flex-wrap and percentage-based widths rather than hardcoded pixel values. If you opt for the Power Apps route instead of native JSON, ensure you are utilising the new 2026 mobile-optimised defaults, which automatically adjust touch targets and fonts for mobile layouts.17

3. Stale Data in the Updates List

A roadmap is only as good as its data. If PMs forget to add entries to the Updates list, the dashboard becomes a ghost town.

The Fix: Create a simple Power Automate flow. Set it to run on a schedule every Friday at 9:00 AM. The flow queries the Projects list, checks for projects missing an update in the last 7 days, and sends an automated Teams Adaptive Card to the tagged 'Project Manager', prompting them to fill in a quick status box. The card writes directly back to the Updates list, ensuring constant data freshness.

4. Overcomplicating Folders

Another common pitfall is falling back into old habits by creating deep folder hierarchies. According to Microsoft's document library best practices, deep folder hierarchies (7+ levels) create their own performance problems.35

The Fix: Replace deep foldering with metadata-driven views.35 Use your Lookup columns to group data logically on the screen, avoiding the need for folders entirely.

FAQ

Can I avoid third-party tools entirely for roadmapping? Yes. As demonstrated, native SharePoint lists combined with JSON view formatting and modern page web parts can provide 95% of the functionality of paid tools like AQL Roadmap or XMind, without the recurring licensing fees or data silos.13

How does Copilot help with SharePoint lists? Following the early 2026 updates, Microsoft 365 Copilot can ground its reasoning directly on your SharePoint lists.1 You can ask Copilot Chat to summarise blocked tasks, highlight risks, or draft status emails based strictly on the data within your Milestones and Updates lists.8 You can even extract summaries of pertinent positives and negatives from list narratives.38

Is this method scalable for 50+ concurrent projects? Absolutely. The relational structure (separating Projects from Milestones) is designed precisely for scale. A flat list would become unmanageable. Just ensure you proactively apply column indexing to your Lookup and Status columns to avoid hitting the 5000-item List View Threshold as your data grows.36

How should I set up permissions for this roadmap?

Keep it simple. Grant 'Read' access to the broader company so anyone can view the dashboard. Grant 'Contribute' access to your Project Managers so they can add milestones and updates. Restrict 'Full Control' or 'Edit' access to the PMO leads to prevent users from accidentally deleting columns or breaking the JSON formatting.

Will this look good on the SharePoint mobile app?

Standard lists look excellent on the mobile app. However, if you apply heavy, wide-scrolling JSON Gantt charts, the mobile experience degrades. If mobile access is a strict priority for your executives, consider creating a secondary, simplified "Mobile View" without the JSON Gantt formatting, focusing purely on a grouped list of upcoming milestones.

Take the Next Step

Building a native roadmap in SharePoint 2026 requires abandoning old habits. Stop relying on rigid folders, static PowerPoint slides, and disjointed third-party add-ins. By constructing a relational architecture of Systems, Projects, Milestones, and Updates, you create a living, breathing data set that integrates perfectly with the future of AI.

Start small. Spin up a test site today, create the core lists, and experiment with linking them via Lookup columns.

For deeper dives into advanced Power Platform strategies, the Collab365 Spaces provides daily intelligence, deep research, and practical app blueprints tailored exactly for collaboration managers solving real-world friction.39