Wikipedia:Article maintenance and Wiki-debt

Those in the tech industry industry are familiar with the concept technical debt, that is, that is the increased cost to maintain a system due to choosing a solution that is expedient in the short term without regard for the long-term consequences.

On wikipedia, every article requires maintenance, whether that's updating an article on current events with the latest developments, expanding an article with extra information, verifying claims and sources or finding and removing vandalism from a stable article. While maintenance is always necessary, there are common issues cause by being in too much of a rush to create an article which take a disproportionate amount of time to fix, creating "wiki-debt".

1. WP:BEEF up that first revision. An excessively short stub, particularly if lacking good sources that establish context and notability, can leave ambiguity about the subject and uncertainty over the suitability of the article for Wikipedia. For these articles, members of the community have to figure out what the subject is, look for sources and go through either WP:PROD or WP:AfD. As the creator of the article you are likely to know more about the subject than the editors who are likely to encounter your article and as such will have an easier time finding sources. If you not have a the time or ability to find more sources right now, create the article in user or draft spaces where you can work on it at your own leisure rather than facing immediate scrutiny in mainspace.
2. Signal articles with problems: don't be afraid to WP:TAG an article if you think they have problems and leave a descriptive edit summary if the tag is not self explanatory enough. This will signal the article to other editors who will be able fix the article.
3. If you have found no indication that the subject merits inclusion, don't be afraid to start an WP:AfD discussion. If WP:BEFORE hasn't turned up any sources to suggest that the subject is notable and you have no reason to believe such sources exist, there is no harm in starting a deletion discussion. Don't be disheartened if other editors are able to find sources that you missed, we all have different ideas and access to different sources. An AfD discussion will reach a conclusion and save future editors from trying to figure out if the article is notable.
4. Don't mass create stubs. While on some occasions mass creation of articles can be justified and get community consensus, mass creation of low effort stubs puts an enormous burden on the rest of the community to clean up, the community will need to verify that these articles are accurate and find adequate sourcing for them. On multiple occasions in the past large batches of articles were created based on a faulty understanding of the sources that the community is still cleaning up more than a decade later (see WP:GNIS).
5. Adopt some neglected articles: Wikipedia is decades old at this point with millions of articles, a lot of them about clearly notable subjects, but which have long been abandoned and don't get many edits, these articles don't get a lot of eyes and its easy for vandalism to sneak in an remain un-noticed for months, years or even decades. Consider adding some of these articles to your watchlist to keep an eye out for vandalism, a few articles that get maybe a couple of edit per year won't need much effort to keep an eye on, but will help keep the encyclopaedia safe from vandalism.

• Wikipedia:Reliability of GNIS data
• Wikipedia:Beef up that first revision
• Wikipedia:Try not to leave it a stub
• Wikipedia:Put a little effort into it
• Wikipedia:One sentence does not an article make

• Wikipedia essays
• Wikipedia essays about editing