7 Comments

Do you think end users will still pick up on this is still a pilot (just called by another name) and fall into the negative behaviors described above. I like to use the term 'early adopters' to identify teams we want to pilot stuff on. We tell them we're coming to them first because they're a 'cut above' the rest of the teams when it comes to adoption and user feedback. Then communicate any limitations and clear expectations around what we want them to do.

Expand full comment

I find the same probability that a participant will assume it’s their role to offer critique when the term “beta” program is used.

I sense there are important considerations - and even a fine line to walk given the reality of how “new and untested” a program is to stay in integrity with potential users - and another, dependent on how much feedback a development team is seeking.

Apple has certainly been successful in the tech field with the term “early adopter” and things like “founder’s program” and “limited release” seem to be compelling for many.

I’d be curious to know what other titles readers have found effective in naming these kinds of new/test programs. Thanks.

Expand full comment