Nufar Gaspar

Because your own meeting prep has your own specifics.

Maybe you wanted to capture what was the undercurrent feel like in the previous meeting.

Maybe you have other sources that are very relevant for this specific audience and so on.

This is something that you should definitely personalize.

And as mentioned at the beginning, the more you document the intangibles as part of the overall usage of AI,

the more your, let's call it personal CRM, aka your traction of what happened with this person previous time, the more context you have about the stakeholders that might not be in any official CRM or other systems, the better you will be ready for meetings and you can think about the analogy and other things that you need to have prepared on a day-to-day basis.

If you want a pro tip, whenever you're contemplating building a dashboard or a meeting prep automation or a morning brief or anything else that you have in mind to automate as part of your day-to-day activities, I want you to never automate before you've tested it manually and repeatedly.

So maybe you created like a morning brief.

I want you to run the morning brief on every morning for maybe a week or two weeks before, and you can do it manually, before you commit to having it run automatically.

Because only after a week or two of seeing the data and seeing how you consume it, you will be able to say, yes, that's a good use of this automation or something that I can improve and then commit to that.

And that, by the way, is applicable to anything else that the rest of the use cases, whether it's research or strategic thinking or anything that you're contemplating automating, it's always better to first test it for a while, sometimes in a stealth mode, meaning in a way that does not truly impact any systems or decisions, and only then to automate.

So kind of to summarize, it doesn't matter where you started today.

Maybe you build a lot of the systems already.

Maybe you're quite a beginner.

But if you build even one of these systems with the principles that we covered, I believe that you will start closing the gap between knowing about AI or using it in a certain way to understand

actually having it work fully for you and feeling like a digital employee that you hire that drives value in the way that moves the needle in your context.

You then become a much better AI user, and then obviously you get better results, hopefully a lot of ROI, but also in the process, you become a better leader of adoption.

Because you'll make much more informed and inspired decisions about where and how your organization uses AI.

And that's why I want you to roll up your sleeves and not rely on others to do everything for you.

And I think that the next steps, once you have these four digital team members that are working well for you or your version of the digital workforce that you should have, the natural one is to start building a chief of staff that can orchestrate across all of them.