Engineering centric software organizations are often too immature and remain prevalent today. Some organizations have no use at all. Existing is enough, especially for a niche product with no real competitors.
Yet for other companies, employees believe they’re doing enough work because they do an occasional user interview or usability test once a year. These organizations think they’re doing enough, but usually suffer low UKCS maturity. Now, the first step to fixing a problem is to realize that it exists. So here are five telltale signs to help you self-diagnosis low UKCS maturity. First, you need to explain the difference between visual design and interaction. Design will do the design and you make it pretty is a common misconception of people who work in organizations with low UKCS maturity. This mean the skills related to design strategy, interaction design and visual design are unclear. Second, usability testing is Dunlea and on only working designs, never on prototypes. In these cases, people may do user research, but only just before or after the app or site goes live. Few or no designs are actually affected by the research. Third, you never do field studies. Research in the user’s home office, the street, a car or any other place where users exist are the most telling kinds of user research organizations with high Unix maturity. Do field studies at key times in the project forthe people in design and user research are not invited to product meetings?
Meetings about the product and its customers are often attended by product managers in engineering. But if people in new roles are considered superfluous, that means their ideas and knowledge are not sought in the same way as that of other teams. Fifth, just one or two people are the key to your success at organizations with a high level of maturity, you would thrive without their best UKCS person or that one executive who champions the cause.