Zetas Product Lifecycle Pipeline UI Design Challenge

Welcome to the “Zetas Product Lifecycle Pipeline, UI Design Challenge.” In this challenge, we would like you to design a UI for a Microsoft PowerApps application for Zetas employees. This application should allow them to efficiently collaborate and manage the project details for creating new insurance products.

Designs MUST follow Microsoft PowerApps platform best practices. Please do some research on the PowerApps platform and get familiar with its purpose, limitations, and possibilities.

CHALLENGE OBJECTIVES

• UI Design for approximately 10-12 screens, desktop
• Ability to implement as a Microsoft PowerApps application built as a Canvas app
• Intuitive workflow to create a project and manage project details

Round 1

Submit your initial designs and any notes you might have for checkpoint review.

1.0 Home (landing screen)

• 1.1 My Work

2.0 Project Creation (multi-step workflow)

• 2.1 General Project Information
• 2.2 Workstreams
• 2.3 Tasks
• 2.4 Objection Assignments

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 initial designs plus checkpoint feedback implemented for the final review.

1.0 Home (landing screen)

• 1.1 My Work
• 1.2 All Projects

2.0 Project Creation (multi-step workflow)

• 2.1 General Project Information
• 2.2 Workstreams
• 2.3 Tasks
• 2.4 Objection Assignments

3.0 Project Summary Display (view)
4.0 Search Results (view)

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

BACKGROUND:
Zetas is a large company in the insurance industry. Projects are executed internally to create new products for their customers or partners. To manage these projects, several teams within Zetas collaborate, provide the necessary details, identify dependencies and plan accordingly. To assist with collaboration, a PowerApps application has been built for the teams to enter the relevant information around projects, workstreams, tasks and sub-tasks. 

Currently, there are several layers to this application. It consists of 4 primary SharePoint lists of data and 1 SharePoint document library. During the journey of capturing project-related information, users are frequently required to navigate between the Sharepoint site and PowerApps. This results in views of multiple tabs and an inconsistent user experience. The Zetas team plans to build a single Microsoft PowerApps application to replace the current mix of multiple PowerApps.

GOALS

• A cohesive design that maximizes efficiency with a modern user experience.
• A single Microsoft PowerApps application to replace the current multiple PowerApps.
• Provide an experience that facilitates limited user interaction with the underlying SharePoint site.

DESIGN EXPECTATIONS

• New and fresh UI Design solution. DO NOT copy the arrangement and workflow from the sample screens. We are looking for an improved user experience.
• The solution must be achievable within the technical feasibility and implementation constraints of Microsoft PowerApps platform as a Canvas App.
• Note: You are expected to research and align your design with the UI and functional capabilities of PowerApps. Some reference sites:
  • https://docs.microsoft.com/en-us/windows/apps/design/
  • https://www.youtube.com/watch?v=jOAJW7RPw0Y
  • https://powerusers.microsoft.com/t5/Community-App-Samples/bd-p/AppFeedbackGallery
  • https://office365atwork.com/power-apps/powerapps-examples/
• The application should include a navigational menu including access to:
  • The user’s My Work and All Projects views
  • All components of a project with the ability to view, edit or create new.
  • Search element and results for finding items
• The design should be flexible enough to handle future additions/deletions of fields with minimal redesign.

GLOSSARY

• Underwriter = A professional who evaluates and analyzes the risks involved in insuring people and assets.
• Workstream = A defined portion of a larger project.
• Objection Assignment = A sub-task that is created in the project as a result of identifying an issue or problem with the product.
• Jurisdiction = A geographic area (i.e. state or territory)

AUDIENCE
Internal teams who collaborate to maintain project information and processes.
A user who logs into the system will have access to all projects.

PERSONAS
Jamie Dias, Insurance Underwriter for Zetas

USER WORKFLOW
Jamie opens the PLP application to see a landing screen with a view of their “My Work” screen.

