---
title: Opolis Commons UX Audit
tags: opolis, raidguild, ux-audit
---

# 1. Objective & Overview :key:

The audit's objective is to identify gaps and suggest improvements to Opolis' current onboarding flow, thereby increasing the onboarding conversion rates for Opolis employee members.

## **1.1 User Persona** :smile:
New freelancers and independent workers looking to solve the following problems:
* Independent working **lacks the security & benefits of conventional employment** (i.e. healthcare, insurance, etc.)
* Independent working is **administratively troublesome because of back-office operations as well as regulatory compliance**

Within the above Employee personas, we have different sub-segments that will
have different maturity and readiness levels to be onboarded to Opolis:

| Users | Potential Friction Point(s) |
| ------------------------------ | -------- |
| Users **not in the United States** | **Excluded** from service. More suitable for Coalition Membership|
| **Beginner users** new to independent working | **Foreign to information** provided, as well as **unprepared for forms & steps** involved |
| **Experienced users** in independent working | - |

## **1.2 Current Flows** :desktop_computer:

<iframe style="border: 1px solid rgba(0, 0, 0, 0.1);" width="800" height="450" src="https://www.figma.com/embed?embed_host=share&url=https%3A%2F%2Fwww.figma.com%2Ffile%2F3JZcOE0ji1POMwi90u0i62%2FRG-Opolis-UX-Audit%3Fnode-id%3D138%253A21" allowfullscreen></iframe>

> **Supplementary materialse**
> * URL: commons.opolis.co/onboarding
> * Figma flows: https://www.figma.com/file/3JZcOE0ji1POMwi90u0i62/RG-Opolis-UX-Audit?node-id=138%3A21
> * List of Fields: https://docs.google.com/spreadsheets/d/1FiQP11B80H66cMzTHyL5W737-2amt91XwHsntnxEhcs/edit?usp=sharing

## **1.3 Factors for a good onboarding experience** :100:

| Factor | What is it? | Why is this important? |
| -------- | -------- | -------- |
| Simplicity & clarity | All **information provided & steps required** must be as **simple and clear** as possible | A lot of complex / foreign information need to be collected, so keeping things simple will reduce friction and improve onboarding rates |
| Succinctness | All information provided & steps required must be **as short as possible. Duplicates should be avoided.** | Given the amount of information and steps required, keeping things succinct and essential will reduce the overload on users |
| Trust | The entire onboarding journey should be **trust-inducing, safe and assuring to users** | Users are providing sensitive information to Opolis. As a start of this business relationship, trust & safety is crucial. |

The above 3 factors will be used to assess and suggest improvements to the current home page and onboarding flows.

Other than the above 3 factors, the value and coverage of policies will play an important role in onboarding and signup success rates, but this exercise is focusing primarily on user experience and should be covered elserwhere.

---
<br>
</br>

# 2. Home Page :house:

## **2.1 General home page hierarchy & flow**

There are too many flows and concepts for an independent worker visiting Opolis' site for the first time. It makes it difficult to grasp what Opolis is, potentially risking drop-offs from confused visitors.

### **2.1.1 Too many flows at once**

From a site organisation POV, there are 3 flows (Employees, Coalition, Job board Opo(list)) to get started that serve very different purposes.

Personally, after understanding what Opolis does, I know why there are 3 different flows and collated the flows in the Figjam diagram below:
* **Employee members**: For independent workers that are applicable to join Opolis
* **Coalition members**: For independent workers not applicable to join Opolis, as well as other people or organisations wanting to contribute
* **Opo(list)**: Seems to me they are creating a portal of job opportunities for all these independent workers.
<iframe style="border: 1px solid rgba(0, 0, 0, 0.1);" width="800" height="450" src="https://www.figma.com/embed?embed_host=share&url=https%3A%2F%2Fwww.figma.com%2Ffile%2Fdu2Br41tDYL0OxWPhITcg4%2FUntitled%3Fnode-id%3D0%253A1" allowfullscreen></iframe>

> For clarity, I've segmented the navbar's actions into the following flows / colours:
> * Blue: For all users
> * Purple: For Employee members
> * Orange: For Coalition members
> * Yellow: For job board users

Another way to visualise this would be to look at the actions available in the navbar here:


**Placing all these flow side by side with equal importance** makes it really confusing for new visitors (which the "employee members" would be the most important).

**Furthermore, the alternating purposes of each flow** makes it hard to form a coherent understanding of what Opolis is as users need to keep context-switching with each click.

