FIT - Ideation Feature in Workspace Module Design Challenge

Welcome to "FIT - Ideation Feature in Workspace Module Design Challenge". In this challenge, we need your help to create new features in our FIT application under the workspaces module where it can be used to collect ideas from stakeholders.

Read the challenge specification carefully and watch the forums for any questions or feedback concerning this challenge. Let us know if you have any questions in the challenge forum!

Round 1

Submit your initial designs for checkpoint feedback
01) Ideation Feature in Workspace Module 

• As part of your checkpoint submission, you must upload your submission to MarvelApp so we can provide direct feedback on your designs. Please include the MarvelApp URL in your notes.txt
• Make sure all pages have the correct flow. Use the proper file numbers, (1, 2, 3, etc.)

Round 2

Submit your final designs with all checkpoint feedback implemented
01) Ideation Feature in Workspace Module

• As part of your Final submission, you must replace your checkpoint submission with the final submission into MarvelApp so we can provide direct feedback on your designs. Please include the MarvelApp URL in your notes.txt
• Make sure all pages have the correct flow. Use the proper file numbers, (1, 2, 3, etc.)
• If you're not submitting in the Checkpoint/Round 1, you are not eligible to submit in the Final/Round 2

CHALLENGE OBJECTIVE

• Create new UI screens for our FIT application to accommodate the new Ideation features that will be put under workspace module
• Need to STRICTLY follow the FIT application design style elements

BACKGROUND OVERVIEW

• The FIT application is a tool that is used by our business and IT users to identify and assess high-level project scope - starting with customer experience, defining capabilities and features for delivery, and estimating the size of the impacts and determining the teams who will do the work
• One of the modules that we have in the FIT application is called "Workspaces":
  • Workspaces are designed to help Product Managers and their IT counterparts to use our Journey and Capability model as a "Common Language" for collaborating to identify scope items and sequence and group them for delivery
  • One of the key benefits of the application is the ability to document Customer Experiences ("Journey Flows" in the app) and then use them as a key input to identify broad-based impacts and determine how to best deliver the work
  • In the past, a Workspace was tied to a specific, one-time identification of scope (3-6 weeks). Once that scope shipped to our delivery tools, the Workspace was marked "Complete". In the future, we want the Workspace to be more of a long-lived construct that Product Managers use to manage their product, their customer experiences, and to ideate on and identify items for their product backlog
• Due to the nature of workspaces function, it is necessary to have ideation feature for the following reasons:
  • In the past, most of the functionality in the Workspace has been completed by people from IT, eliciting input from Product Managers. We want to encourage Product Managers to use the FIT directly, using a single Workspace where they will elaborate Journey Flows and maintain them for the life of the Product (potentially years, rather than weeks).
  • We need a less "intimidating" place for Product Managers to start than Journey Flows, or even Product Scope. It needs to be a place where people can start to enter ideas at whatever level of detail they have, then gradually collect more information, match them up against impacted Journey Flows, determine impacts, identify scope items, prioritize those items for delivery, and ship them to delivery tools
  • The Ideation feature is intended to provide a place to capture semi-structured information, with the ability to add structure to it by way of global and workspace tags, Business Architecture elements, and the ability to add more detail as it comes available
  • The intent is that a Product Manager could readily use Ideation (with a customizable Kanban) feature, plus the existing Product Scope, and Journey Flow features to manage and understand their Product, and identify which Ideas to move forward. This interaction would be non-linear and iterative, so that the user would not need to complete one before moving to the other. Information generated in all three places would "add to" the Product Managers understanding of the Product.
  • Capturing Ideas from Product Managers in one place will also help us to "connect the dots" by enabling OpenSearch on top of the data store, thus enabling discoverability of different Product Managers who might be working on similar or overlapping ideas

PROJECT GOALS

• The goal of this challenge is to create new UI screens for ideation feature that will be added into workspace modules within FIT application

TARGET AUDIENCE

• Product Owners, Product Managers, and their IT partners.

SCREEN REQUIREMENTS

01) Ideation Feature in Workspace Module 