• Views 25 projects on which they collaborate, grouped into Open and Closed projects. From these projects, Jamie is able to see the workstreams and tasks that are active and assigned to them.
• Also has the ability to switch views to see All Projects.
• From either view, Jamie is able to sort and filter the displayed projects so that their desired project(s) can be displayed and managed.

Jamie chooses to create a new project.

• Enters basic project information into the form fields provided.
• Then proceeds to enter some of the project’s workstream information with related details and tasks.

Jamie returns to the My Work landing screen and selects one of the open projects they are working on.

• They view a summary of the workstreams and tasks that make up this project. Jamie is able to understand the state of the project at first glance - what tasks have been completed and other details about the project.
• Jamie selects to edit the project in order to add task information to one of the existing workstream tasks.

SCREENS / FEATURES REQUIREMENTS
Reference for screen content: PLP-samples-current.pdf. Labels and field types for each screen can be found as noted below.

0.0 Global Elements

• Placeholder Logo for Zetas
• Application Title: Product Lifecycle Pipeline
• User ID / Login

1.0 Home (landing screen)
They will have an option to see two different views of projects in the system. From either view, the user should have the ability to:

• Filter and sort the projects displayed
• Create a new project
• View a summary and the details of an existing project.
• Edit / Add to an existing project
• Search to find a specific project to view or edit

1.1 My Work
This default view should display the user’s My Work subset of projects. These projects are those that the user collaborates on.

• My Projects: By default, projects are grouped by Open vs. Closed projects, sorted to most recent.
• The user should be able to see high level details for each project: Project Title, ID#, Project Manager, Project Status, Project Open Date, Target Effective Date, link to the project.
• Average of 20 projects per user
• Regarding the Open projects, three additional areas of content should be surfaced that pertain to the user. These areas should surface the most recent items. Provide a link to See All for each group.
  • My Workstreams - User should see: Workstream Link, Project ID, iTrac Links, Project Link, Title, Workstream Type, Workstream Status
  • My Tasks - User should see: Task Link, Task Type, Project ID#, Project Link, Project Title, Title, Task Status
  • Work I Assigned - User should see: Task Link, Task Type, Project ID#, Project Link, Title, Task Status, Task Assignee

1.2 All Projects
This view should include all projects available in the system.

• Total of approximately 1300 projects
• By default, projects are grouped by Open vs. Closed projects, sorted to most recent.
• In this view the user should see high level details for each project listed: Title, ID, Project Status, Project Manager, Requestor

2.0 Project Creation (multi-step workflow)
When creating and managing a project, collaborators will enter data to fill out multiple tiered sections of project information. In your solution, the process to complete these sections of information should be arranged to allow an intuitive and efficient workflow for the user.

Project Data Structure:
Project > Workstream(s) > Task(s) > Issue Objection Assignment(s) a.k.a. sub-tasks
A project will include general project information: Project Attributes and Jurisdictions/Companies.

• Each project will contain one or more associated workstreams.
  • Each project has an average of 8-10 workstreams.
  • Most projects have 1 of each type of workstream.
  • Projects may have multiple of the same workstreams.
• Each workstream may contain one or more associated tasks.
  • The type of workstream selected will determine the task options available.
  • Some workstreams do not allow any tasks to be associated.
• Each task may contain one or more associated Objection Assignments. 
  • Currently only 3 task types have a sub-task level available.
• Each project includes a folder (with sub-folders) in the document library.
  • The documents reside in a Sharepoint directory. Access to this is NOT in scope.
  • As a project is created and saved the link to this folder would become available.

2.1 General Project Information
Interface to complete all project related details. (all fields PDF Page 1)

• Project Attributes. Includes general information for the overall project. (PDF Page 2)
  • FYI for content samples: Project Title avg. 49 characters (range 6-117). Line(s) of Business avg. 60 characters (5-2000 with multi-select).
