As a DBA define a view on each primary table where the foreign keys are expanded to names and descriptions.

Example the Product table has a column ProductTypeID that is a foreign key.

In the vProduct view instead of ProductTypeID, you put ProductTypeName from the ProductType table.

The result is that select * from vProduct will produce a readable output just like a denormalized table would.
The convention is easy to remember: just place the v prefix in front of the table name.

A frequent complaint of the developers is too many joins in a 3NF database.

As a database architect you can address this issue by combining lookup tables into LookupEntity and Lookup tables.

As a DBA it is your duty to educate developers. Point out that a properly designed database is critical to the success of business applications.

Normalized database designs are much easier to code against, and they make it much easier to accommodate the business requirements of the user community.