To that, we suggest **creating a main flow for "Employee Members" by reducing the importance of the Coalition & Opo(list) flows from the main navbar**.

### **2.1.2 Foreign words & jargon**
The above also results in new foreign terms (e.g. Coalition, Opo(list)) which does not seem related to an employment commons on first sight. This might look irrelevant or like technical jargon, scaring first-time users away.

We suggest reducing the visibility of these side flows to make the call to action and intended user journey clearer.

### **2.1.3 Generic terms that are confusing**

Similarly, there are generic terms that seem to overlap & might confuse new users (e.g. Rewards, features). On a deeper look, this is because Rewards is meant for "Coalition members" whereas Features is meant for "Employee members". However when put side by side, a new visitor will be confused as to why there are these 2 similar-sounding concepts.

To ensure the greatest clarity of our core user (i.e. Employee Members), we suggest reducing the visbility of Coalition flows as well.

## **2.2 Home Page**

### **2.2.1 Content Flow**

Generally the home page's flow is **quite straightforward** (Header > What is Opolis? > We Love Opolis > Membership Perks > Made by Independents, For Independents, Join the Opolis Team)

However, as a first-time user, I felt that the **sections could be re-ordered such that Membership Perks came before We Love Opolis**. This way, as a user, I can better understand what Opolis offered in detail, before understanding why other independent workers like myself loved Opolis. Without the context above, the reviews was not as convincing as it could have been.


### **2.2.2 Copywriting for Membership Perks**
The copywriting for membership perks felt vague and unconvincing when I first read it. It was only when I dived deeper in the "Features" page that I could better understand the specifics and visualise why Opolis is good for independent workers.

Hence, we suggest to **improve the copywriting by prioritising the perks that are important to independent workers, followed by increasing specific details that are relevant to these points**. The user interviews should give us valuable insight to the above.

## **2.3 Sign up Flow**

After I have overcome the previous challenges & want to sign up, I'd have been through 2 different sign up flows and would be confused about what is the right way to sign up.

| | A (Sign up via pop-up) | B (Sign up via "Join" in navbar) |
| ---------- | ------------------------------------ | ----------------------------------------------------------- |
| Image |  |  |
| When does it appear? | Pops up regularly when you're on site | Click "Join in Navbar" |
| Next Steps | Form Submission | Magic sign-in link OR Calendly link for Membership Stewards |

From an information / value proposition POV, there are **2 different angles users would have seen** (to get the coverage and compliance benefits from Opolis OR earn $WORK rewards). These 2 are **quite different and may be confusing to users**, especially for flow A which pops up regularly for most users. If these users are not yet familiar with $WORK token, it will only introduce more confusion to the user.

Furthermore, with 3 rather different sign up flows (form submission, magic sign-in link, Calendly link), it would be **operationally intensive for the Opolis team to track and onboard new members**. It is also confusing for users looking for a clear way to sign up with Opolis.

---
<br>
</br>

# 3. Onboarding - General Observations :inbox_tray:

## 3.1 Log in Flow
The log in flow using the magic sign-in link is frictionless as the user only needs to key in their email. Also, this is beneficial for Opolis as now we have a user record (email address), as well as a way to contact them.

## 3.2 Seven-step Onboarding Flow is too long

### 3.2.1 Why is the onboarding flow too long?
The onboarding flow consists of 7 steps, providing different information and actions required by the user in each step. In total, the user is required to fill in approximately 100 fields which is **too lengthy and will affect the conversion rate.**

Furthermore, at some steps (e.g. Company Information and Election Benefits), the **information provided or actions require more preparation, information and deciding.** For instance, if the user has not set up a company with a EIN or have not decided on the benefits, they would need time to complete these actions.

The following table summarises the user's familiarity and readiness in completing the respective steps.

| | Step | Action required from user | User's familiarity with information | User's readiness to complete step |
| --- | ---------------------- | ---------------------------------------------- | --------------------------------------------- | --------------------------------- |
| 1 | Personal information | ✅ Provide information | ✅ Highly likely | ✅ Ready |
| 2 | Occupation information | ✅ Provide information | ✅ Highly likely | ✅ Ready |
| 3 | Company information | ❓ (Set up company) & provide information | ❓ Depends on whether user has set up company | ✅ Ready |
| 4 | Benefits election | ❌ Understand options & make purchase decision | ❓ Depends on user's financial savviness | ❌ Unlikely (Need to think) |
| 5 | Compliance | ✅ Provide information | ❓ Unlikely to be familiar | ✅ Ready |
| 6 | Legal Stuff | ✅ Agree to T&Cs | ✅ Highly likely | ✅ Ready |
| 7 | Deposit information | ✅ Provide information | ✅ Highly likely | ✅ Ready |

