Video | Tableau | Tool strategy | Industry trends

Feature realeases need to change | What's new in Tableau

Should Tableau drip-feed features every quarter, or wait until they're feature complete? Here's my slightly unpopular opinion.

Watch on YouTube
  • The Tableau Release Navigator is the single best place to see new, changed, deprecated and retired features, filterable by product and version
  • Features such as virtual connections, Ask Data and the data model have been delivered in sporadic increments over 18 months to two years rather than as complete launches
  • Most businesses upgrade Tableau Server roughly once a year and need months to test, document and train, so they rarely keep pace with Tableau's quarterly release cadence
  • Tim's view is that incremental releases can do more harm than good, as features that miss the mark force later tweaks that arrive after businesses have already moved on
  • Older Tableau releases had standout 'big hit' features that generated excitement, whereas recent releases feel like incremental themes rather than statement features

Tim argues that Tableau should ship features only once they're feature complete, rather than drip-feeding them across quarterly releases as it does now — because incremental rollouts often do more harm than good for businesses trying to adopt them.

Using the Tableau Release Navigator, Tim traces how several major features actually rolled out over time to test whether quarterly incremental releases really serve users well.

The Breakdown
  • The core question 0:00

    Should Tableau release features only when feature complete, or keep releasing them in incremental bits each quarter as it has done for years? Tim sets this up as the question he's testing through examples.

  • Use the Release Navigator to trace a feature's history 0:19

    The Tableau Release Navigator is the best single place to see everything new, changed, deprecated or retired, filterable by product and version. You can search for a specific feature name to see its full release history and spot patterns in how it was rolled out.

  • Virtual connections rolled out over 18 months to two years 1:12

    Searching the Navigator for virtual connections shows capability being added in increments from around 2022.1 through to mid-2023, rather than as one complete launch. Tim uses this as his first example of sporadic, staggered delivery.

  • Businesses can't keep pace with quarterly releases 3:11

    Most organisations on Tableau Server upgrade to a new major version only about once a year, and take four to five months to test, document, train and check integrations with other tools. By the time a business is ready to adopt a feature, Tableau may already be several releases further on, so any late tweak to that feature often arrives after the business has moved past it.

  • Ask Data and Ask State show the same pattern 4:49

    Searching the Navigator for Ask Data reveals a long trickle of enhancements from 2019 through to recent releases, rather than a single finished capability. Tim notes that anyone adopting Ask Data early likely had to rework their workflow once major additions like Ask State lenses arrived later.

  • The data model was also built up in phases 6:24

    The data model's feature history in the Navigator shows it was delivered over roughly two years, with more still promised at conferences. Tim uses this to ask whether it would have been better to release such a feature in complete yearly phases instead of quarterly slices.

  • The case for feature-complete releases 7:03

    Tim's view: Tableau is now big enough that it should hold features until they're properly complete, because half-finished releases force later fixes that land after businesses have already adapted or moved on. He also argues older releases had standout 'big hit' features that generated real excitement, whereas recent quarterly releases feel like incremental themes with no single feature people get excited about.

Worth Knowing
  • The Release Navigator can lag behind actual releases and its historical data isn't always complete or perfectly chronological, so treat feature timelines as broadly indicative rather than exact.
  • This is explicitly Tim's opinion piece, not a tutorial — he says upfront it's a 'slightly unpopular' take and invites disagreement.
Use It When

Reach for the Release Navigator when you need to check a feature's real maturity and rollout history before committing to build on it, especially if your organisation only upgrades Tableau once a year.

How this Rollup was made provenance & method

A Rollup is drafted by AI from the video's transcript, then reviewed and edited by Tim. Everything used to produce this one is listed below — the model, the exact prompt, and the source video — so the process is transparent and reproducible.

Transcription
On-device — NVIDIA Parakeet v3 for recent videos, OpenAI Whisper large-v3 for earlier ones. The transcript never leaves the machine or gets published.
Drafting
Claude Sonnet 5 in the cloud, from that transcript.
Prompt
The exact Rollup prompt (v2) — the full system prompt, unedited.
Source video
Watch on YouTube
Drafted
5 July 2026 at 09:38
Reviewed & edited
5 July 2026 at 09:41 · by Tim Ngwena

Model + prompt + video is everything you'd need to recreate a Rollup like this yourself. The one thing we don't share is the transcript.

Rights. The video and its transcript are the property of TN Media Ltd. Unauthorised use or download is prohibited. © TN Media Ltd.