1 of 1 people found this helpful
This guide is a good place to start with the process:
But I have a feeling you mean more high-level like what organizational considerations are there? If you have any specific questions, please let us know and we can try to knock them out. Otherwise, here are some high level things to consider:
1. Hardware - Are you using a cloud service? Getting new machines? How upgradable are your machines? Is your company large enough to have a core license with unlimited users or does it make sense to license individual users? Is your server configured for how your users will use it? You'll likely always be fine-tuning this but understanding how you plan to grow and what your needs are, will save you a headache in the future.
2. Organization and structure - things like naming conventions, who has permissions to what, who can publish, who can only see, how many sites and projects do you have, etc. Have defined roles, spaces, and expectations for organization will go a long way towards making sure you don't end up having a cluttered and inefficient server.
3. Maintenance & Center of Learning - How do your people learn what Tableau Server can do for them? What happens when there's a new version? How do you prevent everyone from upgrading Tableau Desktop when you're still in the testing phase for a new version of Tableau Server?
I hope this helps,