A holistic view into the state of job execution at a glance
Provide the current state of all jobs executed over a period of time.
Help users identify failed jobs and take corrective actions.
Feature Overview
Design Process
Understanding the problem
Re read the brief and start to break it down to it’s core requirements and begin to think about what we are looking to solve for the user.
Start to gather questions and think of how I can tackle the challenge.
Inspiration
Gathering ideas for main dash interface and listing of job. Thinking about who the user is and what are some strengths of other applications. Now that I have a sense of what the large problems I want to solve for, I begin to look for inspiration of how I want it organized.
Ideation
With fresh inspiration, I will start to rapidly sketch out ideas combining elements and quickly exploring ideas.
Wireframing
Once a I am happy with a solid framework that has been sketched out, I will take it into the Sketch App and begin to block out the design .
Iteration 1
Iteration 2
Iteration 3
Final Iteration
Next Steps
Talk to users to get more insight into what their secondary objectives would be, outside of just seeing what jobs had failed. This could inform they type of sort and filter options to include an possibly what ones to bring to the top of the screen.
Learn from users what they see as importance in information architecture. This could inform weather we breakdown the End of Day / Start of Day reports or if it would be more useful to see the Position / Market jobs.
It was a conscious decision to stay neutral on the branding or style to avoid any derailment of the design. With more time, I would like to explore this more.
With more time I would like to see how this fits into the larger process overall so I could make more informed decisions based on what the user has to do next.
Finally, I would like to get it in front of users and have them test it for feedback that we can than iterate and improve.