Would like to learn best practices for a new Director/Manager who is taking on supervision of a Data/Analytics team. Process? Structure? Organizational, facilitation and communication tools used?

Data and Analytics, while adjacent and interrelated, can be two VERY different things. FIRST STEPS:

1. Create a 15-minute daily standup meeting to check-in with your team. The frequency can be lowered later.

2. Create a Jira / MS Planner (whatever you've got already) kanban board and capture ALL the work. Make sure it has categories like Intake, Backlog, In Progress, Blocked, Completed, Reference, etc. GET DOWN IN THE WEEDS WITH YOUR TEAM, but ALSO block out time in your calendar (literally) for focus blocks to work on strategic level things, e.g., Data Architecture and Governance, Analytics tools policies and standards (don't be the guy who has MiniTAB, PowerBI, Python, R, SAS, Tableau, and every other damned thing under the sun -- that's duplication of business capabilities, wasteful of resources, and just plain bad management).

3. Get and read a copy of Accelerate. I second Kyle in getting familiar with Agile and Scrum methods.

4. As universally bad-mouthed as they can be, set Core Values, a Vision, a Mission statement, and strategic Goals with sub-objectives at your team's level. Remind your team, OFTEN, of them to the point that they start rolling their eyes and giving you a hard time about how "preachy" you are about them. You're creating a team culture when you do that, and culture is EVERYTHING.

5. "Chunk it down." If you don't have Data Dictionaries for EVERYTHING and a Master Data Model already, pick one Data source and instruct your Data folks to build best practices Data documentation (some quick Google Fu will provide ideas there). Execution SPEED and building momentum is the key. Just get them MOVING. You'll find as you read Accelerate and other great DevOps books that the entire idea is fail AND LEARN FASTER.

6. If you're not already familiar with personal coaching principles, get yourself some training ASAP. IMHO, coaching style leadership is the only method that produces results with knowledge workers. Learn to ask powerful questions like, "How might we _____?" Books by Tony Robbins are a solid start if nothing else, but it's best to go experience some form of instructor-led training on how to BE a coach. It's a Way of Being, not a set of techniques. If that doesn't make any sense to you right now, it will once you've been properly trained.

Best of luck!

I highly recommend looking at Kanban sprint method. Although this is traditionally for Dev roles, having a regular cadence with your team to streamline objectives onto a single pane of glass is a great place to start. Facilitate these meetings and learn about agile and scrum. Build out kanban boards to align with key performance indicators derived from the executive level.