IBM Cognos or Planning Analytics Power User Training for 2026

We first published a similar blog in 2019. IBM had just released Cognos Analytics 11.1.4, TM1 10.2 had gone off support, and our inbox filled up with the same question from client after client: how do we train our power users on the new functionality?

Almost seven years later, that question still shows up every week, and Cognos or Planning Analytics power user training has gone from nice-to-have to something with a deadline attached. What changed is not the question. It is the answer, and the cost of not having one.

In 2019, falling behind meant your team was a few features short. In 2026, it means your team is missing an entire layer of the platform. Cognos Analytics now ships AI agents that build reports from a plain-language request. Planning Analytics Workspace has an assistant that opens your books, walks you through TurboIntegrator, and explains forecast variances. At the same time, the studios your analysts learned back in 2012 are gone.

So let us revisit this properly.

What Changed Since We First Asked This Question in 2019?

The short version: the platform stopped adding features alongside the old ones and started replacing them. That single shift is why the 2019 advice no longer holds.

Back then, new functionality was additive. New dashboard options, better visualizations, a few extra chart types. Your power users could keep working exactly as they always had and pick up the new material whenever they found a spare hour.

That is no longer how these releases work. Both product lines moved to continuous delivery, both dropped legacy components, and both put an AI assistant at the front door rather than off in a side menu. Training is no longer catching up on features. It is learning a different way to work.

Which Cognos and Planning Analytics Versions Are Still Supported?

Before you plan training, confirm what you are training on. Two support deadlines land this fall, and both catch people who assume they are current.

Cognos Analytics

Planning Analytics

Read those two tables twice. If you are running Cognos Analytics 12.0.4 and you assumed that being on version 12 meant you were fine, you have until September 30. You can confirm that yourself on the IBM Cognos Analytics 12.0.x lifecycle page, which also shows the four-year extended support window behind it. If you are on Planning Analytics 2.0.9.x and bought the extended support year for breathing room, that room closes October 31. We walked through what that transition involves in our post on the end of support for Planning Analytics 2.0.9.

Why Is Being on a Supported Version the First Training Question?

Because an unsupported version turns every unrelated IT change into an emergency, and emergencies are where untrained teams get exposed. Our recommendation from 2019 has not softened by a word:

ALWAYS BE ON A SUPPORTED VERSION.

Not because IBM support is where you spend your days. Most of you open two tickets a year. The problem is everything around the software. Microsoft pushes an Office update and your Excel integration breaks. Security mandates a new TLS standard. Your DBA upgrades the database. When any of that happens on an unsupported release, the first thing you will hear is “upgrade to a supported version.” You do not want that conversation happening in week three of your budget cycle.

What Happened to the Studios Your Power Users Already Know?

They were removed, and no conversion tool fixes the human side of that. This is the part clients consistently underestimate.

Starting with Cognos Analytics 12, Query Studio, Analysis Studio, and Cognos Workspace are no longer in the product. If your analysts have spent a decade doing ad hoc analysis in Analysis Studio, that muscle memory has nowhere to go. IBM's bulk conversion tool, introduced back in 11.2.4, moves the content. Nothing converts the person. That gap is training, not tooling.

The same pattern holds on the planning side. Planning Analytics 2.1.x does not include Architect, Perspectives, TM1 Applications, or Performance Modeler. If your modeler builds dimensions in Architect and your contributors submit through TM1 Applications, the upgrade is not a version bump. It is a new way of working inside Planning Analytics Workspace.

What Does “New Functionality” Actually Mean in 2026?

It means agents, not features. The new capabilities behave less like menu items and more like a co-worker who needs supervision.

Cognos Analytics 12.1.3, released in June 2026, is where this becomes concrete. IBM positions it as governed BI for the agentic enterprise, and the release includes a natural-language Data Query Agent, a Report Authoring Agent that builds and formats reports from plain-language requests, Bring Your Own LLM support so you can point Cognos at a model your organization already approved, and MCP connectivity that exposes Cognos as a governed tool to outside AI assistants. IBM's own 12.1.3 announcement lays out the governance framing, and we broke the release down feature by feature in what's new in Cognos Analytics 12.1.3.

Planning Analytics moved the same direction. The Workspace assistant now runs on watsonx Orchestrate with multilingual support and an expanded command set, and recent releases added a Workspace REST API for managing content programmatically plus AI-generated explanations for forecast values. Our posts on Workspace 3.1.9 and 3.1.10 and on why Workspace is entering its next era cover where this is heading.

Nobody absorbs that from a video at lunch. And here is the part that should worry you: if your power users do not learn the governed AI capabilities inside your analytics platform, your business users will go find ungoverned AI somewhere else. They will export to Excel, paste it into a chatbot, and build a forecast nobody can audit. You will have paid for a governed platform and lost the governance anyway.

What Does It Cost to Put Training Off?

It costs budget and credibility, and we have watched it happen more times than we can count.

Your CFO attends a conference. They sit through a session where a peer describes asking a question in plain English and getting a governed, sourced answer with the variance already explained. They come home and asks why your team cannot do that.

You can do that. You have been able to for a couple of releases. But if nobody on your team has spent focused time with the Assistant, the agents, or modeling workbench, your honest answer is that you would have to look into it. That answer is expensive.

The reverse is also true, and it is the more useful way to think about this. The analyst who invests a day learning what the platform can now do becomes the most valuable person in the finance organization, not because they memorized menus, but because they are the one who can tell leadership what is possible.

