Like everything that has to do with SQL and configuration, the answer depends.
If you have a large database, say 10GB, then adding 10% growth would consume an additional 1GB of space, this is difficult to swallow if you have limited drive resources. However, if you find that the database is growing and requesting additional drive space on a daily basis, maybe you should change the auto-growth to 15-20% each time.
The best design is the one where you anticipated the database size from the initial installation and allocated drive space accordingly, however, without years of tracking growth, it is virtually impossible to get this number right from the beginning.
So, it comes down to resources and the current size of the database.
George: You're kidding.
George: Then lie to me and say you're kidding.