Given that Computer Vision is a fast-paced research topic these days, I'd go for a Systematic Literature Review:
A systematic review (also systematic literature review or structured literature review, SLR) is a literature review focused on a research question that tries to identify, appraise, select and synthesize all high quality research evidence relevant to that question.
More specifically, Guidelines for performing Systematic Literature Reviews in
Software Engineering could be helpful to you:
The stages associated with planning the review are:
• Identification of the need for a review (See Section 5.1).
• Commissioning a review (See Section 5.2).
• Specifying the research question(s) (See Section 5.3).
• Developing a review protocol (See Section 5.4).
• Evaluating the review protocol (See Section 5.5).
The stages associated with conducting the review are:
• Identification of research (See Section 6.1).
• Selection of primary studies (See Section 6.2).
• Study quality assessment (See Section 6.3).
• Data extraction and monitoring (See Section 6.4).
• Data synthesis (See Section 6.5).
The stages associated with reporting the review are:
• Specifying dissemination mechanisms (See Section 7.1).
• Formatting the main report (See Section 7.2).
• Evaluating the report (See Section 7.3).
(source: http://www.elsevier.com/__data/promis_misc/525444systematicreviewsguide.pdf )
As you may not need to report the review, you could skip this part. The thing I foresee more useful to you is that this system gives you insights about what you left behind in case you have to go back to study the literature, and it also helps to share the work among your colleagues.
So, for example, once you've determined the conferences to read, the authors to follow, etc. you can start by reading the titles of the papers, that goes to a table. If the title seems promising, then read the abstract, so to another table. Finally you would have a stack of papers you have read completely, so you can write some lines about them in that very moment... and when you have a problem you didn't have before, you can re-read your previous work before searching for a new solution in the wild.