The BI Cantos: Planning Milestone and Data Workflows


The BI Cantos: Planning Milestone and Data Workflows

It’s impossible to graft a fixed number of data workflows onto every business, non-profit or government entity that is definitive. However, standard data workflows provide generalization and repeatable starting points.

Typical Milestone Durations

Guidelines for work durations, assuming you have a team dedicated to the project:

A table showing tasks to be done from 1 week to 1 year

Many SaaS vendors permit free or discounted pricing during a POC sprint. Most of the cost early in the project will be for project planning, consulting services, project planning and training.

Suppose you have a few technically capable people with experience deploying analytical business information systems. In that case, progress may be slower in the early stages because you may opt for less consulting help to reduce early expenses. If speed to finish is essential, retain an expert consulting partner to deliver excellent work faster.

These “rules of thumb” are based on practical experience with focused effort and senior management buy-in. There are no guarantees. Do you have sloppy workflows that generate unreliable data? Lack of leader sponsorship and buy-in? Your durations may extend beyond my estimates.

Undeniably cloud APIs and modern SaaS software have reduced the time required to go from nothing to a set of interactive dashboards built on a robust, best-of-breed data platform.

Typical Year One Data Workflows

Well-run projects develop data workflows that support the most critical business processes in the first year of a BI deployment. Examples of workflows may include:

Table showing steps of the Data Workflow

All these are high-value targets of opportunity, but you may identify more that are particular to your business.

The priority for each workflow should consider the availability and condition of current data sources, the potential value to your company and the availability of your employees with detailed knowledge of the workflows. Before establishing a cadence for the development sprints, you must assess each workflow’s challenges.

In the next post, we will review what a system-wide data workflow should look like.

More About the Author

Dan Murray

Director of Strategic Innovations
Thoughts on Tableau Conference 2024 I’ve attended every Tableau Conference since the first one in 2008, held at the Edgewood Hotel in Seattle. That conference included 150 ...
Ten Questions for ChatGPT about Tableau and Level of Detail Expressions I had some fun with ChatGPT asking it questions about cohort analysis this week. I’ll spare you the 4,000 words it created on general ...

See more from this author →

InterWorks uses cookies to allow us to better understand how the site is used. By continuing to use this site, you consent to this policy. Review Policy OK


Interworks GmbH
Ratinger Straße 9
40213 Düsseldorf
Geschäftsführer: Mel Stephenson

Telefon: +49 (0)211 5408 5301

Amtsgericht Düsseldorf HRB 79752
UstldNr: DE 313 353 072


Love our blog? You should see our emails. Sign up for our newsletter!