Working through problems and solutions for business intelligence management
A big German enterprise approached us because they needed a solution to manage and provide access to the huge and growing collection of business intelligence resources that are built internally. We got invited to a four-day event where we could work through a design sprint and show a first draft of what a solution could look like.
The goal of this design sprint was to give us insights into the company context and problem details while the client could observe our UX approach and let us compete against other invited teams for the project.
- Stakeholder interviews and result sorting on sticky notes
- Workflow mapping and user goal extraction
- Identify areas for improvement
- Select areas to focus on with stakeholders
- Ideation and sketching
- User flows and wireframes
- Mockups and prototype
- User testing
- Feedback sorting and possible next steps
- Running a four day design sprint can be a very effective way to get a kickstart with a problem space. It yields very fast results that might not be optimal but will certainly create a better understanding. From here you can test and iterate.
- A good portion of the available time is not spend ideating and designing. It can be scary to push what feels like the core work of a project so far back. But trusting the process and taking the time to define and work with problem never failed me.
- A design sprint executed as a try out for a longer project for a big client at Cognizant.
- 4 days
- Used skills
- Design sprints, user interviews, sketching, Sketch, InVision
- Division of work
- I went through the sprint as a two-people team with our Head of UX