Different domain, same model: application issue tracking at CVC Capital Partners

Different domain, same model: application issue tracking at CVC Capital Partners

A private-equity firm wanted a secure issue tracker that wouldn’t pull their developers out of focus. They got a kanban board in Microsoft Teams reading a SharePoint list. Same model as a sales pipeline, very different domain.

26 May 2026

Estimated reading time: 4 minutes

The client

CVC Capital Partners is a private-equity firm with more than four hundred employees worldwide, headquartered in the UK.

The problem

CVC needed a dependable way to track application issues across their internal systems. The brief came with three constraints that, taken together, ruled out most off-the-shelf options:

  • Data safety must not be compromised. Issue tickets routinely contain sensitive operational information; sending it to a third-party SaaS issue tracker was off the table.
  • Developers must remain in focus. Anything that demanded constant context-switching out of their day was a non-starter.
  • Collaboration had to be first-class. A ticket is rarely owned by one person; it has to move between stages, between teams, with the surrounding conversation in reach.

The solution

We ran a discovery session with the CVC team to map their problem-solving process, then translated it into a familiar kanban board. The board lived in a Microsoft Teams channel, reading and writing a SharePoint list inside CVC’s own Microsoft 365 tenancy.

Each ticket received a unique number on creation. Lanes followed CVC’s stages, from intake through investigation, fix, and verification. When a ticket reached the final swim lane it was archived rather than deleted, so cross-referencing earlier issues remained possible. Custom fields specific to the way CVC catalogued their applications were added to the underlying SharePoint list, and the board adapted to show them on the cards that needed them.

Because the board lived inside the Teams channel where the developers already worked, the discussion about a ticket happened in the channel right next to the board. No new app to install, no separate web tool to alt-tab into, no friction.

What this proved

Gamification+ proved that a kanban board on SharePoint, surfaced in Teams, could run a sales pipeline. CVC proved the same model could run something very different: a developer-focused issue queue with strict security requirements and a hard rule against distraction.

The board mechanics did not change. Only the lanes, the fields, and the conversations on top of them did. The pattern adapted because the data layer was the customer’s own SharePoint list, not the product’s opinion about what a process should look like.

Process Planner today

Process Planner is the relaunch of the product CVC and Gamification+ helped prove out, now scaled to support the patterns we kept seeing.

It is a native SharePoint web part rather than a Teams-first app, so the board can live on any SharePoint page in your tenant and the Teams tab is an optional projection. It can unify lists from multiple SharePoint sites into one board, so a programme-wide issue queue across services or teams becomes one view. Thirty-plus built-in business templates cover patterns from issue tracking through security incident management to bug tracking and quality reviews. And the offline queue keeps things moving when connectivity drops, with conflict detection if someone else edited the same ticket while you were offline.

Same model. More room to run.

Ready to run your processes better?

Process Planner is available on the Microsoft commercial marketplace. Install it on your SharePoint tenant and add it to any page or Teams channel where the work happens.