I said a lot about designing for users. We have to observe how people behave, the steps they take, and the steps they refuse to take. Then we create an environment, or a tool, that matches that behavior, that complements that behavior, so they can achieve the things that we need them to achieve. Now, when they come in, they log into the app, log into the traditional tool, whatever it is that you use. As they arrive, you have the welcome screen. What is on your welcome screen? Is it, “Hey, welcome to…”? Do you have options that they can take? Do you have an area that shows them what the next thing is? Because you need to orient them. You need them to know what they are doing next. They probably have daily activities that they carry out. You have that on the screen telling them, “This is what you’re going to do today. This is the action that you’re in charge of.”
Now, moving on from that, what do we have next? We have the action. They act. Then you look at the decisions they take while carrying out that action. What are the activities? What are the steps? What do they do? You have to understand all of these things, and then you build a step-by-step process that properly complements them. It confirms that the action has been completed. Then you send them a confirmation, whether through the app or through email, letting them know that the action has been completed. You provide the next steps for them. When they come in, they should already have a clear overview of what they should do. Which is why it’s good to keep things simple. You do not need to overwhelm them. You have your spaces, you have your pages, and then you prioritize them. Clearly state that this is the first action that this team performs every day, so we want them to see this immediately whenever they log in. Then you have the secondary actions. These are the things they typically do after completing the first action.