• For more details about the existing application, please refer to the "Screen References" document.  
• User will need to login in the FIT application and open "Workspaces" module in FIT application (check image 01 to image 04 - existing flow and no update needed)
• Once the user opens one of the workspace details screen, then we can add the experience for ideation feature. It should start from within the existing FIT navigation. It seems to make the most sense to add a button in the FIT header (similar to Content Map and Product Scope) that opens a dedicated experience for Ideation. To accomplish this, we would likely have to optimize the existing buttons to a more narrow width to include the Ideation button (Please refer to image 05 for references)
• After user click the "Ideation", the dedicated experience for ideations feature will start (Image 06 to Image 09) and user will be able to:
  • Collect Ideas with as much detail as stakeholders wish to/have available to enter - parent idea with multiple child memos, links, screenshots, etc.
  • Assign Ideas to specific users to work on
  • Identify Idea dependencies and enable business value assignment (component of WSJF - Weighted Shortest Job First) - Focused on considering "value" for each scope item identified. One way to do this is by assigning "value" in some way in the ideas module, carry that through, and associate "cost" in the estimation module. We could then apply some formula to help users determine which items are "most valuable for the least effort".
  • Tag Ideas using Common Language elements (Business Dimensions, Journey Model elements, Business Capability Model elements, etc.) filtered by Product Scope + global and workspace tags (References: Image 10). Note: Common Language elements (Business Dimensions (BD), Journey, Business Capability Model (BCM) )  are each hierarchical data forms. 
  • Kanban-style views for drag-and-drop, flexible viewing and grouping of Idea cards into columns that can be configured to reflect global or custom tags
  • Save multiple Kanban view column configurations within a workspace to enable shared viewing experience
  • Enable discovery of related Ideas currently being worked/elaborated (c.f. OpenSearch) - The implementation of OpenSearch will be done by extracting all of the Idea and Journey Flow data and enabling search across all Workspaces. We have a dev internally who handles adding new items into the OpenSearch index. In this context, this could potentially look like allowing the user to actually search the entire repo for adjacent topics. And it could also look like a mechanism for using search in the background to find/suggest similar topics for the user to view. We did something similar to this with Journey Flow creation.
  • HTML and PDF output and Excel extracts - show preview as well 
  • We will need a simplified Mobile UI (mobile web) for this feature to enable frictionless submission of ideas by business stakeholders (OUT OF SCOPE for this challenge)

CHALLENGE FORUM

• If you have any doubts or questions regarding challenge requirements, please ask in our challenge forum

DEVICE SPECIFICATIONS

• Web/Desktop: Follow screen size from our XD files

DOCUMENTATION

• Design Source Files:
  • Use the source files in this folder as starting point to create your design creation so you don’t have to start from scratch
  • Please refer to the screen references document to see the “workspaces” current design and build the design based on that UI appearance 
  • You might want to use the “FIT FF.xd” as the starter, it shows a good example of our current design and carrying the design forward to include high-fidelity mockups and a refined aesthetic
• Screen References

BRANDING GUIDELINES

• Follow our existing FIT design style!

JUDGEMENT CRITERIA

• Creativity: Impactful - the solution is different or unique from what is already out there and can be implemented
• Exploration: Flexible - follow the provided screen requirements section and propose improvements or different paths that positively impact the user goals
• Aesthetics: Hi-fidelity design - provide a top-notch finished looking visual design
• Branding: Strict - carefully follow the provided guidelines and stick to them

MARVEL PROTOTYPE

• We need you to upload your screens to MarvelApp
• Please request your MarvelApp prototype in the respective thread in the challenge forum
• You MUST include your Marvelapp URL (in your marvel app prototype, click on share and then copy the link & share it with your notes/comment this link while you upload)

FINAL DELIVERABLES

Submission File

• Submit JPG/PNG image files based on Challenge submission requirements stated above
• Declaration files document contains the following information:
  • Stock Photos Name and Links from allowed sources
  • Stock Art/Icons Name and Links from allowed sources
  • Fonts Name and Links source from allowed sources
• Full Details of the Topcoder Policy can be found in this LINK

Source Files

• All source files of all graphics created in Adobe XD (Client recommendation), Sketch, or Figma and saved as an editable layer

FINAL FIXES

• As part of the final fixes phase, you may be asked to modify your files, add or remove screens or combine details to create a final presentation