• Jurisdictions/Companies. Include various entry fields. (PDF Page 4 & 5)
  • User should have the ability to easily select multiple jurisdictions from each: US States, US Territories, Canada Province, Canada Territories

2.2 Workstreams
Along with the details above, each project will include one or more workstreams. Users will have the ability to add multiple workstreams as they create or edit their project. There are 3 parts to each workstream:

• The General Information section is a common set of fields that apply to all workstream types. This section is the same for all workstreams. (PDF Page 7)
  • The Title and Line(s) of Business fields default with the content entered from the project Info. Users will have the ability to edit these fields.
• The Details section is dynamic and is specific to each workstream type. Based on the Workstream Type selected, specific fields of information are required. (See Various examples PDF Pages 8-19)
  • Please design an example for: Filing Management Workstream (PDF Page 15) or Implementation Workstream (PDF Page 16).
• The Workstream Tasks section is an embedded table of the available tasks specific to a workstream. (PDF Page 20)
  • Once a Workstream Type is selected, the tasks table will become available (see 2.3 Tasks).
  • A workstream could have an option for 0-50 possible tasks. In addition, some tasks may have the option to include Objection Assignments as sub-tasks (see 2.4 Objection Assignments). 

2.3 Tasks
Users should be able to see a list of all the associated tasks available within a workstream. Users will have the ability to add multiple tasks as they create or edit their project.

• Each task will include common details. (PDF Page 21)
• Based on the Task Type selected, the task will require additional details. (Various examples PDF Page 23-25)
  • Please use one of these samples to show the flow from the workstreams described above.

2.4 Objection Assignments
Some tasks may contain one or more associated Objection Assignments (sub-tasks). A user should be able to see the list of the associated sub-tasks within the parent task. This will function in a similar way to the workstream > task flow.

• Each sub-task will include common details. (PDF Page 22)
  • As an example, in some workstreams each U.S. state included may identify an Objection to produce 50 sub-tasks.

3.0 Project Summary Display (view)
Once a project has been created, it will show the Project Information and the associated Workstreams, Tasks, and Objection Assignments that have been added to date. At this view, the user should be able to quickly know the components that the project contains. They should also be able to see the status of the various tasks included.

Note: Information the users have entered while creating the project should be available in the summary as non-editable fields. However, the user should have a path to edit or add to the existing project.

Currently this screen is displayed in sections. This content should be re-arranged in your solution to best organize and surface the required information. (PDF Page 3 and Page 6 show portions of the current Summary view) 

• Project Information
  • Project Attributes
  • Jurisdictions/Companies
• Workstream Information
  • This section displays all of the workstreams currently entered as part of the project.
• Task Information
  • This section displays all of the tasks currently entered as part of the project.
• Contacts Summary
  • This section displays all of the contact information which has been entered into the project at various input areas.
  • Each project should include a path to the folder of documents stored in Sharepoint. The UI should include a button/link to navigate to this Sharepoint folder.

4.0 Search Results (view)
The user should have a search mechanism to quickly find projects (from Home screens and elsewhere in the application). Please design the view to results as the user would best use them in this PowerApps application.

EXPLORATION SCORE
In terms of expectations, we would like to measure the concept against the following in the one to ten scales:

• 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: Flexible; follow the provided guidelines and suggest improvements where seem appropriate and inline with the goals.

BRANDING GUIDELINES
Brand Guidelines: Zetas Basic Brand Guidelines.pdf

DEVICE SPECIFICATION:
Desktop: 1366px width and height as required

MARVEL PROTOTYPE
We need you to upload your screens to Marvel App
Please request for marvel app in the challenge forum
You MUST include your Marvel app URL (in your marvel app prototype, click on share and then copy the link & share it with your notes/comment on this link while you upload)

SUBMISSION AND SOURCE FILES
Submission File
Submit JPG/PNG image files based on Challenge submission requirements stated above
MarvelApp link for review and to provide feedbackDeclaration 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