loginizer domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/johanrev/public_html/wp-includes/functions.php on line 6131Say hello to the digital age, the age of both analytical and creative trends. To the consumer all is one, product and service is a central experience. Paper has become screens, and the almighty pen the interactions on the screens we use. The big bang of big data was fueled by google and Microsoft alike, with the financial sector now following the trend. New products have started to emerge which challenge the norm in the habitat of ICT. It’s a question of can u adapt to the trend. Can u invest in being first to market or have the edge of attraction. Clients are on top of this game. They expect to be entertained and informed. They were born with television and telephones being the horsecarts of yesterday. They don’t want the cars of tomorrow, they want teleportation, the internet of things and wireless power. Power to the user I say. Power to be empowered and offered a quality experience. ICT say: “hello digital!” Generation Z has arrived.
Way too often I have come across ux designers which are mere tweakers of existing templates. They become voices shouting aristocratic philosophies at skilled and knowledgeable development teams. Wat’s even worse, is that their prototypes may seem to become horror maps to a team that needs confidence when QA keeps luring at them. So what do ux designers need to do.?
*Be a positivity engineer. Face forward, not upward. Humility and action prove to go further than empty promises. We’re not critics, were there to empower a team of awesome people.
*Learn the technology behind the madness and start supporting and problem-solving the UI space for developers by implementation. Learn Java, WPF, MVC and JavaScript. Add a precompiler such as Sass to your lists. Understand web services and component based architecture. In short, have the tools to empower your team at your disposal.
*Be a gentle and subtle disrupter that shows how to achieve the technical result. Don’t just say… do
Mr. Anderson..the code you’re typing is not luminous green, nor strings of pure logic only. Yes, you look at the text, the very syntax you’re typing…more than one shade. Unless your a Cobolt programmer, chances are you’re currently using color codes to distinguish classes, functions, interfaces and variables. The human mind is excellent at processing ideas and handle even the most complex of sums and equations ,but what happens when you hand the brain color is called supercharge. You are essentially handing your mind processing power which is found in its everyday perception. It’s like solid state memory, quick, efficient, instantly accessed. Colors are taught to us since we were kids. Adding a red flashing light to a candy shop ,however does not keep the children at bay. Context is always important. Users need limitations, business rules that help them navigate the rule of law. Understand your users context, what they can or cannot do. Add the brown choc chip cookies in the drawer you want them to go. Guide your user through your UI, As in your USER Interface. You’re working with real people and they don’t always understand what you mean. Why not add a dash of color in-between your views? Take away the gray earth depression ,but don’t add too much of a good thing, it might spoil the taste. Mr. Anderson vibrating colors might take you back to your days in the club, but certainly, won’t land you next coding/UX job. Next time you start up your most famous IDE, check the theming, change to 50 percent gray, supercharge your code and reconsider your UI.
So why should UX be included in the implementation lifecycle? The needs of users constantly change, therefore, products need to change. Institutions such as Google and Apple realize the need for product design within systems. Why shouldn’t the rest of Enterprise? The matter of the fact is that one shoe size does not fit them all. Every product or interface whether administrative or normal, needs to cater for the works of users with different needs and varying business processes. Enterprise is constantly challenged by the fact that users need training to maintain systems. UX challenges this notion of training asking the question: “Is this overhead even necessary?” I’m not saying training can be eradicated, I’m simply asking are we compromising quick delivery for simply researching the very users that use your system? By investing in User Experience you are investing in a company with smoother run processes. Normal information driven websites might attract the information foraging user . Enterprise is however constantly bombarded by the needs of users logging into systems, not to forage, rather to maintain the very works of business. User flow and research thus become the oil that makes the economy of information systems run smoothly. The next question that comes to mind is how do we measure ROI when it comes to User experience and information flow? ROI can only be seen in what I call the Blind Side. The Blind Side is the symptom of well implemented UX. Well Implemented UX goes unnoticed. The opposite thereof is frustrated users and management complaining about not being able to find what they are looking for. Legacy symptoms or should I say systems are infused with these frustrations. By adding UX to your budget you are therefore investing in less frustration ,not prolonging the 1990’s symptoms, but rather creating a future blueprint of excellence.