The current timezone set in the users profile is driving labeling and binning of time data.
For teams working across multiple timezones with audiences across the same I see three features we could benefit from
filtering by timezone,
timezone normalization, and
binning/labeling for a selected timezone.
For filtering
Given that timezone data is collected with the timestamp data from the different sources (or derived by country of origin etc), offer an option in the filtering menu under Demographics to select a set of timezones to filter by.
For normalization
Given the same as for filtering, offer an option in the filtering menu under Demographics to normalize the timezone to more easily analyse hourly trends (figure if audience is Tweeting while drinking the morning coffee, difference in comments during work hours vs off hours, etc).
For binning/labeling
The displayed time of day and binning of which day a post belongs to depends on the current timezone setting of the currently logged on user. This will lead to different statistics displayed for different team members (ie. a member in US will see a spike on the 10th, a member in Japan will see a spike on the 11th, while a member in UK will see a smeared spike over both 10th and 11th) potentially causing confusion in discussions and reporting of observed metrics. This could be solved by offering a "current" timezone selection next to the filters menu, and/or specifying a locked "current" timezone for a specific search, overruling the user setting.
Guest
