There really aren't a lot of steps to implement TDE. The design goal is to make this simple and transparent to apps (hence the name). It does impact more than the user database (e.g. tempdb gets encrypted, tlogs are not protected until cycled, etc...) and there are some performance considerations (especially if you are already under CPU pressure) but actual steps to implement are simple. Just make sure you remember to backup the certificate and keep it in a secure location in case you need to restore to a new/rebuilt instance.
The product documentation provides a lot of details on the technology, how to implement, the side effects, how to maintain, etc... Check it out at https://msdn.microsoft.com/en-us/library/bb934049.aspx
If you need to move the TDE enabled database to another instance/server, you do need to backup/restore the cert to the new instance/server. Details documented at https://msdn.microsoft.com/en-us/library/ff773063.aspx
Check the docs out and come back with specific questions. It really isn't complicated to implement. Just remember that it protects against very specific threats. It's not the cure all for database security ills.