5 Reasons NOT to do this…

Here are 5 Reasons to NOT Join the Technical and Strategic Data Leader cohort this summer.

We launch in 3 weeks. In case any of you are on the fence, here are key reasons you should stay on the fence.

1. You hate following recommendations.
100% of cohort members (people like data architects, director of analytics, VP of BI, etc) recommend it to others and you like bucking the trend.


2. You have all the network, connections, and peers you need.
What you have is good enough for you. You see no benefit in building a deeper network or connections with other data leaders.


3. You are too busy and wouldn't have the time to engage.
The cohort is an intensive experience. You need to commit to 2-4 hours a week for 6 weeks to engage in the content and conversations happening.


4. You are already an expert on Data Architecture, Power BI, Data Leadership, etc., and have nothing to learn.
Perhaps you already wrote a book on Data Architecture (like cohort mentor James Serra). Or you already teach Power BI at a university, consult with large organizations on Power BI strategy, and coach Power BI developers and leaders like Ahmad Chamy. Don't join if you don't have anything to learn.


5. You navigate organizational or data leadership challenges with ease.
Communicating with executive leadership, gaining strategic buy-in from peers, and aligning your team around core objectives - these are skills you've mastered. You don't need to learn any more here.

6. (Bonus) You aren’t interested in bonus content.

We just added a 7th week to the cohort to focus on Generative AI and LLMs. Same price to join, with an additional week of content and conversation led by another industry expert.

But.

If by chance those things aren't true about you.

And you actually do want to build your network, gain invaluable technical skills, and expand your capacity for leading in complex organizations.

You SHOULD join us. We have limited seats.

Register now to guarantee your spot.

thedatashop.co/leader

I’m here,

Sawyer

Previous
Previous

From fluffy unicorns to clear progress

Next
Next

Your mantra for data team success