We have had a number of clients go through power user training for both Cognos and Planning Analytics right after the above changes were enacted which gave them a headstart on the new functionality and ideas on how to replace studios that are no longer part of the product. By getting this head start, these clients saved time in creation, analysis, and reporting.

What Should Your Power Users Learn First?

Focus on the delta between the version you are leaving and the version you are landing on, not a general product tour. Here is roughly what we cover.

Moving to Cognos Analytics 12.1.x

• The Assistant as the front door, since it is now the primary self-service entry point rather than a novelty tile
• The Data Query Agent and Report Authoring Agent: where they are reliable, where they need a human, and how to prompt them well
• What governance looks like with agents in the mix, including lineage, access controls, and audit
• Data modules replacing Framework Manager packages in more and more places, including as an Event agent source as of 12.1.2
• Where Analysis Studio and Query Studio work goes instead, which means Explorations, dashboards, and modern reporting
• Bring Your Own LLM, if your organization has AI hosting or data residency policies, and most of you do

Moving to Planning Analytics 2.1.x and current Workspace

• Modeling in the Workspace workbench instead of Architect and Performance Modeler
• Plans and Applications instead of TM1 Applications, including data context on plan tasks
• Planning Analytics for Excel for the people who are never leaving Excel, which is genuinely fine
• Spreadsheet Services for legacy websheets
• The Planning Analytics assistant and watsonx Orchestrate integration, including custom agents scoped to a specific area
• Forecast insights and AI-generated explanations, plus how to defend them to a controller who wants to know where a number came from
• Infrastructure reality checks, since 2.1 dropped older Windows Server support and Workspace often belongs on Linux

One thing everyone needs to internalize: continuous delivery means training is never finished. Workspace refreshes monthly. Cognos 12.1.x ships incremental releases rather than large fix packs. A single class in 2026 beats nothing, but a cadence is what keeps a team current.

What Are Your Options for Training Power Users?

There are four realistic paths, and they were the same four in 2019. What changed is which one we lead with.

Do it yourself

You read release notes, catch a webinar when you can, and learn it over months. It is free and plenty of good people do exactly this. The catch has not changed: your executives do not get the benefit until you get around to it, and with monthly releases that target keeps moving. If you go this way, put a recurring hour on your calendar and treat it as unmovable. Our Cognos Analytics resources and release breakdowns exist for exactly this purpose.

A focused new functionality program

This is what we build at Lodestar and what we recommend for most teams. We train on the specific gap between your current environment and your target version, using your data and your use cases, rather than running a generic product walkthrough. The part people do not expect is how much value comes from the brainstorming. We stop mid-session and ask what you would build now that you can do this, and that is usually where the roadmap gets written. Delivered privately, on site or virtual.

Recurring touchpoints instead of one large class

This is the biggest change in how we deliver training since 2019. When the platform updates every few weeks, a standing session where your team brings real questions to someone who already read the release notes is worth more than a week-long course once a year. Our Lodestar and IBM Office Hours run twice monthly, on the second Tuesday and last Thursday at 1:00 PM ET, for exactly this reason.

IBM courses and certifications

IBM offers live and self-paced options across both products, and they are good at what they do: deep, structured, product-centric. If your team needs formal certification or a specific technical track, we will help you find the right course.

What Do We Recommend?

Take the focused time, and do it before the upgrade rather than after.

One or two intense days where your power users do nothing but work with the new functionality and think about how your organization could use it. Not an hour squeezed between meetings, and not a video playing in the background during month-end. After we ran our Cognos Analytics new functionality class in Chicago, the feedback from attendees was not about the features. It was that they finally had space to think about their analytics roadmap.

If we were building your plan for the rest of 2026, it would look like this:

1. This month, confirm your exact versions against the dates above. If you are on 12.0.4 or Planning Analytics 2.0.9.x, you have a fall deadline.
2. Within 30 days, pick your target version and get the upgrade on a calendar with a budget attached.
3. Before the upgrade, train the power users. Teams who understand the new capabilities make better decisions about what to convert, what to rebuild, and what to finally retire.
4. After go live, set a monthly learning cadence and protect it.
5. Quarterly, revisit the roadmap, because the platform will keep moving.

For the finance side of the house, many of our educational sessions are eligible for CPE credit through our NASBA-registered program, so the time your team invests in getting current can count toward professional requirements.

Frequently Asked Questions

Is Cognos Analytics being discontinued?

No. IBM shipped 12.1.3 in June 2026 with significant new investment in agentic AI and governance, which is the opposite of a sunset signal. What is ending is support for older versions.

Do we have to move off Planning Analytics 2.0.9?

Yes, if you want support. General support ended October 31, 2025, and purchased extended support ends October 31, 2026. Remember that 2.1.x also drops Architect, Perspectives, TM1 Applications, and Performance Modeler, so plan for the retraining alongside the upgrade.

Our power users are smart. Can they not just figure it out?

They can, and eventually they will. The constraint is calendar, not capability. Every month spent figuring it out is a month your executives do not have the analytics they are asking for.

Should we train before or after the upgrade?

Before, at least for the power users. Teams who understand the new capabilities going in make better architecture decisions and rebuild less.

How long does new functionality training take?

For most power user teams, one to two focused days covers the version gap. After that, a monthly cadence keeps up with continuous delivery.

Where Do You Start?

Tell us what version you are on, where you are going, how many people you need to train, and where you are located. We will build a plan that fits.

Email services@lodestarsolutions.com or schedule an advisor call.

You invested in a serious analytics platform. Let us make sure your people can use all of it.