Challenge Summary
Welcome to "IBM Reading Together Wireframe Concepts Challenge". IBM wants to create new application that will give IBMers ability to find books of interest and borrow them from each other. At the end of this challenge, we are looking to see creative ideas, interactions, and user experience -- "wireframe concepts" that will help us to build the real application in the next phase of this project!
This challenge is focused on "wireframe" output and results. Be creative in your wireframes! This is not just about creating a generic wireframe experience. Wireframe a unique user experience for the Reading Together application!
Round 1
Initial wireframes concept for client review
Round 2
All requirements as stated in challenge details with client feedback applied
This challenge purpose is to create user flow for our new "Reading Together" application, this application will be use by IBM employee to lend or borrow books from their colleagues. Check more details below for more information regarding the apps scenario needed to be create in this challenge!
Application Scenario :
1. Application user needs to login using their IBM credential before able to use the application. Provide error scenario when user input wrong credential or incomplete information. Please note that you should not include any sort of "forgot my password", "sign up" or "remember me" field -- these will not be supported. Only "Intranet ID", "Password" and "Log In" button needed
2. User can act as a lender or borrower in this application, depends on what kind of action they want to do in the apps. There should be some dashboard contains summary of important information, such as the list of books I've borrowed / lent. For gamification, think about whether we want to list somewhere the # of books in the system, who has listed the most books, who has lent the most books, etc...
3. If user act as a lender, they can do the following things :
- As a lender, user can create list of their books that they want to share with other IBM employees, each book needs to have their own information entered by the lender (title, author, keyword, book image, etc), and give their current location.
- As a lender, if other user (borrower) contacts me, we work out the exchange "outside of this app" (e.g., a phone call). When the borrower borrows the book, I mark it as "checked out", and I put the borrower's name (gathered via list), so that I know who has my book.
- As a lender, user should be able to check borrower profiles from the apps.
- As a lender, when a borrower returns a book, I can mark it as "checked in".
- As a lender, user should be able to set the time constraint for book's availability, e.g., I'll lend this out for 90 days?
- Since we have a property of book availability, if the book was not lent out, it is still available except for some reasons (moved, lost, damaged, lent out but not change the status...). Anyway, the borrower can check with the lender. What is your thought?
4. If user act as a borrower, they can do the following things :
- As a borrower, user can search for a book by name, author, or keyword, and see a list of books, along with where they are located (per where the lender is), and the availability of each book (e.g., which ones are already checked out).
- As a borrower, when I find a book listed, I can view the details for that book (who the lender is, where they are located, availability).
- As a borrower, if I find a book that I want, I can contact the lender, and ask them if I can borrow their book.
- As a borrower, I can see which books I have checked out (associated with my name).
- As a borrower, I need a way to say not just my location, but also how far I am willing to travel to get a book. Note that my default location is known in the corporate directory, so I should be able to just say "OK" when shown the location, unless I want to enter something different.
5. On User profile, user can see a number showing how many books they've listed in the app, how many the've lent, % of books returned (counted 90 days after checking out). Anyone can see this information when they see my name in the app (which may mean that each person has a visible "profile" in the app). We want to record user's history for future analysis like users clustering based on the user's borrow/lend history.
Main Features of the apps :
- Search for a book by name (or topic)
- List my books, along with keywords
- View all books matching a search, by distance
- See which of my books have been "checked out" and by whom
- See books in my current location or city
- Check out / check in of the book status
Branding Guidelines
- We are looking a clean wireframe designs, and clear wireframes interactions.
- Create your design for mobile devices, user iPhone 5 ratio when create your wireframe!
Wireframe Expectations
- Produce HTML click-through wireframes that can be used to demonstrate all mentioned functionalities as required in each round.
- The apps flow must be very easy to use and intuitive. Keep that in mind when create your solution for the layout and flow information.
- You MUST cover all requirements mentioned in challenge details below.
- Use note pane in every single page you design to explain what items are addressed in that page from the documentation, what things you added/changed/removed, use it to make your idea clearer and help the client to give you constructive feedback.
Target Audience
- Client Internal Employees
Judging Criteria
Your submission will be judged on the following criteria:
- Wireframe Concepts! Did you try or suggest something new?
- Completeness and accuracy of the areas of functionality and content
- How well your wireframes provide a consistent user flow and clear information architecture for the application
Submission & Source Files
Preview Image
Create your preview image as one (1) 1024x1024 JPG or PNG file in RGB color mode at 72dpi and place a screenshot of your submission within it.
Submission File
Generated HTML files with all the requested contest requirements stated above.
Source Files
Wireframes should be built in Axure. The resulting files should have generated HTML files. Also, all the content must be listed and the pages are linked together to show page flow.
Final Fixes
As part of the Final Fix phase, you may be asked to remove, update, or change some features of the wireframe.
Please read the challenge specification carefully and watch the forums for any questions or feedback concerning this challenge. It is important that you monitor any updates provided by the client or Studio Admins in the forums. Please post any questions you might have for the client in the forums.