A decent portion of any designer's knowledge will probably come from blogs, videos, and content created by others. This is no bad thing as each person is limited in what they can work on and by sharing learnings we can all benefit from each other's experiences.
In recent years many companies—from startups to big corporations—are good at writing up what they've discovered in the process of researching, designing, developing, and launching their products. Often they can be useful for preventing you from making mistakes that others have already made. However you do have to exercise caution as not all content is created equal and you can use this learned knowledge inappropriately.
There are obviously several types of content but I’m referring to those that describe a recommended design, a successful experiment, or offer guidelines that you could cite as evidence for making a design decision.
This is one method where there’s no specific process. You can build an RSS feed; create a list of trusted sources on Twitter; sign up to a selection of mailing lists; subscribe to podcasts or Youtube channels; even subscribe to magazines (very old school). Whatever your method, by setting up a regular content delivery mechanism you save yourself from going hunting for it and it instead finds its way to you.
I'm a big fan of the serendipity of Twitter and the chance to get content from publications you wouldn't otherwise look at in your stream. The content on there is also very current but the downside is you'll have to sift through a lot of noise.
When it comes to the content itself, there are some things to think about before deciding whether to apply the learnings to your product or company. You don't want to go telling everyone in your company you should do something and citing an article as evidence if it doesn't apply to your situation.
How solid is their evidence for what they are recommending? When blogs make big claims about how they 'increased conversion by 50% with one simple change' it's always worth asking how they measured that before rushing off to apply their findings. You may not get the full raw data due to privacy concerns but you should be able to get a sense of it.
Were their results from a focus group of 5 people in their office, or was it done as an A/B test with tens of thousands of users? If the former, take with a heavy pinch of salt and if the latter you might decide it's worth looking into. It doesn't just have to be based on large sums of quantitative data, if it has been learned through several rounds of user testing, that is also high quality research.
Is the business recommending this change in a completely different sector, do they have a different target audience, or are they at a different stage of growth to yours? If so then what they describe may not apply to your product at all. A video from a startup aimed at millennials that describes the perfect mobile navigation may not apply to enterprise software for the financial sector.
Plenty of companies just share what they've learned as a matter of giving back to the community but you'll come across some articles that are actually companies trying to push their software or service. In which case their software usually turns out to be the perfect tool for the job or the hero of their story. It's usually fairly obvious but can be done subtly using paid writers on third party sites.
Generally be very wary of content that makes broad sweeping statements about one design being better than another. I've lost count of the number of people who have asked me what the best colour for a button is because they read that "green increases conversions". Of course there is no such thing as a 'best colour' for conversions as it is going to depend so much on where it is positioned and the colours used around it.
Ultimately there are so many variables that it's hard to carry across statements about what would work on your site. But this doesn't mean you shouldn't keep reading, watching, listening, and getting inspiration for ideas.
One tool that is highly useful for getting through lots of articles is Pocket. Install the plug-in on your browser and the app on your phone then when you come across something interesting you can easily save it to a list on the app for you to digest a quiet moment.
Reading an article doesn't tend to take long – this is something you can dip into at any time.
The following websites feature generally well-researched articles, useful for UX decisions: