Hey fellow developers! Do you have a preferred term of art for software that:
• has captive users
• is designed primarily for the org’s needs
• can frustrating as long as it works
…versus a term for software that:
• people can choose not to use
• must not be frustrating
• requires user-centered design
There are plenty of terms like “enterprise software” and “consumer software” that come close, but say too much (specifying who users are, biz model, etc). Any terms that capture just the above?
@inthehands "software tools"? It doesn't fit the prevailing pattern but what you describe sounds more like any other tool that org members have to use.
Add comment