Just yeet the code change into prod and hope for the best

Pre-s - I’m piloting a two-week program this summer that walks data leaders through how to define and adopt success metrics for their data teams. It’s built on my experience working with dozens of data teams over the last several years.

If that that sounds beneficial to your team, hit reply and I’ll send you a short video walk through of the program.

——————

Don't approach your data development lifecycle this way.

The average data team has:

• Minimal source control.

• Limited testing framework.

• Haphazard deployment process

• Indescribable environment strategy.

It's costing you. Far more than you realize.

Without a meaningful dev lifecycle process you:

• Are slower

• More error prone

• Confused about bug fixes

• Losing the trust of your stakeholders

It's painful to watch. Painful to be a part of.

It drains the life from your team. It kills morale.

But most data professionals don't know any different. They assume prod failures are just a part of the process. They expect merges to always take days to unravel conflicts.

• -> If you want to attract and retain better talent.

• -> If you want your data team to take the next step.

• -> If you want to deliver better data faster and more reliably.

Then your best next step is investing in CI/CD and development lifecycle.

I’m here,

Sawyer