Should I explicitly define my data touch points in a SSIS ETL

So we have written our T-SQL...tested it...and the .csv looks fine. But we DID NOT explicitly define our data touch points...just took what was in the database. In an ETL exercise, does best practice kind of dictate NOT to leave data to chance and explicitly define your output data touch points? Through a CONVERT.