As seen above, most steps are filling in information which are familiar and readily available, especially for `1. Personal Information` and `2. Occupation Information`. After these 2 steps, we come to the natural drop-off points in `3. Company Information` and `4. Benefits Election` sections.

* `3. Company Information` causes drop-offs for users who **have not set up a company with EIN**. According to an interview with Bill, this accounts for 50% of new users.
* `4. Benefits Election` causes drop-offs because the **user is required to make many purchase decisions on the benefits within 1 section**. In my view, it is unlikely that most users can understand, research and decide in 1 sitting.

The rest of the steps are information that users readily have and can provide, but it is unlikely that they will reach this stage as they would have been stopped in steps 3 and 4. This prevents them from signing up for Opolis or speak to a Membership Steward, resulting in **potential lost sales, lower conversion rates and increased cost of acquisition.**

### 3.2.2 How do we optimise the onboarding flow?
We suggest **splitting up the onboarding process into 2 parts**, where the first part consists of easier DIY steps for users, and the second part can be more guided by Membership Stewards or even automated email sequences eventually

| Part | Role | Current Onboarding Steps | Self-serve? |
| ---- | ---------------------- | --------------------------------------------------------------- | --- |
| 1 | Information Collection | 1. Personal, 2. Occupation, 7. Deposit, 3. Company Information | Yes
| 2 | Benefits & Onboarding | 4. Benefits, 5. Compliance, 6. Legal Stuff | Yes, but we could start with human-assistance first |

<!--For a flow representation of this 2-part process, please refer to:
-->

Here is a further breakdown of each section and why it is designed this way.

| Part | Purpose | Information | Goal for Users | Rationale |
| ---- | ---------------------- | ------------------------------------------------------------- | -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 1 | Information Collection | Personal, Occupation, Company, Paycheck & Deposit Information | Click Submit & Complete Part 1 of Onboarding | <li>Here, we want users to **complete the first part of onboarding by asking for simple and readily available information**. As compared to filling in the current flow but being stuck on onboarding, this gives them a **sense of progression, success and joy in onboarding**.</li> <li>The only information that users might not have is Company Information, which should be non-compulsory. <li>For users with a registered company, this information is available to be filled in. For those without a registered company, they should still be able to submit the form and receive a follow-up from a Membership steward or automated email on setting up their company.</li></li><li>For users that wish to complete the second step of the process (i.e. benefits & compliance), we should allow them to proceed to part 2 immediately. </li> |
| 1.5 | Funnel Conversion | N.A. | Get users ready for Part 2 of Onboarding | <li> Here is where Opolis can deploy **ways to nurture and convert users towards onboarding part 2**. </li><li>If a high-touch approach is preferred, the Membership Steward can **go through the incorporation, benefits and compliance on a call**. <li>Otherwise, an email sequence can send information to be read and completed (e.g. Setting up LLC, Benefits Guide, etc) along the way. This gives users more time to read, decide and fill in the form on a self-serve basis. </li><li>In any case, this gives Opolis flexiblity in how they would like to convert different cohorts of users. </li> |
| 2 | Benefits & Onboarding | (Incorporation), Benefits, Compliance, Legal Stuff | Understand what they're signing up for & fully sign up! | <li>Part 2 consists of more detailed and content-heavy information and steps. Depending on the onboarding approach by Opolis, this form could be filled in by users on a self-serve basis, or guided by Membership Stewards </li> |

In conclusion, this approach **makes onboarding less daunting where they can experience progress, assurance and joy during their first experience with Opolis** (instead of previously having many fields and getting stuck in onboarding). Also, the CRM and process that is embedded within the flows **gives Opolis the flexibility and specificity to employ different tools and strategies to increase conversion rates.**

## 3.3 Drop-offs for non-incorporated users
During our call with Bill, we understand that for customers without a registered company, Opolis refers the customers to a partner agent for company registration. While this is a good MVP, this is **likely to cause a huge drop-off as there is added communications, lag time and paperwork between the customer and the company registration agent**.

For potential users filling up the form themselves, they are **led to external links with information but without closing the loop** back to Opolis.


