Imagine this: on the account page, a list of related contacts is displayed.
On the related list, clicking the standard New button opens the standard New Contact page. While this works, sometimes you want to minimize the number of fields displayed and/or introduce automation to prefill some fields.
One approach is to create a new Lightning Web Component and then use it to override the New button. However this requires development, which we generally try to avoid.
A second approach is to create a new action button on the account that creates a contact. This works well as long as you don’t need to introduce automation as part of this process. You can then hide the standard New button on the Contact related list.
A third approach is to create a screen flow and associate it with a “New Contact” button at the top of the Account. This is similar to the second approach but allows more customization.
However the last two approaches change the UX. Users need to understand that sometimes they find the New button on the related list, and sometimes they need to find the related button on the parent record. This is not a good UX.
To resolve this, there’s a useful screen flow hack that places a button on the related Contact list and still looks and feels like a native button.
The takeaway
Ever since I discovered this hack, I’ve been using it profusely.