Currently, I am (successfully) cleaning out my GMail account, but while having achieved "Inbox Zero" (but not "0 Actionables"), my subfolders / labels are still overflowing.
One issue I have: I was quite involved in / occupied with at least two software programs, that I used or still use daily and intensively, both for my studies as well as work.
As I'm rarely content with even a top-notch program and tend to find a lot of bugs, productivity-impeding issues and just in general have ideas and feature requests, I started sending feature requests on a weekly, sometimes daily basis!
As a result I have several (long) drafts as well as a ton of sent as well as unread e-mails to and from the software developers. But to be frank, in the last 6-9 months I have never looked at those e-mails, neither those from the company nor mine.
Please see this screenshot as an example:
All I know is: Obviously not all (i.e. most) feature requests of mine won't be implemented or I am not able to get an ETA for it. Most of all, software organizations seem to not be willing or prepared for keeping their power-users updated, i.e. I have no way to know and follow-up on my feature request. Which drives me crazy - maybe I'm a control freak... Second problem is that the versions of those products have already iterated. I.e. for both software concerned here, there are already new versions out. I frankly cannot keep track of which changes are implemented yet and which aren't. Because I don't get paid to do so and don't have all the information available that the software company does. But those companies don't share such information with a customer, thus I'm at the bad end of information asymmetry.
All that ain't so bad though, but my problem is: What do I do with all these e-mails? Read and archive? Delete? Try to comprise notes and actual results as well as actionables out of them? (Even though that should be the company's duty not mine?...)
All in all I definitely don't want to keep (those) e-mails if not necessary.
So the question now is: What is the best way to deal with these e-mails, if you consider my initial intention and the general goal of getting through those as fast as possible.
The tricky part here is, that those are not clearly actionable via GTD imho, because to have a clear "action-path", I would have to define one in advance. Which is what I ask about here. Because frankly - myself - I don't know if it is worth the time and effort to further process all these e-mails, if I consider the average probability that:
a). My feature request gets accepted b). My feature request gets implemented or c). my feature request is already implemented (i.e. I could've discarded the e-mail conversation about feature XYZ, I just didn't/don't know, because I lack the information that feature XYZ is implemented, until I invest further energy to confirm that it is).