{"id":111,"date":"2010-08-05T08:08:36","date_gmt":"2010-08-05T08:08:36","guid":{"rendered":"https:\/\/portfolio.cherylplatz.com\/?p=111"},"modified":"2021-05-18T23:01:09","modified_gmt":"2021-05-18T23:01:09","slug":"system-center-concept-car-2010","status":"publish","type":"post","link":"https:\/\/portfolio.cherylplatz.com\/?p=111","title":{"rendered":"System Center “Concept Car” 2010"},"content":{"rendered":"

In 2010, we set out to explore a unified approach to the most complex IT processes – software deployment and incident management in large networks.\u00a0From initial scenarios and paper sketches to high-fidelity prototypes, videos, and user testing, we used this “concept car” as a vehicle for exploring the impact of large screens, multiple product integrations and new approaches to object manipulation in a server environment.<\/p>\n

Our work was very well-received by our stakeholders and served as the inspiration for a number of concepts that made it into future design patterns and products, all the way through Azure’s initial release.<\/p>\n

Design Inputs<\/h1>\n

We began the process with a few early concepts from another designer on the team. Together, we worked to build the scenarios around which we’d rally for a far deeper, end-to-end series of explorations.<\/p>\n

Behind our work on these designs was an underlying hypothesis that our users only focus on a few tasks at once, that evolve over time. Rather than exposing long lists, expose frequent and recent objects and use the extra space for visualization and manipulation.<\/p>\n