Agreed that this rollout process is exceedingly confusing, opaque and, most distressingly, hyped in main stream press well in advance of release. So, here we are as admins, trying to answer stakeholder questions about how to use Lists (or the new Tasks app that is also supposedly rolled out but totally MIA on our tenant) or why we don't yet have it in our tenant. It makes us look stupid and impotent.
There are significant limitations to Lists as rendered in Teams, like complete lack of functional search...don't let your lists get long, folks...limited views and absence of many features highlighted in the various rollout videos MS teases us with. We already have power users trying to use Lists for critical tasks, and I can't even determine yet whether it's a functional fit for our organization.
A few suggestions, Microsoft:
- Never hype as "available" services that aren't available to most tenants.
- Provide clearer timelines for how new services will be rolled out: Information about what features to expect in what order and time frame should NOT be delivered by peers making suppositions based on anecdotal experience.
- Never release a product whose content cannot be searched within the container in which it is presented (e.g., Teams wiki, Planner/Tasks, Lists, etc.)
- For the love of God, stop with the branding merry-go-round (I'm looking at you, new Tasks, app...or are you Planner, or Tasks by Planner, or Tasks [which is somehow distinct from the current implementation of Planner]). Kick marketing out of the room when you make these decisions; land on a good name and stick with it. Make sure it doesn't clash with names of existing services. This isn't rocket science; it's astounding you're still THIS bad at it.