How many work trackers do we need? At my last job we a number of them doing small pieces. ServiceNow for ticketing, bastardized JIRA for bug tracking and agile tracking, planview for tracking hours to projects/initiatives, and another 2 Visual Task Boards that my team didn’t have the displeasure of using thankfully. Sharepoint and Workday were mixed in for tracking edge case organizational stuff.
Tables: Tracking work for teams
61–70 of 375 posts
Re: Tables: Tracking work for teams
#62Interesting that they would launch this as a totally separate product and not as a part of G Suite. Do you think they want to create some distance between them and the rest of Google because ofd Google's reputation of shutting down products? Or maybe they want to launch a product outside the usual bureaucracy?
"At Area 120, we work on 20% projects 100% of the time." It literally just has no backing by Google's corporate or business goals.
> "At Area 120, we work on 20% projects 100% of the time."
I laughed at that, at first, thinking it were a joke.
No, no that's a quote from https://area120.google.com/
Re: Tables: Tracking work for teams
#63[deleted]
Re: Tables: Tracking work for teams
#64The following is a sarcastic joke. Probably prescient.
---------------
NOTICE
Tables will be sunset starting 1 november 2022. From that date and onwards Tables is read i ly and you may export your data. January 31 2023 Tables will be shutdown and your data abd instances will be unavailable from here on.
Re: Tables: Tracking work for teams
#65You know Google has a serious credibility problem when half or more of the comments on tech sites covering product launches are questioning when Google will decide to randomly pull the plug.
The opposite end of this spectrum is a company supporting far too many different properties like Yahoo did. How do you strike the right balance?
A good argument for being careful adding new products.
Re: Tables: Tracking work for teams
#66Interesting that they would launch this as a totally separate product and not as a part of G Suite. Do you think they want to create some distance between them and the rest of Google because ofd Google's reputation of shutting down products? Or maybe they want to launch a product outside the usual bureaucracy?
It's the reverse: GSuite products have a mandatory minimum level of support (and integrate with the Suite). Area 120 is for standalone products that have zero promise of support.
Re: Tables: Tracking work for teams
#67Earlier quoted context omitted.
"At Area 120, we work on 20% projects 100% of the time." It literally just has no backing by Google's corporate or business goals.
To be fair, does that mean anything?
It means that the PM cares less about the users than the PM for a 100% time Google product cares the users, which is already very little.
Re: Tables: Tracking work for teams
#68You know Google has a serious credibility problem when half or more of the comments on tech sites covering product launches are questioning when Google will decide to randomly pull the plug.
They don't care. They're revenue is from ads. If they get a bump in revenue from gleaning information off of Tables (tm) to display relevant ads to you for the year this will be active, then maybe it was worth it.
Re: Tables: Tracking work for teams
#69You know Google has a serious credibility problem when half or more of the comments on tech sites covering product launches are questioning when Google will decide to randomly pull the plug.
It seems like 80% of these projects are pet projects by VPs so they can launch a Google project for their career or Google can keep them from leaving for Facebook.
Re: Tables: Tracking work for teams
#70I'd be extremely wary of adopting any new Google product given their tendency to abandon things that don't achieve immediate success.
This comment seems to top any HN post regarding a google product launch so reliably that perhaps there should be a bot which automatically pins it to the top.
A more useful bot would be one that finds and deletes that inevitably-posted noise.