Sicne this affects **50% of new customer signups**, we suggest Opolis **front the company creation process with customers to reduce drop-offs.** Drawing from Jaqi's experience with competitor Collective, they **ask the customers for information and forms to complete the company registration process** during onboarding.

For ideas on how to show the company incorporation journey to users, we can refer to [Collective (competitor)'s onboarding screens collated by Jaqi](https://www.figma.com/file/JHEfxVmWEK5JUXiTwlbKA0/Opolis-Onboarding-References?node-id=2%3A27)

Depending on the resources available, Opolis could adopt more manual processes (request information on forms, register manually via agents) or more automated options such as Stripe Atlas.

## 3.4 Benefits Election's form titles & progress bar not in sync
Among the current 7 step process, **the most complicated step is the Benefits Election, consisting of many sub-sections** (e.g. Dependents, Retirement, Dental Insurance, etc).

Using a progress bar, the current UI helps to assure users and give them better expectations on existing progress and upcoming steps. However, the issue is that the **progress bar's steps and the form titles are not synchronised**. For instance, the following screen is on `Vision Insurance`, but the progress bar shows `Dependents`. Please see the table below for a further breakdown.


Given the number of steps in this section, the differences in progress bar and form titles might introduce additional confusion and mental overload for users who need to process a lot of information and steps here.

| Form Title | Progress Bar Step | Synchronised? |
| --------------------------- | -------------------:| ------------- |
| Retirement | Retirement (Open) | Yes |
| Dependents | Dependents (Open) | Yes |
| Health Insurance | Dependents (Closed) | No |
| DFSA Election | Dependents (Closed) | No |
| Dental | Dependents (Closed) | No |
| Vision Insurance | Dependents (Closed) | No |
| Life & Disability Insurance | Benefits (Open) | Yes |
| Review | Review (Open) | Yes |

To solve this, we suggest:
1. **Synchronising the form titles and steps** in the progress bar
2. **Making the progress bar more detailed** (see visual reference below)

| | Current | Proposed |
| -------- | -------- | -------- |
| Screen |  |  |

## 3.5 Inconsistent levels of details in different steps of Benefits Election

Currently, there are different levels of specificity and information provided in different screens, where some sections are more informative than others.

Please see the table below for examples

| Degree of Information | Screens | Remarks |
| ----------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| Specific | (1) DFSA Election  (2) Life & Disability Insurance  (3) Dependents  (4) Retirement  | In these screens, the copy is typically rather long and can be summarised or hidden in tooltips to prevent content overload for users |
| Vague | (1) Vision Insurance  (2) Health Insurance  (3) Dental Insurance | In these screens, the copy is typically short and links out to the PDF benefits guide, which may create drop-offs |

To minimise having too much or too little information, we suggest standardising the content and copy placements within the benefits election section. First, we must map out the necessary information for users to be well-informed and decide (see table below)

| Copy Type | Purpose | Sample |
| ------------------ | ------------------------------------------------------------------------- | ------------------------------------------------------------------ |
| Title | Signposts content of the section | Dental Insurance |
| Hook | Acts as interesting hook that engage users & give off Opolis' personality | Let us see that smile! |
| Benefits Explainer | Explain what is the benefit & why it's important | Dental Insurance covers all expenses to give you stellar oral and dental health, which is not covered usually in health insurance |
| Opolis Offering | Explain what is the specific benefit offered by Opolis | TBD |
| More information | Link out to other resources for more information | For more information, please see the Opolis Commons Benefits Guide |

As far as it's possible, each content copy should be a **one-liner to prevent information overload**. Any information that **do not belong to the content types** or are meant to **supplement details for something specific** should be **hidden in a tooltip next to the relevant content type**.

This is a visual representation on how this might look like:

This should reduce the information complexity and standardise how users can find information to make their decisions, increasing the conversion rate of onboarding.

## 3.6 Compliance: Some titles are vague
In this section, the flows are straightforward as they mainly consist of requesting information and document uploads from users. However, the **title and copy of some sections are not informative** in explaining to users why these information is required. This is problematic because:
1. It is in **contrast with the assurance and explanation** in long paragraphs in other sections (which the user is used to).
2. **Some information requested are sensitive**, so having more assurance and explanation would lower the friction to submitting these information

More specifically, **the forms of W9 and I4** lack the paragraph copies and we'd suggest adding a brief explainer on what these forms are and why they are needed. For instance, below the "W4" title, we could add "The W4 Form helps informs your employer the amount to withhold from your salary for federal income taxes"


---
<br>
</br>

# 4. Onboarding - Screen/Component Observations :mag_right:

## 4.1 Field & Copy Improvements
This is a minor optimisation to questions, tooltips and helper texts which can be further summarised for more clarity and succinctness.

| Section | Current Copy / Field | Content Type | Proposed Changes |
| ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Personal Information | Membership Start Date | Field (Date Select) | Change this to a month selection, given that the start dates are on a monthly basis |
| Personal Information | Benefits are geared to start on the first day of the first full month of continuous employment. Please select the month that best fits this for you circumstances. If you have questions about benefits eligibility and waiting periods, please contact Opolis support. | Tool tip | Can be removed if date select is switched to month select |
| Occupation Information | What is the total amount you anticipate earning over the next 12 months, minus business expenses, that will be available to spend towards payroll and benefits? | Question | Change copy to "What is the total amount available for payroll and benefits over the next 12 months?" |
| Occupation Information | The amount entered here will be deducted from your business bank account to cover payroll, taxes, and benefits. You can change this later if need be, but this will tell us how much to pay you each pay period and help us estimate your benefits on the coming pages. | Tool tip | Change copy to "This amount will be deducted from your business bank account to cover payroll, taxes, and benefits. This helps us estimate your salary and benefits in the coming pages, and can be changed later." |
| Company Information |You may use a different email for your legal entity than you do for your personal matters. You can choose to use the same email or a different one here. This email will be used to inform your Employer (your entity) of important information regarding the Opolis Commons and your related Employment| Tool tip | Change copy to "This email will be used to inform your Employer (your entity) of important information regarding the Opolis Commons and your related Employment. You can use your legal entity or personal email." |

## 4.2 I9 step is misleading

The current step for choosing applicable I9 documents is confusing and ambiguous.


As a user, the steps can be interpreted in 2 ways `1 from A, 1 from B or C`
OR `1 from A or B, 1 from C`. After trying it out, it seems like the correct understanding is the latter. This is confusing and the visual representation of information creates information overload for the user.

To make this step simpler, more succinct and clearer, we suggest creating 2 dropdowns:
* 1 dropdown (single select) for List A documents
* 1 dropdown (single select) for List B and C documents

This way, it is clear that:
1. There are 2 documents required
2. As a user, I must select one document from field 1 (List A)
3. As a user, I must select one document from field 2 (List B & C)

With a simple drop-down selection, this should reduce the information overload and confusion among users in completing this step.

## 4.3 Address fields are duplicated
During the entire flow, addresses are requested 4 times. These addresses are not completely similar, but are related and possibly repeated for independent workers (such as "what address do you work from?" and Personal Address). **Since there are potential overlaps, this creates additional steps and effort unnecessarily.**

| Step | Step Name | Address Field | Saved & auto-fill enabled? |
| --- | ---------------------- | --------------------------------------------------------- | --------------------------------------- |
| 1 | Occupation Information | What address do you spend most of your time working from? | No |
| 2 | Company Information | Company Legal Address | No |
| 3 | Company Information | Company Mailing Address | Yes. From field `Company Legal Address` |
| 4 | Compliance Forms (W4) | Personal Address | No |

Within the Company Information page, the ability to retrieve Company Legal Address for the Company Mailing Address field helps to reduce the steps required to fill in. This is beneficial in reducing extra effort for filling in repeated information, so we suggest:
1. Ask for Personal Address & "What address do you spend most of your time working from?" in `1. Personal Information` section
2. Allow users to retrieve Personal Address when answering "What address do you spend most of your time working from?"
3. Fill in Personal Address automatically in `5. Compliance > W4` (and allow users to enter custom address if needed)

## 4.4 Dependents / beneficiaries fields are duplicated

During the entire flow, another repeatedly requested information is beneficiaries and dependents. **These are likely to refer to an overlapping but not identical group of people, so we can save and store these information for autofill. This should reduce additional steps and effort unnecessarily.**

| Step | Step Name | Field | Saved & Retrievable? |
| --- | ---------------------- | --------------------------------------------------------- | --------------------------------------- |
| 4 | Benefits Election > Dependents | Dependents | No |
| 4 | Benefits Elections > Life & Disability Insurance | Beneficiaries | No |

We suggest:
1. Save the dependents details when first filled in within Dependents fields
2. Pre-fill beneficiaries name with dependents details in Life & Disability Insurance
3. Allow user to add or remove beneficiaries in Life & Disability Insurance

# 5. Summary :checkered_flag:

## 5.1 Home Page
While the home page brings out various aspects of what Opolis aspires to be now, it does not clearly explain the value proposition of Opolis to a completely new user. As such, the summary of changes to improve this area is as follows:

**Summary of proposed changes**

| | Component | Suggestion | Workstreams |
| --- | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------- |
| 1 | NavBar | **Clean up Navbar to prioritise visiblity of Employees flow** <li>Group "Coalition" & "Rewards" into 1 called "Community" </li><li>Remove "Opo(list)" from Navbar & move it to footer / other sections of the home page </li> <li>Add FAQ into Navbar </li> | Product |
| 2 | Home Page Contents | **Optimise content flow for greater specificity and persuasion** <li>Move "Membership Perks" before "We Love Opolis"</li><li>Make "Membership Perks" content more important to independent workers</li> <li>Make "Membership Perks" content more specific</li> | Product |
| 3 | Sign Up Flows | **Simplify & standardise sign-up flows** <li>Remove sign up flow A (i.e. Join to Earn $WORK Rewards)</li> | Product + Operations |

Doing the above will help to more **clearly communicate the value proposition and steps required to sign up for Opolis**. Following that, we look to improve the onboarding flow for Opolis, and the changes are summarised as follows:

## 5.2 Onboarding Flow

<iframe style="border: 1px solid rgba(0, 0, 0, 0.1);" width="800" height="450" src="https://www.figma.com/embed?embed_host=share&url=https%3A%2F%2Fwww.figma.com%2Ffile%2F3JZcOE0ji1POMwi90u0i62%2FRG-Opolis-UX-Audit%3Fnode-id%3D9%253A3" allowfullscreen></iframe>

**Summary of proposed changes**
<!--
| | Flow | Suggestion | Workstreams involved | Effort / Impact Payoff |
| --- | ---------------------------------------- | ----------------------------------------------------------------- | -------------------- | --- |
| 1 | Whole flow | Split the onboarding flow into 2 parts | Product + Operations | Mid-long term |
| 2 | Personal Information & Election Benefits | Save & auto-fill repeated fields (e.g. dependants, beneficiaries) | Product | Quick wins |
| 3 | Company Information | Create & front incorporation capabilities for customers | Product + Operations | Mid-long term |
| 4 | Benefits Election | Synchronise title & section progress bars | Product | Quick wins |
| 5 | Benefits Election | Standardise title & paragraph copy formats | Product | Quick wins |
| 6 | Compliance | Provide more context & information on forms | Product | Quick wins |
| 7 | Compliance > I9 | Simplify form fields to a dropdown | Product | Quick wins |
-->

| | Flow | Suggestion | Work | PIC | Status |
| --- | ---------------------------------------- | ----------------------------------------------------------------- | ----------------------------- | ---- | ------------------------- |
| 0 | Dashboard & wireframe assets | Create dashboard & wireframe assets | Create screens | Jaqi | Done |
| 1 | Whole flow | Split the onboarding flow into 2 parts | Re-organise flow & fields | Amos | Done |
| 2 | Sign up / Log in | Switch to Oauth logins on Magic Link | Create screens | TBD | Done |
| 3 | Select Membership | Re-order Coalition / Employee Member buttons | Create screens + Copy | TBD | Done |
| 4 | Select Membership | Surface hard requirements early on in the flow | Create screens + copy | Jaqi | Done (eligibility checks) |
| 5 | TBD (Perhaps at Select Membership) | Surface pricing within the flow | Look at flows + Screen + copy | TBD | Done |
| 6 | Personal Information & Election Benefits | Save & auto-fill repeated fields (e.g. dependants, beneficiaries) | Create screens | Amos | Done |
| 7 | Company Information | Collect information from customers for company incorporation | Create flow + screens + copy | Amos | Partially done (placeholders) |
| 8 | Benefits Election | Synchronise title & section progress bars | Create screens | Amos | Done |
| 9 | Benefits Election | Standardise title & paragraph copy formats | Create screens + Copy | Amos | Done |
| 10 | Benefits Election | Link to PDF should jump straight to section | Define sections | Amos | Done |
| 11 | Compliance | Provide more context & information on forms | Create screens | Amos | Done |
| 12 | Compliance > I9 | Simplify form fields to a dropdown | Create screens | Amos | Done |
| 13 | General flow | Other fields & copy improvements | Create flow & screens | Amos | Done |