- You can show conventions. Show that the icons / process / terminology are the same as other well-known and well-used features in other apps. - You can show s

- You can show conventions. Show that the icons / process / terminology are the same as other well-known and well-used features in other apps. - You can show statistics. # of people using it, or, if you really want to entertain alternatives, A/B testing results. It sounds like your service isn't live, so if this is important, hammer out a prototype and get some test users. If it's not that important, propose to do A/B testing when its released. - Figure out the end goal of the process, and ask a number of non-technical people (at least 20) to describe how they'd setup a process that would accomplish it. Do a significant number of them match your process? Do a significant number of them match each other? - Examine all the knowledge you assume a user has in order to go through the process, from the very basic (the button is clickable, "domain" means the URL / web address of a site.) to the more complex (you can undo any changes you make by viewing a list of revisions and rolling it back, clicking 'save' saves content but doesn't publish it, a 'dashboard' is an overview of account activity & a jumping-off point for site actions). Ask test user questions to determine how common the knowledge you assume actually is.